Admin

ODBC Edition 4.
51
OLE DB Edition 2.0
Java Edition 2.0
DataDirect ®
®
SequeLink
Administrator’s Guide
© 1999 MERANT. All rights reserved. Printed in the U.S.A.
INTERSOLV, DataDirect, APS, Maintenance Workbench, PVCS, TechGnosis,

SequeLink, and Middleware are registered trademarks of MERANT. PVCS
SiteSync, INTERSOLV Messaging, DataDirect Connect ODBC, DataDirect
Connect OLE DB, DataDirect Reflector, WebDBLink, Client/Server MiddleWare,
PVCS VM Server, PVCS Dimensions, PVCS Process Manager, PVCS Version
Manager, PVCS Tracker, and PVCS TrackerLink are trademarks of MERANT.
Micro Focus is a registered trademark and Net Express is a trademark of
MERANT International Limited. Other company or product names mentioned
herein may be trademarks or registered trademarks of their respective
companies.
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.
Licensees may duplicate the software product user documentation contained

on a CD-ROM, but only to the extent necessary to support the users
authorized access to the software under the license agreement. Any
reproduction of the documentation, regardless of whether the
documentation is reproduced in whole or in part, must be accompanied by
this copyright statement in its entirety, without modification.
U.S. GOVERNMENT RESTRICTED RIGHTS. It is acknowledged that the Software

and the Documentation were developed at private expense, that no part is in
the public domain, and that the Software and Documentation are Commercial
Computer Software provided with RESTRICTED RIGHTS under Federal
Acquisition Regulations and agency supplements to them. Use, duplication or
disclosure by the U.S. Government is subject to restrictions as set forth in
subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer Software
clause at DFAR 252.227-7013 et. seq. or subparagraphs (c)(1) and (2) of the
Commercial Computer Software Restricted Rights at FAR 52.227-19, as
applicable. Contractor is MERANT, 701 East Middlefield Road, Mountain View,
California 94043. Rights are reserved under copyright laws of the United
States with respect to unpublished portions of the Software.
MERANT
701 East Middlefield Road
Mountain View, California 94043
3
Table of Contents
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
List of Figures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
What Is DataDirect SequeLink? . . . . . . . . . . . . . . . . . . . . . . . . 19
SequeLink ODBC Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
SequeLink OLE DB Edition. . . . . . . . . . . . . . . . . . . . . . . . . . 20
SequeLink Java Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Using This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Other Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Conventions Used in This Book. . . . . . . . . . . . . . . . . . . . . . . . . 25
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 25
Mouse Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Keyboard Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Environment-Specific Information . . . . . . . . . . . . . . . . . . . 27
Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1 Overview of SequeLink. . . . . . . . . . . . . . . . . . . . . . . 31
SequeLink Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
SequeLink ODBC Edition Client . . . . . . . . . . . . . . . . . . . . . 31
SequeLink OLE DB Edition Client . . . . . . . . . . . . . . . . . . . . 32
SequeLink Java Edition Client . . . . . . . . . . . . . . . . . . . . . . . 33
SequeLink Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
SequeLink ODBC Socket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Administrator Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Using Quick Install Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
SequeLink Administrator’s Guide

4
SequeLink’s n-Tier Architecture . . . . . . . . . . . . . . . . . . . . . . . . 39

Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Features and Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Part 1: Data Sources
2 Using Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . 47

SequeLink Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
ODBC Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
OLE DB Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Synchronizing Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Using the SequeLink CAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
On Windows and Macintosh . . . . . . . . . . . . . . . . . . . . . . . 52
On UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
SequeLink CAT Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Value Placeholder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Required and Optional Parameters. . . . . . . . . . . . . . . . . . 71
Encryption and Compression . . . . . . . . . . . . . . . . . . . . . . . 72
Host/Server Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Service (RDBMS) Parameters . . . . . . . . . . . . . . . . . . . . . . . 75
Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Connecting With the SequeLink ODBC Socket. . . . . . . . . . . . 93

Using the SequeLink Data Source SyncTool . . . . . . . . . . . . . . 95
With ODBC Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . 96
With OLE DB Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . 101
Part 2: Network Considerations
3 SequeLink and Your Network. . . . . . . . . . . . . . . . . . 107

TCP Port Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
APPC Support in a SNA Network. . . . . . . . . . . . . . . . . . . . . . . 109

5
Cross-Platform Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Data Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Limiting Access to SequeLink Server Services. . . . . . . . . . . 125
Data Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Data Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Using Encryption and Compression Together . . . . . . . . . . 129
Using SequeLink with the Internet. . . . . . . . . . . . . . . . . . . . . . 130

Using Firewalls with SequeLink . . . . . . . . . . . . . . . . . . . . . 130
Other Security Considerations . . . . . . . . . . . . . . . . . . . . . . 132
System Performance Considerations . . . . . . . . . . . . . . . . . 132
4 Configuring Your SNA Network for SequeLink. . . . 135

AS/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Attachmate (CPIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
IBM Personal Communications . . . . . . . . . . . . . . . . . . . . . . . . . 139
Microsoft SNA Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Rumba Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Client Access/400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Part 3: SequeLink Server Administration
5 Using SequeLink With Your Database . . . . . . . . . . . 149

Using Server-Defined Host User Definitions . . . . . . . . . . . . . . 149
Managing the Retrieval of Database Meta-Information . . . . 151
Using SequeLink Shadow Data Dictionaries (SSDDs). . . . . 152
Using Database Data Dictionary Filters . . . . . . . . . . . . . . . 161
Using Database Data Dictionary Views . . . . . . . . . . . . . . . 162
Using the SequeLink Dictionary Manager . . . . . . . . . . . . . . . . 162

SequeLink Dictionary Manager Scripts. . . . . . . . . . . . . . . . 163
Creating SSDDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

6
Updating SSDDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Managing Different SSDD Versions. . . . . . . . . . . . . . . . . . 168
Using OS/390 Batch Procedures with SSDDs . . . . . . . . . . . . . . 169

Creating SSDD Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Binding DBRMs to DB2. . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Using the Batch Program . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Return Codes (RCs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Alias Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Using Previous Versions of SSDDs in Batch Mode . . . . . . 178
Fine-Tuning System Performance . . . . . . . . . . . . . . . . . . . . . . 179

DB2 for OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
DB2 for AS/400 and Oracle . . . . . . . . . . . . . . . . . . . . . . . . 179
Informix 7 and 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Sybase System 10 and 11 . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Database-Specific Information . . . . . . . . . . . . . . . . . . . . . . . . 182

Cross-Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
DB2 Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Informix 7 Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Informix 9 Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
OpenINGRES Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Oracle7 Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Oracle8 Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
SQL Server Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Sybase Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
6 SequeLink Server for Windows NT . . . . . . . . . . . . . 239

Where and How SequeLink Information Is Stored. . . . . . . . . 239
Using the SequeLink Server Administrator. . . . . . . . . . . . . . . 240
Working in Status or Configuration Mode . . . . . . . . . . . . 241
SequeLink Server Administrator Toolbar . . . . . . . . . . . . . 242
Adding Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Deleting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Upgrading SequeLink 4.0 Services. . . . . . . . . . . . . . . . . . . 244
Starting and Stopping Services . . . . . . . . . . . . . . . . . . . . . 245

7
Stopping a Service Process for a Specific User . . . . . . . . . . 245

Displaying Host Names and IP Addresses . . . . . . . . . . . . . . 246
Changing Configuration Settings . . . . . . . . . . . . . . . . . . . . 246
Configuring SequeLink Server . . . . . . . . . . . . . . . . . . . . . . . . . 247

Activating and Deactivating Services . . . . . . . . . . . . . . . . . 247
Setting the User Authentication Level . . . . . . . . . . . . . . . . 248
Setting Connection Refusal Message Details . . . . . . . . . . . 249
Specifying the Authorized Applications List . . . . . . . . . . . 250
Setting a Default Domain Name. . . . . . . . . . . . . . . . . . . . . 250
Changing the TCP Port Number . . . . . . . . . . . . . . . . . . . . . 251
Turning the Logging Option On and Off . . . . . . . . . . . . . . 252
Specifying the Log File Directory . . . . . . . . . . . . . . . . . . . . 252
Setting AutoStart for Services. . . . . . . . . . . . . . . . . . . . . . . 253
Setting the Shutdown Grace Period for Services . . . . . . . . 253
Preparing Services for SequeLink Client Access . . . . . . . . . . . . 254

Running SequeLink Server 3.5 and 4.x Services on the
Same Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Upgrading SequeLink Server 3.5 Services to 4.x . . . . . . . . . . . 256
7 SequeLink Server for UNIX . . . . . . . . . . . . . . . . . . . . 257

Where and How SequeLink Information Is Stored . . . . . . . . . 257
Using the SequeLink Server Administrator . . . . . . . . . . . . . . . 258
Starting the SequeLink Server Administrator . . . . . . . . . . 258
Specifying Actions and Parameters . . . . . . . . . . . . . . . . . . 259

Adding Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Deleting Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Upgrading SequeLink 4.0 Services . . . . . . . . . . . . . . . . . . . 263
Obtaining a List of Valid Configuration Actions . . . . . . . . 263
Obtaining a List of Existing Services . . . . . . . . . . . . . . . . . . 263
Obtaining a List of Existing Service Templates. . . . . . . . . . 264
Managing Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Displaying Service Attributes . . . . . . . . . . . . . . . . . . . . . . . 266

8
Editing Service Configuration Sections . . . . . . . . . . . . . . . 266

Setting Parameter Values. . . . . . . . . . . . . . . . . . . . . . . . . . 267
Activating and Deactivating Services . . . . . . . . . . . . . . . . 267
Setting the User Authentication Level . . . . . . . . . . . . . . . 268
Setting Connection Refusal Message Details . . . . . . . . . . 269
Specifying the Authorized Applications List. . . . . . . . . . . 270
Changing the TCP Port Number . . . . . . . . . . . . . . . . . . . . 271
Turning the Logging Option On and Off . . . . . . . . . . . . . 272
Preparing Services for SequeLink Client Access . . . . . . . . . . . 273

Running SequeLink Server 3.5 and 4.x Services on the
Same Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
8 SequeLink Server for AS/400 . . . . . . . . . . . . . . . . . . 277

Changing AS/400 SNA Definitions . . . . . . . . . . . . . . . . . . . 279
Setting Translation Options . . . . . . . . . . . . . . . . . . . . . . . . 279
Specifying the Authorized Applications List. . . . . . . . . . . 283
Turning the Logging Option On and Off . . . . . . . . . . . . . 284
Turning Binary Support On and Off . . . . . . . . . . . . . . . . . 285
Changing the Default Class Description . . . . . . . . . . . . . . 285
Changing the Default Isolation Level . . . . . . . . . . . . . . . . 286
Creating and Deleting User-Defined Services. . . . . . . . . . 287
Calling Initialization Programs . . . . . . . . . . . . . . . . . . . . . . . . 289

Issuing OS/400 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Multimember Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
9 SequeLink Server for OS/390 . . . . . . . . . . . . . . . . . . 293

Modifying Base Component Parameters . . . . . . . . . . . . . 301
Modifying Multiple DB2 Interface Parameters. . . . . . . . . 308
Modifying Service Parameters . . . . . . . . . . . . . . . . . . . . . . 314

9
Modifying FILECACHE Parameters . . . . . . . . . . . . . . . . . . . 329

Modifying User ID Mapping . . . . . . . . . . . . . . . . . . . . . . . . 329
Modifying APPC Parameters . . . . . . . . . . . . . . . . . . . . . . . . 332
Modifying IBM TCP/IP Parameters . . . . . . . . . . . . . . . . . . . 333
Modifying the ASCII-to-EBCDIC Tables (Optional) . . . . . . . 335
Automatic Execution of Commands at Startup . . . . . . . . . . . . 338

Specifying the Authorized Applications List . . . . . . . . . . . . . . 338
Logging Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Running Multiple SequeLink Servers . . . . . . . . . . . . . . . . . . . . 342
Using Operator Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
From an Operator's Console . . . . . . . . . . . . . . . . . . . . . . . . 343
From the Instrumentation Interface. . . . . . . . . . . . . . . . . . 344
Repeating Operator Commands . . . . . . . . . . . . . . . . . . . . . 345
APPC NIM Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Server Controller Task (CNTL) Commands . . . . . . . . . . . . . 348
Messaging Component (LOGR) Commands . . . . . . . . . . . 351
IBM TCP/IP NIM Commands. . . . . . . . . . . . . . . . . . . . . . . . . 354
DB2 Application Support Package Commands . . . . . . . . . 356
SMF Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Part 4: SequeLink ODBC Edition Client Administration
10 SequeLink ODBC Edition Client for Windows 9x

and Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Where and How SequeLink Information Is Stored . . . . . . . . . 363
Configuring SequeLink ODBC Edition Client . . . . . . . . . . . . . . 365
Changing the TCP Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Changing the TCP/IP Connection Time-Out . . . . . . . . . . . . 366
Quick Install Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Creating Quick Install Images . . . . . . . . . . . . . . . . . . . . . . . 369
Installing a Quick Install Image. . . . . . . . . . . . . . . . . . . . . . 371
Examining the INSTALL.LOG File. . . . . . . . . . . . . . . . . . . . . 371

10
11 SequeLink ODBC Edition Client for Windows 3.1 . . 373

Configuring SequeLink ODBC Edition Client . . . . . . . . . . . . . 375
Changing the TCP/IP Connection Time-Out . . . . . . . . . . . 376
Specifying Yielding Behavior for TCP/IP . . . . . . . . . . . . . . 377
Specifying Yielding Behavior for APPC . . . . . . . . . . . . . . . 377
Quick Install Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Creating Quick Install Images . . . . . . . . . . . . . . . . . . . . . . 380
Installing a Quick Install Image . . . . . . . . . . . . . . . . . . . . . 382
Examining the INSTALL.LOG File . . . . . . . . . . . . . . . . . . . . 382
12 SequeLink ODBC Edition Client for Macintosh . . . . 385

13 SequeLink ODBC Edition Client for UNIX. . . . . . . . . 389

Part 5: SequeLink OLE DB Edition Client Administration
14 SequeLink OLE DB Edition Client for Windows 9x

and Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Configuring SequeLink OLE DB Edition Client . . . . . . . . . . . . 397

11
Quick Install Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Creating Quick Install Images . . . . . . . . . . . . . . . . . . . . . . . 401
Installing a Quick Install Image. . . . . . . . . . . . . . . . . . . . . . 403
Examining the INSTALL.LOG File. . . . . . . . . . . . . . . . . . . . . 403
Part 6: Appendix
A TCP/IP (UDP) Communication (OS/390) . . . . . . . . . . 407

About TCP/IP (UDP) Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Modifying IBM TCP/IP (UDP) Parameters . . . . . . . . . . . . . . . . . 408
Modifying Interlink TCP/IP (UDP) Parameters . . . . . . . . . . . . . 411
Changing UDP Ports on the SequeLink Client . . . . . . . . . . . . . 414
On Windows 9x and Windows NT . . . . . . . . . . . . . . . . . . . 414
On Windows 3.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Running Multiple SequeLink Servers . . . . . . . . . . . . . . . . . . . . 416

Using Operator Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
IBM TCP/IP (UDP) NIM Commands . . . . . . . . . . . . . . . . . . . 418
Interlink TCP/IP (UDP) NIM Commands. . . . . . . . . . . . . . . . 422
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

12

13
List of Tables
Table 1-1. Administrator Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Table 2-1. Invalid Characters for Data Source Name . . . . . . . . . . . . . . . . . . . . . . 55
Table 2-2. Predefined Service Types for the SequeLink ODBC Socket and
an ODBC Driver on the Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Table 3-1. Default Symbolic Names and TCP Port Numbers for SequeLink
Server Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Table 3-2. Terminology Overview (OS/390, AS/400, End-User Workstations). . . 110
Table 3-3. Cross-Platform Connection Configuration Summary . . . . . . . . . . . . . 113
Table 3-4. User Authentication Combinations of Microsoft SQL Server and
SequeLink Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 4-1. Network Parameters for AS/400. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Table 4-2. Network Parameters for OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Table 4-3. Network Parameters for Attachmate (CPIC) . . . . . . . . . . . . . . . . . . . . 138
Table 4-4. Network Parameters for IBM Personal Communications . . . . . . . . . . . . 139
Table 4-5. Network Parameters for Microsoft SNA Server . . . . . . . . . . . . . . . . . . . . . 141
Table 4-6. Network Parameters for Rumba Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Table 4-7. Network Parameters for Client Access/400 . . . . . . . . . . . . . . . . . . . . . 145
Table 5-1. Data Dictionary Information Extraction for ODBC Calls . . . . . . . . . . 155
Table 5-2. SequeLink Services Supported by the SequeLink Dictionary
Manager and Their Associated Scripts . . . . . . . . . . . . . . . . . . . . . . . . 163
Table 5-3. Supported SSDD and SequeLink Configurations . . . . . . . . . . . . . . . . 168
Table 5-4. Return Codes (RCs) When Working with SSDDs (OS/390). . . . . . . . . . 174
Table 5-5. Error Messages When Working with SSDDs (OS/390) . . . . . . . . . . . . 175
Table 5-6. Sybase System 10/11 Variables That Affect System Performance . . . 181

14
Table 5-7. Data Types (DB2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Table 5-8. SequeLink Functionality with DB2 V5 . . . . . . . . . . . . . . . . . . . . . . . . 189
Table 5-9. SequeLink Functionality with DB2 for AS/400 SQLNKALL . . . . . . . . . . . 192
Table 5-10. SequeLink Functionality with DB2 for AS/400 SQLNKNONE . . . . . . 193
Table 5-11. SequeLink Functionality with DB2 for OS/390 . . . . . . . . . . . . . . . . . 195
Table 5-12. SequeLink Functionality with Informix 7 . . . . . . . . . . . . . . . . . . . . . 201
Table 5-13. Informix 7-Specific Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Table 5-14. Data Types (Informix 7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Table 5-15. SequeLink Functionality with Informix 9 . . . . . . . . . . . . . . . . . . . . . 205
Table 5-16. Informix 9-Specific Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Table 5-17. Data Types (Informix 9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Table 5-18. SequeLink Functionality with OpenINGRES . . . . . . . . . . . . . . . . . . . . 210
Table 5-19. Data Types (OpenINGRES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Table 5-20. SequeLink Functionality with Oracle7 . . . . . . . . . . . . . . . . . . . . . . . . 215
Table 5-21. Data Types (Oracle7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Table 5-22. SequeLink Functionality with Oracle8 . . . . . . . . . . . . . . . . . . . . . . . . 220
Table 5-23. Data Types (Oracle8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Table 5-24. SequeLink Functionality with SQL Server . . . . . . . . . . . . . . . . . . . . . 226
Table 5-25. Data Types (SQL Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Table 5-26. SequeLink Functionality with Sybase System 10/11 . . . . . . . . . . . . . 231
Table 5-27. Data Types (Sybase) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Table 6-1. SequeLink Server Administrator Buttons . . . . . . . . . . . . . . . . . . . . . . 242
Table 8-1. Service Initialization Files (AS/400) . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Table 8-2. Initialization Parameters for SequeLink Server for AS/400 . . . . . . . . 278
Table 8-3. ASCII-to-EBCDIC Conversion Tables . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Table 8-4. EBCDIC-to-ASCII Conversion Tables . . . . . . . . . . . . . . . . . . . . . . . . . . 282

15
Table 8-5. Defaults for the SEQCLS Class (AS/400) . . . . . . . . . . . . . . . . . . . . . . . . 285

Table 9-1. SYSINI Sections (OS/390) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Table 9-2. Base Component Parameters (OS/390) . . . . . . . . . . . . . . . . . . . . . . . . 301
Table 9-3. DB2 Interface ID (ifid) Parameters (OS/390) . . . . . . . . . . . . . . . . . . 309
Table 9-4. General Service Parameters (OS/390) . . . . . . . . . . . . . . . . . . . . . . . . . 316
Table 9-5. DB2 Service Parameters (OS/390) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Table 9-6. Oracle7 Service Parameters (OS/390) . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Table 9-7. APPC Parameters (OS/390) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Table 9-8. IBM TCP/IP Parameters (OS/390) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Table 9-9. Refresh Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Table 9-10. APPC NIM Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Table 9-11. Server Controller Task (CNTL) Commands . . . . . . . . . . . . . . . . . . . . . 348
Table 9-12. Messaging Component (LOGR) Commands . . . . . . . . . . . . . . . . . . . . 351
Table 9-13. IBM TCP/IP NIM Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Table 9-14. DB2 Application Support Package Commands . . . . . . . . . . . . . . . . . . 356
Table 10-1. Client Preferences Resource Sections (Windows 9x and
Windows NT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Table 11-1. Client Preferences Resource Sections (Windows 3.1) . . . . . . . . . . . . . 374
Table 12-1. Client Preferences Resource Sections (Macintosh) . . . . . . . . . . . . . . . 386
Table 13-1. Client Preferences Resource Sections (UNIX). . . . . . . . . . . . . . . . . . . . 390
Table 14-1. Client Preferences Resource Sections (Windows 9x and
Windows NT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Table 14-2. IBM TCP/IP (UDP) Parameters (OS/390) . . . . . . . . . . . . . . . . . . . . . . . . 408
Table 14-3. Interlink TCP/IP (UDP) Parameters (OS/390) . . . . . . . . . . . . . . . . . . . . 411
Table 14-4. IBM TCP/IP (UDP) NIM Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Table 14-5. Interlink TCP/IP (UDP) NIM Commands . . . . . . . . . . . . . . . . . . . . . . . . 422

16

17
List of Figures
Figure 1-1. Functional View of the SequeLink ODBC Socket Accessing

a Microsoft Access Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 1-2. Example: Two-Tier Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Figure 1-3. Example: Three-Tier Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Figure 1-4. SequeLink Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Figure 2-1. Creating SequeLink Data Sources for the SequeLink ODBC Socket. . 94
Figure 3-1. Example: SequeLink over the Internet . . . . . . . . . . . . . . . . . . . . . . . . 131
Figure 5-1. SSDD Tab of the ODBC Administrator . . . . . . . . . . . . . . . . . . . . . . . . . 158

18 List of Figures

19
Preface
This book is your guide to planning for and performing system

administration and runtime tasks for your MERANT™
DataDirect® SequeLink® environment. Read on to find out more
about SequeLink and how to use this book.
What Is DataDirect SequeLink?

DataDirect SequeLink is a series of standards-based client/server
middleware products that allow clients to access databases on
multiple servers using existing operating system and network
infrastructures.
The following SequeLink editions are available:
■ SequeLink ODBC Edition supports Open Database

Connectivity (ODBC) applications.
■ SequeLink OLE DB Edition supports OLE DB applications.
■ SequeLink Java Edition supports Java Database Connectivity

(JDBC) applications.
SequeLink ODBC Edition

SequeLink ODBC Edition Client
■ SequeLink ODBC Edition Client for Windows 9x/Windows NT
■ SequeLink ODBC Edition Client for Windows 3.1x
■ SequeLink ODBC Edition Client for UNIX
■ SequeLink ODBC Edition Client for Macintosh

20 Preface
SequeLink Server
■ SequeLink Server for Windows NT
■ SequeLink Server for UNIX
■ SequeLink Server for AS/400
■ SequeLink Server for OS/390
SequeLink OLE DB Edition

SequeLink OLE DB Edition Client
■ SequeLink OLE DB Edition Client for Windows 9x/Windows NT
SequeLink Server
SequeLink Java Edition

SequeLink Java Edition Client
■ SequeLink Java Edition
■ SequeLink Proxy Server
SequeLink Server

Using This Book 21
Using This Book

Audience and This book assumes that you are familiar with your operating
Prerequisite system and its commands; the concept of directories; the
knowledge management of user accounts and security access; and your
network protocol and its configuration.
How this book is This book is divided into the following parts, chapters, and
organized appendix:
■ Chapter 1, “Overview of SequeLink” provides an overview of

SequeLink, including its components, its architecture, and its
features.
This part provides information about using data sources.
■ Chapter 2, “Using Data Sources” introduces SequeLink data

sources, ODBC and OLE DB data sources, and the tools you
can use to manage them.
This part provides network-related information about

SequeLink.
■ Chapter 3, “SequeLink and Your Network” introduces and

explains concepts that you need to understand to plan and
administer SequeLink and your network.
■ Chapter 4, “Configuring Your SNA Network for SequeLink”

describes how to configure your SNA network for SequeLink.

22 Preface
Part 3: SequeLink Server Administration
This part provides information about using SequeLink with

databases and provides platform-specific information about
administration tasks you may need to perform for SequeLink
Server.
■ Chapter 5, “Using SequeLink With Your Database”

■ Chapter 6, “SequeLink Server for Windows NT”
■ Chapter 7, “SequeLink Server for UNIX”
■ Chapter 8, “SequeLink Server for AS/400”
■ Chapter 9, “SequeLink Server for OS/390”
Part 4: SequeLink ODBC Edition Client Administration
This part provides platform-specific information about

ODBC Edition Client.
■ Chapter 10, “SequeLink ODBC Edition Client for Windows 9x

and Windows NT”
■ Chapter 11, “SequeLink ODBC Edition Client for

Windows 3.1”
■ Chapter 12, “SequeLink ODBC Edition Client for Macintosh”
■ Chapter 13, “SequeLink ODBC Edition Client for UNIX”
Part 5: SequeLink OLE DB Edition Client Administration

OLE DB Edition Client.
■ Chapter 14, “SequeLink OLE DB Edition Client for Windows 9x

and Windows NT”

Other Documentation 23
Part 6: Appendix
■ Appendix A, “TCP/IP (UDP) Communication (OS/390)”
provides additional information about TCP/IP (UDP) support
for OS/390.
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
SequeLink OLE DB Edition:

■ SequeLink OLE DB Edition Client Installation Guide
■ SequeLink OLE DB Provider Reference
Note: Getting Started with DataDirect for OLE DB also is

available.
SequeLink Java Edition:

■ SequeLink Java Edition Client Installation Guide
■ SequeLink JDBC Driver Reference

24 Preface
The following table provides a guide for finding the information

you need about SequeLink.
For information about… Go to…

Installing SequeLink Server SequeLink Server Installation Guide
Installing SequeLink Clients SequeLink ODBC Edition Client Installation Guide
SequeLink OLE DB Edition Client Installation Guide
SequeLink Java Edition Client Installation Guide
Installing the SequeLink Online Instructions are available on the DataDirect CD

Documents Insert and on the Web site.
Planning, configuring, and SequeLink Administrator’s Guide

administering your system and
network for SequeLink; creating and
managing data sources; using
SequeLink with your database
Troubleshooting problems and SequeLink Error Codes and Messages Reference

referencing error codes
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
Using the SequeLink OLE DB Provider SequeLink OLE DB Provider Reference

Getting Started with DataDirect for OLE DB
Using the SequeLink JDBC Driver SequeLink JDBC Driver Reference

Conventions Used in This Book 25
Conventions Used in This Book

This section describes the typography, terminology, and other
conventions used in this guide.
Typographical Conventions
This guide uses the following typographical conventions:
Convention Explanation
italics Introduces new terms that you may not be familiar
with, 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 you specify; for example, filename.
forward slash / Separates menus and their associated commands.
For example, Select File / Copy means to select
Copy from the File menu.
vertical rule | Indicates an OR separator to delineate items.
brackets [ ] Indicates optional items. For example, in the
following statement: SELECT [DISTINCT], DISTINCT
is an optional keyword.

26 Preface
Convention Explanation
braces { } Indicates that you must select one item. For
example, {yes | no} menus 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
press the left mouse button.
Double-click Click the left mouse button twice.
Right-click Click the right mouse button.
Drag Press and hold the left mouse button while
dragging item(s) to another part of the screen.
SHIFT+Click Press and hold the SHIFT key; then click a
selection. This lets you select a series of objects.
CTRL+Click Press and hold the CTRL key; then click a
selection. This lets you select objects randomly.
Keyboard Conventions
Select menu items by using the mouse or pressing ALT+ the key
letter of the menu name or item.

Conventions Used in This Book 27
Environment-Specific Information
This guide supports users of various operating environments.
Where it provides information that does not apply to all
supported environments, the following symbols are used to
identify that information.
Symbol Environment
Windows. Information specific to the Microsoft Windows
environment is identified by this symbol, which is a
trademark of Microsoft Corporation.
Windows 9x. Information specific to the Microsoft
Windows 95 and Windows 98 environment is identified by
the Windows symbol and “9x.”
Windows NT. Information specific to the Microsoft
Windows NT environment is identified by the Windows
symbol and the letters “NT.”
Macintosh Power PC. Information specific to the
Macintosh Power PC environment is identified by the
MacOS symbol, which is a registered trademark of Apple
Computer, Inc., and the words “Power PC.”
UNIX. Information specific to UNIX environments is
identified by this symbol, which applies to all UNIX
environments supported. UNIX is a registered trademark in
the United States and other countries, licensed exclusively
through X/Open Company Ltd.
OS/390 OS/390. Information specific to OS/390 environments is

identified by the letters, OS/390.
AS/400 AS/400. Information specific to AS/400 environments is

identified by the letters, AS/400.

28 Preface
Contacting Technical Support

MERANT provides technical support for all registered users of
SequeLink, including limited installation support, for the first 30
days. For support after that time, contact us using one of the
following methods or purchase further support by enrolling in
the SupportNet program. For more information about
SupportNet, contact your sales representative.
World Wide http://www.merant.com/datadirect/support

Web
The MERANT Web site provides the latest support information
through SupportNet Online, our global service network that
provides access to valuable tools and information. Our
SupportNet users access information using the Web, automatic
email notification, newsgroups, and regional user groups.
SupportNet Online includes a knowledge base that allows you to
search on keywords for technical bulletins and other information.
You also can download product fixes for your DataDirect
products.
Internet
Australia and New australia.answerline@merant.com

Zealand
EMEA int.datadirect.answerline@merant.com
Japan jpn.answerline@merant.co.jp
USA and Canada datadirect.answerline@merant.com
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

Contacting Technical Support 29
Germany 0130 822 496 or 9:00-6:30 p.m. CET

+44 1727 812898
Japan 81-3-5401-9660 9:00-12:00, 1:00-5:00 p.m. JST
The Netherlands 0800 022 1609 9:00-6:30 p.m. CET
New Zealand 1 800 335 664 8:30-5:30 p.m. LMT
United Kingdom +44 1727 811881 8:00-5:30 p.m. GMT
and Ireland
USA and Canada 1 800 443 1601 8:30-8:00 p.m. EST
Fax and Mail

Information
Fax US 1 919 461 4527

Fax International +32-15-320919
Mail 1500 Perimeter Park Drive, Suite 100, Morrisville, NC 27560 USA
When you contact us, make sure that you can provide the
following information:
■ The product serial number located on the Product

Registration Information card or on a product serial number
card in your package. The number will be checked to verify
your support eligibility. If you do not have a SupportNet
contract, we will ask you to speak with a sales representative.
■ Your name and organization. For a first-time call, you may be

asked for full customer information, including location and
contact details.
■ The version number of your DataDirect product.
■ The type and version of your operating system.
■ Any third-party software or other environment information

required to understand the problem.
■ A brief description of the problem, including any error

messages that you have received, and the steps preceding
the occurrence of the problem. Depending on the complexity

30 Preface
of the problem, you may be asked to submit an example so

that we can recreate the problem.
■ An assessment of the severity level of the problem.

31
1 Overview of SequeLink
This chapter provides an overview of SequeLink, including its

components, architecture, and features.
SequeLink Clients
The following SequeLink clients provide a universal client
interface for ODBC, OLE DB, and JDBC applications:
■ SequeLink ODBC Edition Client

■ SequeLink OLE DB Edition Client
■ SequeLink Java Edition Client
The thin-client architecture facilitates installation and

administration. It also prevents client conflicts with multiple
Dynamic Link Libraries (DLLs), databases, and network stacks.

SequeLink ODBC Edition Client is a universal client component
that includes an ODBC driver. The SequeLink ODBC Driver
provides a single interface with plug-and-play connectivity for
commercial and customized ODBC applications.
On Windows, Windows NT, and Windows 9x, you can create a

Quick Install image with predefined, customized settings, which
can be distributed to and installed on client workstations for
easier installation and administration of SequeLink ODBC
Edition Client. For more information about using Quick Install
images, see “Using Quick Install Images” on page 38.

32 Chapter 1 Overview of SequeLink
SequeLink ODBC Edition Client administration varies from

platform to platform. For platform-specific information about
administration tasks, see:

and Windows NT”

Windows 3.1”
For more information about using the SequeLink ODBC Driver,

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 information about system requirements for the SequeLink

ODBC Edition Client, refer to the SequeLink ODBC Edition Client
Installation Guide.

SequeLink OLE DB Edition Client is a universal client component
that includes an OLE DB provider.
On Windows NT and Windows 9x, you can create a Quick Install

image with predefined, customized settings, which can be
distributed to and installed on client workstations for easier
installation and administration of SequeLink OLE DB Edition
Client. For more information about using Quick Install images,
see “Using Quick Install Images” on page 38.
For information about administration tasks, see Chapter 14,

“SequeLink OLE DB Edition Client for Windows 9x and
Windows NT.”

SequeLink Server 33
For more information about using the SequeLink OLE DB

Provider, refer to the SequeLink OLE DB Provider Reference.
For information about system requirements for the SequeLink

OLE DB Edition Client, refer to the SequeLink OLE DB Edition
Client Installation Guide.
SequeLink Java Edition Client

SequeLink Java Edition Client provides JDBC access through a
Java-enabled applet, application, or web browser. It includes the
SequeLink JDBC Driver and the SequeLink Proxy Server. For
information about installing SequeLink Java Edition Client, refer
to the SequeLink Java Edition Client Installation Guide. For
information about using the SequeLink JDBC Driver, refer to the
SequeLink JDBC Driver Reference.
SequeLink Server
SequeLink Server is a common, server component for SequeLink
ODBC Edition, SequeLink OLE DB Edition, and SequeLink Java
Edition. It uses a common architecture and provides the same
functionality across its supported platforms, with a few
platform-specific differences.
SequeLink Server handles the starting and stopping of processes,

host security authentication, logging, and configuration, as well
as communication and data access activities between the client
and database. SequeLink Server administration varies from
platform to platform. For platform-specific information about
administration tasks, see:



For information about system requirements for SequeLink Server,

refer to the SequeLink Server Installation Guide.
SequeLink ODBC Socket

The SequeLink ODBC Socket is an open ODBC service, supported
on Windows NT and UNIX, that can load any ODBC driver
installed on the server. It provides access to a variety of data and
databases, including nonrelational data and databases.
Note: The SequeLink ODBC Socket can be used with the

SequeLink ODBC Driver, SequeLink OLE DB Provider, or SequeLink
JDBC Driver.
Figure 1-1 shows a functional view of the SequeLink ODBC Socket

accessing a Microsoft Access database.
Figure 1-1. Functional View of the SequeLink ODBC Socket

Accessing a Microsoft Access Database
Microsoft Access
.MDB file
ODBC driver for

Microsoft Access
SequeLink SequeLink ODBC Socket ODBC Driver

ODBC Edition Manager
Client SequeLink Server
Client Server

SequeLink ODBC Socket 35
In this example, SequeLink Server accepts the ODBC data source

name sent by the connection request from the client. The ODBC
Socket calls the ODBC driver manager with this ODBC data
source name to load the appropriate ODBC driver for that
database—in this case, the Microsoft Access ODBC driver.
Administration for the SequeLink ODBC Socket is similar to

administration required for other SequeLink Server services and
depends on your platform. For platform-specific information
about administration tasks you may need to perform for the
SequeLink ODBC Socket, see:

Additionally, the ODBC driver on the server is administered using

the ODBC Administrator. For more information about the ODBC
Administrator, refer to the DataDirect ODBC Drivers Reference,
available with the DataDirect Connect ODBC™ Drivers.
For Information about configuring connection information with

the SequeLink CAT for the SequeLink ODBC Socket, see
“SequeLink CAT Parameters” on page 71.
For information about connecting with the SequeLink ODBC

Socket, see “Connecting With the SequeLink ODBC Socket” on
page 93.

Administrator Tools
Table 1-1 shows the tools that SequeLink provides to help you
perform administration tasks.
Table 1-1. Administrator Tools
ODBC OLE DB Java

Tool Edition Edition Edition
SequeLink Connect Administration Tool (CAT) ✓ ✓
SequeLink Data Source SyncTool ✓ ✓
SequeLink Data Source SyncTool Administrator ✓ ✓
SequeLink Dictionary Manager ✓ ✓
SequeLink Server Windows NT Administrator ✓ ✓ ✓
SequeLink Server UNIX Administrator ✓ ✓ ✓
The SequeLink Connect Administration Tool (CAT) is supported

for Windows, Windows 9x, Windows NT, and Macintosh
Power PC (PPC) platforms as a graphical interface. On UNIX, it is
supported as a command-line tool. Use it to create, modify,
delete, and test SequeLink data sources.
The SequeLink Data Source SyncTool is supported on Windows,

Windows 9x, and Windows NT platforms for ODBC data sources
and is supported on Windows 9x and Windows NT platforms for
OLE DB data sources. End users can use it to import data source
definitions from data source files which you create and
distribute.
Note: The SequeLink ODBC Data Source SyncTool can only be

used with ODBC data sources; the SequeLink OLE DB Data Source
Synctool can only be used with OLE DB data sources.
The SequeLink Data Source SyncTool Administrator is supported

on Windows, Windows 9x, and Windows NT platforms for ODBC

Administrator Tools 37
data sources and is supported on Windows 9x and Windows NT

platforms for OLE DB data sources. Use it to create data source
files and synchronize your SequeLink and ODBC and OLE DB data
sources on servers and clients.
Note: The SequeLink ODBC Data Source SyncTool Administrator

can only be used with ODBC data sources; the SequeLink OLE DB
Data Source Synctool Administrator can only be used with
OLE DB data sources.
The SequeLink Dictionary Manager is supported on Windows 9x

and Windows NT platforms. Use it to create and manage
SequeLink Shadow Data Dictionaries (SSDDs). For more
information about SSDDs and using this tool, see “Using the
SequeLink Dictionary Manager” on page 162.
The SequeLink Server Windows NT Administrator. Use it to

configure and control SequeLink Server runtime tasks. For more
information about using this tool, configuring SequeLink Server
for Windows NT, and controlling SequeLink Server runtime tasks
for Windows NT, see Chapter 6, “SequeLink Server for
Windows NT.”
The SequeLink Server UNIX Administrator is a command-line

tool. Use it to configure and control SequeLink Server for UNIX.
For more information about using this tool, configuring
SequeLink Server for UNIX, see Chapter 7, “SequeLink Server for
UNIX.”

Using Quick Install Images

A Quick Install image is a predefined, customized installation
image, which can be used to install the same SequeLink ODBC or
OLE DB Edition Client configuration on multiple workstations. It
can be stored on a file server and used for all SequeLink ODBC or
OLE DB client installations within a workgroup. Installing a Quick
Install image requires minimal user interaction and ensures that
every client you are responsible for administering is installed with
the same settings.
A Quick Install image automatically includes required

components, such as the SequeLink ODBC Driver or SequeLink
OLE DB Provider, and the SequeLink CAT. You can select
additional optional components to install, such as the SequeLink
Data Source SyncTool and at least one SequeLink network
module. You also can create multiple Quick Install images with
different configurations, allowing you to customize each image
for different workgroups within your organization.
For information about creating and installing Quick Install

images for:
■ SequeLink ODBC Edition Client on Windows 9x/Windows NT,

see “Quick Install Images” on page 367
■ SequeLink ODBC Edition Client on Windows 3.1x, see “Quick

Install Images” on page 378
■ SequeLink OLE DB Edition Client, see “Quick Install Images”

on page 399

SequeLink’s n-Tier Architecture 39
SequeLink’s n-Tier Architecture

SequeLink offers n-Tier flexibility. SequeLink Server can be
installed and configured on the same server on which the
database engine resides. This often is referred to as a two-tiered
architecture.
Figure 1-2 shows an example of a two-tiered architecture using

SequeLink, TCP/IP, and an Oracle database. For a list of
supported network protocols and databases, refer to the
SequeLink Server Installation Guide.
Figure 1-2. Example: Two-Tier Architecture
Tier Tier 1 Tier 2
DBMS
ODBC, OLE DB, or JDBC Oracle

Applications
SequeLink ODBC, OLE DB,

SequeLink Server
or Java Edition Client
TCP/IP TCP/IP
In this example, SequeLink Server binds directly to the Oracle

database engine, providing maximum throughput and
minimizing network bandwidth.

For maximum flexibility and centralized access, SequeLink Server

can be installed on an intermediate server between the client and
database server. This often is referred to as a three-tier
architecture. Figure 1-3 on page 40 shows a three-tier
architecture using SequeLink ODBC Edition Client, TCP/IP, and an
Oracle database. For a list of supported network protocols and
databases, refer to the SequeLink Server Installation Guide.
Figure 1-3. Example: Three-Tier Architecture
Tier 1 Tier 2 Tier 3

Tier
DBMS
Database Server/
ODBC Applications SequeLink ODBC Socket Oracle Database
SequeLink ODBC
Edition Client ODBC Driver & Oracle
TCP/IP Oracle Middleware
TCP/IP Middleware
In this example, the SequeLink ODBC Socket uses an ODBC driver

and Oracle’s middleware to connect from the SequeLink Server
server to the Oracle server. The SequeLink ODBC Driver can
connect to a variety of database servers using the SequeLink
ODBC Socket in an n-Tier environment.

Functional Overview 41
Functional Overview
Functionally, SequeLink uses network and database services. The
network service is provided by compatible network modules
residing at the client and server which establish connections, and
send and receive packets. Database services, which are designed
to access specific database systems, reside on the server. For
example, an Oracle service provides optimized communication
with an Oracle database.
For most SequeLink Server platforms, the network service

spawns a process (or thread, for OS/390 and some SequeLink
Server services on Windows NT) for each connection. Host
authentication is performed to validate user rights on the host,
providing an additional level of security than validating access to
the database only.
Alternatively, on Windows NT and UNIX servers, a single master

account can be configured for all client workstations.
Figure 1-4 shows a typical SequeLink process, from client

connection to spawned service process.

Figure 1-4. SequeLink Process
SequeLink ODBC SequeLink

Edition Client
Tier Server
SequeLink Network
Service
Listener process,
Client inetd, VTAM
Connection
Request
Host Authentication
Service Database Process or Thread

DBMS
Process
to Client SequeLink Database Service
Features and Advantages

Simplified Administration:
■ A single-client component allows easy installation and
configuration for access to multiple database systems.
■ The SequeLink CAT allows you to administer client

configuration files locally or with shared access across a Local
Area Network (LAN).
■ The SequeLink Dictionary Manager allows you to create and

manage SequeLink Shadow Data Dictionaries (SSDDs).

Features and Advantages 43
■ The SequeLink Data Source SyncTool allows you to configure

data sources centrally and distribute data source definitions
to client workstations.
■ Quick Install images allow you to create a predefined,

customized image that can be used to install the same
SequeLink client configuration, including data source
definitions, on multiple workstations.
■ The SequeLink Server Windows NT Administrator and

SequeLink Server UNIX Administrator allow you to set
SequeLink Server service attributes and monitor client
connections.
Improved System Performance:

■ Using SSDDs streamlines data access, ensuring that only
predefined subsets of tables are returned from databases.
■ The compression of data sent between the server and client

guarantee efficient use of network resources.
■ Efficient use of packets and packet limits reduce overall

network bandwidth requirements.
For information about developing performance-optimized

ODBC applications, 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 information about developing OLE DB applications, refer to

the SequeLink OLE DB Provider Reference and Getting Started
with DataDirect for OLE DB.
Full Database Support:

■ ODBC API function compliance of Core, Level 1, and selected
Level 2, and ODBC SQL grammar compliance of Core and
Minimum allow full ODBC access.
■ Dynamic SQL and full SQL passthrough provide access to

database-specific grammar and functions.

■ Common data types, representation, formatting, and

conversion routines are supported.
■ Transaction control is supported, including commit/rollback

and multiple isolation levels.
■ Cursors and parameters are supported, including bound

variables (input, output, and input/output).
■ Transliteration is performed using standard mechanisms and

routines.
■ OLE DB access is provided through the SequeLink OLE DB

Provider.
■ JDBC access is provided through the SequeLink JDBC Driver.
For more information about support for specific databases, see

“Using SequeLink With Your Database” on page 149.
Extended Security:
■ SequeLink server user and password validation ensures
appropriate access to hosts, not just to databases.
■ Encryption of data, including account information such as

user and password authorizations, provides secure data
transmission.
■ ReadOnly and Autocommit filters offer extended security.
■ Firewall-enabled, TCP/IP network services allow

communication between clients and servers across firewalls
for Internet/intranet access.
■ Ability to limit access to SequeLink Server services to a subset

of client applications provides additional security.

45

This part contains the following chapter:
■ Chapter 2, “Using Data Sources” introduces SequeLink data

sources, ODBC data sources, and the tools you can use to
manage them.

46 Part 1: Data Sources

47
2 Using Data Sources
SequeLink uses SequeLink data sources, and ODBC or OLE DB

data sources. This chapter introduces these data sources and the
tools you can use to manage them.
SequeLink Data Sources

SequeLink data sources are named collections of data source
information that allow client applications to connect to a
particular database, on a particular server, using a particular
network protocol.
You associate a SequeLink data source with ODBC data sources.

For more information about ODBC data sources, see “ODBC Data
Sources” on page 49.
■ ODBC data sources. For more information about ODBC data

sources, see “ODBC Data Sources” on page 49.
■ OLE DB data sources. For more information about OLE DB

data sources, see “OLE DB Data Sources” on page 50.
You can create, modify, delete, and test SequeLink data sources
using the SequeLink Connect Administration Tool (CAT). For
more information about using the SequeLink CAT, see “Using the
SequeLink CAT” on page 52.
The information stored in a SequeLink data source depends on

the database type, server, and network protocol, but can include
any of the following items:
Data source name This is a unique name identifying the

data source.

48 Chapter 2 Using Data Sources
Description This a comment describing the data

source—for example, “Oracledb in
Accounting” may identify a particular
database to be used for accounting
applications.
Transliteration This specifies the runtime transliteration
resource/Dynamic function that will be used, if
Link Library (DLL) transliteration is required.
Server/Host settings These specify the server or host on which
the SequeLink Server software resides,
and the user ID and password required
to access that server or host.
Network settings These specify the network protocol used
to connect to the server and various
network-dependent parameters.
Service (database) These specify the database on the server
settings to which SequeLink will connect and
various database-specific parameters.
You specify this information when you configure a SequeLink

data source. Also, you can prompt the end user for specific
information by specifying a value placeholder. For example, you
may want to prompt the end user for a valid user ID and
password. For information about configuring SequeLink data
sources with the SequeLink CAT, see “Using the SequeLink CAT”
on page 52.

ODBC Data Sources 49
ODBC Data Sources

ODBC data sources are named collections of ODBC data source
information, including a defined association with a SequeLink
data source. You can configure an ODBC data source using the
SequeLink ODBC Administrator. You must configure a SequeLink
data source before you can configure its associated ODBC data
source.
Note: You can access the SequeLink CAT from the SequeLink
ODBC Administrator.
ODBC data source definitions include the following items:
Data source name This identifies the ODBC data source

configuration in the ODBC.INI.
Examples include “Accounting” and
“SequeLink to Informix Data.”
Description This an optional comment
describing the data source—for
example, “My Accounting
Database” or “Accounting Data in
Informix.”
SequeLink data source This is the SequeLink data source
associated with this ODBC data
source.
Optional settings These are optional settings that
control how an application interacts
with this ODBC data source.
For information about configuring ODBC data sources, 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.

OLE DB Data Sources

OLE DB data sources are named collections of OLE DB data source
information, including a defined association with a SequeLink
data source. You can configure an OLE DB data source using the
INTERSOLV OLE DB Administrator. You must configure a
SequeLink data source before you can configure its associated
OLE DB data source.
Note: You can access the SequeLink CAT from the INTERSOLV
OLE DB Administrator.
OLE DB data source definitions include the following items:
Data source name This identifies the OLE DB data

source configuration. Examples
include “Accounting” and
“SequeLink to Informix Data.”
Description This an optional comment
describing the data source—for
example, “My Accounting
Database” or “Accounting Data in
Informix.”
SequeLink data source This is the SequeLink data source
associated with this OLE DB data
source.
Optional settings These are optional settings that
control how an application interacts
with this OLE DB data source.
For information about configuring OLE DB data sources, refer to

the SequeLink OLE DB Provider Reference.

Synchronizing Data Sources 51
Synchronizing Data Sources

The SequeLink Data Source Synctool allows you to synchronize
SequeLink data sources, and ODBC or OLE DB data sources. The
SequeLink Data Source SyncTool has two different user
implementations—one for the SequeLink administrator and
another for the end user.
As the administrator, you can use the SequeLink Data Source

SyncTool Administrator to create data source files (collections of
data source definitions), and import and export data source
definitions to and from data source files. These data source files
can be distributed easily to hundreds of SequeLink clients. The
end user simply imports these data source definitions from the
distributed data source file using the end user implementation
of the SequeLink Data Source SyncTool.
In addition, you can create a customized, installable image of

SequeLink ODBC or OLE DB Edition Client with predefined, site-
specific settings, including data source files created with the
SequeLink Data Source SyncTool. The Quick Install image can be
distributed to and installed on each client in your workgroup.
When installed, the data source in the specified data source file
automatically will be imported also, resulting in a consistent,
fully configured SequeLink client installation on every
workstation.
Note: The SequeLink ODBC Data Source SyncTool can only be
used with ODBC data sources; the SequeLink OLE DB Data Source
SyncTool can only be used with OLE DB data sources.
For more information about creating Quick Install images for:
■ SequeLink ODBC Edition Client on Windows 9x and

Windows NT, see “Quick Install Images” on page 367
■ SequeLink ODBC Edition Client on Windows 3.1x, see “Quick

Install Images” on page 378

■ SequeLink OLE DB Edition Client on Windows 9x and

Windows NT, see “Quick Install Images” on page 399
For more information about using the SequeLink Data Source

SyncTool for ODBC and OLE DB data sources, see “Using the
SequeLink Data Source SyncTool” on page 95.
Using the SequeLink CAT

The SequeLink CAT allows you to create, modify, delete, and test
SequeLink data sources. It is installed when you install SequeLink
ODBC or OLE DB Edition Client. How you use the SequeLink CAT
depends on your client’s operating system. For information about
using the SequeLink CAT:
■ See the following section “On Windows and Macintosh,”

■ See “On UNIX” on page 63
Online help for the SequeLink CAT is provided for Windows,

Windows 9x, and Windows NT.
On Windows and Macintosh

This section provides information about the following tasks for
Windows and Macintosh users:
■ Starting SequeLink CAT

■ Creating new data sources
■ Modifying data sources
■ Deleting data sources
■ Testing data sources

Using the SequeLink CAT 53
Starting the SequeLink CAT

1 Open the SequeLink program group, and double-click
SequeLink CAT.
Locate the SequeLink folder, and double-click SequeLink™

CAT PPC.
The SequeLink CAT dialog box appears.
List of data sources configured for your system
Click here to configure a

new data source.
Click here to duplicate a

selected data source and
give it a new name.
Click here to edit a

selected data source.
Click here to delete a

selected data source.
Click here to test a selected

data source.
The first time you start the SequeLink CAT, the SequeLink Data
Sources list will be empty. Once you create data sources for your
system, these data sources will be listed in this list box.

Note: When using the SequeLink CAT, you can quit from any
procedure, discarding any changes, by clicking Cancel.
Creating Data Sources

You can create data sources from scratch or base them on existing
data sources.
Creating a Data Source from Scratch

1 On the SequeLink CAT dialog box, click the New button. The
Add SequeLink Data Source dialog box appears.

This dialog box contains different panes for entering the

following types of information:
■ Data source identification and transliteration

■ Service
■ Host (or server)
■ Network
2 In the Name and Description fields, enter information for the

new data source. If required, enter the transliteration DLL or
resource to be used for transliteration in the SequeLink
transliteration DLL/resource field.
The data source name can be up to

80 characters; it cannot contain
spaces or certain special characters.
For a list of these special characters,
see Table 2-1.
Your own comment describing the

data source.
Italicized labels indicate optional The name of a Macintosh transliteration

entries. resource or Windows DLL.
Name: Use this field to identify the data source. This name
must be unique. It can contain a combination of uppercase
and lowercase letters, digits, and any special characters not
listed in Table 2-1, up to a maximum of 80 characters.
However, you cannot specify two data source names that are
the same except for case.
Table 2-1. Invalid Characters for Data Source Name
Character Character Description

@ At sign
* Asterisk

Table 2-1. Invalid Characters for Data Source Name (cont.)
Character Character Description

, Comma
= Equal sign
! Exclamation mark
{ Left brace
[ Left bracket
( Left parenthesis
? Question mark
} Right brace
] Right bracket
) Right parenthesis
; Semicolon
Space
Description: Use this field to describe the data source. For

example, you may want to use a description of “Northwest
Region: Personnel” to describe a data source used by the
personnel department in the northwest region of your
company. The data source description can be up to 160
characters.
Transliteration: A transliteration facility may be required by

users of data sources. This facility is implemented as a DLL on
Windows, Windows 9x, and Windows NT. It is implemented as
a resource on Macintosh. If transliteration is required, enter
one of the following types of information:
■ DLL name, or click ... (Ellipsis button) and select a DLL

from a list of available DLLs. The name must include the
.DLL extension and the full path (if the DLL directory is not
in the PATH environment variable).
■ Resource name.

3 Select an appropriate service, host, and network type from

the appropriate drop-down list boxes in each pane. Then,
enter information as required.
Fields that do not apply are unavailable. Some fields are

required; others are optional. Optional parameters have
italicized labels. Passwords are encrypted and do not appear
when you enter them.
When you select a service, host, or network type, the

remaining fields adjust to show the type of information you
need to enter (for example, <user>, <password>, or
default values).
The following figure shows an example of how the Service

pane adjusts when an Oracle database service is selected in
the Service pane. The Host and Network panes adjust
similarly.
A drop-down list of the

types of service you can
connect to; for example,
Fields that are
an Oracle database
not applicable
are disabled.
This parameter is
required for Oracle. It
can be supplied here or
Check this box if at connection.
you want the
user to be
prompted for the
password at Optional parameters are indicated by italic
labels. You can supply them here, supply
them at connection, or omit them.
You may enter the parameters or prompt the end user for
some information (user ID and password, for example).

To prompt the end user for information, you can perform

either of the following actions:
■ Enter a prompt value placeholder in the appropriate field.

For example, type <prompt>.
■ Leave the field as-is. SequeLink CAT will replace it with a

prompt value placeholder.
Note: For a password, you also can check the Prompt for
password box. A prompt value placeholder will be entered in
the Password field.
4 To test the new data source, click Test. An attempt is made to

connect to the specified service. If the test fails, verify that the
following conditions have been met:
■ The information you entered was correct.

■ SequeLink Server has been started on the server or host.
■ Your network is running.
For more information about testing data sources, see “Testing

a Data Source” on page 61.
5 Click Add. The data source is added to your system.

Creating a Data Source from an Existing Data Source

1 In the SequeLink CAT dialog box, select the data source on
which you want to base the new data source and click
Duplicate.

The Add SequeLink Data Source dialog box appears, showing

the parameters configured for the selected data source.
2 Enter a name, description, and transliteration DLL/resource

for the new data source.
3 Change other parameters as needed.
4 Click Add.

Modifying a Data Source

1 In the SequeLink CAT dialog box, select the data source you
want to change and click Edit. The Edit SequeLink Data
Source dialog box appears, showing the configuration
information for the selected data source.
2 Change the information as needed.
3 Optionally, test the data source.
4 Click Add.
If you specify a name that already exists, a message appears

asking you to confirm the action. If you confirm, the
configuration of the existing data source is overwritten with the
configuration of the data source you have just modified.
Deleting a Data Source

1 In the SequeLink CAT dialog box, select the data source you
want to remove and click Delete.
2 Confirm the deletion.
Testing a Data Source

You can test a data source from the SequeLink CAT dialog box or
from the Add/Edit SequeLink Data Source dialog box.
To test a data source from the SequeLink CAT dialog box:

1 In the SequeLink CAT dialog box, select a data source from
the list and click Test.
2 Supply any parameters, if prompted for them.
If a <prompt> value placeholder was substituted for a field in

the configuration information, you will be prompted to
supply an appropriate value. For example, the following

dialog box prompts for the Oracle password required to

access an Oracle database on a Windows NT server.
Parameters are requested in the following order: network,

server, and service.
If the connection is unsuccessful, an error message is returned.

For more information about error messages, refer to the
SequeLink Error Codes and Messages Reference.
3 If prompted, confirm that you have read the error message.
4 Confirm success or failure of the test.

On UNIX
On UNIX, the SequeLink CAT is command line-driven. The
SequeLink executable is named sqlnkcau and can be found in
the bin subdirectory of your SequeLink directory (for example,
/usr/sqlnk/bin).
This section provides guidelines for using the command line

interface and shows examples of the following tasks:
■ Creating a data source

■ Modifying a data source
■ Testing a data source
Using the Command Line Interface

Note the following guidelines about the command line
interface:
■ User information (for example, the type of operation or

parameter) is typed after the sequence [……]:. For example:
Select an action [0]:

■ To accept a default value, press the RETURN key. Default
values are shown enclosed by lesser than and greater than
symbols (< NO >, for example).
■ User input is indicated by bold text. For example:
Name[]:SQLNK_RS_ORACLE7
■ Comments appear in italics and are preceded by a pound sign
(#). For example:
Name[]:SQLNK_RS_ORACLE7 # enter new data source

name

■ Parameters can be required or optional. Optional parameters

have labels preceded by an asterisk (*). For example:
*Description[<description>]:
■ Passwords are encrypted and appear as asterisks when you
type them.
■ You can prompt the end user for parameters in any of the
following ways:
• Type a prompt value placeholder; for example, type

<prompt>.
• Type RETURN. The SequeLink CAT replaces the existing

placeholder in the configuration with a prompt value
placeholder.
• If you want to clear a parameter (for example, to connect

to a service without a password), type the pound sign
character, #. This is equivalent to entering an empty string.
Example: Creating a Data Source

The following example shows how to create a data source on
UNIX.
Note: The SequeLink executable is named sqlnkcau and can be

found in the bin subdirectory of your SequeLink directory (for
example, /usr/sqlnk/bin).
$ ./sqlnkcau # launch of the CAT
SequeLink Connect Administration Tool

(c) Copyright 1994-1999 MERANT, Inc., All rights reserved.
The following Data Source is selected :
[1] Select a Data Source
[2] New
[7] About
[0] Cancel
Select an action [0]: 2

Name[]:SQLNK_RS_ORACLE7 # enter new data source name

*Description[<description>]:Oracle 7 DB on RS6000 # description
*Transliteration[<transliteration>]: # no transliteration
The following network types are available:
[1] TCP/IP
Select a network [1]:1 # enter network settings
Host[<host>]:rs6000
The following server types are available:
[1] AS/400
[2] OS/390
[3] UNIX
[4] VAX
[5] VM
[6] Windows NT
Select a server [1]:5 # enter server settings
User[<user>]:pascal
Password[*****]: # accept the default
The following service types are available:
[1] DB2/HP
[2] DB2 on OS/390
[3] DB2/Solaris
[4] DB2/VM
[5] DB2/2
[6] DB2/400
[7] DB2/6000
[8] Informix
[9] Ingres
[11] Oracle
[12] Rdb
[13] SQL Server
[14] Sybase
Select a service [1]:12 # enter service settings
Name[<service>]:Oracle7ssp25
*User[<user>]:scott
*Password[*****]:tiger # normally not visible
The following Data Source is selected : SQLNK_RS_ORACLE7.
[2] New
[3] Duplicate
[4] Edit
[5] Delete

[6] Test
[7] About
[0] Cancel
Select an action [0]: 6 # test new configuration
Test passed: connection to 'SQLNK_RS_ORACLE7' made.

[2] New
[3] Duplicate
[4] Edit
[5] Delete
[6] Test
[7] About
[0] Cancel
Select an action [0]: # exit from the CAT
$
Example: Modifying a Data Source

The following example changes the Oracle password of the data
source configured in the previous section. The subsequent test
will fail as a result of an Oracle security error.



[2] New
[7] About
[0] Cancel

The following SequeLink Data Sources are available:

[1] SQLNK_RS_Informix6
[2] SQLNK_RS_ORACLE7
[0] Cancel
Select a Data Source [0]: 2
[2] New
[3] Duplicate
[4] Edit
[5] Delete
[6] Test
[7] About
[0] Cancel
Name[SQLNK_RS_ORACLE7]: # accept existing value
*Description[Oracle 7 DB on RS6000]:
*Transliteration[<transliteration>]:
The following network types are available:
[1] TCP/IP
Select a network [1]:
Host[rs6000]:
The following server types are available:
[1] AS/400
[2] OS/390
[3] UNIX
[4] VAX
[5] VM
[6] Windows NT
Select a server [5]:
User[pascal]:
Password[*****]:
The following service types are available:
[1] DB2/HP
[2] DB2 on OS/390
[3] DB2/Solaris
[4] DB2/VM
[5] DB2/2
[6] DB2/400
[7] DB2/6000
[8] Informix

[9] Ingres
[10] Oracle
[11] Rdb
[12] SQL Server
[13] Sybase
Select a service [12]:
Name[Oracle7ssp25]:
*User[scott]:
*Password[*****]:
[2] New
[3] Duplicate
[4] Edit
[5] Delete
[6] Test
[7] About
[0] Cancel
ORA-01017: invalid username/password; logon denied
Test failed: connection to 'SQLNK_RS_ORACLE7' failed.

[2] New
[3] Duplicate
[4] Edit
[5] Delete
[6] Test
[7] About
[0] Cancel
$

Example: Testing a Data Source

The following example tests a defined data source.



[2] New
[7] About
[0] Cancel
The following SequeLink Data Sources are available:
[1] hp9Test
[2] hp9
[3] rs6000
[4] Ora7Dev
[5] hp9cr
[6] SQLNK_RS_Informix6
[7] SQLNK_RS_ORACLE7
[0] Cancel
Select a Data Source [0]: 7
[2] New
[3] Duplicate
[4] Edit
[5] Delete
[6] Test
[7] About
[0] Cancel
Test passed: connection to 'SQLNK_RS_ORACLE7' made.


[2] New
[3] Duplicate
[4] Edit
[5] Delete
[6] Test
[7] About
[0] Cancel
$

SequeLink CAT Parameters 71
SequeLink CAT Parameters

This section provides information about the parameters you
supply when you define a SequeLink data source.
Value Placeholder
A value placeholder serves as a mnemonic for a field. It is
indicated by a value between a lesser than symbol (<) and a
greater than symbol (>). If a value placeholder is specified for a
field, the end user will be prompted at connection to fill in the
parameter with an appropriate value.
Required and Optional Parameters

To configure a data source using SequeLink CAT, you supply
values for the Server/Host, Network, and Database parameters.
Some parameters are required; others are optional.
A required parameter is one for which you or the end user must
supply a valid value. At administration, a required parameter can
be supplied with a valid value, can be left equal to its value
placeholder, or set to the prompt value <prompt>. If the
parameter is left equal to its value placeholder or set to the
prompt value <prompt>, the end user will be required to supply
this information at connection.
An optional parameter is one which you or the end user can

leave empty. At administration, it can be supplied with a valid
value, cleared, left equal to its value placeholder, or set to
<prompt>. If the parameter is left equal to its value placeholder
or set to the prompt value <prompt>, the end user will be
prompted to supply a valid value.

Encryption and Compression

You can set encryption and compression for a particular service
using the Service name parameter. To use encryption, prefix the
service name with *byteswap*, specifying the byteswap
encryption module. To use compression, prefix the service name
with #huffman#, specifying the compression module. For
example:
*byteswap*SLOracle
#huffman#SLSybase
*byteswap*#huffman#SLInformix
#huffman#*byteswap*SLDB2
For more information about encryption and compression, see

“Data Transmission” on page 117.
Host/Server Parameters
A SequeLink host/server setting is a collection of settings that
describes the host/server on which the SequeLink service resides.
These settings include a host/server type, a user name, and
password. This section lists the host/server parameters for each
supported server.
AS/400 Parameters
To connect to SequeLink Server on an AS/400 host, you must
supply a user name and password.
Field Req/Opt Prompt Value Description

User name Required <user> or <prompt> AS/400 user
name
Password Required <password> or AS/400
<prompt> password

OS/390 Parameters
To connect to SequeLink Server on an OS/390 host, you must
supply a user name and password. The user name and password
are passed to the security system installed on OS/390. If no
security system is installed, you must supply dummy values.
SequeLink supports the following security systems on OS/390:

RACF, CA-ACF2, and CA-TOP SECRET.

User name Required <user> or <prompt> OS/390 user
name
Password Required <password> or OS/390
<prompt> password
UNIX Parameters
To connect to SequeLink Server on a UNIX server, you must
supply a user name and password. The user name and password
must follow the conventions required by the UNIX server and are
case-sensitive.

User name Optional <user> or <prompt> UNIX user name
Password Optional <password> or UNIX password
<prompt>
If the SequeLink service specifies the host user name or no host

user authentication is required, you can leave the User name and
Password fields empty. For information about setting the user
authentication level for a service, see “Setting the User
Authentication Level” on page 268.

Windows NT Parameters
To connect to SequeLink Server on a Windows NT server, you
must supply a user name and password. The user name and
password must follow the conventions required by the
Windows NT server and are case-sensitive.

User name Optional <user> or <prompt> Windows NT
user name
Password Optional <password> or Windows NT
<prompt> password
If guest access on the Windows NT server is enabled, the user

name and password of this guest account must be entered.
Consult your Windows NT system administrator to obtain
information about the security level available on your
Windows NT machine.
You can specify a domain name for the user by preceding the user
name with the domain name, separated by a backslash (\). If the
domain is the local domain of the Windows NT server, you may
want to specify the domain explicitly. This can facilitate user
authentication when the Windows NT server is not a primary
domain controller.
If the SequeLink service specifies the host user name and

password or if no host user authentication is required, you can
leave the User name and Password fields empty. For information
about setting the user authentication level for a service, see
“Setting the User Authentication Level” on page 248.

Service (RDBMS) Parameters

A SequeLink service setting is a collection of service-specific
settings that describe the services SequeLink can access. These
settings include a service type, database name, user name,
password, and service settings. This section lists the service
parameters for each supported service.
DB2 on AS/400 Parameters

To use a SequeLink DB2 on AS/400 service, supply the following
parameters:

Name Required <prompt> Service name
Database Optional <library> or <prompt> Library name
Service name: This identifies the DB2 service. Encryption and

compression can be enabled through the service name.
You can specify any of the following values for the Service name:
SQLNKALL This service has been compiled with

commitment control *ALL. All rows that
are read are locked until the transaction
is committed or rolled back. A Commit
statement must be issued to commit any
database changes and release the locks.
This SequeLink service can be used for
Data Manipulation Language (DML) and
Data Definition Language (DDL)
statements. Transactions are supported;
however, DDL statements, such as Create
Table, do not participate in the
transaction. For example, a Rollback
statement will not roll back a Create
Table statement.

SQLNKNONE This service has been compiled with

commitment control *NONE. Each SQL
statement is finalized as it is completed.
Any database changes are immediately
executed. It can be used for both DML
and DDL statements. Commitment
statements like Commit and Rollback
have no effect.
TCP_Port_Number A user-defined port number, which
identifies a user-defined service on the
AS/400, can be specified. User-defined
services can be created using the
CRTSQSRV command and can be used to
connect to a service with a specific
isolation level or library list. For more
information about user-defined services,
refer to “Creating and Deleting User-
Defined Services” on page 287.
Note: This parameter applies only to TCP/IP connections. When

using another network protocol, the service is specified with the
Host parameter in the network settings of the SequeLink CAT.
Library Name: This parameter specifies the library to be used. By

default, the library that will be used is specified by the library list
configured on the AS/400 for the user who issues the connection.
This parameter allows additional operations to be performed on
the library list. You can choose from the following values:
Empty string If an empty string is specified, no changes are

made to the library list.
SQADDLIBLE <Lib1> [<Lib2>] … The specified libraries are added to the top
of the library list of the server process.
SQRPLLIBLE <Lib1> [<Lib2>] … The current user library list is replaced by the
specified libraries.

SQAPPLIBL <Lib1> [<Lib2>] … The specified libraries are added to the

bottom of the user library list.
Application_name The SequeLink server process will call this
AS/400 program during connection setup.
DB2 on NT Parameters
To use a SequeLink DB2 on NT service, supply the following
parameters:

Database Optional <database alias> or Database name
<prompt>
User name Optional <user> or <prompt> Database user
name
Password Optional <password> or Database

<prompt> password
Service name: This identifies the DB2 service. The default is

SLDB2. Encryption and compression can be enabled through the
service name.
Database name: This identifies the DB2 database alias. For more
information, refer to your DB2 documentation.
Database user name/Database password: These are the DB2 user

name and user authorization required to log on to DB2. If
specified, the host user name specified at connection is
overridden.

DB2 on OS/390 Parameters

To use a SequeLink DB2 on OS/390 service, supply the following
parameters:

Service name: This identifies the SequeLink service. The default is

MVSDB2. Encryption and compression can be enabled through the
service name.
DB2 on UNIX Parameters

To use a SequeLink DB2 on UNIX service, supply the following
parameters:

Database Optional <database alias> or Database name
<prompt>
name

<prompt> password
Service name: This identifies the DB2 service. The default is

SLDB2. Encryption and compression can be enabled through the
service name.
Database name: This identifies the DB2 database alias. For more
information, refer to your DB2 documentation.
Database user name/Database password: These are the DB2 user

name and user authorization required to log on to DB2. If

specified, the host user name specified at connection is

overridden.
INFORMIX on NT Parameters
To use a SequeLink INFORMIX on NT service, supply the
following parameters:

Database Optional <server name> or Database name
<prompt>
name

<prompt> password
Service name: This identifies the Informix service. The default is

SLInformix. Encryption and compression can be enabled
through the service name.
Database name: This identifies the Informix database you want

to access—for example, stores7.
Database user name/Database password: These are the Informix

user name and user authorization required to log on to Informix.

INFORMIX on UNIX Parameters

To use a SequeLink INFORMIX on UNIX service, supply the

Database Optional <name> or <prompt> Database name
Service name: This identifies the INFORMIX on UNIX service. The

default is SLInformix. Encryption and compression can be
enabled through the service name.
Database name: This identifies the Informix database that you

want to access.
■ For INFORMIX-OnLine databases, enter the name of the

database.
■ For INFORMIX-SE databases, enter the full pathname and the

name of the database. For example, if your database is called
“production” and is located in /usr/informix, enter:
/user/informix/production
Microsoft SQL Server Parameters

To use a SequeLink Microsoft SQL Server service, supply the

Database Optional <database> or Database name
<prompt>


User name Required <user> or <prompt> Database user
name
Password Required <password> or Database

<prompt> password

SLSQLServer. Encryption and compression can be enabled
Database name: This identifies the SQL Server database you

want to access. If unspecified, the default database of the
specified user will be used.
Database user name/Database password: These are the SQL

Server user name and user authorization required to log on to
the Microsoft SQL Server database.
ODBC Btrieve Parameters

To use the SequeLink ODBC Socket with the MERANT Connect
ODBC for Btrieve driver, supply the following parameters:

<prompt>

SLDataServer. Encryption and compression can be enabled
Database name: This identifies the full pathname of the

directory on the server that contains the Btrieve files and the
data dictionary files (DDFs). DDFs describe the Btrieve data
structure and are required for a connection to succeed.

ODBC dBASE Parameters

ODBC for dBASE driver, supply the following parameters:

<prompt>

SLSocket. Encryption and compression can be enabled through
the service name.
Database name: This identifies the full pathname of the directory

on the server that contains the dBASE files.
ODBC Excel
ODBC for Excel driver, supply the following parameters:

<prompt>

the service name.
Database name: This identifies the full pathname of the .XLS

workbook filename on the server.

ODBC FoxPro Parameters

ODBC for FoxPro driver, supply the following parameters:

<prompt>

the service name.
Database name: This identifies the full pathname of the

directory on the server that contains the FoxPro files and DDFs.
ODBC MS Access Parameters

To use the SequeLink ODBC Socket with the Microsoft Access
driver, supply the following parameters:

<prompt>

the service name.
Database name: This identifies the fully qualified path of the

.MDB Microsoft Access database file on the server. You must
specify the .MDB filename extension.

ODBC Paradox Parameters

ODBC for Paradox driver, supply the following parameters:

<prompt>

the service name.

on the server that contains the Paradox files.
ODBC Socket Parameters

To use the SequeLink ODBC Socket, supply the following
parameters:

<prompt>
name

<prompt> password
Settings Optional <server name> or ODBC Data
<prompt> Source

the service name.

Database name: This is the name of the database on the server

host. When connecting to a database, SequeLink Server will use
the value of this field as the DB= parameter when executing the
ODBC SQLDriverConnect call.
Database user name/Database password: This is the user name

and password authorization required to log on the server host.
When connecting to a database, SequeLink Server will use the
values of these fields as the UID= and PWD= parameters when
executing the ODBC SQLDriverConnect call.
ODBC Data Source: This is the ODBC data source that will be
used for this connection. Specify this parameter using either of
the following formats:
■ A value without equal signs (=). The value indicates the

ODBC data source name that will be used. This ODBC data
source must be defined on the server. If you are connecting
to a Windows NT server, the specified data source must be a
System data source (not a User data source).
■ A value in the Keyword1=Value1;Keyword2=Value2;...

format. The value of this field is used to build the ODBC
SQLDriverConnect input string used by SequeLink Server to
establish an ODBC connection. The complete value SequeLink
Server will pass to the ODBC SQLDriverConnect call is
DB=Database Name;UID=Database user
name;PWD=Database password;settings where
database name, database user, database password,
and settings are the values that are entered in the
corresponding SequeLink CAT fields.
For more information about connecting using the SequeLink

ODBC Socket, see “Connecting With the SequeLink ODBC
Socket” on page 93.

ODBC Text Parameters

ODBC for Text driver, supply the following parameters:

<prompt>

the service name.

on the server that contains the Text files.
OpenIngres Parameters
To use a SequeLink OpenIngres service, supply the following
parameters:

Database Required <name> or <prompt> Database name
Settings Optional <flags> or <prompt> Database flags
Service name: This identifies the OpenINGRES service. The default

is SLIngres. Encryption and compression can be enabled
Database name: This specifies the name of the OpenINGRES

database you want to access.
Database flags: This specifies flags that control OpenINGRES

session behavior. Some flags require the OpenINGRES Knowledge
Management Extension.

Valid flags include:
Empty string The client connects to the database

using the host user name specified at
connect time.
Database user name This name is used to identify the user to
the database. If the host user name is an
Ingres superuser, this user name can be
different from the host user name.
Ingres users can be created and viewed
through the Ingres utility accessdb.
Ingres command-line These flags control the database
flags behavior for each session. Specify the
flag, separated by spaces. Some
examples of valid values include:
■ -uusername will override the host user
name.
■ -Ggroupid specifies the group identifier

for this Ingres session. Use this flag only
if you run the OpenINGRES Knowledge
Management Extension.
■ -Rroleid specifies the role ID for an

application image. You can specify this
flag only if you run the OpenINGRES
Knowledge Management Extension.
For more information about
OpenINGRES flags, refer to your
OpenINGRES documentation.

ORACLE Parameters
To use a SequeLink ORACLE service, supply the following
parameters:

name

<prompt> password

SLOracle. Encryption and compression can be enabled through
the service name.
Database user name/Database password: These are the Oracle

user name and user password required to log on to Oracle. You
also can log on to Oracle with an empty user name and password.
In this case, Oracle will try to connect through an Oracle OPS$
user. Once defined, an Oracle OPS$ user can access Oracle directly
from the operating system, without entering a database user
name and password. For instructions on how to create Oracle
OPS$ users, refer to your Oracle documentation.
Sybase Parameters
To use a SequeLink Sybase service, supply the following
parameters:

<prompt>


User name Required <user> or <prompt> Database user
name
Password Required <password> or Database

<prompt> password
Settings Optional <server name> or Server name
<prompt>

SLSybase. Encryption and compression can be enabled through
the service name.
Database name: This identifies the Sybase database you will

access. If unspecified, the default database will be used.
Database user name/Database password: These are the Sybase

user name and user authorization required to log on to Sybase.
Server name: This identifies the Sybase server name (also known
as DSQUERY). It identifies the name of an entry in the Sybase
interfaces file on the host. Normally, you can leave this field
empty, which causes SequeLink to connect to the default Sybase
instance on the server. If your server is running multiple Sybase
instances, you can specify a value for this field to connect to
another Sybase instance. For more information about DSQUERY,
refer to your Sybase documentation.

Network Parameters
A SequeLink network setting is a collection of settings that
describes the network protocol SequeLink uses to establish access
with the SequeLink service. These settings include a network
type, a server name, a client name, and network settings. This
section lists the network parameters for supported network
types.
Attachmate Parameters
Supply the following parameters to connect using Attachmate:

Host Required <user> or <prompt> Symbolic
destination name
Symbolic destination name: This name is the symbolic destination

name defined in the Side Information configuration. The
maximum length of this name is 8 characters.
Note: The Remote Local logical unit (LU) name and the Mode
name are extracted from the Side Information configuration.
Client Access/400 Parameters

Supply the following parameters to connect using Client
Access/400:

Host Required <host> or <prompt> Host system name
Host system name: This is the name of the AS/400 host to which
you want to connect. If you specify an asterisk (*) for this
parameter, the default system is used.

IBM Personal Communications

Supply the following parameters to connect using IBM Personal
Communications:

Host Required <host> or <prompt> Symbolic
destination name
Symbolic destination name: This is the symbolic destination

name defined in the Side Information configuration. The
maximum length of this name is 8 characters.
name are taken from the Side Information configuration.
Microsoft SNA Server Parameters

Supply the following parameters to connect using Microsoft SNA
Server:

destination name
Symbolic destination name: This name is the symbolic

destination name as defined in the Side Information
configuration on the Windows NT server where the Microsoft
SNA Server server component is installed. The maximum length
of this name is 8 characters.

Rumba Parameters
Supply the following parameters to connect using Rumba:

destination name
Symbolic destination name: This is the symbolic destination name

as defined in the Side Information configuration. The maximum
length of this name is 8 characters.
TCP/IP Parameters
Supply the following parameters to connect using TCP/IP:

Host Required <host> or <prompt> Host node
Host node: This is the IP address or name of the host to which you
want to connect.

Connecting With the SequeLink ODBC Socket 93
Connecting With the SequeLink ODBC Socket

Using the SequeLink ODBC Socket and an ODBC driver on the
server, you can access a variety of data and databases, including
nonrelational data and databases. To connect using the
SequeLink ODBC Socket, select the appropriate service type
when you configure your data source.
Table 2-2 shows the predefined service types for the SequeLink
ODBC Socket that you can select using the SequeLink CAT.
Table 2-2. Predefined Service Types for the SequeLink ODBC Socket and an ODBC
Driver on the Server
ODBC Driver Service Type

MERANT Connect ODBC for Btrieve Driver ODBC Btrieve
MERANT Connect ODBC for dBASE Driver ODBC dBase
MERANT Connect ODBC for Excel Driver ODBC Excel
MERANT Connect ODBC for FoxPro Driver ODBC FoxPro
Microsoft ODBC Driver for Microsoft Access ODBC MS Access
MERANT Connect ODBC for Paradox Driver ODBC Paradox
MERANT Connect ODBC for Text Driver ODBC Text
Note: MERANT Connect ODBC is the updated product name for the INTERSOLV ODBC Driver
Pack.
For example, to connect to a Microsoft Access database using the

SequeLink ODBC Socket, select ODBC MS Access in the Service
Type field when configuring a SequeLink data source with the
SequeLink CAT.
To connect with other ODBC drivers using the SequeLink ODBC

Socket:
1 On the server, create an ODBC system data source for that
data store using the ODBC Administrator. For information

about defining a system data source, refer to your ODBC

driver documentation.
2 On the client, create a SequeLink data source. Select ODBC

Socket in the Service Type field when configuring a SequeLink
data source with the SequeLink CAT. Also, specify the name of
the ODBC system data source defined on the server in the
Settings field.
For information about specifying ODBC data sources for a specific

ODBC driver on the server, refer to the documentation supplied
with the driver product.
Figure 2-1 shows an example of configuring a SequeLink data

source for a Progress database on Windows NT.
Figure 2-1. Creating SequeLink Data Sources for the SequeLink ODBC Socket
Progress Database
System Data Progress Driver

Source=Sales
Database
ODBC Driver Manager
SequeLink ODBC Socket
SequeLink
Client Server
Create a system data source with the

ODBC Administrator on the server

Using the SequeLink Data Source SyncTool 95
Using the SequeLink Data Source SyncTool

The SequeLink Data Source SyncTool allows you to export ODBC
and OLE DB data source definitions that use the SequeLink ODBC
Driver or SequeLink OLE DB Provider, to data source files and
distribute them to multiple end users. The data source
definitions of the associated SequeLink data sources are
exported to the data source file automatically.
The SequeLink Data Source SyncTool provides two user

implementations: one for the SequeLink Administrator and
another for the end user. The SequeLink Data Source SyncTool
Administrator can import and export data sources; this tool
should be made available to the SequeLink administrator only.
The SequeLink Data Source SyncTool can import data sources

only and should be installed on every client. The procedure for
importing data sources is the same, regardless of whether the
administrator’s or end user’s version of the SequeLink Data
Source SyncTool is used.
The window title bar indicates which operation, export or

import, you or the end user is performing. Also, context-sensitive
online help is available on Windows 9x and Windows NT by
clicking ? on the title bar; then, clicking the area about which
you want more information.
For information about using the SequeLink Data Source Synctool

with:
■ ODBC data sources, see the following section “With ODBC

Data Sources” on page 96
■ OLE DB data sources, see “With OLE DB Data Sources” on

page 101

With ODBC Data Sources

Use the SequeLink ODBC Data Source Synctool to sychronize
ODBC data sources.
Exporting ODBC Data Sources

1 From the SequeLink program manager group, double-click
the ODBC Data Source SyncTool Administrator icon. The
SequeLink ODBC Data Source SyncTool Administrator
Welcome window appears.
2 Select the Manage Data Sources Files radio button, and

click Next.
3 Select a data source file from the Filename list box, or click
Browse to find a data source file not listed. The default
extension for data source files is .DSF.
To create a new data source file, Click New.
4 Indicate whether you want to export your User or System

data sources to the data source file you selected, and
click Next.
5 Select the data sources you want to export to the data

source file.
You cannot export grayed-out data sources, which means that

the data source is incomplete or the data source is used with
the MERANT 2.12 32-bit SequeLink ODBC Driver.
6 Using the following symbols, verify the appropriate actions to

be performed on the data sources in the data source file:
The data source will remain unchanged.

The data source will be added to the data source file.

The data source will be deleted from the data source

file.
The data source will be updated in the data source
file.
7 Select the option that will determine how the end user will
be able to import the data sources you just exported to the
data source file:
■ Suggest SequeLink User DSN. When imported, the

SequeLink ODBC Data Source SyncTool will suggest to the
end user that these data sources be imported as User data
sources, but will allow them to be imported as User or
System data sources.
■ Suggest SequeLink System DSN. When imported, the

SequeLink ODBC Data Source SyncTool will suggest to the
end user that these data sources be imported as System
data sources, but will allow them to be imported as User
or System data sources.
■ Force SequeLink User DSN. When imported, the

SequeLink ODBC Data Source SyncTool will allow these
data sources to be imported as User data sources only.
■ Force SequeLink System DSN. When imported, the

SequeLink ODBC Data Source SyncTool will allow these
data sources to be imported as System data sources only.
Then, click Next.
8 Type a description for the data source file. This description

will appear when the end user selects this file for importing.
9 Click Next.
10 Select the mode with which the end user can import these
data sources:
■ Interactive mode allows the user to select which of the

data sources in this file will be imported. This mode is not

supported by the Quick Install feature. The Quick Install

feature supports only data source files created with the
Merge or Overwrite options.
For more information about creating Quick Install images

on Windows 95 or Windows NT, see “Quick Install Images”
on page 367. For more information about creating Quick
Install images on Windows 3.1x, see “Quick Install Images”
on page 378.
■ Merge mode adds or updates all the data sources in the
data source file without deleting other SequeLink data
sources for the SequeLink ODBC Driver.
■ Overwrite mode adds or updates all the data sources in

the data source file and deletes other SequeLink data
sources for the SequeLink ODBC Driver.
11 Click Next.
12 Click Finish to quit.
Importing ODBC Data Sources

The SequeLink administrator and end user use a slightly different
implementation of the SequeLink ODBC Data Source SyncTool to
import ODBC data source definitions.

the appropriate ODBC SyncTool icon. The Welcome window
appears.
2 Select the Import radio button, and click Next.
Note: If using the SequeLink ODBC Data Source SyncTool

Administrator, you would select the Import Data Sources
radio button, and click Next.
extension for data source files is .DSF.

4 Indicate whether you want to import the data sources in the

data source file you just selected as User or System data
sources, and click Next.
5 Verify that the appropriate actions will be performed on the

data sources on your local machine. Depending on the
import mode that was set when the data source file was
exported, you may see the following symbols:

The data source will be added to your local machine.
The data source will be deleted from your
local machine.
The data source will be updated to your local machine.
Note: If the data source is grayed out, that data source is

incomplete or is used with the MERANT 2.12 32-bit
SequeLink ODBC Driver. In this case, the data source will
remain unchanged.
6 Click Next.
Synchronizing ODBC 3.0 File Data Sources

With ODBC 3.0, you can define file data sources. File data source
attributes are stored in a file that can be placed on a file server
and can be made available to any user who can access it.
When you create an ODBC file data source for the SequeLink
ODBC driver, the file data source references a SequeLink data
source. The SequeLink data source attributes are stored in the
end user’s local registry. To use the ODBC file data source, the
end user must have the SequeLink data source defined locally.
You can export the associated SequeLink data source by first

creating a dummy ODBC data source which uses the SequeLink
data source used by the ODBC file data source. When you export

and import the dummy ODBC data source, the data source
definitions of the associated SequeLink data source are exported
also and are placed in the local registry of the end user. The end
user can then use the ODBC file data source on the file server.
Using the SyncTool with Different Versions of

the SequeLink ODBC Driver
On Windows 9x and Windows NT, the SequeLink ODBC Data
Source SyncTool can synchronize data sources only for the
MERANT 3.10 32-bit SequeLink ODBC Driver. You can use the
ODBC Administrator to check the version of the driver used for a
data source.
On Windows 9x and Windows NT platforms, data sources for the

MERANT 2.12 32-bit SequeLink ODBC Driver cannot be imported
or exported by the SequeLink 4.5 ODBC Data Source SyncTool. To
export or import data sources for the SequeLink ODBC 2.12
Driver, use a previous release of the SequeLink Data Source
SyncTool or upgrade your data source files to be ODBC 3.0-
compliant.
To upgrade a data source file that was created for the MERANT
2.12 32-bit SequeLink ODBC Driver to an ODBC 3.0-compliant
data source file for the MERANT 3.10 SequeLink ODBC Driver, you
can use the SequeLink 4.5 ODBC Data Source SyncTool
Administrator.
To upgrade a data source file to an ODBC 3.0-compliant data

source file:
1 Start the SequeLink ODBC Data Source SyncTool
Administrator.
2 Select the Manage Data Sources Files radio button from the
Welcome window.
3 Select the data source file that contains your 2.12 data
sources; then, click Next.

4 On the next window, you are prompted to upgrade the data

source file. Click Yes.
All data sources in the data source file are now configured to use
the SequeLink ODBC 3.0 Driver.
With OLE DB Data Sources

Use the SequeLink OLE DB Data Source Synctool to synchronize
OLE DB data sources.
Exporting OLE DB Data Sources

the OLE DB Data Source SyncTool Administrator icon. The
SequeLink OLE DB Data Source SyncTool Administrator
Welcome window appears.
2 Select the Manage Data Sources Files radio button, and

click Next.
extension for data source files is .OSF.
To create a new data source file, Click New.
4 Select the data sources you want to export to the data

source file.
You cannot export grayed-out data sources, which means

that the data source is incomplete.

5 Using the following symbols, verify the appropriate actions to

be performed on the data sources in the data source file:

The data source will be added to the data source file.
The data source will be deleted from the data source
file.
The data source will be updated in the data source
file.
6 Type a description for the data source file. This description

will appear when the end user selects this file for importing.
7 Click Next.
8 Select the mode with which the end user can import these
data sources:
■ Interactive mode allows the user to select which of the

data sources in this file will be imported. This mode is not
supported by the Quick Install feature. The Quick Install
feature supports only data source files created with the
Merge or Overwrite options.
For more information about creating Quick Install images

for SequeLink OLE DB Edition Client, see “Quick Install
Images” on page 399.
■ Merge mode adds or updates all the data sources in the
data source file without deleting other SequeLink data
sources for the SequeLink OLE DB Provider.
■ Overwrite mode adds or updates all the data sources in

the data source file and deletes other SequeLink data
sources for the SequeLink OLE DB Provider.
9 Click Next.

Importing OLE DB Data Sources

The SequeLink administrator and end user use a slightly
different implementation of the SequeLink OLE DB Data Source
SyncTool to import OLE DB data source definitions.

the appropriate OLE DB SyncTool icon. The Welcome window
appears.
2 Select the Import radio button, and click Next.
Note: If using the SequeLink OLE DB Data Source SyncTool

Administrator, you would select the Import Data Sources
radio button, and click Next.
extension for data source files is .OSF.
4 Verify that the appropriate actions will be performed on the

data sources on your local machine. Depending on the
import mode that was set when the data source file was
exported, you may see the following symbols:

The data source will be added to your local machine.
The data source will be deleted from your
local machine.
The data source will be updated to your local machine.
Note: If the data source is grayed out, that data source is

incomplete. In this case, the data source will remain
unchanged.
Click Finish to quit.


105

This part contains the following chapters:
■ Chapter 3, “SequeLink and Your Network” introduces and

explains some concepts that you need to understand to plan
and administer SequeLink and your network.
■ Chapter 4, “Configuring Your SNA Network for SequeLink”

describes how to configure your SNA network for SequeLink.

106 Part 2: Network Considerations

107
3 SequeLink and Your Network
This chapter describes concepts that you need to understand to

plan and administer SequeLink and your network.
TCP Port Numbers

With TCP/IP support, each SequeLink Server service is assigned a
unique TCP port number which is used at connection. On
Windows NT, OS/390, and AS/400 servers, a listener monitors the
TCP port for each service. A listener is a functional application
component which monitors, or listens, for incoming connection
requests. When a connection request is received on a particular
service’s TCP port, the listener spawns the corresponding service
program and passes the connection to it. On OS/390, this listener
is called the TCP/IP Network Interface Manager (NIM). On UNIX
servers, SequeLink services are serviced by the UNIX Internet
daemon, inetd.
The TCP/IP network stack on the client uses the TCP port number
to make a connection. In the SequeLink data source definition
on the client, you must specify the port number as the service
name. For more information about specifying service names, see
“Using the SequeLink CAT” on page 52. Alternatively, you can
specify a symbolic name for the service name. The SequeLink
client will look up the value of the TCP port for this name and
make the correct substitution.

108 Chapter 3 SequeLink and Your Network
Table 3-1 shows the default symbolic names and TCP port
numbers for SequeLink Server services. During installation, these
values are used. Unless the default TCP port number conflicts
with a TCP port already being used, no further configuration is
required.
Table 3-1. Default Symbolic Names and TCP Port Numbers for
SequeLink Server Services
Symbolic Name Service Type TCP port

SQLNKALL DB2 on AS/400 4001
SQLNKNONE DB2 on AS/400 4002
SLOracle Oracle 4003
SLInformix Informix 4004
SLSybase Sybase 4005
SLSQLServer SQL Server 4006
SLDB2 DB2 V5 4007
SLDB2 DB2 on NT 4007
OS/390DB2 DB2 for OS/390 4007
SLIngres OpenINGRES 4010
SLSocket ODBC Socket 4011
For platform-specific information about changing port numbers,

see the following chapters in the appropriate server and client
administration sections:
SequeLink Server

APPC Support in a SNA Network 109

and Windows NT”

Windows 3.1”

■ Chapter 14, “SequeLink OLE DB Edition Client for
Windows 9x and Windows NT”
APPC Support in a SNA Network

System Network Architecture (SNA) is the network environment
traditionally provided by OS/390 mainframes and AS/400 hosts.
SNA networks provide various communication services, such as
terminal emulation and printer sharing. Also, communication in
a peer-to-peer fashion is offered through Advanced
Program-to-Program Communication (APPC).
SNA networks are statically defined, meaning that an

application on one machine can communicate with an
application on another machine only when an explicit
communication path is defined in advance. Corresponding
definitions must exist on both machines. These definitions
identify the machines on the SNA network, the communication
path between the machines, and the logical characteristics of
the conversation.
Different APPC implementations provide their own

configuration mechanism and use different terminology for the

same concepts. Table 3-2 provides an overview of the

terminology used on OS/390, AS/400, and end-user workstations.
Table 3-2. Terminology Overview (OS/390, AS/400, End-User Workstations)
Description OS/390 AS/400 Workstation

Machine identification Network Control Network attributes Node definition and
Program (NCP) service definition
definitions
Physical communication Physical Unit (PU) Line/Controller Connections
attributes
Logical communication Logical Unit (LU) Controller/Device Logical Unit (LU)
attributes
Communication modes LOGMODE Mode Mode
Local and remote LUs and APPC modes are used to define the
logical characteristics of the conversation. The local LU contains
information about the local side of the conversation, and the
remote LU contains information about the target partner’s side.
A fully defined LU is identified by a combination of the network

ID and LU name. The local and remote LUs defined on the local
machine are identified by an alias name. All local and remote
APPC definitions must match. For example, in an AS/400
environment, the same LU definition must exist on your local
workstation and AS/400 server.
In a SNA network, each workstation is defined as an independent

or dependent LU, according to the capabilities of the gateway or
controller to which the workstation is attached. To make
multiple, simultaneous connections from a workstation to a
remote AS/400 or OS/390 machine, the services of an
independent LU are required.
Note: Some ODBC-enabled applications may open simultaneous

connections, although the application may be using only one
ODBC data source.

APPC Support in a SNA Network 111
To establish a session with another application, an application

specifies its local LU, the target remote LU, an APPC mode name,
and the name of the remote application (transaction program
name). If communication has any security requirements that
must be met, the application also may need to supply a valid
user name and password.
Applications often use the same combinations of LU definitions

and APPC modes. For this reason, APPC network stacks provide
an alternative interface called CPIC. Using CPIC, specific local LUs,
remote LUs, and APPC modes can be grouped together and
identified with an alias. These aliases are also called Side
Informations. IBM also provides a SNA product for connecting
Windows workstations to AS/400 hosts called Client Access/400.
This product uses its own addressing mechanism.
For more information about configuring your SNA network for

SequeLink, see Chapter 4, “Configuring Your SNA Network for
SequeLink.”

Cross-Platform Configuration
Table 3-3 on page 113 summarizes the possible cross-platform
connections between SequeLink Server and, SequeLink ODBC
Edition Client, and SequeLink OLE DB Edition Client, listing
network protocol and configuration exceptions, if any, for each
connection listed.
Unless specified otherwise, the following configuration notes

apply for each connection listed:
■ You can perform all configuration during installation and by

using the SequeLink CAT.
■ The client and server must be on the same network. For

example, if SequeLink ODBC Edition for Windows 9x will be
connecting to SequeLink Server for UNIX using TCP/IP, the
Windows 9x client and UNIX server must be on the same
TCP/IP network.
■ If the default TCP port number conflicts with one being used
by another service, you will need to change the port number
to an unused port number after installation.
For platform-specific information about changing port numbers,

see the following chapters in the appropriate server and client
administration sections:
SequeLink Server

Cross-Platform Configuration 113

and Windows NT”

Windows 3.1”

For software requirements, refer to the SequeLink Server

Installation Guide, SequeLink ODBC Edition Client Installation
Guide, and SequeLink OLE DB Edition Client Installation Guide.
Table 3-3. Cross-Platform Connection Configuration Summary
SequeLink SequeLink
SequeLink ODBC Edition OLE DB Network
Server Client Edition Protocol Configuration
Client Notes
Windows NT Windows 3.1 TCP/IP
Windows NT or Windows NT or TCP/IP
Windows 9x Windows 9x
Macintosh (PPC) TCP/IP
UNIX TCP/IP
UNIX Windows 3.1 TCP/IP
UNIX TCP/IP

Table 3-3. Cross-Platform Connection Configuration Summary (cont.)
SequeLink SequeLink
Client Notes
AS/400 Windows 3.1 TCP/IP
APPC Additional SNA
(Attachmate) configuration is
required on the client
and server.
APPC (Rumba) Additional SNA
configuration is
and server.
APPC Additional SNA
(Client configuration is
Access/400) required on the client
and server.
Protocol Hopping Additional SNA
(Microsoft SNA configuration is
Server) required on the
Microsoft SNA Server
server and AS/400.
Windows NT or Windows NT or APPC Additional SNA
Windows 95 Windows 95 (Attachmate) configuration is
and server.
Windows 95 Windows 95 (IBM Personal configuration is
Communications) required on the client
and server.

Cross-Platform Configuration 115
SequeLink SequeLink
Client Notes
Windows NT or Windows NT or APPC (Rumba) Additional SNA
Windows 95 Windows 95 configuration is
and server.
Windows NT or Windows NT or Protocol Hopping Additional SNA
Windows 9x Windows 9x (Microsoft SNA configuration is
server and AS/400.
UNIX TCP/IP
OS/390 Windows 3.1 TCP/IP
APPC Additional SNA
(Attachmate) configuration is
and server.
APPC (Rumba) Additional SNA
configuration is
and server.
Protocol Hopping Additional SNA
(Microsoft SNA configuration is
server and OS/390
server.

SequeLink SequeLink
Client Notes
Windows 95 Windows 95 (Attachmate) configuration is
and server.
Windows 95 Windows 95 (IBM Personal configuration is
Communications) required on the client
and server.
Windows NT or Windows NT or APPC (Rumba) Additional SNA
Windows 95 Windows 95 configuration is
and server.
Windows NT or Windows NT or Protocol Hopping Additional SNA
Windows 9x Windows 9x (Microsoft SNA configuration is
server and OS/390
server.
UNIX TCP/IP

Data Transmission 117
Data Transmission
Data security and system performance are valid concerns for
many organizations. SequeLink provides the following data
security features:
■ User authentication
■ SequeLink Server service access limits
■ Data encryption
Additionally, the data compression feature, which reduces the

size of data being transported, may improve system
performance.
User Authentication
When connecting to a server, the client provides certain
information for user authentication. This information varies,
depending on the server to which the client is connecting. For
example, the server may require a user ID and password. Using
the server’s native security environment, SequeLink checks this
information, and, if verified, starts the requested service.
Windows NT
You can configure the level of user authentication that will be
performed to use both server and database user authentication,
or to use database user authentication only. If you do not want
the additional level of security provided by using both
mechanisms, you can rely exclusively on database user
authentication for the following SequeLink Server services:
■ DB2 Universal Database
■ Informix

■ Microsoft SQL Server (when user authentication is standard or

mixed). For more information about Microsoft SQL Server
database user authentication, see “Microsoft SQL Server
Database User Authentication” on page 119.
■ Oracle (when no OPS$ accounts are used)
■ Sybase
Generally, using database user authentication as the exclusive

security mechanism allows for faster connections without
sacrificing data security. You will need to use server user
authentication for all other SequeLink Server services, because
these databases use the underlying security mechanism of the
server’s operating system.
You also can specify a default host user and password to be used,
regardless of the user name and password specified in the
connection parameters in the SequeLink CAT data source
definition. For information about defining user authentication
levels for Windows NT, see “Setting the User Authentication
Level” on page 248.
When a connection is refused because of an invalid user name

and password combination, an error message is returned to the
client application with details about why the connection was
refused. Alternatively, you can specify that the server return a
basic error message, with minimal details, to the client so that an
unauthorized user cannot receive further information about your
security system. In both cases, a message is sent to the Event log
facility with details about why the connection was refused. For
instructions on setting the connection refusal message details,
see “Setting Connection Refusal Message Details” on page 249.
Users are identified by a unique domain name and user name

combination with the following format:
DOMAIN_NAME\user_name

For example, the users HOT\pepper and MILD\pepper are unique

combinations that can represent users who have different user
authority on the same server.
If a domain name is not specified at connection, the server’s local

domain will be used. You can specify a default domain name in
the service configuration resource. For information about
specifying default domain names for Windows NT, see “Setting a
Default Domain Name” on page 250.
Note: For local users of the Windows NT server on which

SequeLink Server is installed, explicitly specify the local domain.
This will speed user authentication when your Windows NT
server is not a primary domain controller.
Microsoft SQL Server Database User Authentication

Microsoft SQL Server can be configured to use the following
authentication types:
■ Standard. A user ID and password are required to log on

SQL Server.
■ Mixed. When a user ID and password is not supplied, the

user ID under which the user is logged on the Windows NT
network is used to authenticate the user to SQL Server.
■ Integrated. The user ID under the user is logged on the

Windows NT network is used to authenticate the user to
SQL Server.

Table 3-4 shows the results of different combinations of Microsoft

SQL Server and SequeLink settings on user authentication.
Table 3-4. User Authentication Combinations of Microsoft SQL Server and SequeLink
Settings
SequeLink Server
SequeLink SequeLink CAT SequeLink CAT Service
SQL Server Service Data Source: Data Source: Configuration:
Server Authentication Host User ID/ Service User ID/ Host User ID/
Security Level Password Password Password
Standard CLIENT Required. When supplied, Ignored.
The host user ID the service user ID
and password are and password are
verified, and if used to log on
correct, the SQL Server; when
service thread not supplied, SQL
impersonates this Server will return
user. an error.
SERVER Ignored. When supplied, The host user ID
the service user ID and password are
and password are verified, and if
used to log on correct, the
SQL Server; when service thread
not supplied, SQL impersonates this
Server will return user.
an error.
NONE Ignored. When supplied, Ignored.
the service user ID
and password are
used to log on
SQL Server; when
not supplied, SQL
Server will return
an error.

Settings (cont.)
SequeLink Server
Mixed CLIENT Required. When supplied, Ignored.
The host user ID the service user ID
and password are and password are
verified, and if used to log on
correct, the SQL Server.
service thread
impersonates this
user; when not
supplied, the
service user ID
and password are
used to log on
SQL Server
implicitly.
SERVER Ignored. When supplied, The host user ID
the service user ID and password are
and password are verified, and if
used to log on correct, the
SQL Server. service thread
impersonates this
user; when not
supplied, the
service user ID
and password are
used to log on
SQL Server
implicitly.

Settings (cont.)
SequeLink Server
NONE Ignored. When supplied, Ignored.
the service user ID
and password are
used to log on
SQL Server; when
not supplied, the
account under
which the
SequeLink service
is running
(default is the
local system
account) is used to
log on SQL Server.
Integrated CLIENT Required. Ignored. Ignored.
The host user ID
and password are
verified, and if
correct, the
service thread
impersonates this
user; is used to log
on SQL Server
implicitly.

Settings (cont.)
SequeLink Server
SERVER Ignored. Ignored. The host user ID
and password are
verified, and if
correct, the
service thread
impersonates this
user; is used to log
on SQL Server
implicitly.
NONE Ignored. Ignored. The account
under which the
SequeLink service
is running
(default is the
local system
account) is used to
log on SQL Server.
UNIX
On UNIX servers, SequeLink supports all features offered by your
UNIX operating system, including shadow passwords, password
aging, and administratively locked accounts.
You can configure the level of user authentication that will be

performed to use both server and database user authentication,
or to use database user authentication only. If you do not want
the additional level of security provided by using both

mechanisms, you can rely exclusively on database user

authentication for the following SequeLink Server services:
■ DB2 Universal Database

■ Oracle (only when no OPS$ accounts are used)
■ Sybase
Generally, using database user authentication as the exclusive

security mechanism allows for faster connections without
sacrificing data security. You will need to use server user
authentication for all other SequeLink Server services, because
these databases use the underlying security mechanism of the
server’s operating system.
You also can specify a default host user to be used, regardless of

the user name specified in the connection parameters in the
SequeLink CAT data source definition. For information about
defining user authentication levels for UNIX, see “Setting the
User Authentication Level” on page 268.

refused. Alternatively, you can specify that the server return a
basic error message, with minimal details, to the client so that an
unauthorized user cannot receive further information about your
security system. In both cases, a message is sent to the syslog
facility with details about why the connection was refused.
OS/390 OS/390
On OS/390, SequeLink supports the following security
environments:
■ IBM RACF, V1R8 or higher

■ Computer Associates CA-ACF2, V6.0 or higher
■ Computer Associates CA-TOP SECRET

Limiting Access to SequeLink Server

AS/400 OS/390 Services
You can limit access to SequeLink Server services to specific
applications. For example, you may want to restrict access to a
SequeLink Server Oracle service to applications using the Oracle
database and exclude all other applications. This prevents users
who do not require access to the database from browsing it with
commonly available query tools.
You limit access to applications by identifying your applications

with an alphanumeric string, called an application ID, and by
adding this string to the appropriate service configuration
resource at the server. If an application does not identify itself to
the server with the correct application ID, all SQL statements will
fail.
For instructions on limiting access to SequeLink Server services,

see one of the following sections:
■ Windows NT, see “Specifying the Authorized Applications

List” on page 250.
■ UNIX, see “Specifying the Authorized Applications List” on

page 270.
■ AS/400, see “Specifying the Authorized Applications List” on

page 283.
■ OS/390, see “Specifying the Authorized Applications List” on

page 338.
The method that client applications use to identify themselves to

the server depends on whether the client uses the SequeLink
ODBC Driver, SequeLink OLE DB Provider, or SequeLink JDBC
Driver.

Using Application IDs with the SequeLink ODBC

Driver
The client application can identify itself to the server in either of
the following ways:
■ Using the SequeLink ODBC Driver call, SQLSetConnectOption.

Immediately after each call to SQLConnect or
SQLDriverConnect that connects to the SequeLink ODBC
Driver, call SQLSetConnectOption as shown:
short res_code;
res_code=SQLSetConnectOption(hdbc, 1053,
“myAppId”)
where “myAppId” is the application ID.
The SQLSetConnectOption is defined in SQL.H. If an invalid

application ID is specified, the SQLSetConnectOption fails and
all subsequent SQL statements will fail.
■ Specifying the application ID in the ODBC connect string that

is passed to SQLDriverConnect. For example:
....;APPID=myOrderEntryApp;
or
....;ApplicationID=myOrderEntryapp;
where myOrderEntryApp is the application ID.
For more information about the SQLDriverConnect function,

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.

Using Application IDs with the SequeLink

OLE DB Provider
The client application must specify a key-value pair:
APPID=...; or ApplicationID=...;
in the DBPRO_INIT_PROVIDERSTRING property of the

DBPROPSET_DBINITALL property set.
Using Application IDs with the SequeLink

JDBC Driver
After establishing a connection with the SequeLink JDBC Driver,
immediately invoke setApplicationId. The setApplicationId
method is defined on the interface
intersolv.jdbc.SlExtensionInterface, and uses the following
method prototype:
public void setApplicationId(String s) throws SQLException
You can set the application ID as shown in the following code

example:
import java.sql.*;
import intersolv.jdbc.SlExtensionInterface;
...
Connection con = DriverManager.getConnection(...);
String appId = "...your application id...";

if (con instanceof SlExtensionInterface)
{
SlExtensionInterface slCon = (SlExtensionInterface)con;
slCon.setApplicationId(appId );
}

Data Encryption
With SequeLink 3.5 and higher, data can be encrypted for
transmission using byte swapping. Byte swapping means that
bytes of data are randomly swapped to scramble data. Different
encoded mappings are used for data sent from the client to the
server and data sent from the server to the client. These encoded
mappings are changed dynamically as the session proceeds.
To use encryption, precede the SequeLink service name in the

SequeLink data source with the name of the byteswap encryption
module, byteswap, enclosed within asterisks (*):
*byteswap*service_name
For example, to connect to an Oracle service named “SLOracle”

using encryption, you would specify:
*byteswap*SLOracle
The server must be running SequeLink Server 3.5 or higher.
Data Compression
SequeLink 3.5 and higher supports compression using the
Huffman coding technique, which uses a static weight table to
assign encoded bit strings based on the contents of the
SequeLink service protocol messages and the character type of
the data. The goal is to reduce the size of the data being
transmitted and improve system performance.
To use compression, precede the SequeLink service name in the

SequeLink data source with the name of the Huffman
compression module, huffman, enclosed within pound symbols:
#huffman#service_name


using Huffman compression, you would specify:
#huffman#SLOracle
The server must be running SequeLink Server 3.5 or higher.
Note: Although compression can improve system performance,

in some situations, the additional computations involved create
enough overhead to negate any gain in system performance.
Generally, on high-speed LANs, compression can degrade the
system performance of the entire transport process; on WANs, it
often results in less network traffic and more efficient use of the
underlying data network.
Using Encryption and Compression

Together
Compression and encryption can be invoked simultaneously by
using the following format in the SequeLink data source:
*byteswap*#huffman#service_name

using byteswap encryption and Huffman compression, specify:
*byteswap*#huffman#SLOracle

Using SequeLink with the Internet

Today, many organizations use an internal network of
workstations, routers, and gateways to transport data for a
variety of business applications. These networks, or intranets, are
interconnected by a larger collection of networks physically
connected by Internet Protocol (IP) gateways called the Internet.
At the IP level, the Internet provides routing for TCP/IP protocols.

It also provides other services, such as File Transfer Protocol (FTP).
Today, one of the most popular services provided by the Internet
is the World Wide Web (WWW), which uses the Hypertext
Transfer Protocol (HTTP).
Because SequeLink supports TCP/IP and uses an underlying

transport network to send SequeLink Service Protocol (SSP)
messages, the Internet can function as the underlying network
for communication between SequeLink clients and servers. For
example, with SequeLink Java Edition, a client can use a Java
application or applet to access a database over the Internet.
Using Firewalls with SequeLink

Increasingly, firewalls are being used to protect data from
malicious or inadvertent intrusion over the Internet. Firewalls run
on isolated systems and control the traffic between the Internet
and an internal network. This control can be applied at the
network-protocol level (IP, UDP, or TCP) or application-protocol
level.
At the network-protocol level, the control method commonly is

referred to as a packet filter. At the application-protocol level,
the control method uses a proxy to inspect the data and
commands in every message and requires knowledge of the
protocol used by the application. A dedicated proxy agent does
not exist for SequeLink; however, a generic proxy agent can be

Using SequeLink with the Internet 131
used with SequeLink to connect internal and external TCP ports

without inspecting the contents of messages.
You also can use a firewall to limit access to servers. When a

client or server is running at a site protected by a firewall, it is
said to be running behind a firewall. How you use firewalls with
SequeLink depends on your business needs. For example, if your
company employs staff at various locations throughout the
world who need to access data stored at a centralized site, you
may want to provide your SequeLink clients with direct access to
the Internet through their local Internet service provider and
protect the server by a firewall, as shown in Figure 3-1.
Figure 3-1. Example: SequeLink over the Internet
Firewall
Internet
SequeLink Client
Server Internet
Service
Provider
Note: This configuration also makes sense when some locations

or departments within an organization on the same intranet
require a higher level of security than others.
Firewall configuration depends on the type of firewall used:
■ Transparent Firewalls. These firewalls check the source and

destination addresses of packets and determine whether the
communication is allowed based on a defined table of
allowed communications. Clients specify a target address
with each connection request. Because the SequeLink client

specifies a real, unique TCP port number and IP address

combination for a particular SequeLink service, the firewall
administrator must define a rule to allow access to or from
specific sets of IP addresses.
■ Non-Transparent Firewalls. Clients specify a locally defined

port number and the IP address of the firewall with each
connection request. The firewall substitutes this local address
with the real destination address and forwards the packet.
The firewall administrator must define a local TCP port for
every external SequeLink service a user might want to access,
but this type of firewall provides a greater degree of security
than transparent firewalls
Other Security Considerations

Firewalls using a generic proxy limit access to a particular service
by restricting access to a defined set of client IP addresses; they
do not restrict access at the application level. For servers, you can
use the inherent security mechanisms of your database system to
limit user access. Even so, you must restrict access to user ID and
password combinations and treat them confidentially.
SequeLink allows you to encrypt data (user ID and password

information, for example), preventing data from being
transported as readable text. For more information about
encryption, refer to “Data Encryption” on page 128.
System Performance Considerations

Because network traffic on the Internet can sometimes cause
slow response times, you may want to use a value higher than the
default of 10 seconds for the SequeLink connection time-out. For

Using SequeLink with the Internet 133
more information about changing connection time-outs, see the

following chapters:

and Windows NT”

Windows 3.1”

Also, you can use compression to reduce the size of data that is
transported over the Internet, resulting in quicker response
times. For more information about using compression, see “Data
Compression” on page 128.


135
4 Configuring Your SNA

Network for SequeLink
This chapter describes how to configure your SNA network for

SequeLink. It contains a section for AS/400 and OS/390, and a
section for each supported APPC implementation. Consult your
SNA administrator for site-specific, SNA naming conventions,
and configuration guidelines.
AS/400
AS/400 Network settings include:
■ Line descriptions
■ Mode descriptions
■ Controller descriptions
■ Device descriptions
Note: To display your current settings, use the DSPNETA

command.
During installation, new AS/400 network descriptions are

created or existing ones are modified to accommodate
SequeLink. For information about creating new AS/400 network
descriptions or modifying existing descriptions for SequeLink,
refer to the SequeLink Server Installation Guide.
Note: If you change any SNA attributes on your AS/400, you may
need to reconfigure all machines that communicate with that
AS/400 server on the SNA network. In most environments, SNA
networks are centrally configured and administered.

136 Chapter 4 Configuring Your SNA Network for SequeLink
Table 4-1 lists the network parameters that can be defined for the
AS/400, where you define them, their names, and their locations
on the client or server.
Table 4-1. Network Parameters for AS/400
Parameter Defined on Name Location

Server network address Server ADPTADR CRTLINTRN
Server node ID Server EXCHID CRTLINTRN
Client network address Client ADPTADR CRTCTLAPPC
Server network name Server N/A From DSPNET
Server control point Server N/A From DSPNETA
Client network name Client RMTNETID CRTCTLAPPC
Client control point name Client RMTCPNAME CRTCTLAPPC
Server LU network ID Server N/A From DSPNETA
Server LU name Server LCLLOCNAME CRTDEVAPPC
Client LU network ID Client RMTNETID CRTDEVAPPC
Client LU name Client RMTLOCNAME CRTDEVAPPC
APPC mode name Server & Client MODD CRTMODD
Maximum number of APPC Server & Client MAXSSN CRTMODD
sessions
Send pacing limit on client/ Server/Client INPACING CRTMODD
receive pacing limit on server
Receive pacing limit on client/ Server/Client OUTPACING CRTMODD
send pacing limit on server
Note: The same value must be used on your server and client for the RMTNETID,
RMTCPNAME, and ADPTADR parameters.

OS/390 137
OS/390
OS/390 On OS/390, APPC communication is provided through VTAM.
Table 4-2 shows the network parameters that can be defined for
OS/390, where you define them, their names, and their locations
Table 4-2. Network Parameters for OS/390
Link Parameter Defined on Name Location

Server network address Server MACADDR NCP gen
Server network name Server NETID VTAM startup
Server control point name Server SSCPNAME VTAM startup
Client network name Client NETID VTAM startup
Client control point name Client PU name PU definition
Server LU name Server APPLID VTAM applid
Client LU network ID Client IDBLK PU definition for this client
Client LU name Client IDNUM PU definition for this client
APPC mode name Server & Client LOGMODE VTAM logmode table
Maximum number of APPC Server & Client N/A VTAM logmode table
sessions
Receive pacing limit on the Server/Client SRCVPAC VTAM logmode table
server/Send pacing limit on
the client
Send pacing limit on the Server/Client SSNDPAC VTAM logmode table
server/Receive pacing limit
on the client

Attachmate (CPIC)
You can configure the APPC connection parameters using the
Node Operator Facility. For information on how to configure
APPC connection parameters using this facility, refer to the online
help provided with the Node Operator Facility. When you define
a local LU, make sure that the “LU in the pool of default LUs”
check box is checked. You do not need to start the node explicitly.
Table 4-3 shows the network parameters that can be defined for
Attachmate, where you define them, their names, and their
locations on the client or server.
Table 4-3. Network Parameters for Attachmate (CPIC)
Link Parameter Defined on Name Location

Server network address Server Destination Address Token Ring Connection
Dialog Box
Server node ID Server Node ID to Receive Token Ring Connection
Dialog Box
Client node ID Client Node ID to Send Token Ring Connection
Dialog Box
Client network name Client Network ID SNA Parameters Dialog
Box
Client control point name Client Control Point Name SNA Parameters Dialog
Box
Server LU network ID Server Full Network Name Configure APPC Remote
(First Part) LU Dialog Box
Server LU name Server Full Network Name Configure APPC Remote
(Second Part) LU Dialog Box
Client LU network ID Client Full Network Name Configure APPC Local LU
(First Part) Dialog Box
Client LU name Client Full Network Name Configure APPC Local LU
(Second Part) Dialog Box

IBM Personal Communications 139
IBM Personal Communications

You can configure the APPC connection parameters using the
SNA Node Operations facility on Windows 95 or Windows NT.
For information about configuring APPC connection parameters
using these facilities, refer to your IBM documentation.
Table 4-4 lists the parameters that can be defined for IBM
Personal Communications, where you define them, their names,
and their locations on the client or server.
Table 4-4. Network Parameters for IBM Personal Communications

Server network address Server Destination Address Configure Connection/
Basic Tab
Client node ID Client Local Node ID Configure Node/Basic Tab
Client network name Client Control Point (CP) Configure Node/Basic Tab
Client control point Client Control Point (CP) Configure Node/Basic Tab
name
Server network name Server Fully qualified CP Configure Partner LU 6.2/
name Basic Tab
Server Control Point Server Fully qualified CP Configure Partner LU 6.2/
name Basic Tab
Server LU name Server Partner LU Name Configure Partner LU 6.2/
Basic Tab
Server LU network ID Server Partner LU Name Configure Partner LU 6.2/
Basic Tab
Client LU name Client Defined implicitly from
Node configuration or in
Configure Local LU 6.2
Client LU Network ID Client Defined implicitly from
Node configuration or in
Configure Local LU 6.2
APPC Mode Name Server & Client Mode name Configure Mode/Basic Tab

Table 4-4. Network Parameters for IBM Personal Communications (cont.)

Maximum number of Server & Client Maximum Configure Mode/
APPC sessions Negotiable session Advanced Tab
limit
Send pacing limit on Server/Client Receive pacing Configure Mode/
the server/Receive window size Advanced Tab
pacing limit on the
client

Microsoft SNA Server 141

When you configure the server component of Microsoft SNA
Server, you can configure your SNA network for SequeLink.
Notes:
■ On Windows NT, you can configure network definitions using

the Microsoft SNA Server Administrator. For information
about using the Microsoft SNA Server Administrator, refer to
your Microsoft SNA Server documentation.
■ Microsoft SNA Server uses the CPIC interface. Make sure you
define the correct CPIC names.
Table 4-4 lists the parameters that can be defined for Microsoft
SNA Server, where you define them, their names, and their
locations on the client or server.
Table 4-5. Network Parameters for Microsoft SNA Server

Server network address Server Remote Network 802.2 Setup Dialog Box
Address
Server node ID Server Remote Node 802.2 Setup Dialog Box
Name: Remote
Node ID
Client network address Client Link Service: Connection Properties
token-ring Dialog Box
address is
extracted from
the link service
definition
Client node ID Client Local Node Name: 802.2 Setup Dialog Box
Local Node ID
Server network name Server Remote Node 802.2 Setup Dialog Box
Name: Network
Name

Table 4-5. Network Parameters for Microsoft SNA Server (cont.)

Server control point Server Remote Node 802.2 Setup Dialog Box
Name: Control
Point Name
Client network name Client SNA Network Server Properties Dialog
Control Point Box
Name: Network
Name
Client control point Client SNA Network Server Properties Dialog
name Control Point Box
Name: Control
Point Name
Server LU network ID Server Network Name APPC Remote LU Properties
Server LU name Server LU Name APPC Remote LU Properties
Client LU network ID Client Network Name APPC LU Properties
Client LU name Client LU Name APPC LU Properties
APPC mode name Server & Client Mode Name APPC Mode Properties
Maximum number of Server & Client Parallel Session APPC Mode Properties
APPC sessions Limit
Receive pacing limit on Server/Client Pacing Send APPC Mode Properties
the server/Send pacing Count
limit on the client
Send pacing limit on the Server/Client Pacing Receive APPC Mode Properties
server/Receive pacing Count
limit on the client

Rumba Office 143
Rumba Office
You can configure parameters for Rumba Office using the APPC
Configuration Facility. For information about using the APPC
Configuration Facility, refer to your Rumba Office
documentation.
Note: Rumba uses the CPIC interface. Make sure you define the
correct side info entries (you can define these entries by
selecting SideInfo on the main menu of the APPC Configuration
Facility).
Table 4-6 lists the parameters that can be defined for Rumba
Office, where you define them, their names, and their locations
Table 4-6. Network Parameters for Rumba Office

Server network address Server Options: Destination Token-Ring
Address Configuration Dialog
Box
Client network address Client Defined in your
Windows Network
Setup
Client node ID Client Options: Block ID Token-Ring
and Node ID Configuration Dialog
Box
Client network name Client Network Name RUMBA(R) APPC
Configuration Utility
Client control point Client Control Point Name RUMBA(R) APPC
name Configuration Utility
Server LU network ID Server LU Name Configure Remote LUs
Dialog Box
Server LU name Server Network Name Configure Remote LUs
Dialog Box

Table 4-6. (cont.)Network Parameters for Rumba Office (cont.)

Client LU name Client LU Name Configure Local LUs
Dialog Box
APPC mode name Server & Client Mode Name Configure Modes
Dialog Box
Maximum number of Server & Client Session Limit Configure Modes
APPC sessions Dialog Box
Receive pacing limit on Server/Client Send Parameters: Configure Modes
the server/Send pacing Pacing Count Dialog Box
limit on the client
Send pacing limit on the Server/Client Receive Parameters: Configure Modes
server/Receive pacing Pacing Count Dialog Box
limit on the client

Client Access/400 145
Client Access/400
When you install Client Access/400 on a Windows client, the
installation program creates the file CONFIG.PCS. The network
parameters reside within this file.
Table 4-7 lists the parameters that can be defined for

Client Access/400, where you define them, and their names.
Table 4-7. Network Parameters for Client Access/400
Parameter Defined on Name

Server network Server System LAN address
address
Client network name Client PC location name (First Part)
Client control point Client PC location name (Second Part)
name
Server LU name Server Name of system to which to
connect
Client LU network ID Client PC location name (First Part)
Client LU name Client PC Location Name (Second Part)


147
Part 3: SequeLink Server

Administration
This part provides information about using SequeLink with
databases and provides platform-specific information about
administration tasks for SequeLink Server. It contains the
following chapters:
■ Chapter 5, “Using SequeLink With Your Database”


148 Part 3: SequeLink Server Administration

149
5 Using SequeLink With Your

Database
This chapter provides information about using SequeLink with

your database, including information about:
■ Server-defined host user definitions
■ Retrieval of database meta-information
■ SequeLink Dictionary Manager and the creation and

management of SequeLink Shadow Data Dictionaries (SSDDs)
■ Fine-tuning system performance
■ Database-specific information
Using Server-Defined Host User Definitions

To connect to SequeLink Server for Windows NT or SequeLink
Server for UNIX, you must specify a valid host user ID and
password. Once the service process is started, the security
context of the process switches to the security context of
the user.
The database’s security mechanism can rely on the underlying

operating system authentication (as in the case of Informix or
OpenINGRES), or the database’s own security mechanism can be
implemented (as in the case of Oracle, Sybase, or DB2 Universal
Database). If the latter security mechanism is implemented, the
host user ID is not required.

150 Chapter 5 Using SequeLink With Your Database
You can define the following levels of host authentication:
■ None. No host user ID or password checking is performed. The

service process runs in the security context of the account
under which it was started. On UNIX, service processes are
started under the root account. On Windows NT, they are
started under the system account.
■ Server. The service process is mirrored in the security context

of a user you specify in the service configuration resource. On
UNIX, you do not need to specify a password for this user. On
Windows NT, the password is required. The password is saved
and encrypted in the service configuration resource.
■ Client. The service program is mirrored in the security context

of the host user ID specified at the client. The client must also
specify a valid password for the user.
For information about specifying the host user ID for

Windows NT, see “Setting the User Authentication Level” on
page 248.
For information about specifying the host user ID for UNIX, see
“Setting the User Authentication Level” on page 268.

Managing the Retrieval of Database Meta-Information 151
Managing the Retrieval of Database

Meta-Information
Meta-information is information that describes the data stored
in the database and can include information about the tables in
the database, the columns in those tables, and the indexes that
are defined for those tables. This data also is referred to as the
database’s data dictionary or system catalog.
Typically, ODBC, OLE DB, and JDBC applications extract and use
information from the database’s data dictionary using specific
ODBC, OLE DB, or JDBC API calls, such as the ODBC calls
SQLTables, SQLColumns, and SQLPrimaryKeys.
In large databases, the amount of meta-information that is

retrieved can be considerable. Because some client applications
cannot manage large amounts of information efficiently, system
performance can be adversely affected.
Some ODBC, OLE DB, and JDBC calls have parameters that accept
search patterns. You can use these parameters to limit the
amount of meta-information that is retrieved; however, not
every client application supports these parameters.
To help manage the retrieval of meta-information, SequeLink

provides the following methods for limiting the amount of
meta-information that is retrieved:
■ SequeLink Shadow Data Dictionaries (SSDDs)

■ Database data dictionary filters
■ Data dictionary views

Using SequeLink Shadow Data

Dictionaries (SSDDs)
A SSDD is a collection of tables that contains meta-information
about tables in a database, much like a database’s native data
dictionary or system catalog. You can use the SequeLink
Dictionary Manager (or OS/390 batch procedures) to create and
populate a SSDD with dictionary information about all, or a
subset of, the tables in your database.
Once a SSDD is populated, your ODBC, OLE DB, and JDBC

applications can use the SSDD, instead of the native database
data dictionary, for retrieving data dictionary information.
Read further to learn more about using SSDDs. For more

information about using the SequeLink Dictionary Manager to
create and manage SSDDs, see “Using the SequeLink Dictionary
Manager” on page 162. For more information about using
OS/390 batch procedures to create SSDDs, see “Using OS/390
Batch Procedures with SSDDs” on page 169.
Advantages of Using SSDDs

■ Enhanced Administration. You can create different,
user-specific dictionaries for different groups of clients,
providing end users with data dictionary views that are
optimized for their specific requirements.
■ Extended Security. Most ODBC applications provide access to

the database for all types of queries and browse the complete
data dictionary. SSDDs allow you to restrict access to the data
dictionary information.
■ Improved System Performance. Because SSDDs can be smaller

than native data dictionaries and are prepared in the format
required by ODBC applications, system performance may
improve significantly, especially when the remote database

contains a large number of tables or when data dictionary

access is slow.
■ Increased Functionality. Some SequeLink Server services or

database systems limit the amount of data dictionary
information that can be retrieved in one session or by one
data dictionary query. Using SSDDs allows you to combine
data dictionary information that would otherwise span
several sessions or several data dictionary queries. For
example, by using SSDDs with DB2 for AS/400, you can group
information about different collections and de-couple them
from the library list.
It is important to remember that the information in a SSDD is

static, which means that a SSDD must be updated when
database tables or indexes are altered or dropped. Despite this
limitation, SSDDs can provide significant system performance
and functionality benefits. Although a database’s native data
dictionary is dynamic, it provides slower system performance and
less flexibility.
SSDD Catalog and Schema Names

SequeLink uses the terms catalog and schema for concepts
commonly known in many database systems as qualifiers and
owners, respectively. The catalog and schema terminology is
compliant with the X/Open, ANSI, and ODBC V3 definitions and
standards. For example, for DB2 Universal Database V5, a
schema or owner is referred to as an authorization ID. A SSDD is
identified by a unique combination of a catalog and schema
name, allowing you to create multiple SSDDs.
A SSDD must contain the following tables:
SSDD3TBL SSDD3PRI
SSDD3COL SSDD3FOR
SSDD3SPC SSDD3TPR
SSDD3STS SSDD3CPR

Note: For previous versions of SequeLink, the SSDD table names

were in the format SQLNKxxx.
These table names, and the columns they contain, cannot be

modified.
Example:
If you created a SSDD with the schema name FINANCE, the

following tables would be created:
FINANCE.SSDD3TBL
FINANCE.SSDD3COL
FINANCE.SSDD3SPC
FINANCE.SSDD3STS
FINANCE.SSDD3PRI
FINANCE.SSDD3FOR
FINANCE.SSDD3TPR
FINANCE.SSDD3CPR
Extracting Data Dictionary Information

You can control the extraction of data dictionary information by
setting the DataDictionary parameter:
DataDictionary=DBMS Extracts data dictionary

information from the database’s
native data dictionary.
DataDictionary=SQLNK Extracts data dictionary
information from a SSDD.

DataDictionary=HYBRID Extracts data dictionary

native data dictionary or a SSDD,
depending on the type of data
that is requested. Table, schema,
and catalog information is
extracted from a SSDD; column,
index, and key information is
extracted from the database’s
When the DataDictionary parameter is set to SQLNK or

HYBRID, you can also set the following parameters:
DataDictionaryOwner Sets the schema (or owner)

name of the SSDD.
DataDictionaryQualifier Sets the catalog (or qualifier)
name of the SSDD.
Table 5-1 shows specific ODBC calls and indicates from where
data dictionary information is extracted, when the
DataDictionary parameter is set to DBMS, SQLNK, or HYBRID.
Table 5-1. Data Dictionary Information Extraction for

ODBC Calls
DataDictionary Setting
ODBC Call DBMS SQLNK HYBRID
SQLTables Native SSDD SSDD
SQLColumns Native SSDD Native
SQLStatistics Native SSDD Native
SQLSpecialColumns Native SSDD Native
SQLColumnPrivileges Native SSDD Native
SQLTablePrivileges Native SSDD Native
SQLPrimaryKeys Native SSDD Native
SQLForeignKeys Native SSDD Native
SQLGetTypeInfo Native Native Native

Table 5-1. Data Dictionary Information Extraction for

ODBC Calls (cont.)
DataDictionary Setting
ODBC Call DBMS SQLNK HYBRID
SQLProcedures Native Native Native
SQLProcedureColumns Native Native Native
Note: To execute a SQL statement, the database uses its native

data dictionary. The SSDD is used only to return requested data
from the data dictionary and is not used to enforce database
security. For example, applications can still access tables that are
not in the SSDD, if allowed by the database’s security.
You can set SequeLink’s DataDictionary parameter using any

of the following methods:
■ On the server, edit the SequeLink Server configuration

resource.
■ On the client, configure your ODBC 3.0 data source or OLE DB

data source using the SSDD tab of the ODBC Administrator
(for ODBC data sources) or the SSDD tab of the INTERSOLV
OLE DB Administrator (for OLE DB data sources).
■ On the client, the client application can dynamically control

what SSDD to use through the SequeLink ODBC Driver,
SequeLink OLE DB Provider, or SequeLink JDBC Driver.
■ On the client, edit the ODBC.INI file.

Configuring SSDD Information by Editing the

SequeLink Server Configuration Resource
The following keys control how data dictionary information is
extracted and define the schema and catalog name for SSDDs:
DataDictionary = DBMS
The default setting, DBMS, returns all data dictionary information

from the database’s native data dictionary.
To extract all data dictionary information from the SSDD, set this
key to SQLNK.
To use information from the data dictionary and SSDD, set this
key to HYBRID. Table, schema, and catalog information are
returned from the SSDD; column, index, and key information are
returned from the native data dictionary.
DataDictionaryOwner =
This key indicates the schema (owner) name of the SSDD that
will be used when the DataDictionary key is set to SQLNK or
HYBRID.
DataDictionaryQualifier =
This key indicates the catalog (qualifier) name of the SSDD that
will be used when the DataDictionary key is set to SQLNK or
HYBRID.
Example:
Using the SSDD example introduced in “SSDD Catalog and

Schema Names” on page 153, you would use the following
settings for these keys:
DataDictionary = SQLNK
DataDictionaryOwner= FINANCE
DataDictionaryQualifier=

Configuring SSDD Information in ODBC 3.0 and OLE DB

Data Sources
To configure SSDD information in your:
■ ODBC data sources, you can use the SSDD tab in the ODBC
Administrator as shown in Figure 5-1.
■ OLE DB data sources, you can use the SSDD tab in the
INTERSOLV OLE DB Administrator, which is similar to that
shown in Figure 5-1.
Figure 5-1. SSDD Tab of the ODBC Administrator

Data Dictionary: Select the type of data dictionary to be used:
■ (Default) to use the default setting of SequeLink Server
■ DBMS to return all data dictionary information from the

database’s native data dictionary
■ SQLNK to extract all data dictionary information from the

SSDD
■ HYBRID to use data dictionary information from the

database’s native data dictionary and the SSDD
DD Catalog: Type the catalog (qualifier) name of the SSDD that

will be used when Data Dictionary field is set to SQLNK or
HYBRID.
DD Schema: Type the schema (owner) name of the SSDD that will
be used when Data Dictionary field is set to SQLNK or HYBRID.
For more information about configuring your ODBC 3.0 data

sources, refer to the SequeLink ODBC Driver Reference for
Windows 9x, Windows NT, UNIX, and Macintosh.
For more information about configuring your OLE DB data

sources, refer to the SequeLink OLE DB Provider Reference.
Configuring SSDD Information Dynamically Using the

SequeLink ODBC Driver
Using the SequeLink ODBC Driver, call SQLSetConnectOption.
The syntax for this call is:
RETCODE SQLSetConnectOption(HDBC hdbc,UWORD fOption,UDWORD

vParam)
where hdbc identifies your ODBC connection, VParam is a

pointer to a NULL-terminated string, and fOption is one of the
following values:
1047 Sets the DataDictionary parameter using the

value in the vParam input argument.

1048 Sets the DataDictionaryOwner parameter using

the value in the vParam input argument.
1049 Sets the DataDictionaryQualifier parameter
using the value in the vParam input argument.

SequeLink OLE DB Provider
In your client application, specify any of the following key=value
pairs in the DBPROP_INIT_PROVIDERSTRING property of the
DBPROPSET_DBINITALL property set:
■ DataDictionary or DD
■ DataDictionarySchema or DDC
■ DataDictionaryCatalog or DDS
For example:
DataDictionary=SQLNK;DataDictionarySchema=FINANCE;
tells the SequeLink OLE DB Provider to connect to an Oracle

service and activate the SSDD with a schema name of FINANCE.
For more information about specifying connection attributes,

refer to the SequeLink OLE DB Provider Reference.

SequeLink JDBC Driver
Using the SequeLink JDBC Driver, specify any of the following
additional connection attributes:
■ DataDictionary
■ DataDictionarySchema
■ DataDictionaryCatalog

For example:
jdbc:sequelink://189.23.5.132:4003/[Oracle];
DataDictionary=SQLNK;DataDictionarySchema=FINANCE
tells the SequeLink JDBC Driver to connect to an Oracle service

and activate the SSDD with a schema name of FINANCE.
For more information about specifying connection attributes,

refer to SequeLink JDBC Driver Reference.
Editing the ODBC.INI File

You can add the following attributes to each ODBC data source
definition on the client by editing the data source section in the
ODBC.INI file.
For example, using the SSDD example introduced in “SSDD

Catalog and Schema Names” on page 153, you would add the
following information to the appropriate data source section in
the ODBC.INI file.
DataDictionary=SQLNK
DataDictionarySchema=FINANCE
DataDictionaryCatalog=
Using Database Data Dictionary Filters

Database Data Dictionary filters limit the amount of
meta-information that can be retrieved from the database’s
native data dictionary; specifically, they limit the number of
result rows that can be returned for data dictionary calls, such as
SQLTables, SQLColumns, and SQLProcedures. The data dictionary
filters override any call parameters that are passed by the
application when it accesses the database’s native data
dictionary.

SequeLink provides the following types of database data

dictionary filters, which must be defined on the server:
■ Filter by catalog list

■ Filter by schema list
■ Filter by table type
■ Filter by database (DB2 for OS/390 only)
For more information about the filters provided by SequeLink,

see the section for your database in “Database Data Dictionary
Filters” on page 186.
Using Database Data Dictionary Views

The DB2_CatalogOwner parameter allows you to limit the
meta-information that is returned by using views on the
database data dictionary. It is available for DB2 for OS/390 only.
For more information about the DB2_CatalogOwner parameter,
see “DB2 for OS/390-Specific Settings” on page 199.
Using the SequeLink Dictionary Manager

The SequeLink Dictionary Manager is a 32-bit application which
runs on Windows 9x and Windows NT. You can use it to create,
modify, or remove SSDDs that are used with ODBC, OLE DB, and
JDBC applications. For more information about SSDDs, see “Using
SequeLink Shadow Data Dictionaries (SSDDs)” on page 152.
The SequeLink Dictionary Manager is an installable option you

can select when you install SequeLink ODBC Edition Client.
Typically, data dictionary maintenance is performed by a
database administrator or another central coordinator;
therefore, the SequeLink Dictionary Manager should be made
available to only those people who will be using it.

Using the SequeLink Dictionary Manager 163
For information about installing the SequeLink Dictionary

Manager, refer to the SequeLink ODBC Edition Client Installation
Guide.
SequeLink Dictionary Manager Scripts

When you create an SSDD, SSDD tables are created in the remote
database using a script executed by the SequeLink Dictionary
Manager. The script is a standard text file which contains SQL
commands separated by new lines and semicolons.
Table 5-2 lists the SequeLink services supported by the SequeLink

Dictionary Manager and their associated scripts:
Table 5-2. SequeLink Services Supported by the SequeLink

Dictionary Manager and Their Associated Scripts
SequeLink Server Script

DB2 for OS/390 DMDB2.SQL
DB2 for AS/400 DMDB2400.SQL
DB2 for UNIX and DB2 for Windows NT DMDB2CS.SQL
Informix DMINF.SQL
Microsoft SQL Server DMMSSQLS.SQL
OpenINGRES DMING.SQL
Oracle DMORA.SQL
Sybase DMSYB.SQL
To customize the SSDDs for your environment, you edit these

scripts. The scripts also include placeholders for the catalog and
schema names, <catalog> and <schema>, allowing you to create
multiple SSDDs. At connection, the SequeLink Dictionary
Manager substitutes these placeholders with catalog and
schema names you specify.

Creating SSDDs
Note: Before you can create a SSDD, an ODBC data source must
exist. For information about creating ODBC data sources, 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.
To create a SSDD:
1 Edit the appropriate SSDD script for your database.
Information about optimizing the script for your
configuration is included in the script file.
2 Start the SequeLink Dictionary Manager, and select File / New

Transfer. A dialog box appears, allowing you to select an
ODBC data source.
Note: For AS/400 services, use the SQLNKALL service. Do not

use SQLNKNONE.

3 Select a data source and enter a name for the catalog and
schema of the SSDD you want to create. If the SSDD you
specify does not exist, the SequeLink Dictionary Manager will
prompt you to open a script.
Note: Some SequeLink services do not support catalogs

(DB2, for example). In these cases, leave the catalog field
blank:
CATALOG =
SCHEMA = FINANCE
4 Select the appropriate script and click OK. The SequeLink
Dictionary Manager creates the SSDD in the database.
Note: For DB2 for AS/400, the SSDD tables must be journaled. To
explicitly activate journaling, issue the OS/400 command
STRJRNPF for all SSDD tables you create. Alternatively, you can
create the SSDD tables in a collection, automatically activating
journaling. For more information about creating a collection and
activating journaling, see the information contained in the
DMDB2400.SQL script.

Updating SSDDs
Information in a SSDD is static, which means that a SSDD must be
updated using the SequeLink Dictionary Manager when database
tables or indexes are altered or dropped.
When you create a new SSDD, the Transfer Document window

appears, listing information about the native data dictionary and
the SSDD side-by-side. This window allows you to browse
through the database’s native data dictionary and add, update,
or delete items in the SSDD.

You can perform the following operations on items in the SSDD:
■ To add tables, schemas, or catalogs to the SSDD, click and

drag them from the native data dictionary to the SSDD.
■ To delete items from the SSDD, click them to select them, and
press the DELETE key.
■ To update an item with new information in the native data

dictionary, double-click that item in the SSDD. For example,
double-clicking a table updates that table with any new
indexes or columns that have been added to it or removes
any tables that have been deleted.
Any action on a schema affects its underlying tables; any action

on a catalog affects its underlying schemas.
When Immediate mode is turned on in the SequeLink Dictionary

Manager, changes are implemented as you make them. When
Immediate mode is turned off, you can insert, delete, or update
one or multiple objects; then, implement all changes at once.
Notes:
■ Tables that contain columns with data types that are not
supported by the SequeLink ODBC Driver cannot be added to
a SSDD, including Oracle tables that contain a column of type
MLSLABEL, and DB2 for AS/400 tables that contain a column
of type GRAPHIC, VARGRAPHIC, or LONG VARGRAPHIC.
■ You cannot add the Sybase system table dbo.sysindexes to

a SSDD.
■ If your system performance is slow, we recommend that you

work with Immediate mode turned off.
■ To use the SequeLink Dictionary Manager with OpenINGRES

databases, edit the SequeLink Server configuration resource
and set the ING_ReadLock key to NOLOCK. For more
information about the configuration resource for
OpenINGRES, see “SequeLink Server Configuration Resource
(OpenINGRES)” on page 212.

■ When using the SequeLink Dictionary Manager with Oracle

databases, you will not see the different Oracle catalogs. The
SSDDs also will not contain catalog information.
Managing Different SSDD Versions

The SequeLink Dictionary Manager 3.0 is used to manage SSDDs
created at the 3.0.x level only. If you have 1.0.00 or 2.0.00 SSDDs,
you must delete them and recreate an SSDD at the 3.0.x level.
Table 5-3 lists supported SSDD and SequeLink configurations.
Table 5-3. Supported SSDD and SequeLink Configurations
SequeLink
SequeLink ODBC SequeLink Dictionary
Edition Client Server SSDD Manager
3.0 3.0 1.0.00 1.0.00
3.0 3.5 or 4.0.x 2.0.x 2.0.x
3.5 or 4.0.x 3.5 or 4.0.x 2.0.x 2.0.x
4.5.x 4.5.x 3.0.x 3.0.x
Note: The SequeLink Dictionary Manager does not support the

SequeLink ODBC Socket or Microsoft SQL Server 6.0.

Using OS/390 Batch Procedures with SSDDs 169
Using OS/390 Batch Procedures with SSDDs

Using SSDDs helps you manage resources in your OS/390 system
more efficiently and can make it easier and faster to work with
DB2 catalog information within any ODBC or OLE DB
application. You can use the SequeLink Dictionary Manager to
create and manage SSDDs, or you can populate and refresh
SSDDs in Batch mode with an OS/390 batch program that is
shipped with SequeLink Server.
Advantages to using OS/390 batch procedures, rather than the

SequeLink Dictionary Manager, include:
■ Populating or refreshing SSDDs can be performed in off-peak

hours (for example, at night).
■ Because the batch program uses static SQL (the SequeLink

Dictionary Manager uses dynamic SQL), populating the SSDD
in batch mode consumes fewer resources than using the
SequeLink Dictionary Manager.
The batch program and the SequeLink Dictionary Manager can

be used concurrently and provide the same functionality. The
difference is the way each tool performs their tasks.
Creating SSDD Tables

The SSDD tables must be created before the batch program can
be run to populate the SSDD. You can create a SSDD as described
in “Creating SSDDs” on page 164, or you can execute an SQL
script in SPUFI on OS/390.
To create SSDD Tables using an SQL script:

1 For each SSDD, create the SSDD tables using the DMDB2
script in the CNTL dataset of the SequeLink server. This script
contains the SQL that will be used to create the SSDD tables.

2 Customize this script, as explained in the script. If necessary,

you can change the CURRENT SQLID and the tablespaces
names, storage group names, and the database name. You
must replace <SCHEMA> with a DB2 authorization ID that will
identify the SSDD. Do not change the table names.
Note: Execute the script under SPUFI (DB2I). You can create
multiple SSDDs by running the script multiple times using
different DB2 authorization IDs for <SCHEMA>.
Binding DBRMs to DB2

The following DBRMs are members of the DBRM dataset:
SQLNKCL3 SQLNKSPC
SQLNKCL4 SQLNKSSD
SQLNKCPR SQLNKSTS
SQLNKDEL SQLNKTBL
SQLNKFOR SQLNKTMP
SQLNKPRI SQLNKTPR
SQLNKRPT SQLNKALI
SQLNKSC2
To bind DBRMs to DB2:

1 Customize the member SSDDBIND of the CNTL dataset. The
DBRMs must be bound to your DB2 system. The default plan
name is SC451C4.
2 Submit the job SSDDBIND.
Using the Batch Program

The main program, SQLNKSC2, can be executed in batch to
populate or refresh one or multiple SSDDs, based on an input file
(DDname SYSIN). A sequential control file (DDname CNTL) is used
to define general execution parameters. Customize the members

SSDDRUN, SSDDIN, and SSDDCNTL of the CNTL dataset, and

submit SSDDRUN.
The main program, SQLNKSC2, is written in VS COBOL II. To

execute SQLNKSC2, the COBOL runtime library must be specified
in the STEPLIB (for example, SYS1.COBLIB2).
Alternatively, to run a job in the IBM language environment, you

must execute another version of this program. To execute this
alternate program, the library SCEERUN is required. Change the
SSDDRUN member to execute SQLNKSCL, instead of SQLNKSC2.
Also, change the plan name (parameter PLAN) to the plan name
you used to bind the DBRMs to DB2 in “Binding DBRMs to DB2”
on page 170. The default plan name is SC451C4. The name of the
language environment program is SQLNKSCL.
CNTL Input Record Usage

The MODE parameter determines how a table in the SSDD will be
handled. This parameter starts at position 1 in the CNTL file.
Valid settings include:
MODE=UPDATE All DB2 objects defined in the SYSIN file

are used to populate the SSDD. Only
tables that are selected in the SYSIN file
are updated with catalog information.
MODE=REFRESH The contents of the SSDD are deleted;
then, all DB2 objects defined in the
SYSIN file are used to populate the
SSDD.
COLUMNPRIV=YES|NO To force updating of
SQLColumnPrivileges information, use
COLUMNPRIV=YES. It starts at position 1
and is the second line of the CNTL file.
Because populating the SQLNKCPR
table is time-consuming and only a few
applications use this information,
COLUMNPRIV=NO is the default.

If your SYSIN input may contain DB2 objects that can cause
inconsistencies when running a job with MODE=UPDATE, use
MODE=REFRESH instead. For example, suppose your SYSIN input
contains a DBNAME object and you run a job with MODE=UPDATE.
The SQLNKTBL table could contain old tables from a previous run,
if tables were deleted from the database before the job was run.
SYSIN Input Record Usage

Input statements in the SYSIN file can be used to specify the:
■ Tables and views to include in the SSDD
■ Name of the DB2 database from which all DB2 tables must be
stored in the SSDD
The SYSIN file records:
SSDDNAME Owner of the SSDD tables (column 2).

DB2OBJ Constant string to identify the record type
(column 11). Valid values are DB2OBJ or
DBNAME.
AUTHORID DB2 Object (table/view/synonym/alias)
authorization ID (column 18).
DB2OBJECTNAME DB2 object name (column 27).
AuthorID and DB2ObjectName will accept the following

wildcard characters:
■ * or % represents zero or multiple characters.

■ ? or _ represents any single character.
Note: To use % or _ as a character (not as a wildcard character),

precede it by +. For example, if you want to include all tables
starting with the string 'TAB_', use TAB+_* in your input line.
If multiple SSDD names are specified in the input file, a COMMIT

of the work that is completed is executed before switching to the
new SSDD. Input records are ordered by SSDD Name.

Example:
SSDD Funct. Authid DB2 objectname
0+++5++++1++++5++++2++++5++++3++++5++++4+++
0 0 0 0
SSDD001 DB2OBJ * * (1)
SSDD002 DB2OBJ SYSIBM * (2)
SSDD002 DB2OBJ MKTG DEPT1* (3)
SSDD999 DB2OBJ * XYZ (4)
SSDD999 ZDPRNG EMPLOYEES (5)
■ Record 1 causes all DB2 objects defined in the DB2 system
catalog to be stored in SSDD SSDD001.
■ Record 2 will COMMIT all work that is complete for SSDD001

and causes all system tables identified by SYSIBM to be
stored in SSDD SSDD002.
■ Record 3 causes all DB2 objects with MKTG as an

authorization ID name and a name starting with DEPT1 to be
added to SSDD002.
■ Record 4 will COMMIT all work that is complete for SSDD002

and causes all DB2 objects named XYZ to be stored in the
SSDD named SSDD999.
■ Record 5 adds the definition needed for

ZDPRNG.EMPLOYEES to SSDD999.
At the end of the input, a COMMIT is executed.

Return Codes (RCs)

Table 5-4 lists the Return Codes (RCs) that you may receive when
working with SSDDs. Information enclosed within lesser than (<)
and greater than symbols (>) indicate additional variable
information that may be returned.
Table 5-4. Return Codes (RCs) When Working with SSDDs

(OS/390)
Severity code RC Description

I Information 0 An Information message informs you of
events that occur during execution about
which you may need to know.
W Warning 4 Indicates that there may be an error or
inconsistencies in the update of a SSDD for
a table/view/synonym or alias.
E Error 8 An error occurs during the execution of the
update of a SSDD for a table/view/synonym
or alias. The data in the SSDD for this DB2
object is inconsistent. The module
SQLNKSSD stops processing the SSDD tables
at the point of error and the data is deleted
from the SSDD. The next DB2 object (if any)
will be processed.
S Severe 12 During the processing of a SSDD, a severe
error occurred. Updates are rolled back for
this SSDD. The data of the next SSDD will be
processed.
U Unrecoverable 16 During the processing of a SSDD, an
unrecoverable error was detected. Updates
in the current SSDD are rolled back and the
program is terminated. Contact MERANT
technical support.

Table 5-5 lists the error messages that may be returned when you
work with SSDDs on OS/390.
Table 5-5. Error Messages When Working with SSDDs (OS/390)
Module RC MsgId Description

SQLNKSSD 8 DB2SD-0001-E DB2 object not found in System Catalog. The
DB2 object cannot be found in the DB2
System Catalog. Object is skipped.
SQLNKSSD 0 DB2SD-0002-I Executed updates have been committed
<Name of SSDD that has been committed>.
For the current DB2 object, a new SSDD will
be used. All updates for the previous SSDD
are committed.
SQLNKSSD 12 DB2SD-0003-S Unexpected error on PREPARE for DELETE
<SSDD table in error>. One of the PREPARE
statements that was used to delete the data
for the current DB2 object in the SSDD tables
returns an RC other than 0.
SQLNKSSD 12 DB2SD-0004-S Unexpected error on EXECUTE for DELETE
<SSDD table in error>. One of the EXECUTE
of the DELETE statements used to erase the
data of the current DB2 object in the SSDD
tables returns an RC other than 0 or +100.
SQLNK*** 16 DB2SD-0005-U Error on PREPARE for INSERT. The PREPARE
for INSERT statements in one of the SSDD
tables returned a nonzero SqlCode.
SQLNK*** 16 DB2SD-0006-U Row already exists. A row INSERT statement
in one of the SSDD tables returns a duplicate
error condition on a unique index.
SQLNK*** 16 DB2SD-0007-U Unexpected error on row INSERT. A row
INSERT statement in one of the SSDD tables
returned an abnormal condition.
SQLNKTBL 16 DB2SD-0008-U Undefined DB2 object type. An undefined or
invalid internal DB2 object table
identification was found in SQLNKIF1-TYPE.
SQLNKSTS 12 DB2SD-0009-S Index data not found in SYKEYS/SYSTABLES
SQLNKPRI data on the Primary Key columns cannot be
found.

Table 5-5. Error Messages When Working with SSDDs (OS/390) (cont.)

SQLNKCL* 12 DB2SD-0010-S No column definition found in
SYSCOLUMNS. No column definition was
found in SYSCOLUMNS for a DB2 object that
was not defined as an ALIAS.
SQLNKSPC 12 DB2SD-0011-S Undefined DB2 column type.
SQLNKALI 12 DB2SD-13-S Commit statement returns an error
condition. Analyze the SQL code, correct the
problem and run the job again.
SQLNKSPC 8 DB2SD-0010-E No column definition found in SYSCOLUMNS
<Index name>. No column definition was
found in SYSCOLUMNS for an index of the
current DB2.
SQLNKPRI 16 DB2SD-0012-U More than 50 columns in PrimaryKey. The
SQLNKFOR PrimaryKey of the DB2 current object is
defined on more than 50 columns. Internal
table overflow occurs. Contact MERANT
technical support.
SQLNKCL* 16 DB2SD-30-U Unrecoverable error on TMPFILE operation.
SQLNKALI 16 DB2SD-31-U Overflow on RemoteServer table (maximum
30). There are more than 30 remote DB2s.
Internal error. Contact MERANT technical
support.
SQLNKALI 16 DB2SD-34-U Unexpected error when reconnecting to a
local DB2 <local location>. Analyze SQL
code, correct the problem, and run the job
again.
SQLNKALI 8 DBSD-28-E Unable to connect to the DB2 remote system
<remote system>.
SQLNKALI 8 DB2SD-32-E Remote server type/version not supported
<DB2 version>.
SQNKCL* 4 DB2SD-18-W No column definition found for ALIAS.
SQLNKCOL 4 DB2SD-0018-W No column definition found in
SYSCOLUMNS. No column definition was
found in SYSCOLUMNS for a DB2 ALIAS
defined on another DB2 system.


SQLNKCPR 4 DB2SD-0013-W Column authorization info not found. No
column authorization information was
found for the DB2 current object.
SQLNKCL* 12 DB2SD-27-S Undefined DB2 default column value
<value>. The column DEFAULT of
SYSIBM.SYSCOLUMNS contains a value that
is different from the values that are
accepted by your version of DB2. Check the
integrity of your catalog.
SQLNKCL* 12 DB2SD-0015-S Invalid length for DB2 FLOAT <returned
SQLNKSPC length>. The length of a column defined as
FLOAT is a value other than 4 or 8.
SQLNKFOR 12 DB2SD-19-S Index data not found in
SYSKEYS/SYSTABLES. No column info is
found for the primary key.
SQLNKSC2 00 DB2SD20-I Successful execution. All work committed.
SQLNKSC2 00 DB2SD21-I No Table/View/Alias/Synonym selection.
Check your SYSIN parameters. You are
referring to a database name or a database
object that does not exist.
SQLNKSC2 12 DB2SD-22-S Shadow Catalog tables do not exist. Run
your DMDB2 script and create the missing
tables.
SQLNKSC2 12 DB2SD-23-S Shadow Catalog tables inconsistent <ODBC
3.0>. One or more shadow catalog tables do
not exist.
SQLNKSC2 04 DB2SD-24-W Successful execution with warning(s).
SQLNKSC2 00 DB2SD-25-I Clean-up of Shadow Catalog executed.
SQLNKSC2 12 DB2SD-26-S Unsuccessful execution. Check messages.


SQLNKTPR 4 DB2SD-0014-W Table authorization info not found. No table
authorization information was found for the
DB2 current object.
SQLNK*** 12 DB2SD-0016-S Cannot get DBNAME from SYSTABLES
<creator table if not equal to the current
DB2 object>. The database name of the
current DB2 object (or of another table)
cannot be found in SYSIBM.SYSTABLE object.
Alias Support
The Shadow Catalog is populated for local and remote aliases
with the following conditions:
■ Aliases for a combination of DB2 V4 and V5 subsystems are

supported.
■ Aliases for a combination of DB2 V3 and DB2 V4 or V5

subsystems are not supported.
■ Cascading aliases (an alias that points to a remote table,

which is another alias pointing to another remote table) are
not supported.
Using Previous Versions of SSDDs in

Batch Mode
In this SSDD version, MODE=UPDATE/SELECTIVE is no longer
used; MODE=UPDATE is used instead. When MODE=UPDATE, all
tables, except SQLColumnPrivileges, are updated. If

Fine-Tuning System Performance 179
COLUMNPRIV=YES, all tables are updated, including

SQLColumnPrivileges.
In addition, SQLNKTABLE=xxx is no longer used. You cannot

select individual tables to be populated.
Note: The structure and table names of ODBC 2.0 Shadow

Catalog tables is different from ODBC 3.0 Shadow Catalog
tables.
Fine-Tuning System Performance

This section provides some guidelines for fine-tuning system
performance for SequeLink Server DB2, Informix 7 and 9, Oracle,
and Sybase System 10 and 11 services.
OS/390 DB2 for OS/390

For DB2 V4R1 and higher, you can reduce the processing time of
ODBC catalog statements by creating additional indexes on the
DB2 Catalog. SequeLink Server for OS/390 can take advantage of
the following additional indexes:
■ SYSFOREIGNKEYS (CREATOR, TBNAME, RELNAME)

■ SYSTABAUTH (TCREATOR, TTNAME)
■ SYSCOLAUTH (TIMESTAMP)
AS/400 DB2 for AS/400 and Oracle

ArrayFetchMaxBytes sets the maximum number of bytes that
can be fetched for array fetches. Use ArrayFetchMaxBytes=n
where n is a positive integer in the range of 1 to 262,144
(256 KB). The default is 60000.

When deciding this value, remember that large values for

ArrayFetchMaxBytes can cause the SequeLink Server service to
allocate a substantial amount of memory on your server at
runtime, especially if you have a large number of concurrent
open cursors.
Informix 7 and 9
On UNIX, communication with Informix 7 and 9 databases is
governed by the Informix configuration file, sqlhosts. Usually, the
application communicating with the database and the database
are located on the same machine. Because SequeLink Server for
Informix is usually installed on the same server that is running the
Informix database, communication between the SequeLink
Server for Informix service and the database is optimized when
shared memory communication is used.
You can verify that shared memory is being used by checking the
value of the environment variable INFORMIXSERVER using the
SequeLink Server Administrator. This value specifies a line in the
Informix etc/sqlhosts file containing a specific nettype. If this
nettype contains “shm”, shared memory communication is used
between the SequeLink Server service and the Informix database.
For more information about the Informix sqlhosts file, refer to
your Informix documentation.
Sybase System 10 and 11

Table 5-6 lists environment variables that can affect system
performance for SequeLink Server Sybase services. To change any
values for these environment variables, start the SequeLink

Fine-Tuning System Performance 181
Server Administrator and edit the session configuration of your

Sybase System 10/11 service.
Table 5-6. Sybase System 10/11 Variables That Affect System Performance
Variable Valid Values Description

SYB_CTLIBCURSORROWS 1 - 250 Sets the number of rows used for each
The default is 50. internal fetch call from the client to
server.
SYB_DESCNONSELECT YES or NO. Determines whether the output
The default is NO. column description will be required
when a Select statement is processed.
Setting this variable to NO results in no
output column description. Although
setting this variable to NO can improve
system performance, syntax errors may
not be reported when SQAssociate is
issued.
SYB_TDSPACKETSIZE 512 - 32,767. Sets the maximum size of the packets
The default is 512. used to communicate between the
client and server. Increasing this value
can improve system performance.
Also, ArrayFetchMaxBytes sets the maximum number of bytes

that can be fetched for array fetches. Use
ArrayFetchMaxBytes=n where n is a positive integer in the
range of 1 to 262144 (256 KB). The default is 60000.

open cursors.

Database-Specific Information
This section describes the functionality available to the SequeLink
ODBC Driver, SequeLink OLE DB Provider, or the SequeLink JDBC
Driver when connected to a particular SequeLink Server service
type. It also describes settings that can be configured on the
server. Settings that are configured at the server service level
apply to all clients that connect to that SequeLink Server service.
For example, activating the ReadOnly setting ensures that all
clients that connect to that SequeLink Server service can only
send Select statements to the database.
Suppose that you install SequeLink Server for Oracle. After

installation, one SequeLink Server service for Oracle would be
available. You can add additional SequeLink Server services using
the SequeLink Server Administrator. For example, you may want
to add a SequeLink Server Oracle service that is ReadOnly and
another that is ReadWrite. Each SequeLink Server service
publishes itself on a specific network port. By specifying the
correct network port, SequeLink clients can connect to either the
ReadOnly service or ReadWrite service.
For instructions on changing settings for your server platform,

see:


Database-Specific Information 183
Cross-Database Settings
This section describes those SequeLink Server settings that apply
to all SequeLink Server services. The syntax is key=value. How a
value is stored and changed depends on your platform.
Connection Section
Diagnostic Formats
The SequeLink service can return warnings generated by the
database to client applications; however, be aware that the
number of warnings generated by some databases can be
substantial. To configure your SequeLink service to:
■ Send database warnings to the SequeLink client, use

Diagnostics=ALL.
■ Not send database warnings to the SequeLink client, use

Diagnostics=NOWARNINGS. This is the default.
Note: Because some database types generate a substantial

number of warnings, the increase in network traffic caused by
activating the sending of database warnings can downgrade
your system performance.
Session Section
Open Transactions at Logoff

You can control the behavior of the SequeLink server if an
SQLDisconnect occurs while a transaction is still open. For
example, this situation can occur when a SequeLink client
application does not call SQLEndTran before calling
SQLDisconnect, or when the workstation running the SequeLink
client is restarted without the application closing properly.

You can set the LogoffBehaviour parameter to direct the

SequeLink server to commit or rollback any open transaction
before stopping:
■ To implicitly commit open transactions, use

LogoffBehavior=COMMIT.
■ To implicitly roll back open transactions, use

LogoffBehavior=ROLLBACK.
■ To use the database default behavior, use

LogoffBehavior=DEFAULT. This is the default.
Read-Only SequeLink Services

By default, the SequeLink server allows clients to send any SQL
statement to the database. The database processes the SQL
statement, after checking whether the user has the required
privileges. Sometimes, you may want to limit all users of a specific
SequeLink Server service to read-only access, allowing the
SequeLink server to pass only Select statements to the database.
If you want a SequeLink Server service to:
■ Provide read only access, use ReadOnly=SELECT.
■ Provide read write access, use ReadOnly=NO. This is the

default.
■ Allow processing of all Select statements and stored

procedures, use ReadOnly=SELECT_BATCHES. In this case,
the stored procedures can perform read/write operations
internally.
For more information about SQL batch statements, refer to

the ODBC SDK.

Data Dictionary Information Extraction

You can control the extraction of data dictionary information by
setting the DataDictionary parameter:
DataDictionary=DBMS Extracts data dictionary

native data dictionary. This is the
default.
DataDictionary=SQLNK Extracts data dictionary
information from a SSDD.
DataDictionary=HYBRID Extracts data dictionary
information from either the
database’s native data dictionary
or a SSDD, depending on the type
of data that is requested. Table,
schema, and catalog information
is extracted from a SSDD; column,
index, and key information is
extracted from the database’s
When the DataDictionary parameter is set to SQLNK or

HYBRID, you can also set the following parameters:
DataDictionaryOwner Sets the schema (or owner)

name of the SSDD.
DataDictionaryQualifier Sets the catalog (or qualifier)
name of the SSDD.
For more information about using SSDDs, see “Using SequeLink

Shadow Data Dictionaries (SSDDs)” on page 152. For more
information about using the SequeLink Dictionary Manager to
create and manage SSDDs, see “Using the SequeLink Dictionary
Manager” on page 162.

Database Data Dictionary Filters

When DataDictionary=DBMS, you can limit the amount of
result rows that are returned for data dictionary calls by using
one of the following database data dictionary filters:
CatalogList Is a list of comma-separated values

specifying the catalogs from which table
names are retrieved by a SQLTables call. The
default is an empty string. You cannot use
quotes. For example:
CatalogList=personnel,invoicing
causes a SQLTables call to return
information from tables in the personnel or
invoicing catalogs.
SchemaList Is a list of comma-separated values
specifying the schemas from which table
names are retrieved by a SQLTables call. You
cannot use quotes. For example:
SchemaList=scott,tom
causes a SQLTables call to return
information from tables owned by the users,
scott or tom.
Alternatively, you can specify:
SchemaList=current schema
which causes a SQLTables call to return
information from tables owned by the
current user of the database. For example, if
the user, scott, connects to the database, a
SQLTables call will return information from
tables owned by scott.

TabletypeList Is a list of comma-separated values

specifying the table types from which table
names are retrieved by a SQLTables call. The
default is an empty string. You cannot use
quotes. Valid values include:
TABLE
VIEW
SYNONYM
ALIAS
SYSTEM TABLE
For example:
TabletypeList=VIEW
causes a SQLTables call to return view
names.
Note: For DB2 for OS/390, you should use the DB2 filter settings
described in “DB2 for OS/390-Specific Settings” on page 199.

DB2 Databases
The DB2 family of databases includes
■ DB2 Universal Database V5 (DB2 V5 on Windows NT & UNIX)

■ DB2 for AS/400 (DB2 on AS/400)
■ DB2 for OS/390 (DB2 on OS/390)
Data Types (DB2)
Table 5-7. Data Types (DB2)
DB2 ODBC
Char SQL_CHAR
Char() for Bit Data SQL_BINARY
Date SQL_TYPE_DATE
Decimal SQL_DECIMAL
Float SQL_FLOAT
Integer SQL_INTEGER
Long Varchar SQL_LONGVARCHAR
Long Varchar for Bit Data SQL_LONGVARBINARY
RealSQL REAL
Smallint SQL_SMALLINT
Time SQL_TIME
Timestamp SQL_TIMESTAMP
Varchar SQL_VARCHAR
Varchar() for Bit Data SQL_VARBINARY

SequeLink and DB2 V5 (Windows NT and UNIX)

Table 5-8 outlines the functionality available to the SequeLink
Driver with DB2 V5 databases.
Table 5-8. SequeLink Functionality with DB2 V5
Characteristic Description
Binary large object support Yes (maximum size depends on your DB2
configuration (DB2CLI.INI file). For more
information about binary large object support,
and LOGDATACOMPAT and
LOBMAXCOLUMNSIZE, refer to your IBM DB2
documentation.
Character large object support Yes (maximum size depends on your DB2
configuration (DB2CLI.INI file). For more
information about character large object
support, and LOGDATACOMPAT and
LOBMAXCOLUMNSIZE, refer to your IBM DB2
documentation.
Convert function Not supported
Cursor types Read/write, hold, and no-hold*
Cursor commit behavior Preserve (hold) and close (no-hold)*
Cursor rollback behavior Preserve (hold) and close (no-hold)*
Maximum number of concurrent open Limited by available system resources
statements
Numeric functions ABS, ACOS, ASIN, ATAN, ATAN2, CEILING, COS,
COT, DEGREES, EXP, FLOOR, LOG, LOG10, MOD,
POWER, SIGN, SIN, SQRT, TAN, PI, RADIANS,
RAND, ROUND, and TRUNCATE are supported
ODBC Catalog support No
Outer join support left, right, full, nested, not ordered
SQL92 String functions None
Stored procedure support Yes
* The hold/no-hold cursor attribute is determined by the value of CursorHold in the
SequeLink Server configuration resource and by your DB2CLI.INI file. For more information
about the DB2CLI.INI file, refer to your DB2 documentation.

Table 5-8. SequeLink Functionality with DB2 V5 (cont.)
String functions ASCII, CHAR, CONCAT, DIFFERENCE, INSERT, LEFT,
LTRIM, LENGTH, LCASE, LOCATE, LOCATE_2,
REPEAT, REPLACE, RIGHT, RTRIM, SOUNDEX,
SPACE, SUBSTRING, and UCASE are supported
System functions DBNAME, IFNULL, and USERNAME are supported
Time/date functions CURDATE, CURTIME, DAYNAME, DAYOFMONTH,
DAYOFWEEK, DAYOFYEAR, HOUR, MINUTE,
MONTH, MONTHNAME, NOW, QUARTER,
SECOND, TIMESTAMPADD, TIMESTAMPDIFF,
WEEK, and YEAR are supported
Transaction isolation levels Read uncommitted, read committed, repeatable
Read, serializable
Note: To change the isolation level, edit the
DB2CLI.INI file. For information about changing
isolation levels, refer to your DB2
documentation.
* The hold/no-hold cursor attribute is determined by the value of CursorHold in the
SequeLink Server configuration resource and by your DB2CLI.INI file. For more information
about the DB2CLI.INI file, refer to your DB2 documentation.

AS/400 SequeLink and DB2 for AS/400

For DB2 for AS/400, the following services are provided:
■ SQLNKALL provides an isolation level that DB2 calls Cursor

Stability. SequeLink and ODBC refer to this isolation level as
Committed Read. When using SQLNKALL, transaction control
is active. Your tables must be journaled for SequeLink Server
services to work correctly.
■ SQLNKNONE does not provide transaction capabilities or a

defined isolation level, and may offer improved system
performance for read-only databases. SequeLink and ODBC
refer to this isolation level as No Commit.
Both of these services are available over TCP/IP and LU 6.2.
Additional user-defined services can be created to obtain other

types of isolation levels supported on the AS/400. Supported
isolation levels are:
■ Repeatable read ■ Uncommitted read

■ Read stability ■ No Commit
■ Cursor stability
For more information about creating and deleting user-defined

services, see “Creating and Deleting User-Defined Services” on
page 287. For more information about changing the default
isolation level of services, see “Changing the Default Isolation
Level” on page 286.
SequeLink functionality with DB2 for AS/400 depends on the

isolation level. Table 5-9 outlines the functionality provided by

SQLNKALL. Table 5-10 outlines the functionality provided by

SQLNKNONE.
Table 5-9. SequeLink Functionality with DB2 for AS/400 SQLNKALL
Binary large object support No
Character large object support Yes (maximum size is 32,765 bytes)
Convert function Source Target
char date, time
date char, varchar
decimal numeric, decimal, integer, float, double,
bigint
double numeric, decimal, integer, float, double,
bigint
float numeric, decimal, integer, float, double,
bigint
integer numeric, decimal, integer, float, double,
bigint
numeric numeric, decimal, integer, float, double,
bigint
time char, varchar, time
timestamp char, varchar, timestamp
varchar date, time
Cursor commit behavior Preserve (hold)
Cursor rollback behavior Close
Cursor types Read/write, hold
Database type ANSI transactional
Date/time functions CURDATE, CURRENTDATE, CURTIME, DAYOFMONTH,
DAYOFWEEK, DAYOFYEAR, HOUR, MINUTE, MONTH,
NOW, QUARTER, SECOND, and YEAR are supported
Maximum number of 30
concurrent open statements
Numeric functions ABS, ACOS, ASIN, ATAN, COS, COT, EXP, LOG, LOG10,
MOD, PI, POWER, SIN, SQRT, and TAN are supported

Table 5-9. SequeLink Functionality with DB2 for AS/400 SQLNKALL (cont.)
Outer join support left, not ordered, all comparison, inner
SQL92 String functions UPPER, SUBSTRING, TRANSLATE, TRIM_BOTH,
TRIM_LEADING, and TRIM_TRAILING are supported
Stored procedure support No
String functions CHAR_LENGTH, CHARACTER_LENGTH, CONCAT, INSERT,
LEFT, LTRIM, LENGTH, RIGHT, RTRIM, SUBSTRING, and
UCASE are supported
System functions IFNULL and USERNAME are supported
Transaction isolation levels Cursor stability (read committed)
Table 5-10. SequeLink Functionality with DB2 for AS/400 SQLNKNONE
Binary large object support No
char date, time
date char, varchar
bigint
bigint
bigint
bigint
Source Target
bigint

Table 5-10. SequeLink Functionality with DB2 for AS/400 SQLNKNONE (cont.)
varchar date, time
Cursor commit behavior No
Cursor rollback behavior No
Cursor types Read/write, hold
Database type Non-transactional
Numeric functions ABS, ACOS, ASIN, ATAN, COS, COT, EXP, LOG, LOG10,
MOD, PI, POWER, SIN, SQRT, and TAN are supported
Outer join support left, not ordered, all comparison, inner
SQL92 String functions UPPER, SUBSTRING, TRANSLATE, TRIM_BOTH,
TRIM_LEADING, TRIM_TRAILING
Stored procedure support No
String functions CHAR_LENGTH, CHARACTER_LENGTH, CONCAT, INSERT,
LEFT, LTRIM, LENGTH, RIGHT, RTRIM, SUBSTRING, and
UCASE are supported
Transaction isolation levels None

OS/390 SequeLink and DB2 for OS/390

Driver with DB2 for OS/390 databases.
Table 5-11. SequeLink Functionality with DB2 for OS/390
Support Description
Binary large object support Yes (maximum size is 32,690 bytes)
char date, time
date char, varchar, date
bigint
bigint
bigint
bigint
Source Target
bigint
varchar date, time
Cursor commit behavior Preserve (hold) or close (no-hold)
Cursor types Read/write, hold, or no-hold
Database type ANSI transactional
HOUR, MINUTE, MONTH, NOW, QUARTER, SECOND, and
YEAR are supported

Table 5-11. SequeLink Functionality with DB2 for OS/390 (cont.)
Support Description
Math functions None supported
Outer join support (DB2 V4R1 left, right, full, not ordered, all comparison, nested
and higher)
SQL92 String functions SUBSTRING, TRIM_BOTH
String functions CHAR_LENGTH, CHARACTER_LENGTH, CONCAT, LEFT,
RIGHT, and SUBSTRING are supported
Transaction isolation levels All levels supported by the database are supported
Using Stored Procedures (DB2 for OS/390)

To use stored procedures with SequeLink, make sure that they are
designed and implemented as described in your DB2
documentation. In addition, the binding process requires that
each stored procedure must be bound to a package that must be
included in the packagelist of the plan used by SequeLink Server
for OS/390 (for example, SL451C4).
Bind Package SequeLink Server:

BIND PACKAGE(SQLNK) MEMBER(DB2MSPC4) +
ACTION(REP) ISOLATION(CS) +
OWNER(SMITH) VALIDATE(BIND)
Bind Package Stored Procedures:

BIND PACKAGE(SQLNK) MEMBER(SP001) +
OWNER(JOHN) VALIDATE(BIND)

During the bind step of the installation, the plan was bound
with a generic packagelist (for example, collectionid.*), allowing
you to execute a bind package on the stored procedure with the
same collectionid of the SequeLink Server package. The
execution of the bind plan can be omitted for the stored
procedure.
Bind Plan SequeLink Server:

BIND PLAN(SL451C4) PKLIST(SQLNK.*) +
VALIDATE(BIND) OWNER(SMITH) RETAIN
Bind Plan Stored Procedures:

none
If the stored procedure and the calling program are in the same
location, the package for the stored procedure must be bound
with the plan that invokes it.
SequeLink Server for OS/390 does not use the LUNAME column
information in SYSIBM.SYSPROCEDURES to determine which
procedure to execute. If SequeLink Server encounters more than
one entry with the same PROCEDURE and AUTHID in
SYSIBM.SYSPROCEDURES, it will assume blanks for the LUNAME
and any program can call the stored procedure.
Note on SQLProcedures & SQLProcedureColumns: The SequeLink

Server DB2 for OS/390 service does not support owners for stored
procedures. If the server detects that the OWNER parameter has a
value other than NULL or %, an error message is returned. The
returned result set displays the stored procedures (or its
columns) that the client is allowed to execute.

SequeLink Server Configuration Resource (DB2)

This section lists DB2-specific settings and their default values in
the SequeLink Server configuration resource. The file name
about initialization information storage, see:

Cursor Behavior at Commit/Rollback

DB2 allows you to retain open cursors across transactions, even
after executing a Commit (not on a Rollback call). To open
cursors:
■ With the hold attribute (retaining cursors across transactions),

use the setting CursorHold=YES.
■ Without the hold attribute (allowing the database to close

cursors implicitly after a Commit or Rollback call), use the
setting CursorHold=NO.
Support for Graphic Data Types

You can specify how the DB2 Graphic data type is supported
using the GraphicSupport key. Valid values are:
■ GraphicSupport=ASCHAR. Graphic data is enclosed within

the shift-in and shift-out symbols while fetching. When
executing an Insert statement, the shift-in and shift-out
characters are removed. Graphic columns are described and
treated like character data.
■ GraphicSupport=NO. An error occurs when you try to select

or insert from a Graphic column.

DB2 for OS/390-Specific Settings

DB2_CatalogOwner = SYSIBM
This setting specifies the catalog owner and is found in the

service configuration file. Specify SYSIBM if you are making
selections on the native DB2 Catalog tables.
Specify a different value for the catalog owner to limit the

number of tables retrieved by SequeLink. For example, you can
create views on the catalog, then access only your own set of
Catalog tables. If you use this option, you should create a copy of
the DB2 Catalog tables and populate them with your own data
selection.
DB2_DatabaseList =
This setting is a list of comma-separated values specifying the

databases from which tables can be retrieved by an SQLTables
call. The default is an empty string. You cannot use quotes. For
example:
DB2_DatabaseList=DSNDB04,DSNDB06
causes an SQLTables call to return table information only from

tables in the catalogs named Personnel or Invoicing.
DB2_OwnerList =
Is a list of comma-separated values specifying the owners of

tables that can be retrieved by an SQLTables call. You cannot use
quotes. For example:
DB2_OwnerList=CURRENT SQLID
specifies the connected user.

DB2_TabletypeList =
Is a list of comma-separated values specifying the table types of

the tables that can be retrieved by an SQLTables call. The default
is an empty string. You cannot use quotes. Valid values include:
TABLE
VIEW
SYNONYM
ALIAS
SYSTEM TABLE
Note: For DB2 for OS/390, DB2_DatabaseList, DB2_OwnerList,

and DB2_TabletypeList should be used as database data
dictionary filters instead of the filters described in “Database
Data Dictionary Filters” on page 186.

Informix 7 Databases
SequeLink supports INFORMIX-OnLine Dynamic Server 7,
INFORMIX-OnLine Workgroup Server 7, INFORMIX-SE 7, and
Informix Dynamic Server.
Note: The information in this section also applies to Informix 5

databases, unless stated otherwise.
Informix 7 is a relational database that runs on UNIX and

Windows NT.
SequeLink and Informix 7

Driver with Informix databases.
Table 5-12. SequeLink Functionality with Informix 7
Support Description
Binary large object support INFORMIX-OnLine Dynamic Server and
INFORMIX-OnLine Workgroup Server: Yes
(maximum size, 2 GB)
INFORMIX-SE: No
Character large object support INFORMIX-OnLine Dynamic Server and
INFORMIX-OnLine Workgroup Server: Yes
(maximum size, 2 GB), literal text value support
INFORMIX-SE: No
Cursor commit behavior Preserve (hold) or close (no hold)
Cursor rollback behavior Preserve (hold) or close (no hold)
Cursor types Read-only or read-write, hold, or no-hold
Database type Non transactional, ANSI transactional, and
non-ANSI transactional
Maximum number of concurrent open 1000
statements

Table 5-12. SequeLink Functionality with Informix 7 (cont.)
Support Description
ODBC Catalog support INFORMIX-OnLine 7: Yes:
INFORMIX-SE: No
INFORMIX-OnLine 5: No
Informix Dynamic Server 9: Yes
Stored procedure support Yes, with a maximum of one result set
Date functions CURDATE, DAYOFMONTH, DAYOFWEEK, MONTH,
NOW, QUARTER, and YEAR are supported
Math functions ABS, ACOS, ASIN, ATAN, ATAN2, COS, COT, EXP,
LOG, LOG10, MOD, POWER, ROUND, SIN, SQRT,
TAN, and TRUNCATE are supported
Outer join support left, right, all comparison, not ordered
String functions CONCAT, LENGTH, LTRIM, and RTRIM are
supported
System functions USERNAME is supported

(Informix 7)
This section lists Informix 7-specific settings and their default
values in the SequeLink Server configuration resource. The file
name depends on your platform. For platform-specific
information about changing settings, see:

Note: Do not change the setting of keys in the file that are not
listed here; they are used for backward compatibility.


Informix allows you to retain open cursors across transactions,
even after executing a Commit or Rollback call. To open cursors:
■ With the hold attribute (retaining cursors across

transactions), use the setting CursorHold = YES.

them implicitly after a Commit or Rollback call), use the
setting CursorHold = NO.
Maximum Number of Concurrent Active SQL

Statements
INF_MaxNrActiveStatements=250
This setting specifies the maximum number of concurrent active

SQL statements that a single SequeLink connection can keep
open. Valid values range between 1 to 1000.
Informix 7-Specific Settings
Table 5-13. Informix 7-Specific Settings
Platform Keys
Windows NT Client_Locale Informixdir
DB_Locale Informixserver
Dbnls Lang
DELIMIDENT Service
Host
UNIX DELIMIDENT
Informixdir
Informixserver
Note: For information about values for these keys, refer to your
Informix documentation.

Data Types (Informix 7)
Table 5-14. Data Types (Informix 7)
Informix ODBC
Byte (see note) SQL_LONGVARBINARY
Char SQL_CHAR
Date SQL_DATE
Datetime year to fraction(5) SQL_TIMESTAMP
Datetime hour to second SQL_TIME
Decimal SQL_DECIMAL
Float SQL_DOUBLE
Integer SQL_INTEGER
Interval SQL_CHAR
Money SQL_DECIMAL
Serial SQL_INTEGER
Smallfloat SQL_REAL
Text (see note) SQL_LONGVARCHAR
Varchar (see note) SQL_VARCHAR
Note: Not supported for INFORMIX-SE.

Informix 9 Databases
Informix 9 (also called INFORMIX-Universal Server) is a relational
database that runs on UNIX and Windows NT.
SequeLink and Informix 9

Driver with Informix databases.
Table 5-15. SequeLink Functionality with Informix 9
Support Description
Binary large object support Yes
Character large object support Yes
Complex data types (set, multiset, list, row) Yes (as Ivarchar)
Cursor commit behavior Preserve (hold) or close (no hold) *
Cursor rollback behavior Preserve (hold) or close (no hold) *
Cursor types Read-only or read-write, hold, or no-hold
Database type Non transactional, ANSI transactional, and
non-ANSI transactional
Distinct data types Yes
Maximum number of concurrent open 1000
statements
ODBC Catalog support Yes
Opaque data types Yes (as Ivarchar)
Smart large objects (clob, blob) Yes, no literals
Stored procedure support Yes, with a maximum of one result set
Transaction isolation levels Read uncommitted, Read committed, and
Repeatable read
*Whether cursor behavior is active depends on the CursorHold setting in the SequeLink
Server configuration resource. For more information about the SequeLink Server
configuration resource, see “SequeLink Server Configuration Resource (Informix 9)” on
page 206.

Table 5-15. SequeLink Functionality with Informix 9 (cont.)
Support Description
Date functions CURDATE, DAYOFMONTH, DAYOFWEEK,
MONTH, NOW, QUARTER, and YEAR are
supported
Math functions ABS, ACOS, ASIN, ATAN, ATAN2, COS, COT,
EXP, LOG, LOG10, MOD, POWER, ROUND,
SIN, SQRT, TAN, and TRUNCATE are
supported
Outer join support left, right, all comparison, not ordered
String functions CONCAT, LENGTH, LTRIM, and RTRIM are
supported
System functions USERNAME is supported
*Whether cursor behavior is active depends on the CursorHold setting in the SequeLink
Server configuration resource. For more information about the SequeLink Server
configuration resource, see “SequeLink Server Configuration Resource (Informix 9)” on
page 206.

(Informix 9)
This section lists Informix-specific settings and their default values
in the SequeLink Server configuration resource. The file name
about changing settings, see:



Informix allows you to retain open cursors across transactions,
even after executing a Commit or Rollback call. To open cursors:
■ With the hold attribute (retaining cursors across

transactions), use the setting CursorHold = YES.

them implicitly after a Commit or Rollback call), use the
setting CursorHold = NO.
Maximum Number of Concurrent Active SQL State-

ments
INF_MaxNrActiveStatements=250
This setting specifies the maximum number of concurrent active

SQL statements that a single SequeLink connection can keep
open. Valid values range between 1 to 1000.
Informix 9-Specific Settings
Table 5-16. Informix 9-Specific Settings
Platform Keys
Windows NT Client_Locale Informixdir
DB_Locale Informixserver
Dbnls Lang
DELIMIDENT Service
Host
UNIX DELIMIDENT
Informixdir
Informixserver
Note: For information about values for these keys, refer to your
Informix documentation.

Data Types (Informix 9)
Table 5-17. Data Types (Informix 9)
Informix ODBC
Blob (see note 1) SQL_LONGVARBINARY
Boolean (see note 2) SQL_BIT
Byte SQL_LONGVARBINARY
Char SQL_CHAR
Clob (see note 1) SQL_LONGVARBINARY
Date SQL_DATE
Datetime year to fraction(5) SQL_TIMESTAMP
Datetime hour to second SQL_TIME
Decimal SQL_DECIMAL
Float SQL_DOUBLE
Int8 SQL_BIGINT
Integer SQL_INTEGER
Interval SQL_CHAR
List SQL_LONGVARCHAR
Lvarchar SQL_LONGVARCHAR
Money SQL_DECIMAL
Notes:
1 With Informix 9, smart large objects are stored in a separate
smart blob space called an sbspace. Before you can insert
blob or clob values in your tables using SequeLink, you must
create an sbspace with the onspaces command. This sbspace
must be the default sbspace. For more information about
creating a smart blob space and making it the default, refer
to your Informix 9 documentation.
2 In Informix, a literal boolean is a character value, not a

numeric value. SequeLink supports numeric boolean literals
(0 and 1) enclosed by caret (^) symbols. For example:
INSERT INTO BOOLTABLE(BOOLCOL) VALUES (^1^)

Table 5-17. Data Types (Informix 9) (cont.)
Informix ODBC
Multiset SQL_LONGVARCHAR
Row SQL_LONGVARCHAR
Serial SQL_INTEGER
Serial8 SQL_LONGVARCHAR
Set SQL_LONGVARCHAR
Smallfloat SQL_REAL
Text SQL_LONGVARCHAR
Varchar SQL_VARCHAR
Notes:
1 With Informix 9, smart large objects are stored in a separate
smart blob space called an sbspace. Before you can insert
blob or clob values in your tables using SequeLink, you must
create an sbspace with the onspaces command. This sbspace
must be the default sbspace. For more information about
creating a smart blob space and making it the default, refer
to your Informix 9 documentation.
2 In Informix, a literal boolean is a character value, not a

numeric value. SequeLink supports numeric boolean literals
(0 and 1) enclosed by caret (^) symbols. For example:
INSERT INTO BOOLTABLE(BOOLCOL) VALUES (^1^)

OpenINGRES Databases
OpenINGRES is a relational database that runs on UNIX and
Windows NT.
SequeLink and OpenINGRES

Driver with OpenINGRES databases.
Table 5-18. SequeLink Functionality with OpenINGRES
Support Description
Binary large object support Yes
Character large object support Yes
Cursor commit behavior Close
Cursor types Read, read/write, no-hold
Maximum number of concurrent 50
open statements
Stored procedure support Yes, but SQLFetch after stored procedure execution is
not supported.
Transaction isolation levels Read uncommitted, read committed, repeatable read,
serializable
binary char, varchar, binary, varbinary
char char, integer, smallint, float, real,
double, varchar, binary, varbinary,
tinyint
date char, varchar
decimal char, numeric, decimal, integer,
smallint, float, real, double, varchar,
tinyint

Support Description
Source Target
double char, numeric, decimal, integer,
tinyint
float char, numeric, decimal, integer,
tinyint
integer char, numeric, decimal, integer,
tinyint
longvarbinary char, varchar
numeric char, numeric, decimal, integer,
tinyint
real char, numeric, decimal, integer,
tinyint
smallint char, numeric, decimal, integer,
tinyint
timestamp char, varchar
tinyint char, numeric, decimal, integer,
tinyint
varbinary char, varchar, binary, varbinary
varchar char, integer, smallint, float, real,
tinyint
Date functions CURDATE, DAYOFMONTH, HOUR, MINUTE, MONTH,
Numeric functions ABS, ATAN, COS, COT, EXP, LOG, LOG10, MOD, SIN,
SQRT, and TAN are supported
Outer join support left, right, full, nested, not ordered, inner, all
comparison

Support Description
String functions CONCAT, LCASE, LEFT, LENGTH, LOCATE_2, RIGHT,
RTRIM, and UCASE are supported

(OpenINGRES)
This section lists OpenINGRES-specific settings and their default
values in the SequeLink Server configuration resource. The file
name depends on your platform. For platform-specific
information about changing settings, see:

OpenINGRES-Specific Settings
ING_QueryTimeOut = 5
This setting specifies how long (in seconds) your query will wait
for a lock to be released by another user of the OpenINGRES
database. For more information about setting the lock mode,
refer to your OpenINGRES documentation.
ING_ReadLock = LOCK
This setting specifies whether locks are placed on records being

queried. When set to NOLOCK, no locks will be acquired on

records that are selected. This setting can be overridden when a

client application sends a SQL “set lockmode” statement.
ING_TidInStatistics = NO
Microsoft Access users sometimes encounter problems when

accessing tables with composite unique indexes in read/write
mode.
If you use Microsoft Access and receive the following error:
[INTERSOLV][ODBC SequeLink driver][OpenINGRES]

[S1000]Service - E_OP0002 optimizer ran out of
memory before generating execution plan.
turn on the ING_TidInStatistics setting

(ING_TidInStatistics=YES). After activating this setting,
make sure to reattach the table in Microsoft Access.
ING_ModifyInfoInStats = NO
With OpenINGRES, you can define a unique index on a table in

either of the following ways:
■ Using the SQL create unique index statement.
■ Using the SQL modify statement. By default, SequeLink

Server for OpenINGRES only returns SQLStatistics information
for indexes created using a create index statement.
If ING_ModifyInfoInStats = YES, SQLStatistics will return

index information for indexes created by the Modify statement.

Data Types (OpenINGRES)
Table 5-19. Data Types (OpenINGRES)
OpenINGRES ODBC
Byte SQL_BINARY
Byte varying SQL_VARBINARY
Char SQL_CHAR
Date SQL_TIMESTAMP
Float SQL_DOUBLE
Real SQL_REAL
Integer SQL_INTEGER
Integer1 SQL_TINYINT
Long byte SQL_LONGVARBINARY
Long varchar SQL_LONGVARCHAR
Money SQL_DECIMAL
Varchar SQL_VARCHAR
Decimal SQL_DECIMAL

Oracle7 Databases
The Oracle7 database is a relational database that runs on
Windows NT, UNIX, and OS/390.
SequeLink and Oracle7

Table 5-20 outlines the functionality of the SequeLink ODBC
Driver, SequeLink OLE DB Provider, and the SequeLink JDBC
Driver with Oracle7 databases.
Table 5-20. SequeLink Functionality with Oracle7
Support Description
Binary large object support Yes (maximum size 2 GB)
Character large object support Yes (maximum size 2 GB)
Cursor commit behavior Preserve
Cursor rollback behavior Preserve
Cursor types Read, read/write, hold
open statements
Transaction isolation levels Read Committed, Serializable
Outer join support left, right, nested, inner, all comparison
bigint char, numeric, decimal, integer,
bit, tinyint, bigint
bit char, numeric, decimal, integer,

Table 5-20. SequeLink Functionality with Oracle7 (cont.)
Support Description
Source Target
char char, numeric, decimal, integer,
bit, tinyint, bigint, date, time,
timestamp
date char, varchar
varchar char, numeric, decimal, integer,
timestamp

Support Description
Math functions ABS, CEILING, COS, COT, EXP, FLOOR, LOG, LOG10,
MOD, POWER, ROUND, SIGN, SIN, SQRT, TAN, and
TRUNCATE are supported
String functions ASCII, CHAR, CONCAT, INSERT, LCASE, LEFT, LENGTH,
LOCATE, LOCATE_2, LTRIM, REPEAT, REPLACE, RIGHT,
RTRIM, SOUNDEX, SPACE, SUBSTRING, and UCASE are
supported
Date/time functions CURDATE, DAYNAME, DAYOFMONTH, DAYOFWEEK,
DAYOFYEAR, HOUR, MINUTE, MONTH, MONTHNAME,
NOW, QUARTER, SECOND, WEEK, and YEAR are
supported

(Oracle7)
This section lists Oracle7-specific settings and their default values


Oracle7-Specific Settings
ArrayFetchMaxBytes=n
Some services use array fetches (bulk fetches) to fetch database

rows. This setting specifies the maximum number of bytes that
where n is a positive integer in the range of 1 to 262144 (256 KB).

open cursors.
ORA_MaxColumnsInSelect = 254
This setting specifies a limitation on the number of Select list

items. If you use Select statements with more than 254 columns in
the Select list, increase the value of this setting.
ORA_SynOnDbLinkObj_Support = YES
This setting specifies synonym support. When you make a

SQLColumns or another Data Dictionary Call (DDC), SequeLink
can support synonyms of objects that are stored using an Oracle
database link; however, when using calls such as SQLTables and
SQLColumns, providing information about these objects can
downgrade system performance. If you do not want support for
synonyms of objects that are stored using an Oracle7 database
link, change this setting to NO.
Note: If your ODBC application calls SQLProcedureColumns and

you link to remote procedures, execute oraprep.sql on the
remote Oracle7 database.

Data Types (Oracle7)
Table 5-21. Data Types (Oracle7)
Oracle7 ODBC
Char SQL_CHAR
Date SQL_TYPE_TIMESTAMP
Long SQL_LONGVARCHAR
Long Raw SQL_LONGVARBINARY
Number SQL_FLOAT
Number(p,s) SQL_DECIMAL
Raw SQL_VARBINARY
Varchar2 SQL_VARCHAR

Oracle8 Databases
The Oracle8 database is a relational database that runs on
Windows NT and UNIX.
SequeLink and Oracle8

ODBC Driver, SequeLink OLE DB Provider, and SequeLink JDBC
Driver with Oracle8 databases.
Table 5-22. SequeLink Functionality with Oracle8
Support Description
Binary large object support Yes (maximum size 2 GB)
Character large object support Yes (maximum size 2 GB)
Cursor types Read, read/write, hold
active SQL statements
Stored procedure support Yes (With SequeLink 4.5, SQLProcedures and
SQLProcedureColumns will return a full list of
procedure names, including procedures grouped in an
Oracle package.)
Transaction isolation levels Read Committed, Serializable
Outer join support left, right, nested, inner, all comparison
bigint char, numeric, decimal, integer, smallint,
float, real, double, varchar, bit, tinyint,
bigint
bit char, numeric, decimal, integer, smallint,
bigint

Support Description
Source Target
char char, numeric, decimal, integer, smallint,
bigint, date, time, timestamp
date char, varchar
decimal char, numeric, decimal, integer, smallint,
bigint
double char, numeric, decimal, integer, smallint,
bigint
float char, numeric, decimal, integer, smallint,
bigint
integer char, numeric, decimal, integer, smallint,
bigint
numeric char, numeric, decimal, integer, smallint,
bigint
real char, numeric, decimal, integer, smallint,
bigint
smallint char, numeric, decimal, integer, smallint,
bigint
tinyint char, numeric, decimal, integer, smallint,
bigint
varchar char, numeric, decimal, integer, smallint,
bigint, date, time, timestamp

Support Description
Date/time functions CURDATE, CURRENT_DATE, DAYNAME, DAYOFMONTH,
MONTHNAME, NOW, QUARTER, SECOND, WEEK, and
YEAR are supported
Numeric functions ABS, CEILING, COS, COT, EXP, FLOOR, LOG, LOG10,
MOD, POWER, ROUND, SIGN, SIN, SQRT, TAN, and
TRUNCATE are supported
String functions ASCII, BIT_LENGTH, CHAR, CONCAT, INSERT, LCASE, LEFT,
LENGTH, LOCATE, LOCATE_2, LTRIM, OCTET_LENGTH,
REPEAT, REPLACE, RIGHT, RTRIM, SOUNDEX, SPACE,
SUBSTRING, and UCASE are supported
Maximum Number of Concurrent Active SQL State-

ments
To return the correct maximum number of concurrent active SQL
statements in a connection (the Oracle parameter
open_cursors), your database administrator must execute the
following SQL statement:
grant select on v_$parameter to public
against the Oracle8 database. Otherwise, the default Oracle

setting of 50 will be returned.

(Oracle8)
This section lists Oracle8-specific settings and their default values



Note: Do not change the setting of keys in the file if they are not
Oracle8-Specific Settings
ReadOnly=DBMS
You can activate the Oracle 8 native database ReadOnly feature

by setting ReadOnly=DBMS in the .ini file or the .cfg file. In this
case, SequeLink Server for Oracle does not enforce the
ReadOnly setting; Oracle8 enforces it. For information about
which SQL statements can be processed when ReadOnly=DBMS,
refer to your Oracle documentation.

where n is a positive integer in the range of 1 to 262144
(256 KB).

open cursors.

ORA_SynOnDbLinkObj_Support = YES
This setting specifies whether synonym support will be used.

When you make a SQLColumns or another Data Dictionary Call
(DDC), SequeLink can support synonyms of objects that are stored
using an Oracle database link; however, when using calls such as
SQLTables and SQLColumns, providing information about these
objects can downgrade system performance. If you do not want
support for synonyms of objects that are stored using an Oracle
database link, change this setting to NO.
ORA_ObjectMode = YES
This setting specifies the object mode. Because SequeLink does

not support Oracle8 Object Types, initializing the connection
between the SequeLink Server and the Oracle database in object
mode is unnecessary. When ORA_ObjectMode=NO, however, a
known problem in Oracle8 prevents SequeLink from working
correctly. If Oracle Corporation fixes this problem in your Oracle
database, you can specify NO for this setting.
Data Types (Oracle8)
Table 5-23. Data Types (Oracle8)
Oracle8 ODBC
Bfile SQL_LONGVARBINARY
Blob SQL_LONGVARBINARY
Char SQL_CHAR
Clob SQL_LONGVARCHAR
Date SQL_TYPE_TIMESTAMP
Long SQL_LONGVARCHAR
Long Raw SQL_LONGVARBINARY
Nchar SQL_CHAR
Nclob SQL_LONGVARCHAR
Number SQL_FLOAT

Table 5-23. Data Types (Oracle8) (cont.)
Oracle8 ODBC
Number(p,s) SQL_DECIMAL
Nvarchar2 SQL_VARCHAR
Raw SQL_VARBINARY
Varchar2 SQL_VARCHAR

SQL Server Databases

The Microsoft SQL Server database is a relational database that
runs on Windows NT.
SequeLink and SQL Server

Driver with SQL Server.
Table 5-24. SequeLink Functionality with SQL Server
Support Description
Binary large object support Yes (For Insert and Update operations, size is limited to
65,500 bytes.)
Character large object support Yes (For Insert and Update operations, size is limited to
65,500 bytes.)
Cursor commit behavior Delete
Cursor rollback behavior Delete
Cursor types Read/write
Maximum number of Limited by
concurrent open statements system resources
Transaction isolation level Read uncommitted, read committed, repeatable read,
serializable
Outer join support left, right, full, nested, not ordered, inner, all comparison
binary char, integer, smallint, varchar, binary,
varbinary, tinyint, longvarbinary
bit char, integer, smallint, float, real,
varchar, binary, varbinary, bit, tinyint

Table 5-24. SequeLink Functionality with SQL Server (cont.)
Support Description
Source Target
char char, decimal, integer, smallint, float,
real, varchar, longvarchar, binary,
varbinary, bit, tinyint, timestamp,
longvarbinary
decimal char, decimal, integer, smallint, float,
real, varchar, binary, varbinary, bit,
tinyint
float char, decimal, integer, smallint, float,
real, varchar, bit, tinyint
integer char, decimal, integer, smallint, float,
tinyint
longvarbinary binary, varbinary, longvarbinary
longvarchar char, varchar, longvarchar
real char, decimal, integer, smallint, float,
real, varchar, bit, tinyint
timestamp char, varchar, binary, varbinary,
timestamp
tinyint char, decimal, integer, smallint, float,
tinyint
varbinary char, decimal, integer, smallint, float,
tinyint, longvarbinary
varchar char, decimal, integer, smallint, float,
real, varchar, longvarchar, binary,
varbinary, bit, tinyint, timestamp,
longvarbinary
Numeric functions ABS, ACOS, ASIN, ATAN, ATAN2, CEILING, COS, COT,
DEGREES, EXP, FLOOR, LOG, LOG10, MOD, PI, POWER,
RADIANS, RAND, ROUND, SING, SIN, SQRT, and TAN are
supported
SQL92 String functions Lower and upper are supported

Table 5-24. SequeLink Functionality with SQL Server (cont.)
Support Description
String functions ASCII, CHAR, CONCAT, DIFFERENCE, LCASE, LEFT, LENGTH,
LTRIM, REPEAT, RIGHT, RTRIM, SOUNDEX, SPACE,
SUBSTRING, and UCASE are supported
Date/time functions DAYNAME, DAYOFMONTH, DAYOFWEEK, DAYOFYEAR,
HOUR, MINUTE, MONTH, MONTHNAME, NOW, QUARTER,
SECOND, and YEAR are supported

(SQL Server)
This section lists SQL Server-specific keys and their default values
in the SequeLink Server configuration resource. For information
about changing settings on Windows NT, see Chapter 6,
“SequeLink Server for Windows NT.”
SQL Server-Specific Settings

MSSQL_USE_PROC_PREPARE = 0
By default, SequeLink does not use stored procedures during

statement preparation.
Setting this key to 1 or 2 causes the behavior documented in the

Microsoft ODBC SQL Server SQL_USE_PROCEDURE_FOR_PREPARE
help file. For more information about this setting, refer to this
help file.

MSSQL_MULTISTATEMENTS = TRUE
By default, SequeLink supports multiple concurrent SQL

statements. Setting this key to FALSE causes the server to remain
in a busy state when processing an SQL statement until all data
for that statement has been fetched. When all data for that
statement has been fetched, the server can process results for
another SQL statement.
Data Types (SQL Server)
Table 5-25. Data Types (SQL Server)
SQL Server ODBC

binary SQL_BINARY
bit SQL_BIT
char SQL_CHAR
datetime SQL_TIMESTAMP
decimal SQL_DECIMAL
decimal() identify SQL_DECIMAL
float SQL_FLOAT
image SQL_LONGVARBINARY
int SQL_INTEGER
int identify SQL_INTEGER
money SQL_DECIMAL
numeric SQL_NUMERIC
numeric() identity SQL_NUMERIC
real SQL_REAL
smalldatetime SQL_TYPE_TIMESTAMP
smallint SQL_SMALLINT
smallint identity SQL_SMALLINT
smallmoney SQL_DECIMAL
sysname SQL_VARCHAR
text SQL_LONGVARCHAR

Table 5-25. Data Types (SQL Server) (cont.)
SQL Server ODBC

timestamp SQL_VARBINARY
tinyint SQL_TINYINT
tinyint identity SQL_TINYINT
varbinary SQL_VARBINARY
varchar SQL_VARCHAR

Sybase Databases
The Sybase database is a relational database that runs on
Windows NT and UNIX.
SequeLink and Sybase

Driver with Sybase System 10/11.
Table 5-26. SequeLink Functionality with Sybase System 10/11
Support Description
Character large object support Yes (maximum size is 2 GB; see the
SYB_MAXBLOBSIZE setting)
Binary large object support Yes (maximum size is 2 GB; see the
SYB_MAXBLOBSIZE setting)
Maximum number of concurrent Stored procedures, 1; otherwise, 256
open statements
Cursor types Forward
Database type ANSI or non-ANSI transactional
Transaction isolation levels Sybase System 10: Read Committed, Serializable
Sybase System 11: Read Uncommitted, Read
Committed, Serializable
Outer join support left, right

Table 5-26. SequeLink Functionality with Sybase System 10/11 (cont.)
Support Description
bigint char, numeric, decimal, integer,
binary, varbinary, bit, tinyint, bigint
binary char, integer, smallint, float, real,
timestamp, longvarbinary
bit char, numeric, decimal, integer,
char char, numeric, decimal, integer,
binary, varbinary, bit, tinyint, bigint,
date, time, timestamp, longvarchar
date char, varchar, binary, varbinary,
date, time, timestamp
longvarbinary binary, varbinary
longvarchar char, varchar

Support Description
Source Target
time char, varchar, binary, varbinary,
timestamp char, varchar, binary, varbinary,
varbinary char, integer, smallint, float, real,
timestamp, longvarbinary
varchar char, numeric, decimal, integer,
longvarchar, binary, varbinary, bit,
tinyint, bigint, date, time,
timestamp
Math functions ABS, ACOS, ASIN, ATAN, ATAN2, CEILING, COS, COT,
DEGREES, EXP, FLOOR, LOG, LOG10, MOD, PI,
POWER, RADIANS, RAND, ROUND, SIGN, SIN, SQRT,
and TAN are supported
String functions ASCII, CHAR, CONCAT, DIFFERENCE, INSERT, LCASE,
LEFT, LENGTH, LTRIM, REPEAT, RIGHT, RTRIM,
SOUNDEX, SPACE, SUBSTRING, and UCASE are
supported

Support Description
Date functions CURDATE, DAYNAME, DAYOFMONTH,
DAYOFWEEK, DAYOFYEAR, HOUR, MINUTE,
MONTH, MONTHNAME, NOW, QUARTER, SECOND,
WEEK, and YEAR are supported

(Sybase)
This section lists Sybase-specific settings and their default values

Sybase-Specific Settings

where n is a positive integer in the range of 1 to 262144 (256 KB).



open cursors.
SYB_MAXBLOBSIZE= 200000
This setting specifies the largest image or text that Sybase can
return. Increase this value if you will be fetching large BLOBS or
CLOBS (text or images) from your Sybase database.
SYB_TDSPACKETSIZE= 512
This setting specifies the maximum size of the packets to be used

for communication between the client and server. Increasing this
value to 4096 bytes results in the best performance; however, if
you increase this value, make sure that you also increase the
maximum network packet size.
SYB_CTLIBCURSORROWS= 50
This setting specifies the number of rows used per internal fetch
call from the client to the server.
SYB_DESCNONSELECT= NO
This setting specifies whether SequeLink asks for output column

descriptions when a statement other than a Select statement is
prepared using the function call SQLPrepare. If set to NO, syntax
errors in the SQL statement are reported only when SQLExecute
is issued.
SYB_DDLINTRAN= NO
This setting specifies whether you can issue DDL statements

within a multi-statement transaction.
SYB_SERVER_CHARSET=
This setting specifies the Sybase character set you want to use
with SequeLink, for example, iso_1, cp850, cp437, mac, or
roman.

SYB_QUOTED_IDENT= NO
This setting specifies whether double-quoted character sequences

in SQL statements are interpreted as identifiers or char/varchar
character strings.
SYB_WARNINGLEVEL= 1
This setting specifies the type of database warnings returned to

the client. To dismiss all warnings, set this key to 0. To dismiss
informational warnings, set this key to 1. Important warnings or
print messages within stored procedures are still returned to the
client. To return all warnings, set this key to 2. Be aware that, if
you set this key to 2, the Diagnostics key should be set to ALL.
Data Types (Sybase)
Table 5-27. Data Types (Sybase)
Sybase ODBC
binary SQL_BINARY
bit SQL_BIT
char SQL_CHAR
datetime SQL_TIMESTAMP
decimal SQL_DECIMAL
float SQL_FLOAT
image SQL_LONGVARBINARY
int SQL_INTEGER
money SQL_DECIMAL
numeric SQL_NUMERIC
real SQL_REAL
smalldatetime SQL_TIMESTAMP
smallint SQL_SMALLINT
smallmoney SQL_DECIMAL
sysname SQL_VARCHAR

Table 5-27. Data Types (Sybase) (cont.)
Sybase ODBC
text SQL_LONGVARCHAR
timestamp SQL_VARBINARY
tinyint SQL_TINYINT
varbinary SQL_VARBINARY
varchar SQL_VARCHAR


239
6 SequeLink Server for

Windows NT
This chapter describes administration tasks you may need to

perform for SequeLink Server for Windows NT.
Where and How SequeLink Information Is

Stored
The configuration information for SequeLink Server for
Windows NT is stored in the Windows NT Registry, under
the key:
\HKEY_LOCAL_MACHINE\SOFTWARE\Intersolv\SequeLink\
40Server\instances
Note: To configure a SequeLink Server service, use the SequeLink

Server Administrator tool. Do not edit the Windows NT Registry
directly unless you are asked to do so by DataDirect Support. For
more information about configuration tasks, see “Configuring
SequeLink Server” on page 247.
Under this key, there is a subkey for each SequeLink Server

service defined on the Windows NT server. These subkeys, in
turn, contain the following subkeys:
■ General ■ Session
■ Access control ■ TCP/IP
■ Database environment ■ Compression modules
■ Connection ■ Encryption modules

240 Chapter 6 SequeLink Server for Windows NT
For information about setting subkey values, see “Changing

Configuration Settings” on page 246.
Using the SequeLink Server Administrator

Use the SequeLink Server Administrator to perform the following
tasks:
■ Add and delete services
■ Change service configuration settings
■ Monitor SequeLink system status (for example, track which

clients are using which services)
■ Control SequeLink run-time operations (for example,

interrupt client connections)
To start the SequeLink Server Administrator, double-click the

SequeLink Server Administrator icon in the SequeLink for
Windows NT (Common) Program group. The SequeLink Server
Administrator window appears.

Using the SequeLink Server Administrator 241
The SequeLink Server Administrator window is divided into two

panes. The left pane contains a tree structure, listing installed
services. When you click on a plus sign (+) in this tree, the tool
displays more information about that item. When you click on a
leaf node, the tool displays detailed information about that
attribute of that service in the right pane.
Working in Status or Configuration

Mode
The SequeLink Server Administrator window indicates the mode
in which you are working—Status or Configuration mode.
■ Status Mode allows you to monitor system status and control

run-time operations. The left pane of the window shows all
services. A green traffic light indicates that the listener is
running; a red traffic light indicates that it is stopped. Also,
this area numerically identifies the connected clients. When
you click a client number, the right pane provides specific
information about that client (for example, the client’s IP
address).
■ Configuration Mode allows you to set or change

configuration settings for SequeLink services. The left pane
shows all installed SequeLink services. When you click a tree
node, the right pane shows the settings for the subkeys that
are defined at that level.

SequeLink Server Administrator

Toolbar
Table 6-1 describes the buttons on the SequeLink Server
Administrator window toolbar.
Table 6-1. SequeLink Server Administrator Buttons
Icon Function Function Description

Configuration Switches to Configuration mode. Available
Mode only in Status mode. In configuration mode,
clicking the pushed-in button refreshes the
window.
Status Mode Switches to Status mode. Available only in
Configuration mode. In status mode, clicking
the pushed-in button refreshes the window.
Save Config Saves changes to the configuration. Available
only in Configuration mode.
Add Service Adds a service configuration. Available only in

Configuration mode.
Delete Service Deletes a service. Available only in
Configuration mode.
Start/Stop Starts or stops a service. Available only in

Status mode.
Adding Services
You can base a new service on a service template or an existing
service. Service templates are created when you install SequeLink
Server and contain default values for service parameters.

SequeLink Server services are identified by a unique SequeLink

service name and TCP port number. You will be prompted for
these values.
To add a service:
1 In Configuration mode, click the Add Service button. A
dialog box appears with a drop-down list box listing all
service templates and existing services. Existing services are
identified by the designation “Copy of”).
2 Select the service template or existing service on which you

want to base the service that you want to add. When you
select the template or existing service, the edit boxes for the
SequeLink service name and TCP port show the default
values for these settings.
3 Enter a unique value for the SequeLink service name and the
TCP port, or use the defaults. The SequeLink Server
Administrator verifies that the port you specify is not being
used by any other service on your server.
Note: If you do not use the default values, default SequeLink

Client installations will not be able to connect to this server.
For instructions on changing TCP port numbers, see
“Changing the TCP Port Number” on page 251.
4 Click OK.
5 Click the Start/Stop button to start the new service.
Deleting Services
1 In Status mode, verify that the SequeLink service that you
want to delete is not running. If it is running, stop the service
before continuing.
2 In Configuration mode, select the service you want to delete.

3 Click the Delete Service button. You are asked to confirm the
deletion.
4 Click OK to confirm the deletion.
5 Click the Save Config button.
Upgrading SequeLink 4.0 Services

When a SequeLink service is installed, previous versions are not
automatically overwritten. Upgrading your 4.0 services to the
current 4.x version ensures that the latest service executables are
used and any new configuration settings are available. When you
upgrade, any attributes that you have configured for your
SequeLink Server services are retained and used, such as TCP port,
user authentication level, and SSDD settings.
To upgrade your SequeLink Server 4.0 software to 4.x:

1 Using the SequeLink Server Administrator in Status mode,
verify that the service that you want to upgrade is stopped. If
it is not stopped, select the service; then, click the Start/Stop
button.
This action interrupts all connections to this service.
2 In Configuration mode, select the service that you want to

upgrade.
3 Select Action/Upgrade service. A dialog box appears listing all

versions of the service templates to which you can upgrade.
4 Select the appropriate service template version, and click OK.
5 Click the Save Config button to save the configuration.
6 In Status mode, click the Start/Stop button to start the

service.

Starting and Stopping Services

When you upgrade a service or change the TCP port number for
a service, you must stop and restart the service.
To start or stop a service:

1 In Status mode, click the service you want to start or stop. A
green light indicates services that are running; a red light
indicates services that are not running.
2 Click the Start/Stop button. You are asked to confirm the

start or stop operation.
3 Click OK to confirm.
Note: Stopping a service stops all running service processes.

Before you stop a service, make sure that no users are
connected.
Stopping a Service Process for a

Specific User
There are times when you may want to stop a service process for
a particular user, such as when a user’s client machine has
stopped without disconnecting.
In status mode, you can view the following information about

each service:
■ Number of clients connected to the service
■ Host name or IP address of each client connected to the

service
■ Windows NT user name used to connect to the service
■ Time the connection was made

To stop a service process for a specific user:

1 Click the number corresponding to the service process you
want to stop.
2 Click the Start/Stop button. You are asked to confirm the start
or stop operation.
3 Click OK to confirm.
When you stop a service process while a client application is

running, the user will receive a network read error.
Displaying Host Names and IP

Addresses
In status mode, the symbolic host names of clients are shown by
default (not the IP addresses). IP address are resolved to the host
name by accessing the hosts database. If the Windows NT server
is using DNS and the DNS server is heavily loaded, this request
may be time consuming and affect the response time of the
SequeLink Server Administrator. You can then decide whether to
display client IP addresses instead of host names.
To display IP addresses in status mode:
Start the SequeLink Server Administrator with the following

command line option:
-clientip
Changing Configuration Settings

1 In configuration mode, double-click the value you want to
change. An edit dialog box appears.
2 Type the new value.

Configuring SequeLink Server 247
3 Click the Save Config button to save the new configuration.

The service will use the new value for subsequent
connections.
Configuring SequeLink Server

You can perform the following configuration tasks:
■ “Activating and Deactivating Services” on page 247
■ “Setting the User Authentication Level” on page 248
■ “Setting Connection Refusal Message Details” on page 249
■ “Specifying the Authorized Applications List” on page 250
■ “Setting a Default Domain Name” on page 250
■ “Changing the TCP Port Number” on page 251
■ “Turning the Logging Option On and Off” on page 252
■ “Specifying the Log File Directory” on page 252
■ “Setting AutoStart for Services” on page 253
■ “Setting the Shutdown Grace Period for Services” on

page 253
Activating and Deactivating Services

To deny access to a particular service for new connections
without interrupting current connections, you can deactivate a
service. For example, you may want to deactivate a service when
you change configuration parameters. Clients connecting to a
deactivated service will receive a connection error, indicating
that the service is inactive.

Note: Alternatively, you can stop a service, interrupting all

current connections and refusing any new connection requests.
Clients requesting a connection to a stopped service will receive a
network error.
This configuration option is controlled by the

access control\Active subkey. Valid values include:
Yes Activates a service

No Deactivates a service
For instructions on changing configuration values, see “Changing

Setting the User Authentication Level

This configuration option is controlled by the access
control\AuthenticationLevel subkey. Valid values include:
Client or The user ID and password provided by the client

leave blank are used to log on the Windows NT server.
Values specified in the access control\HostUser
and access control\HostPassword subkeys are
ignored. The service process runs under the local
system account of the Windows NT server.
Server The user ID and password specified in the
access control\HostUser and
access control\HostPassword subkeys are used to
log on the Windows NT server.
Note: For local users of the Windows NT server
on which SequeLink Server is installed, specify
the local domain explicitly in the
access control\HostUser key or in the
access control\Domain key. This will speed user
authentication, if your Windows NT server is not
a primary domain controller.

None No user authentication is performed. Values

specified in the access control\HostUser and
access control\HostPassword subkeys, or in the
data source definition at the client are ignored.
The service process runs under the system
account of the Windows NT server. Use this
value only for the following types of SequeLink
Server services:
■ DB2 Universal Database V5
■ Informix
■ Microsoft SQL Server (when configured to

use standard or mixed security)
■ Oracle (when no OPS$ accounts are used)
■ Sybase
For more information about server-defined host user definitions,

see “Using Server-Defined Host User Definitions” on page 149.
For instructions on changing configuration values, see
“Changing Configuration Settings” on page 246.
Setting Connection Refusal Message

Details
refused. Alternatively, the server can return a basic error
message, with minimal details, to the client so that an
unauthorized user cannot receive further information about
your security system. In this case, a message is sent to the Event
log facility with details about why the connection was refused.


access control\ReasonCode key. Valid values include:
detailed A detailed description about why the

connection was refused is returned to the client.
basic A minimal description about why the
connection was refused is returned to the client.
Specifying the Authorized Applications

List
You can limit access to SequeLink Server services to a list of
specific applications. Before the service will accept any SQL
statement, the client application must identify itself to the service
with its application ID. This configuration option specifies which
application IDs will be accepted and is controlled by the access
control\Appld key.
Specify application IDs as a list of strings separated by semicolons.

For example:
myOrderEntry;theBossesReport
The list cannot contain spaces and no trailing blanks after the last
specified application ID. An empty value for this key indicates
that any application can access the service.
For more information about how a client application identifies

itself to the service, see “Limiting Access to SequeLink Server
Services” on page 125.
Setting a Default Domain Name

You can specify a default domain name. This is the domain that
will be used if a domain name is not specified in the user name. If
this subkey is not configured (is empty), the local machine will be

used as the domain. This configuration option is controlled by

the access control\Domain subkey.
Note: For local users of the Windows NT server on which

SequeLink Server is installed, specify the local domain explicitly
in the user name in the client data source definition or in the
access control\Domain key. This will speed user authentication, if
your Windows NT server is not a primary domain controller.

Changing the TCP Port Number

TCP/IP services are identified by a unique TCP port number. This
configuration option is controlled by the tcp/ip\TcpPort subkey.
Notes:
■ Before you change a TCP port number, make sure that it is

not being used by another service. Check the SERVICES file in
your SYSTEM32/drivers/etc directory for entries with the
format xxxx/tcp, where xxxx is a port number. TCP port
numbers lower than 1024 are reserved (for example, for
Telnet) and cannot be used. The maximum TCP port number
that you can specify is 65534.
■ The port number on the client and server must match. If you
change the port number on your server, change it in your
client configuration also.
■ If you have SequeLink Server services running on multiple

servers, you may want to configure the same port number on
each server. This will allow you to configure the same port
for every client.
■ After you change the port number for a service, you must
stop and restart that service.

■ The SequeLink Server Administrator verifies that the port you

have specified is not being used by another service (including
a SequeLink 3.5 service, SequeLink 4.0 service, or any other
service defined in the SYSTEM32\drivers\etc\services file). If
another service is using this port, you can use this port for
your new service; however, you must stop the other service,
before you can start using the new service. If the other service
is not a SequeLink service, we recommend that you do not use
the port of the other service.

Turning the Logging Option On and Off

Logging allows you to trace what data was sent from the client to
the server and what data was returned. This configuration option
is controlled by the connection\Logging subkey. Valid values
include:
No Logging is turned off.

Yes Logging is turned on.
Note: Because logging uses considerable disk space and slows

processing, it is recommended that you turn on the logging
option only when you are troubleshooting. After creating the log
file, turn off logging.

Specifying the Log File Directory

By default, the log files that are generated when the logging
option is turned on are placed in the logging subdirectory of the
SequeLink Server directory. You can override this default

directory in the service configuration resource. If the user under

which the service process runs does not have write permission to
that directory, the default is used.

connection\LoggingPath subkey. Valid values include:
Blank The default value is used.

Fully qualified pathname The log file will be created in the
of the log file specified directory.

Setting AutoStart for Services

SequeLink Server services can be started automatically when the
Windows NT system is started. This configuration option is
controlled by the tcp/ip\AutoStart subkey. Valid values include:
Yes or blank The AutoStart option is turned on.

No The AutoStart option is turned off.

Setting the Shutdown Grace Period for

Services
When you stop a service, most of its processes are stopped
immediately, except those that are in a blocked state waiting for
an external event from the database. You cannot restart a
stopped service if it has service processes still running.

This option allows you to set the maximum number of seconds

that blocked processes are allowed to exist before they are killed.
general\ShutDownGracePeriod subkey. Valid values include:
blank The default value of 180 seconds is used.

A value in seconds The grace period is set to this value.

Preparing Services for SequeLink Client Access

During installation, the Installer prompts you for the steps you
need to perform to prepare your SequeLink Server services for
SequeLink ODBC, OLE DB, or JDBC Client access. Database
preparation is required for:
■ Informix
■ Oracle7
■ DB2
You can prepare the database during installation or after

installation. For example, you may need to prepare your Informix
database after installation if you add an Informix database to
your database system.
For instructions on preparing your database, refer to the


Running SequeLink Server 3.5 and 4.x Services on the Same Server 255
Running SequeLink Server 3.5 and 4.x

Services on the Same Server
When you install SequeLink Server 4.5, it does not overwrite
older versions of SequeLink Server. This allows you to install
SequeLink Server 4.5 and test it without interfering with your
current production environment. You can run SequeLink Server
3.5 and SequeLink Server 4.x services concurrently on the same
server. However, if you do, you must identify them with a unique
SequeLink service name and port number. Also, make sure that
you are using the correct configuration in your SequeLink client
data sources.
On Windows NT, SequeLink Server services are uniquely

identified by the TCP port on which they listen for incoming
connection requests. To run SequeLink Server 3.5 and 4.x services
concurrently on the same server, you must assign them different
TCP ports. The SequeLink Server Administrator 4.x verifies that
the TCP port you specify is not being used by another service on
the server. You also must specify this port number in the
SequeLink data source at your clients. For more information
about using the SequeLink CAT and SequeLink data sources, see
“Using the SequeLink CAT” on page 52.
To test a new SequeLink Server 4.x service using an existing

SequeLink Client data source, assign the new service the same
TCP port number as a SequeLink Server 3.5 service using that
data source. Before you can start the SequeLink Server 4.x
service, stop the SequeLink Server 3.5 service using the
SequeLink Server Administrator 3.5.
Note: Testing a new SequeLink Server 4.x service using an

existing SequeLink data source may interfere with your current
production applications.

Upgrading SequeLink Server 3.5 Services

to 4.x
Note: Only SequeLink Server 3.5 services using TCP/IP support can
be upgraded using the following procedure. TCP/IP (UDP) services
cannot be upgraded. You must add a new SequeLink Server 4.x
service and update your SequeLink data sources at your clients to
use TCP/IP.
1 Using the SequeLink Server Administrator 3.5, stop the

SequeLink Server 3.5 tcpsrvext service you want to upgrade.
Note the TCP port that it is using and any configuration
settings that you have changed.
2 Using the SequeLink Server Administrator 4.0, define a new

SequeLink Server 4.x service and assign it the TCP port that
the SequeLink Server 3.5 service was using. In addition,
change the configuration values of the newly created 4.x
service to the values that are used in the 3.5 SequeLink
service.
The SequeLink Server Administrator 4.x will warn you that a

SequeLink Server 3.5 service is using this port. Click YES.
3 Start the SequeLink Server 4.x service. Your SequeLink clients

will be able to access the SequeLink Server 4.x service without
any change in their configuration.
4 Using the SequeLink Server Administrator 3.5, delete the

SequeLink Server 3.5 service.

257
7 SequeLink Server for UNIX

perform for SequeLink Server for UNIX.
Note: Commands and filenames on the UNIX operating system

are case-sensitive. Make sure that you enter commands and
filenames described in this guide exactly as shown.

Stored
For SequeLink Server for UNIX, all executable and configuration
files are stored in subdirectories of the SequeLink Server
directory. The name and location for this directory is specified
during installation. The default location for this directory is /usr/
sqlnk. The slsrvfg file is a shell script for the SequeLink Server
Administrator.
Service executables are stored in subdirectories of the SequeLink

Server directory. To use a particular service, you first must define
the service using the SequeLink Server Administrator. All service
attributes are stored in a service configuration file.
All service configuration files are stored in the subdirectory

instances. The service configuration files are named
ServiceName.cfg, where ServiceName is a unique name
identifying a particular service. The same directory also contains
a shell script which starts the service executable.
Service configuration files are created and administered using

the SequeLink Server Administrator tool.

258 Chapter 7 SequeLink Server for UNIX
Using the SequeLink Server Administrator

The SequeLink Server Administrator is a command line tool for
administering SequeLink Server services on UNIX. Use this tool to
create and edit service configuration files and shell scripts in the
directory instances.
Some actions require additions and deletions of SequeLink

Server-specific entries in the /etc/services and /etc/inetd.conf
system files. If the SequeLink Server Administrator is used under
the root account, these edits are performed automatically.
Alternatively, the SequeLink Server Administrator can generate a

shell script with commands you can issue to perform these
additions and deletions. The SequeLink Server Administrator will
prompt you for this option. If your account privileges do not
allow you to edit these files, the SequeLink Server Administrator
generates a shell script which you must run (with root privileges)
to complete this task.
Starting the SequeLink Server

Administrator
You can start and use the SequeLink Server Administrator in
Interactive or Batch mode. In Interactive mode, you can perform
multiple actions in the same interactive session. In Batch mode,
you must specify all the parameters.
Note: To quit the SequeLink Server Administrator, issue the

following command: quit.

To start the SequeLink Server Administrator in Interactive mode:

1 Issue the following command:
slsrvcfg
2 Perform the appropriate action by issuing the following
command:
ActionName ActionParameters
Note: For a description of ActionName and
ActionParameters, see “Specifying Actions and
Parameters” on page 259.
To start the SequeLink Server Administrator in Batch mode:

1 Issue the following command:
slsrvcfg ActionName ActionParameters

Note: For a description of ActionName and
ActionParameters, see “Specifying Actions and
Parameters” on page 259.
Specifying Actions and Parameters

Regardless of whether the SequeLink Server Administrator is
started in Interactive or Batch mode, you use it by specifying the
action you want to be performed and supplying the parameters
required for that action.
For example, you would enter:
ActionName ActionParameters
where:
ActionName indicates the action to be taken. You can

specify the full action name or use the
abbreviated form. For example, to create
a new service, use NewService or ns.

ActionParameters specifies details about the action to be

taken. Action parameters are positional;
if you leave them empty, you will be
prompted to supply them in interactive
mode.
The following section lists configuration tasks you may need to

perform, action commands for that action (ActionName) and the
parameters required to perform that action
(ActionParameters). After specifying the action and
parameters, you may need to run the generated shell script to
make the appropriate edits to /etc/services and /etc/inetd.conf,
and refresh inetd, if necessary.


■ “Adding Services” on page 261
■ “Deleting Services” on page 263
■ “Upgrading SequeLink 4.0 Services” on page 263
■ “Obtaining a List of Valid Configuration Actions” on

page 263
■ “Obtaining a List of Existing Services” on page 263
■ “Obtaining a List of Existing Service Templates” on page 264
■ “Managing Connections” on page 264
■ “Displaying Service Attributes” on page 266
■ “Editing Service Configuration Sections” on page 266
■ “Setting Parameter Values” on page 267
■ “Activating and Deactivating Services” on page 267
■ “Setting the User Authentication Level” on page 268
■ “Setting Connection Refusal Message Details” on page 269
■ “Changing the TCP Port Number” on page 271
Adding Services
When you add a service, you can base that service on a service
template or an existing service. Service templates contain default
values for service parameters and are created when you install

SequeLink Server. You can use the default values or change these
values later with the SequeLink Server Administrator.
A SequeLink Server service is identified by a unique service name

and TCP port number. You will be prompted for these values
when you add a service.
Adding a Service Based on a Service Template

NewService|ns servicetype servicename portnr
where:
servicetype is the name of the service template on which

you are basing this service.
servicename is a unique name for this service.
portnr is a unique TCP port for this service. You can
specify any available port in the range of 1024
to 65534.
Adding a Service Based on an Existing Service

CopyService|cs oldservice newservice portnr
where:
oldservice is the name of the existing service on which

you are basing this service.
newservice is a unique name for this service.
portnr is a unique TCP port for this service. You can
specify any available port in the range of 1024
to 65534.

Deleting Services
DeleteService|ds servicename
where servicename is the name of the service you want to

delete.
Upgrading SequeLink 4.0 Services

When a SequeLink Server is installed, previous versions are not
automatically overwritten. Upgrading your 4.0 services to the 4.x
version ensures that the latest service executables are used and
any new configuration settings are available. When you
upgrade, any attributes that you have configured for your
SequeLink Server services are retained and used, such as TCP
port, user authentication level, and SequeLink Shadow Data
Dictionary settings.
UpgradeService|us servicename servicetype

upgrade and servicetype is the name of the template version
to which you want to upgrade.
Obtaining a List of Valid Configuration

Actions
Help|h
Obtaining a List of Existing Services

ListServices|ls

Obtaining a List of Existing Service

Templates
ListserviceTypes|lt
Managing Connections
All SequeLink connections are recorded in the sqlnksrv.log file,
which is located in the logging subdirectory of the SequeLink
Server installation directory. You can use commands to list the
connections in this file, truncate the file, and kill active
connections.
Listing Connections in sqlnksrv.log

listconnections [servicename]
lc [servicename]
This command displays a list of all the current connections for the
service mentioned in servicename. If no service name is
specified, this list is displayed for all services.
Under each service name in the list, the following information is

displayed for a connection:
■ pid of the process that corresponds to the connection
■ Logon ID under which the service process runs
■ Client IP address in DNS format (when name resolution is

successful) or numeric format
■ Start time of the connection

Truncating sqlnksrv.log
TruncateLog [number of lines to leave]
tl [number of lines to leave]
This command truncates the server log file to the number of

lines specified (the default is 100). It also ensures that the syslog
is refreshed correctly.
Killing an Active Connection

killconnection servicename [pid]
kc servicename [pid]
This command kills one or more SequeLink client connections

based on the following rules:
■ If the pid parameter is specified, the SequeLink

Administrator verifies that this pid represents a connection
to the service specified with the servicename parameter.
Upon successful verification, the Administrator (running in
interactive mode) displays a prompt to confirm the
disconnection.
■ If the pid is specified but the Administrator cannot verify it,

the command is aborted and, running in interactive mode, a
message is displayed.
■ If no pid is specified, all connections for the service are

killed. If the Administrator is running in interactive mode, it
displays a prompt to confirm the disconnections for the
specified service.

Displaying Service Attributes

This command displays the service attributes in the [session],
[connection], or [environment] sections of the service
configuration file. For more information about the attributes in
the [session] section, see “Database-Specific Information” on
page 182.
DisplayParameters|dp servicename [session|connection|environment]
where:
servicename is the name of the service for

which you want to display
attributes.
[session|connection| is the section of the service
environment] configuration file for which you
want to display attributes.
Editing Service Configuration Sections

This command starts the editor defined in $EDITOR (or vi),
allowing you to edit service attributes in a particular section. For
more information about the attributes in the [session] section,
see “Database-Specific Information” on page 182.
EditConfig|ec servicename [session|connection|environment]
where servicename is the name of the service whose attributes

you want to edit.

Setting Parameter Values

This command sets the values of the parameters in the [session],
[connection], or [environment] sections. For more information
about the attributes in these sections, see “Database-Specific
Information” on page 182.
SetParameter [session|connection|environment] parameter value
where:
[session|connection| is the section of the service

environment] configuration file for which you
want to set parameters.
parameter is the name of the parameter you
want to set.
value is the value to which you want to
set the parameter.
Activating and Deactivating Services

There are times when you may need to deny access to a
particular service for new connections without interrupting
current connections, such as when you want to change
configuration parameters. Clients connecting to a deactivated
service will receive a connection error indicating that the service
is inactive.
To activate a service:
EnableService|es servicename

activate.

To deactivate a service:
SuspendService|ss servicename

deactivate.
Setting the User Authentication Level

SetAuthentication|sa servicename [CLIENT|SERVER|NONE] username
where:
servicename is the name of the service for which you

want to set the user authentication level.
[CLIENT|SERVER| is the level of user authentication. Valid
NONE] values include:
CLIENT or The user ID and password
blank provided by the client will
be used to log on. Values
specified in
[access control]\HostUser
are ignored.
SERVER The user ID specified in
[access control]\HostUser
will be used to log on. The
host user ID must be
specified; the password is
not required.

NONE User authentication will

not be performed. The
service process will run as
root. Values in the data
source definition at the
client are ignored. This
value should be used only
if the database provides
user authentication.
Databases that provide
user authentication
include Oracle (if no OPS$
account is used), Sybase,
and Informix.
username is the UNIX user under which the server
process will run when the authentication
level is set to SERVER.
For more information about server-defined host user definitions,

see “Using Server-Defined Host User Definitions” on page 149.
Setting Connection Refusal Message

Details
refused. Alternatively, the server can return a basic error
message, with minimal details, to the client, so that an
unauthorized user cannot receive further information about
your security system. In this case, a message is sent to the syslog
facility with details about why the connection was refused.
SetReasonCode|sr servicename [basic|detailed]

where:
servicename is the name of the service for which you want

to set the connection refusal message.
detailed specifies that a detailed description about
why the connection was refused will be sent
to the client.
basic specifies that a minimal description about
why the connection was refused will be
returned to the client.
For more information about connection refusal messages, see

“User Authentication” on page 117.

List
statement, the client application must identify itself to the service
with its application ID.
SetApplicationIds|si servicename [application_id_list][append]
where:
servicename is the name of the service for which

you want to specify authorized
applications.
application_id_list is a list of application IDs that can
use the service. The application IDs
in this list must be separated by
semicolons. No spaces or tabs are
allowed. Omitting this parameter
will delete any existing application
ID list, allowing all client
applications access to the service.

append specifies that the application ID list

will be appended to any existing
application ID list.

Changing the TCP Port Number

TCP/IP services are started by inetd, the UNIX Internet daemon.
Each SequeLink Server service is identified as a separate Internet
service, like FTP or Telnet, with a unique TCP port number.
All inetd services are described in the files /etc/services and /etc/
inetd.conf. The file /etc/services contains a list of mappings
between inetd service names and their corresponding port
number. The file /etc/inetd.conf links the inetd service names to
the executable files for the service. The inetd service names are
used internally by inetd.
When you define a new service, the SequeLink Server

Administrator proposes default values for the TCP ports. For a
list of TCP port defaults, see Table 3-1, “Default Symbolic Names
and TCP Port Numbers for SequeLink Server Services” on
page 108.
Note: If your UNIX server subscribes to NIS, it obtains the service

name-to-TCP port mappings from the master /etc/services file on
your NIS server.
To change the TCP port number:

1 Create a new service, copying the service for which you want
to change the TCP port.
This new service will serve as a temporary service. When you

create it, use any unused TCP port, except for the TCP port

with which you eventually want to complete the

configuration (the target TCP port).
2 Delete the original service.
3 Copy the temporary service that you created in Step 1, using

the target TCP port and the service name of the service you
deleted in Step 2.
4 Delete the temporary service you created in Step 1.
Note: The client must specify the TCP port number for the service
at connection. Alternatively, the client can use a symbolic service
name. For platform-specific information about using symbolic
names and TCP ports, see:

and Windows NT”

Windows 3.1”

■ Chapter 14, “SequeLink OLE DB Edition Client for Windows 9x
and Windows NT”

Logging allows you to trace the data that is sent and returned.
When you turn logging on, you also can specify where you want
the log file to reside. By default, log files are placed in the home
directory of the user under which the service process is running.

Preparing Services for SequeLink Client Access 273
To turn logging on:

EnableLogging|el servicename [loggingpath]
where:
servicename is the name of the service for which you

want to turn on logging.
[loggingpath] is the fully qualified path of the log file to
be created. If this parameter is omitted,
the corresponding attribute is cleared.

processing, we recommend that you turn on the logging option
only when you are troubleshooting. After creating the log file,
turn off logging.
To turn logging off:

SuspendLogging|sl servicename
where servicename is the name of the service for which you

want to turn off logging.
Preparing Services for SequeLink Client Access

During installation, the Installer prompts you for the steps you
need to perform to prepare your SequeLink Server services for
SequeLink ODBC, OLE DB, or JDBC Client access. Database
preparation is required for:
■ Informix
■ Oracle7
■ DB2
You can prepare the database during installation or after

installation. For example, you may need to prepare your

Informix database after installation if you add an Informix

database to your database system.
For instructions on preparing your database, refer to the

Running SequeLink Server 3.5 and 4.x Services

on the Same Server
When you install SequeLink Server 4.x, it does not overwrite older
versions of SequeLink Server. This allows you to install SequeLink
Server 4.x and test it without interfering with your current
production environment. You can run SequeLink Server 3.5 and
SequeLink Server 4.x services concurrently on the same server.
However, if you do, you must assign them a unique SequeLink
service name and port number. Also, make sure that you are
using the correct configuration in your SequeLink client data
sources.
On UNIX, SequeLink Server services using TCP/IP support are

uniquely identified by a TCP port. Connection requests are
serviced by inetd, the standard Internet daemon. Services serviced
by inetd are listed in the file /etc/inetd.conf. Corresponding TCP
port numbers for these services are stored in the file /etc/services.
Note: If your UNIX server is a NIS client, the TCP port numbers for
these services are stored in the /etc/services file on your NIS server.
To run SequeLink Server 3.5 and 4.x services concurrently on the

same server, you must assign them different TCP ports. The
SequeLink Server Administrator 4.x verifies that the TCP port you
specify is not being used by another service specified in the /etc/
services file on the server (or the /etc/services file on your NIS
server, if the UNIX server is a NIS client). You also must specify this
port number in the SequeLink data source at your clients. For

Running SequeLink Server 3.5 and 4.x Services on the Same Server 275
more information about using the SequeLink CAT and SequeLink

data sources, see “Using the SequeLink CAT” on page 52.
To test a new SequeLink Server 4.x service using an existing

SequeLink data source, assign the new service the same TCP port
number as a SequeLink Server 3.5 service that is accessed by that
data source. Before you do this, you must comment out or
remove the lines in /etc/inetd.conf and in /etc/service for the
existing 3.5 service and refresh inetd.
To refresh inetd, send a SIGHUP signal:
kill -HUP inetdpid
where inetdpid is the process ID of the inetd daemon.
To restore the SequeLink Server 3.5 service, delete the SequeLink

Server 4.x service with the SequeLink Server Administrator 4.x.
Then, replace the lines you removed in /etc/inetd.con and /etc/
services, and refresh inetd.
Note: Testing a new SequeLink Server 4.x service using an

existing SequeLink data source may interfere with your current
production applications.


277
8 SequeLink Server for AS/400
AS/400 This chapter describes administration tasks you may need to

perform for SequeLink Server for AS/400.

Stored
A separate initialization file exists for each SequeLink Server
AS/400 service in the SequeLink Product Library. The name of the
initialization file consists of the concatenation of the string 'SS'
and the service name.
Table 8-1 lists the names of initialization files used for SQLNKALL
and SQLNKNONE services. These service initialization files are
configured automatically when you install SequeLink Server.
Table 8-1. Service Initialization Files (AS/400)
Isolation Level Network Protocol Service name Initialization File

Cursor stability (SQLNKALL) TCP TCPALL SSTCPALL
No Commit (SQLNKNONE) TCP TCPNONE SSTCPNONE
Cursor stability (SQLNKALL) APPC APPCALL SSAPPCALL
No Commit (SQLNKNONE) APPCN APPCNONE SSAPPCNONE
The initialization file contains options that are read each time a
connection is established. The file must be stored in the

278 Chapter 8 SequeLink Server for AS/400
SequeLink Product Library. Initialization files contain parameters

that control the following options:
■ ASCII-to-EBCDIC and EBCDIC-to-ASCII conversion

■ Binary data support
■ Database names
■ Default isolation levels
■ Logging
■ Translation
Table 8-2 lists parameters that can be changed in the service

initialization file.
Table 8-2. Initialization Parameters for SequeLink Server for

AS/400
Parameter Purpose
Asctoebc Specifies the names of the library and
table to be used when performing
ASCII-to-EBCDIC conversion on data
from the client.
Binarysupport Specifies whether “For Bit data” is
supported by this service.
Database Specifies the library list that to be
used with this service.
Defaultisolationlevel Specifies the default isolation level
used for this service.
Ebctoasc Specifies the names of the library and
table to be used when performing
EBCDIC-to-ASCII conversion on data
from the client.
Logging Specifies whether log files will be
created for each connection.
Translate Specifies whether ASCII-to-EBCDIC
and EBCDIC-to-ASCII translations will
be performed by the server.

Note: To change parameters in the service initialization files, use

the EDTSQSRV command in the SequeLink Product Library or use
the OS/400 Source Entry utility.

■ “Changing AS/400 SNA Definitions” on page 279
■ “Setting Translation Options” on page 279
■ “Turning Binary Support On and Off” on page 285
■ “Changing the Default Class Description” on page 285
■ “Changing the Default Isolation Level” on page 286
■ “Creating and Deleting User-Defined Services” on page 287
Changing AS/400 SNA Definitions

For information about changing SNA definitions, see “AS/400”
on page 135.
Setting Translation Options

ASCII-to-EBCDIC and EBCDIC-to-ASCII character code translation
can be performed at the server or client. To control where
translation will be performed, set the Translate parameter.

For translation at the:
■ Client, set the Translate parameter to *NO.
■ AS/400 server, set the Translate parameter to *YES. This is

the default. If you set this parameter to *YES, you also must
specify the table names that will be used by specifying the
Asctoebc and Ebctoasc parameters.
Conversion Table Name Formats

Your AS/400 system supplies different conversion tables,
depending on the type of conversion you want to perform. These
tables reside in the library QUSRSYS. Names of ASCII-to-EBCDIC
conversion tables have the following format:
Qxxxyyyzzz
where:
xxx is the ASCII code page on the client.

yyy is the character ID on the host.
zzz is the EBCDIC code page on the host.
For example: Q850337285.
Names of EBCDIC-to-ASCII conversion tables have the following

format:
Qzzzyyyxxx
where:
zzz is the EBCDIC code page on the host.

yyy is the character ID on the client.
xxx is the ASCII code page on the client.
For example: Q285337850.

ASCII-to-EBCDIC Conversion
For ASCII-to-EBCDIC conversion, specify an appropriate value for
the Asctoebc parameter. Table 8-3 lists the values you can use
for ASCII-to-EBCDIC conversion by country:
Table 8-3. ASCII-to-EBCDIC Conversion Tables
Country Conversion Table Name

Multinational Q850337500
Austria Q437337273
Belgium Q850337500
Denmark Q850337277
Finland Q850337278
France Q437337297
Germany Q850337273
Italy Q437337280
Netherlands Q850337037
Norway Q850337277
Portugal Q850337037
Spain Q850337284
Sweden Q437337278
Switzerland Q850337500
United Kingdom Q437337285
United States Q850337037

EBCDIC-to-ASCII Conversion
For EBCDIC-to-ASCII conversion, specify an appropriate value for
the Ebctoasc parameter. Table 8-4 lists the values you can use
for EBCDIC-to-ASCII conversion by country:
Table 8-4. EBCDIC-to-ASCII Conversion Tables
Country Conversion Table Name

Multinational Q500337850
Austria Q273337437
Belgium Q500337850
Denmark Q277337850
Finland Q278337850
France Q297337437
Germany Q273337437
Italy Q280337437
Netherlands Q037337850
Norway Q277337850
Portugal Q037337850
Spain Q284337850
Sweden Q278337437
Switzerland Q500337850
United Kingdom Q285337437
United States Q037337850
Conversion Example
For translation at the AS/400 server using United States version
code tables Q850337037 (ASCII-to-EBCDIC) and Q037337850

(EBCDIC-to-ASCII), specify the following values for the

Translate, Asctoebc, and Ebctoasc parameters:
Parameter Value
ASCTOEBC Q850337037
ESCTOEBC Q037337850
TRANSLATE YES

List
statement, the client application must identify themselves to the
service with their application ID.
The list of application IDs that have access to SequeLink Server

services can be set or changed in the service initialization file. In
the section, Access control, the list of valid application IDs is
listed in the AppId keyword:
[access control]
AppId = Accounting;Invoicing;
In this example, two applications have access to the SequeLink

Server service, Accounting and Invoicing.
The application ID can only be an alphanumeric value and

cannot contain any blanks.



The logging option for SequeLink Server for AS/400 creates a log
file for every connection to the AS/400 server. All log files are
called QPRINT. They can be accessed using the AS/400 command
WRKOUTQ.
To access the information logged for a specific connection, you

locate and access the log file created at the approximate time the
connection was made. Remember to disconnect from the server
before examining the log file. This ensures that all packets
associated with a specific connection are written to the file.
To turn on logging:
Set the LOGGING parameter in the service initialization file

to YES.

your server’s processing, we recommend that you turn on the
logging option only when you are troubleshooting. Also, to
conserve disk space, remove the spooled log files from your
system after printing them.
To turn off logging:
Set the LOGGING parameter in the service initialization file to NO.

This is the default.
Note: In addition to logging, you can use the following methods

to trace problems that may occur on the client or server:
■ Message queue. Information about network and operating

system problems are logged in the message queue. Use the
DSPMSG QSYSOPR command to view the list of messages in
the queue. If you want more information about a specific
message, use the Help function.
■ Job logs. Job logs are useful for detecting problems and will
be created if the job description used has the appropriate

entries. For more information about using job logs, refer to

your AS/400 documentation.
Turning Binary Support On and Off

SequeLink supports “for bit data” on both char and varchar
columns. SequeLink detects the difference between a char
column and a char for bit data column based on the CCSID of
that column. Normally, char columns are assigned the CCSID the
system is using and the char for Bit data columns are assigned a
CCSID of 65535.
If columns containing char data are created with a CCSID of

65535, the client receives the data within these columns in
hexadecimal format. Binary support can be switched off by using
the Binarysupport key in the Connection section of the service
Changing the Default Class Description

During installation, routing entries are added to the QCMN
subsystem if your network protocol is APPC. In these routing
entries, the SEQCLS class is used for SequeLink. This class resides
in the SequeLink product library. Table 8-5 shows the defaults for
SEQCLS:
Table 8-5. Defaults for the SEQCLS Class (AS/400)
Description Defaults for SEQCLS

Library LLLLLLLLLL
Run priority 20
Time slice, in milliseconds 3000
Eligible for purge *YES
Default wait time, in seconds 30

Table 8-5. Defaults for the SEQCLS Class (AS/400) (cont.)
Description Defaults for SEQCLS

Maximum CPU time, in milliseconds *NOMAX
Maximum temporary storage in KB *NOMAX
Text SequeLink Class
The primary parameters that affect system performance are:
■ Run priority. For optimal system performance, all jobs

running in the same storage pool should run at the same run
priority; however, you may want certain jobs to run faster.
Batch jobs usually run at priority 50; interactive jobs usually
run at 20. If you have not created a separate storage pool for
interactive jobs, we suggest that you run all SequeLink jobs at
the same run priority so that SequeLink jobs will not have to
wait until all interactive (terminal) activity has stopped before
being swapped into memory.
■ Time slice. This parameter defines how long a job can

remain in a storage pool before it is swapped out to make
room for jobs with a higher run priority. Because swapping
takes time and some SQL actions may need a couple of
seconds to complete, we suggest that you set this value to 3
seconds.
Changing the Default Isolation Level

When a connection is established to a SequeLink Server service,
the service is assigned a default isolation level specified by the
Defaultisolationlevel key in the Connection section of the service

Valid values for the default isolation level include:
■ RR (repeatable read)
■ RS (read stability)
■ CD (cursor stability)
■ UR (uncommitted read)
■ NC (no commit)
If no value is specified, an isolation level value of NC (no commit)

is assumed.
Note: The default isolation level can be changed by the client

application by sending SQLSetConnAttr for
SQL_ATTR_TXN_ISOLATION; however, this must be done before
the first SQL statement is processed.
Creating and Deleting User-Defined

Services
When SequeLink Server is installed, TCPALL and TCPNONE
services are configured as the default services, if TCP was
specified as the connection method. If APPC was specified as the
connection method, APPCNONE and APPCALL are configured as
the default services.
You can create other user-defined SequeLink services. For

example, you may want to do this to have:
■ Multiple services for different databases (library lists)

■ Different services with different isolation levels
■ Different services for different groups of users

To create user-defined services:
Use the command CRTSQSRV in the SequeLink product library.
For TCP services:

CRTSQSRV SRVNAME(NAME) PROTOCOL(TCP)
PORTNR(9999)
where NAME is the name of the service you are creating.
Notes:
a For user-defined TCP services, you must specify an

available port number for the service.
b Newly created user-defined TCP services will not be

available for use until you stop and restart the TCP
spawner.
For APPC services:

CRTSQSRV SRVNAME(NAME) PROTOCOL(APPC)
where NAME is the name of the service you are creating.
To delete user-defined services:
Use the DLTSQSRV command. For example:
DLTSQSRV SRVNAME(NAME) PROTOCOL(TCP) PORTNR(9999)

or
DLTSQSRV SRVNAME(NAME) PROTOCOL(APPC)
where NAME is the name of the service you are deleting.

Calling Initialization Programs 289
Calling Initialization Programs

SequeLink Server for AS/400 allows you to call an AS/400
program when you log on the database—for example, to
perform initialization tasks. You specify the program you want
to run in the SequeLink Data Source attributes in the database
attribute on the client. The command specified will be run when
a connection is established using this data source.
For example, when specifying SQADDLIBLE MYLIB in the

database attribute, the program SQADDLIBLE will be invoked at
connection and MYLIB will be passed as the first parameter. The
SQADDLIBLE program is shipped with the AS/400 server and adds
the library passed in the first parameter to the library list of the
current job.
Note: To invoke a self-written program, make sure that the

program can be found from within the server process by placing
the program object in the SequeLink product library or by fully
qualifying the program.
The following programs, whose names are reserved, are shipped

with SequeLink Server for AS/400:
SQADDLIBLE Adds a list of libraries to the top of the user

library list.
SQAPPLIBLE Adds a list of libraries to the bottom of the
user library list.
SQRPLLIBLE Replaces the library list with a new one.

Issuing OS/400 Commands

In a way similar to how SequeLink allows you to execute SQL
statements, it also allows you to execute OS/400 commands on
the server. If preceded by OS400CMD, OS/400 commands are
detected by the server process and executed.
Example A:
The following command:
OS400CMD: CALL PGM(QGPL/REORGANIZE)
causes the server process to execute the program REORGANIZE

stored in the library QGPL. After this program is executed, control
is returned to the client process.
In example A, the execution of OS/400 commands is synchronous,

meaning that the client process waits for the OS/400 to complete
before continuing.
To execute long-running OS/400 commands asynchronously, use

the OS/400 command SBMJOB, as shown in example B.
Example B:
OS400CMD: SBMJOB CMD(RGZPFM FILE(QGPL/ORDERS))
JOB(RGZORD)
causes the server process to activate a separate job on the server

in which the command RGZPFM FILE(QGPL/ORDERS) is executed.
After the separate job is activated, control returns to the client
process, allowing the client to continue other operations.
When an error occurs in executing an OS/400 command, an error

message is returned to the client. For detailed information about
the error, examine the joblog of the server job.
Standard security-checking is performed before the server

executes an OS/400 command. A user who does not have

Multimember Support 291
authority to perform specific OS/400 operations, will receive an

error message when they attempt to do so.
Multimember Support
Native AS/400 applications sometimes store data in members.
Members are subsets of rows within a table to which a separate
name is assigned (member name). These rows can be accessed by
specifying the member name.
If the database used by applications has been created on the

AS/400 with single member tables and all SQL statements default
to this member, these applications cannot identify the member
substructure. To access data in a database that uses the
multimember technique, SequeLink allows you to set the name
of the member you want to use before executing the SQL
command that actually accesses the data.
To do this, you can execute the OS/400 command with the

OVRDBF command.
Example:
Suppose an AS/400 native application exists which stores all

orders in a file called ORDERS. This application uses one member
each month. To retrieve the orders for March, enter the
following commands:
OS400CMD: OVRDBF FILE(ORDERS) TOFILE(QGPL/ORDERS) MBR(MARCH)

Select * from ORDERS
Note: Remember that the file override will remain active until a
new OVRDBF is issued for the same file or the DLTOVR command
is used.
For more information about file overrides, refer to your IBM DB2
documentation.


293
9 SequeLink Server for OS/390
OS/390 This chapter describes the administration tasks you may need to
perform for SequeLink Server for OS/390.

Stored
The system configuration information for SequeLink Server for
OS/390 is stored in the system initialization file (referred to as
the SYSINI file). The SYSINI file resides in the CNTL library and
contains parameters that control how the server operates. This
file is loaded at server startup.
The database configuration information for SequeLink Server

for OS/390 is stored in the database configuration file:
■ SRVCDB2 (for DB2)

■ SRVCORA7 (for Oracle7)
These files reside in the CNTL library and contain

database-specific parameters that control client connections to
the server. The database configuration file is loaded at server
startup and accessed when each connection is made. For more
information about database configuration information, see
Chapter 5, “Using SequeLink With Your Database.”
The SYSINI Data Definition name (ddname) of the server’s JCL

code points to the SYSINI file. The SYSINI file can be a sequential
file or a member of a Partitioned Data Set (PDS) with RECFM=FB,
LRECL=80, and BLKSIZE set to a multiple of 80. For example:
//SYSINI DD system_ini_file,DISP=SHR

294 Chapter 9 SequeLink Server for OS/390
The SYSINI file contains entries that control the behavior of the
following items:
■ SequeLink Server base components

■ DB2 Call Attachment Facility (CAF) interface
■ Network interface
■ Runaway task detection
■ Enhanced error recovery
■ File caching
The SYSINI file consists of sections with associated keys. Sections

are enclosed in square brackets ([ ]). A typical SYSINI file might
look like this:
;
; Sample SequeLink for OS/390 SYSINI file. "Sections" are enclosed
; in square brackets and their associative "keys" immediately
; follow them. The section names in this example all start in
; position 1, and the keys are indented for clarity/readability,
; but the section names and their associative keys can begin
; anywhere on the statement.
;
; Comments are identified with a semicolon. A line
; consisting entirely of blanks may also be inserted to improve
; readability.
;
; All specifications are case-insensitive.
;
; Restrictions :
;
; Duplicate section names must not be specified.
;
; Service names and loadmodule names in the SERVICE section
; cannot exceed eight characters.
;
; The underscore character (_) should NOT be used in any key
; value. The underscore is reserved for use by the
; SequeLink for OS/390 SYSINI parsing mechanism.
;
; For startable components and applications, LAUNCH=YES may

Where and How SequeLink Information Is Stored 295
; be specified to cause that component to be automatically

; started during SequeLink for OS/390 initialization.
; Valid SequeLink for OS/390 startable components are:
;
; APPC APPC/LU6.2 Network Interface Manager
; IBM_XTCP/IP IBM TCP/IP Network Interface Manager (TCP)
; DB2_ifid DB2 Application Support Package
; for a specific DB2 interface id.
; INSTRUMENTATION_INTERFACE SNA/LU2 Instrumentation Interface
;
;If the LAUNCH parameter is omitted for any startable component
;or the component is not started. LAUNCH is
;not valid for any other section.
;
;
[ASSORTED_PARMS]
TIMERINTERVAL=60 ;Timer tick interval

COMMANDBUFFERS=20 ;Operator command buffers
SWAP=NO ;Swappable (YES or NO)
SMFRECORDTYPE=197 ;SMF record type
RECOVERY=ON ;Turn on recovery
RESTARTS=3 ;Max # of restarts after failure
COMMANDCHARACTER=! ;Command recognition character
SUBSYSID=SQLK ;SequeLink for OS/390 SSID
[IBM_XTCP/IP]
LAUNCH=YES ;Start this NIM at initialization

MAXIMUMSESSIONS=128 ;Max # of concurrent TCP/IP sessions
TRACE=NO ;Turn off internal tracing
DEBUG=NO ;Not running in debug mode
USERID=TCPIP ;IBM TCP/IP address space userid
ETCSERVICES=TCPIP.ETC.SERVICES;Name of ETC.SERVICES dataset
SOSLIMIT=1024 ;Short on storage limit in K
[APPC]
LAUNCH=YES ;Start this NIM at initialization

VTAMAPPLNAME=SRS01ACB ;SequeLink for OS/390 APPC server ACB name
MAXIMUMSESSIONS=200 ;Max # of concurrent APPC sessions

MAXIMUMPACKETSIZE=32000;Maximum packet size

INACTIVITYTIME=30 ;# seconds before session declared idle
[DB2_DSNA]
;Since DSNA is the first DB2 interface specified, it becomes

;the “default interface”, i.e. DSNA will be the DB2 interface
;associated with any DB2 service(s) defined without a
;DB2INTERFACE parameter
SUBSYSTEMNAME=DSN ;DB2 address space subsystem id

TRACETABLESIZE=64 ;DB2ASP internal trace table size
THREADCLOSEOPTION=ROLLBACK ;Default thread termination option
DB2STOPOPTION=LEAVE ;Status of DB2 connection if DB2 dies
MAXIMUMTHREADS=0 ;Max # of concurrent threads to DB2
DEFAULTPLAN=SQLNKPLA ;Default DB2 plan
[DB2_DSNG]
SUBSYSTEMNAME=DSNG ;DB2 address space subsystem id

THREADCLOSEOPTION=ROLLBACK;Default thread termination option
MAXIMUMWAITINGTHREADS=50 ;Max # of sessions waiting on DB2 thread
DEFAULTPLAN=SQLNKPLG ;Default DB2 plan
[MESSENGER]
INITIALBUFFERS=300 ;Initial # of logging buffers

BUFFERINCREMENT=50 ;Logger buffer expansion increment
MAXIMUMBUFFERINCREMENT=5 ;Max # times buffers will be expanded
ROUTECODE=11 ;Route code for console messages
DESCRIPTORCODE=06 ;Descriptor code for console messages
[INSTRUMENTATION_INTERFACE]

LAUNCH=YES ;Start this component at initialization

VTAMAPPLNAME=SRS0IACB ;ACF/VTAM applname
SECURITY=Y ;Security required
AUTHORIZATIONCHECK=N ;Additional security req'd for auth cmds
SECURITYCLASS=FACILITY ;Auth cmds security class name
[SERVICES]
; Use loadmodule VAICDB2X for any DB2 version
MVSDB23=VAICDB2X ;DB2 service=loadmodule (DB2 v3 service)

MVSDB24=VAICDB2X ;DB2 service=loadmodule (DB2 v4 service)
MVSORA7=VAICORAX ;DB2 service=loadmodule (Oracle7 service)
;
;DB2 services
;
;if DB2INTERFACE is omitted from DB2 service entries, the default
;DB2 interface (DSNA) is assigned as the associative DB2
interface
;
[SERVICE_MVSDB23]
DB2INTERFACE=DSNA ;Name of DB2 interface

MAXIMUMSESSIONS=60 ;Maximum # of concurrent sessions
LOGHLQ=SQLNK.DB23.V4R5M1 ;High level qualifier for packet log
VOL=TBS023 ;Volume serial number of packet log
UNIT=3390 ;Unit to allocate packet log
;MGMTCLAS=EMNB1ND ;SMS Management class of packet log
;STORCLAS=BASE ;SMS Storage class of packet log
IDLETIME=30 ;Idle time before action is taken
IDLEACTION=MESSAGE ;Action taken if svc is stalled
SECURITY=SAFBASIC ;Security checking
UIDMAP=MAP1 ;Userid mapping
RECOVERY=ON ;Activate restart/recovery
ABENDEXIT=VAICDB2J ;Exit taken at abnormal end
DUMPOPTION=FIRSTONLY ;Control how dumps are taken
CONVERSION=Y ;Activate ASCII/EBCDIC conversion
DISPATCHPRIORITY=1 ;Dispatching priority of service
PLAN=SL450C4 ;DB2 plan name that will be used
PORT=4007 ;TCP port used by service

THROTTLE=30 ;Maximum CPU time per timer cycle

MAXCPUTIME=100 ;Total amount of CPU time allowed
RATACTION_THROTTLE=LOG ;Action taken if THROTTLE exceeded
RATACTION_MAXCPUTIME=LOG ;Action taken if max CPU time exceeded
CFGFILE=SQLNKCFG ;Sequelink configuration file
ATOETRT=VAILATE2 ;Service specific ASCII/EBCDIC table
ETOATRT=VAILTEA2 ;Service specific EBCDIC/ASCII table
[SERVICE_MVSDB24]
DB2INTERFACE=DSNG ;Name of DB2 interface

UIDMAP=MAP2 ;Userid mapping
ABENDEXIT=VAICDB2J ;Exit taken at abnormal end
RATACTION_MAXCPUTIME=LOG ;Action taken if total CPU time exceeded
CFGFILE=SQLNKDB2 ;Sequelink configuration file
[SERVICE_MVSORA7]
SUBSYSID=MPMA ;OS/390 SSID of your Oracle database

LOGHLQ=SQLNK.ORA ;High level qualifier for packet log


RATACTION_MAXCPUTIME=LOG ;Action taken if total CPU time exceeded
CFGFILE=SQLNKORA ;Sequelink configuration file
[FILECACHE]
SQLNKDB2=CACHED
SQLNKORA=CACHED
[UIDMAP_MAP1]
SMITH=SMITHA
ERICK=ERICKA
UIDNOTFOUND=DENY


To customize SequeLink Server, modify the keys in the
appropriate sections of the SYSINI. Table 9-1 shows the different
sections in the SYSINI and the attribute that they control.
Table 9-1. SYSINI Sections (OS/390)
Section Description
[ASSORTED_PARMS] Controls server tasks.
[MESSENGER] Controls message logging.
[INSTRUMENTATION_INTERFACE] Controls monitoring of the server.
[DB2_ifid] Controls DB2 assistance routines.
[SERVICES] Controls services that clients may
request from their workstations.
[SERVICE_servicename] Controls service or application
behavior. servicename
identifies the service.
[APPC], [IBM_XTCP/IP] Controls network protocol
behavior.
[FILECACHE] Controls file caching.
[UIDMAP_mapname] Controls userid mapping for DB2
services.

Modifying Base Component

Parameters
The [ASSORTED_PARMS], [MESSENGER], and
[INSTRUMENTATION_INTERFACE] sections contain parameters
that control SequeLink Server’s base components. Table 9-2 lists
the base component parameters you can customize and provides
a description and valid values.
Table 9-2. Base Component Parameters (OS/390)
Section Parameter Description

[ASSORTED_PARMS] COMMANDBUFFER This specifies the number of
command buffers to be allocated for
the server operator interface. It
represents the maximum number of
outstanding server operator
commands that can be allocated at
one time. The default is 10. Valid
values include any number in the
range of 5 to 20.
COMMANDCHARACTER This specifies the subsystem ID
command recognition character.
There is no default.
You can comment out
COMMANDCHARACTER and SUBSYSID
by preceding these parameters with
a semicolon (;). SequeLink will run
normally, a subsystem ID will not be
used, and commands cannot be
issued with a command character,
but, you can use the OS/390 modify
command or the SequeLink
Instrumentation Interface to issue
commands.

Table 9-2. Base Component Parameters (OS/390) (cont.)

RECOVERY This turns on and off the
restart/recovery feature for an
application or eligible SequeLink for
OS/390 component. Valid values
include ON or OFF.
The RECOVERY parameter also can be
specified in any [SERVICE] section or
an eligible SequeLink for OS/390
component section. When specified
in the [ASSORTED_PARMS] section,
this parameter applies to the entire
SequeLink for OS/390 system. If
specified in a [SERVICE] section, it
applies to that service only.
If RECOVERY=OFF, recovery is
turned off for the entire SequeLink
for OS/390 address space. In the
[ASSORTED_PARMS] and [SERVICE]
sections, the default is
RECOVERY=OFF. For eligible
SequeLink for OS/390 components
sections, the default is
RECOVERY=ON.
Eligible SequeLink for OS/390
components include:
APPC
INSTRUMENTATION_INTERFACE
IBM_TCP/IP
MESSENGER
DB2_ifid
Note: We recommend that you do
not turn off recovery for these
components unless advised by
MERANT Technical Support.


RESTARTS This specifies the maximum number
of times a component will be
automatically restarted after a
failure. The default is 3.
Note: Automatic restart affects
SequeLink for OS/390 core
components only and can only be
specified in this section. User services
are never automatically restarted.
SMFRECORDTYPE This specifies the System
Management Facilities (SMF) record
type to be used for SMF records
produced by the server. If the value is
0, SMF recording is turned off. The
default is 197.
Also, change the OS/390 SMF
parameters (SMFPRMxx member of
the SYS1.PARMLIB). Issue the
command SET SMF=xx to make
them effective.
SUBSYSID This specifies a unique OS/390
subsystem ID for SequeLink Server.
Note: The subsystem ID must be
unique. Look in the OS/390
Subsystem Name table (IEFSSNxx
member of SYS1.PARMLIB) to make
sure that the subsystem ID is not
already defined.
See the description for
COMMANDCHARACTER for related
information.
SWAP This specifies whether the server
address space is swappable. The
default is YES.


TIMERINTERVAL This specifies the server heartbeat
interval, a time-driven task which
posts the server's tasks when the
specified time interval has elapsed
and alerts the server about possible
stalled tasks. The default is 30
(seconds).
[MESSENGER] BUFFERINCREMENT This specifies the number of
additional message logging buffers
that will be allocated when the
initial number is allocated. The
default is 50.
COMPONENTTRACE This specifies the server components
for which tracing will be turned on.
Tracing can be turned on for all
components (ALL) or specific
components (component ID).
To turn on tracing for a specific
component, specify one of the
following values:
■ A - APPC component
■ C - Shared component
■ D - DB2 component (not
available)
■ I - Instrumentation Interface (II)
component
■ H - CSHELL component
■ S - Server controller component
■ X - TCP/IP component


This parameter should be specified
for each component for which
tracing will be turned on. For
example, the following lines:
CMPTRACE(T)
CMPTRACE(I)
turn on tracing for the IBM TCP/IP
and II components of the server.
Messages are logged in the server's
log files (VAILOGP and VAILOGS).
DESCRIPTORCODE This specifies the WTO descriptor
code for all messages directed to a
console by the message logging task.
The default is 06.
INITIALBUFFERS This specifies the initial number of
buffers to be allocated by the server
message logging task. The default is
150.
MAXIMUMBUFFERINCREMENT This specifies the maximum number
of times the message logging task
will allocate additional buffers. The
default is 5. If the message logging
task cannot allocate message buffers,
log messages will be lost.
ROUTECODE This specifies the Write-to-Operator
(WTO) route code for all messages
directed to a console by the message
logging task. The default is 11.


TERMINALTRACE This specifies the clients for which
tracing will be turned on. Tracing can
be turned on for all clients (ALL) or
for specific clients (terminal ID). To
turn on tracing for an individual
client, provide its identifier in string
format (16-byte maximum).
The format of the terminal ID varies,
depending on the network protocol
used by the client. Supply the
appropriate network type:
■ For APPC, supply the VTAM LU
name of the client workstation.
■ For TCP/IP, supply the TCP/IP

address of the client.
USERIDTRACE This specifies the users for which
tracing will be turned on. Tracing can
be turned on for all users (ALL) or
for specific users (user ID) up to a
maximum of 20 users.
[INSTRUMENTATION_ AUTHORIZATIONCHECK This turns on and off additional
INTERFACE] security features. The default is N
(No).
LAUNCH This parameter is used to
automatically start the
instrumentation interface at
initialization. Valid values are YES
and NO. The default is NO. If YES,
you first must define the
VTAMAPPLNAME and make changes
to the VTAMLST dataset. If you start
with NO, use the modify command to
issue SequeLink operator commands.


SECURITY This specifies whether a user logging
on the II will be verified through
your security system. The default is Y
(Yes).
Note: For Oracle7, this means host
user ID and password verification.
SECURITYCLASS This parameter is used only when
AUTHORIZATIONCHECK=Y. It
specifies whether a general resource
class name is used by the server. The
default is FACILITY. Within this
class, the following classes of users
exist:
■ SQLNKACC. These users are
granted read-only access to the II.
They can log on the II, but are
limited to issuing display-type
commands. These users cannot
alter the way the server operates.
■ SQLNKAUT. These users can issue

any server command normally
entered from an operator’s
console.


VTAMAPPLNAME This specifies the ACF/VTAM
application ID to be used for the II.
Make sure that you give this name to
your ACF/VTAM administrator to
include in the VTAMLST. The default
is SRS0IACB.
Note: The COMPONENTTRACE, TERMINALTRACE, and

USERIDTRACE parameters can be omitted from the SYSINI. If you
do this, tracing is not used. You can activate tracing at any time
by issuing the LOGR ALTER operator command.
Modifying Multiple DB2 Interface

Parameters
SequeLink Server for OS/390 can be connected to multiple DB2
address spaces concurrently. The number of DB2 address spaces
that can be connected to concurrently is limited only by the
system resources that are available to the SequeLink for OS/390
address space, such as storage and CPU cycles.

The [DB2_ifid] section contains parameters required by the

CAF. Table 9-3 lists the DB2 interface ID (ifid) parameters you
can customize and provides a description and valid values for
each parameter.
Table 9-3. DB2 Interface ID (ifid) Parameters (OS/390)

[DB2_ifid] DB2STOPOPTION This affects the DB2ASP connection to
the DB2 address space when a DB2
shutdown occurs. Valid values include:
■ LEAVE allows the current
connection to the DB2 address
space to remain active. It also
allows DB2ASP to be notified
immediately when DB2 is back
online, so that it can reinitialize the
DB2ASP environment. This is the
default.
■ BREAK breaks the connection to

the DB2 address space by issuing a
DB2 DISCONNECT request, if DB2
becomes unavailable. You must
explicitly issue the DB2 CONNECT
ID=ifid operator command to
reestablish the connection with the
DB2 address space when DB2
becomes available again.
DEFAULTPLAN This specifies the DB2 plan name that
will be used if the plan name is
omitted from the DB2 service entry in
the SYSINI. If the DB2ASP facility is
turned on, this parameter is required.
Specify one of the following default
plans shipped with SequeLink Server:
■ SL451C5 (for DB2 V5R1)

Table 9-3. DB2 Interface ID (ifid) Parameters (OS/390) (cont.)

ifid This specifies the interface ID of the
SequeLink for OS/390 DB2ASP
component. ifid can be 1 to 4
characters in length. A DB2ASP root
segment is launched for each
[DB2_ifid] section in the SYSINI.
Each DB2 service in the SYSINI should
specify the DB2 interface ID that is
associated with that service using the
ID specified in the DB2INTERFACE
parameter in the service’s SYSINI
definition. If a DB2 service is invoked
and the DB2INTERFACE parameter
has not been specified, the default
DB2 interface ID will be used.
The DB2 interfaces will be launched as
their [DB2_ifid] sections in the
SYSINI are detected.
There is no default. If the SYSINI
contains [DB2_] instead of
[DB2_ifid], the error message
VAIL012E will be returned when you
try to connect to the SequeLink Server
service.


MAXIMUMTHREADS This specifies the maximum number of
DB2 threads that can execute
concurrently. The default is 0 (no
thread management). A nonzero value
from 1 to nnnn, where nnnn is the
DB2 maximum thread limit, turns on
the SequeLink for OS/390 thread
management facility.
If you exceed the MAX BATCH
CONNECT value for your DB2
configuration, OPEN_THREAD failures
may occur. Do not confuse this value
with the maximum number of DB2
sessions that SequeLink Server can
handle concurrently. SequeLink Server
ensures that the number of active
thread attachments to the DB2 address
space does not exceed this value,
preventing SequeLink Server from
violating DB2’s MAX BATCH CONNECT
value.
Note: The thread management facility
cannot be turned on or off by operator
command. For example, if you set this
value to 0, you cannot change it using
the DB2 ALTER THREADS command.
MAXIMUMWAITINGTHREADS This specifies the maximum number of
DB2 sessions that can be waiting on an
available thread. When this threshold
is reached, subsequent attempts to
open a DB2 thread will be rejected and
an error will be returned to the service.
The default is 100.


SUBSYSTEMNAME This specifies the subsystem ID of the
DB2 address space. This value cannot
exceed 4 characters and is required if
the DB2ASP facility will be activated. If
SUBSYSTEMNAME (DB2 ssid) is
omitted from the DB2 interface
definition, ssid defaults to the
interface ID name (ifid).
TRACETABLESIZE This specifies the number of entries of
the DB2ASP circular trace buffer. Each
entry is 32 bytes. The default is 128
entries. Each call to the DB2ASP
interface is recorded in the trace buffer
so that application flows can be
analyzed if problems occur. The trace
buffer is automatically formatted and
printed if DB2ASP unexpectedly stops.
THREADCLOSEOPTION This specifies the DB2 CLOSE_THREAD
termination option that will be used if
this value is omitted from the service’s
CLOSE_THREAD request. Valid values
include COMMIT and ROLLBACK. The
default is ROLLBACK.
Example:
The following example shows SYSINI entries that may be

specified to allow SequeLink Server for OS/390 to connect to the
DB2 address spaces DSNP and DSNT.
Note: In this example, there are three DB2 interfaces defined—

DSNA, DSNB, and DSNC. DSNA and DSNC are both entries for
DSNP; DSNB is an entry for DSNT.

[DB2_DSNA]
;Since DSNA is the first DB2 interface specified, it becomes

;the “default interface”, i.e. DSNA will be the DB2 interface
;associated with any DB2 service(s) defined without a
DB2INTERFACE
;parameter
SUBSYSTEMNAME=DSN ;DB2 address space subsystem ssid

THREADCLOSEOPTION=ROLLBACK ;Default thread termination option
MAXIMUMTHREADS=0 ;Thread management is disabled
DEFAULTPLAN=SQLNKPLA ;Default DB2 plan
[DB2_DSNB]
SUBSYSTEMNAME=DSNT ;DB2 address space subsystem ssid

DEFAULTPLAN=SQLNKPLB ;Default DB2 plan
[DB2_DSNC]
SUBSYSTEMNAME=DSNP ;DB2 address space subsystem ssid

DEFAULTPLAN=SQLNKPLC ;Default DB2 plan
[SERVICES]
MVSDB23=VAICDB2X ;Production DB2 application

MVSDB24=VAICDB2X ;Test DB2 application

[SERVICE_MVSDB23]
;If DB2INTERFACE is omitted from DB2 service entries,
;the default DB2 interface (DSNA) is assigned as the associated
;DB2 interface
;
;Production DB2 application
;
DB2INTERFACE=DSNA ;Name of DB2 interface
...
THROTTLE=30 ;Maximum amount of CPU time per timer cycle
...
[SERVICE_MVSDB24]
;
;Test DB2 application
;
DB2INTERFACE=DSNB ;Name of DB2 interface
...
THROTTLE=30 ;Maximum amount of CPU time per timer cycle
Modifying Service Parameters

The [SERVICES] section allows you to specify which services that
clients can request. Multiple SequeLink DB2 services can be
defined with their own set of specific settings.

Specifying Available Services

To specify services that clients can request, create an entry with
the following format:
clientservicename=servicemodulename
where:
clientservicename is the 1- to 8-character service name the

client specifies to invoke a service when
using TCP/IP.
servicemodulename is the 1- to 8-character loadmodule name
of the service.
Note: The built-in service CONNECT does not need to be

specified with this entry. This service is reserved for MERANT
internal use.
Modifying General Service Parameters

Service names point to service entries. For example,
MVSDB2=VAICDB2X points to SERVICE_MVSDB2, where
VAICDB2X is the OS/390 loadmodule name of the DB2 service. A
different [SERVICE_servicename] must be created for every
service that is defined.

Table 9-4 lists the general service parameters you can customize
and provides a description and valid values for each parameter.
Table 9-4. General Service Parameters (OS/390)

[SERVICE_SERVICENAME] ABENDEXIT This can be specified to invoke an exit
routine when the service abnormally
terminates. An ABENDEXIT can be
used to format critical control block
structures to help with debugging.
The exit must exist in the
JOBLIB/STEPLIB datasets or in the
LNKLST concatenation. If both
ABENDEXIT and EOTEXIT are
specified, ABENDEXIT receives
control before EOTEXIT. If omitted,
no abend exit routine is invoked.
This parameter is ignored by Oracle7.
ATOETRT This specifies the loadmodule name
of the ASCII-to-EBCDIC customized
translation table (for more
information, see “Modifying the
ASCII-to-EBCDIC Tables (Optional)”
on page 335.
CFGFILE This specifies the ddname of the
Sequelink configuration file. The
ddname must be unique and must be
specified in the [FILECACHE] section
of the SYSINI.
CONVERSION This specifies whether
ASCII-to-EBCDIC translation will be
performed. Valid values include Y
(Yes) and N (No).
The default is Y. If omitted, the error
message VAIIL011W is returned.
DATACLAS This specifies the data class of the
NETSRVR.LOG file. If you do not use
this class, delete this parameter.

Table 9-4. General Service Parameters (OS/390) (cont.)

DISPATCHPRIORITY This determines a service's
dispatching priority within the
SequeLink Server address space.
Specify a value from 0 to 9, with 0 as
the highest priority and 9 as the
lowest. If unspecified, 0 is assumed,
all user services are assigned the same
dispatching priority, and all user
services compete as peers for CPU
cycles.
Note: SequeLink Server core
components execute at a higher
dispatching priority than user
services.
DUMPOPTION This can be specified in any
[SERVICE_SERVICENAME] section to
control how dumps are taken when a
service abnormally terminates. Valid
values include:
■ NODUMP. No dumps are taken
when a service terminates
abnormally.
■ FIRSTONLY. A dump is taken for

the first abnormal termination
only; any subsequent abnormal
terminations for the service do
not produce dumps. If
unspecified, a dump will be
produced.
ETOATRT This specifies the loadmodule name
of the EBCDIC-to-ASCII customized
translation table (for more
information, see “Modifying the
ASCII-to-EBCDIC Tables (Optional)”
on page 335.


EOTEXIT This can be specified in any [SERVICE]
section to invoke an end-of-task
routine when the service terminates.
Use it to perform task cleanup not
provided by the service or to capture
service accounting information. The
exit must exist in the server's
JOBLIB/STEPLIB datasets or in the
LNKLST concatenation. If omitted, no
end-of-task routine is invoked.


EXECLIBDDNAME This specifies the ddname of the DD
definition defining the PDS that
contains the service load module.
Note: The DD definition must be
specified in the startup JCL for
SequeLink Server.
You also can authorize a service by
using the string 'AUTH' after the
ddname.
If the EXECLIBDDNAME parameter is
omitted, the service load module is
assumed to reside in the server’s
JOBLIB/STEPLIB or the OS/390 LNKLST
concatenation, and the service is
considered authorized.
For example:
EXECLIBDDNAME=(APPNLIB,
AUTH) specifies that the dataset
referenced by the APPNLIB DD
definition contains authorized
services. This keyword allows a
service to invoke authorized OS/390
functions, such as the MODESET SVC.
If AUTH is used, the dataset defined
by the ddname must reside in the
OS/390 APF list and the executable
load module must have been
linkedited with the AC=1 attribute.


IDLEACTION This specifies the action to be taken
by the server when a stalled service is
detected and is applicable only when
the IDLETIME parameter has a
nonzero value.
Valid values include:
■ ABORT terminates the service
immediately.
■ MESSAGE posts a message

(VAIS163W) to the server log file
and to the operator console and
allows the service to continue
running. This is the default.
■ IGNORE bypasses the facility to

detect stalled conditions (same as
IDLETIME=0).
IDLETIME This specifies the maximum time the
service can be idle before the action
determined by the IDLEACTION
parameter is taken. This time is
measured in server time intervals (as
determined by the TIMERINTERVAL
parameter in the [ASSORTED_PARMS]
section). Use this parameter to detect
possible stalled services. If this
parameter is unspecified or set to 0,
stalled services will not be detected.


LOGHLQ This specifies the high-level qualifier
of the dynamically allocated dataset
used to record SequeLink packet
trace entries and service-generated
debugging entries, when
tracing/debugging is turned on for
this service.
The trace dataset name has the
following format:
hlq.NETSRV.LOG.T#nnnnnn
The debug dataset name has the
following format:
hlq.DEBUG.LOG.T#nnnnnn
where:
■ hlq is the high-level qualifier
(maximum of 24 characters). If this
qualifier is omitted, the user ID
entered at the client is used.
■ nnnnnn is the thread identifier

that is linked to a specific client
workstation.
MAXCPUTIME The total amount of CPU time (in
seconds) that the service is allowed to
consume. If MAXCPUTIME is
unspecified or set to zero (0), the
service is not monitored for total CPU
time excession.
MAXIMUMSESSIONS This specifies the maximum number
of concurrent sessions for this service.
When this threshold is reached, the
server will refuse subsequent
connection requests for the service.


MGMTCLAS This specifies the management class
of the NETSRVR.LOG file. If specified,
the VOL and UNIT parameters are
ignored. If you do not use this class,
delete this parameter.
RATACTION_MAXCPUTIME This specifies the action to be taken if
the total CPU time used by the service
exceeds the MAXCPUTIME value. Valid
values include:
■ LOG. A warning message is posted
in the SequeLink Server log when
CPU time excession occurs. The
service continues running. This is
the default.
■ DIE. A warning message is posted

in the SequeLink for OS/390 log
when CPU time excession occurs
and the service is terminated.
■ MSG. A warning message is posted

when total CPU time excession
occurs and monitoring is
discontinued for this thread. The
service continues running.
If MAXCPUTIME is set to zero (0), this
parameter is ignored.


RATACTION_THROTTLE This specifies the action to be taken if
THROTTLE has been exceeded during
a timer cycle. Valid values include:
■ LOG. A warning message is posted
when CPU time excession occurs.
The service continues running.
■ DIE. A warning message is posted

when CPU time excession occurs
and the service is terminated. This
is the default.
If THROTTLE=0, this parameter is
ignored.
RECOVERY This specifies whether the
restart/recovery feature will be
turned on for services or eligible
SequeLink for OS/390 components.
Valid values include ON and OFF.
Recovery can be specified in the
[ASSORTED_PARMS] section, any
[SERVICE] section, or any eligible
SequeLink for OS/390 core
component section.


SECURITY This specifies the security type for the
service. Valid values include:
■ NONE bypasses all security
checking; any user ID and
password are accepted.
■ SAFBASIC validates the client’s

user ID and password. This is the
default.
■ SAFRESOURCE validates the

client’s user ID and password, and
its authority to access the service.
If specified, the service
servicename must be defined in
the security system’s general
resource class profile. The default
resource class name is FACILITY.
It can be overridden with the
SECURITYCLASS parameter, if the
resource class name is defined in
your security system.
SECURITYCLASS This parameter is used only when
SECURITY=SAFRESOURCE. It
specifies whether a general resource
class name is used by the server. The
default is FACILITY.
STORCLAS This specifies the storage class of the
NETSRVR.LOG file. If you do not use
this class, delete this parameter.


THROTTLE The maximum amount of CPU time
(in seconds) that the service is
allowed to consume during a
SequeLink for OS/390 timer cycle
(TIMERINTERVAL parameter). If
THROTTLE is unspecified or set to
zero, the service is not monitored for
timer cycle CPU excession.
VOL This specifies the serial number of the
volume to which the NETSRVR.LOG
file is allocated.
UNIT This specifies the description of the
unit to which the NETSRVR.LOG file is
allocated.
Note: Runaway task detection detects when a thread (service)

has exceeded site-defined CPU limits. It detects services that may
be looping, but it also can be used to limit the total CPU time a
service may consume. It is turned on by specifying the
MAXCPUTIME, THROTTLE, RATACTION_THROTTLE, and
RATACTION_MAXCPUTIME parameters.
The synchronous timing facilities used to monitor service CPU

time are not precise. If the timer cycle value (TIMERINTERVAL) is
a high value, a service may use more CPU time than the limits
specified in MAXCPUTIME or THROTTLE before SequeLink Server
will detect a CPU time excession.
For example, suppose a service's THROTTLE parameter is set to

10 (seconds) and its TIMERINTERVAL parameter is set to 20
(seconds). A looping service could possibly consume 20 seconds
CPU time before SequeLink Server detects the excession. Greater
precision in time excession detection can be achieved by

reducing TIMERINTERVAL or by ensuring that MAXCPUTIME and

THROTTLE are always equal to or higher than TIMERINTERVAL.
Example:
THROTTLE=10
MAXCPUTIME=100
RATACTION_THROTTLE=LOG
RATACTION_MAXCPUTIME=DIE
In this example, a message is posted to the SequeLink Server log

when this service uses more than 10 CPU seconds in a specific
timer cycle and the service is allowed to continue
(RATACTION_THROTTLE=LOG). If the total CPU time used by the
service exceeds 100 seconds at any time, the service is terminated
(RATACTION_MAXCPUTIME=DIE). If
RATACTION_MAXCPUTIME=LOG, a VAIS212W message is issued at
each SequeLink Server timer cycle until the service terminates. If
MAXCPUTIME=MSG, a VAIS212W message is issued once and the
thread is no longer monitored for total CPU time excession.
Modifying DB2 Service Parameters

Table 9-5 lists the DB2 service parameters you can customize and
provides a description and valid values for each parameter. These
parameters modify the creation of the server packet logging file.
Table 9-5. DB2 Service Parameters (OS/390)

[SERVICE_servicename] PLAN This specifies the DB2 plan name to be used. If
unspecified, DEFAULTPLAN in the [DB2_ifid]
section is used.
Note: To support stored procedures, the DBRM of
the stored procedure must be bound to a package.
This package must be included in the packagelist
of the plan that is used by SequeLink Server.

Creating Multiple DB2 Services

You can define multiple DB2 services using different service
names and plan names. For example, if you have one group of
users who requires more processing time than another group of
users, you may want to define multiple DB2 services. The
Resource Limit Facility can limit processing time for interactive
SQL statements, and this resource limit can be applied to the
plan. Therefore, you would need two services and two plans. To
create these services:
1 Add an additional entry in the [SERVICES] section with a

different service name and plan name.
2 Define a DB2 service entry in the [SERVICE_servicename]

section with a different service name equal to the
SequeLink/DB2 loadmodule name.
3 Run an additional bind with a different plan name with the

usual SequeLink DBRM module as input.
Each group of users will only have access to their service (for
more information, see SAFRESOURCE).
Your service entry in the [SERVICES] section might look like this:
[SERVICES]
MVSDB2B=VAICDB2X ;second DB2 service
Your DB2 service section name might look like this:
[SERVICE_MVSDB2B]

Modifying Oracle7 Service Parameters

Table 9-6 lists the Oracle7 service parameters you can customize
and provides a description and valid values for each parameter.
Table 9-6. Oracle7 Service Parameters (OS/390)

[SERVICE_servicename] SUBSYSID This specifies the subsystem ID of the Oracle
address space. This value cannot exceed 4
characters and is required for Oracle access (see
SERVICE_servicename=VAICORAX). There is no
default.
Modifying TCP/IP Service Parameters

To change the TCP/IP port a SequeLink Server service uses, you
can modify the PORT parameter in the [SERVICE_servicename]
section, which specifies the TCP port number assigned to a
service.
Specify a decimal value between 1024 to 65534. The example
SYSINI file on the SequeLink tape uses the default port number of
4007 (for a DB2 service) and 4003 (for an Oracle7 service). If you
specify a different port number, make sure that your clients use
this port number also. For more information about specifying
port numbers, see the appropriate client administration chapters.
If this parameter is unspecified or omitted, the TCP/IP NIM will
resolve this port using the dataset specified in the ETCSERVICES
parameter of the [IBM_XTCP/IP] section.
Note: This parameter sets the service-specific TCP port for the
TCP/IP NIMs. If you receive the error -382 on the client, make sure
that you added the ddname entry in the [FILECACHE] section of
the SYSINI.

Modifying FILECACHE Parameters

The [FILECACHE] section allows the caching of the SequeLink
configuration file specified in the [SERVICE] section entry. The
format is ddname=CACHED. Cached files are loaded into
memory at startup.
Example:
[SERVICE_MVSDB23]
CFGFILE=SQLNKCFG
[FILECACHE]
SQLNKCFG=CACHED
Note: The ddname must be added to the startup JCL.
Modifying User ID Mapping

User ID mapping prevents users from updating DB2 tables using
commonly available tools, such as QMF or SPUFI, and preserves
their update access through SequeLink. For example, suppose a
user, SMITH, is defined as shown:
DB2 Table SequeLink

User ID Privilege Plan Privilege Application
SMITH UPDATE EXECUTE SequeLink service
SMITH UPDATE EXECUTE SPUFI
In this example, SMITH can update tables using SPUFI and the
SequeLink service.
To prevent SMITH from updating the tables through SPUFI, you

can define a pseudo, or alternate, user ID. For example, you can

provide the alternate user ID, SMITHB, with the Update privilege
and provide SMITH with the readonly privilege. For example:
DB2 Table SequeLink

User ID Privilege Plan Privilege Application
SMITHB UPDATE EXECUTE SequeLink service
SMITH SELECT EXECUTE SPUFI
Each service that requires user ID mapping must be defined in the

SYSINI with the UIDMAP=mapname parameter. This parameter
identifies the service as one that requires the client’s logon ID
(UID) to be mapped to an alternate UID, which defines the user’s
access privileges and authorization requirements for the service
through DB2 security administration. The UIDMAP parameter is
ignored if the requested service is not a DB2 service.
If the SequeLink module that issues the DB2 open thread detects
a UIDMAP=mapname specification for the service, it will query the
SYSINI UIDMAP_mapname section, extract the alternate UID, and
use the alternate UID as the DB2 authorization ID for connecting
to DB2. If an alternate UID cannot be found in the
UIDMAP_mapname section, the real logon UID will be used as the
DB2 authorization ID, if UIDNOTFOUND=PERMIT
(UIDMAP_mapname section). All status displays will continue to
show the client’s real logon ID.
Note: Alternate UIDs are used internally for UID mapping only. If
a client attempts to log on with an alternate UID, the logon will
be rejected. You can also map an RACF group to a single
alternate user, simplifying the administrative task of managing
multiple users.

Valid values for the parameter UIDNOTFOUND

(UIDMAP_mapname section) include:
PERMIT If user ID mapping is set for the service and the

user ID cannot be found in the UIDMAP_mapname
section, the connection is allowed.
DENY If user ID mapping is set for the service and the
user ID cannot be found in the UIDMAP_mapname
section, the connection is refused.
Example SYSINI entries include:
[SERVICE_MVSDB2A]
...
UIDMAP=MAP1
...
[SERVICE_MVSDB2B]
...
UIDMAP=MAP2
...
[SERVICE_MVSDB2C]
...
UIDMAP=MAP3
...
[SERVICE_MVSDB2D]
...
...
[UIDMAP_MAP1]
SMITH=SMITHA
ERICK=ERICKA
UIDNOTFOUND=DENY
...
[UIDMAP_MAP2]
SMITH=APPDB2B
EDWARDS=APPDB2B
UIDNOTFOUND=DENY
...

[UIDMAP_MAP3]
SMITH=SMITHC
ERICK=ERICKC
UIDNOTFOUND=PERMIT
Using this example, the following scenarios could occur:
User ID Service Map ID Action Comments/Reason

ALBERT MVSDB2A n/a Denied ALBERT not in MAP1
ALBERT MVSDB2C n/a Permit Connects to MVSDB2C as ALBERT
SMITH MVSDB2B APPDB2B Connect Connects to MVSDB2B as APPDB2B
EDWARDS MVSDB2B APPDB2B Connect Connects to MVSDB2B as APPDB2B
ERICK MVSDB2B n/a Denied ERICK not in MAP2
ERICK MVSDB2C ERICKC Connect Connects to MVSDB2C as ERICKC
SMITH MVSDB2D n/a Connect No mapping for MVSDB2D
Modifying APPC Parameters

The [APPC] section contains parameters required by the
APPC/LU 6.2 network interface manager (APPCNIM). Table 9-7
lists the APPC parameters you can customize and provides
descriptions and valid values for each parameter.
Table 9-7. APPC Parameters (OS/390)

[APPC] INACTIVITYTIME This specifies the heartbeat interval (in
seconds) allowed to elapse before a
session is labelled inactive. If a session is
inactive for this value, it is declared
inactive and a message is posted to the
server log. The session is not terminated.
The default is 30. Valid values range from
1 to 600.

Table 9-7. APPC Parameters (OS/390)

LAUNCH This starts the APPCNIM at initialization.
Valid values include YES and NO. The
default is NO. If you want to use APPC,
specify YES.
MAXIMUMPACKETSIZE This specifies the maximum APPC PIU size.
MAXIMUMSESSIONS This specifies the maximum number of
concurrent sessions that APPCNIM can
handle. The default is 100.
VTAMAPPLNAME This specifies the ACF/VTAM application ID
to be used for APPCNIM sessions. The
default is SRS01ACB.
Modifying IBM TCP/IP Parameters

The [IBM_XTCP/IP] section contains parameters required by the
IBM TCP/IP NIM. For more information about TCP/IP
communication, see “TCP Port Numbers” on page 107.
Table 9-8 lists the IBM TCP/IP parameters you can customize and
provides a description and valid values for each parameter.
Table 9-8. IBM TCP/IP Parameters (OS/390)

[IBM_XTCP/IP] DEBUG This puts the NIM in debugging mode. Only
specify this parameter if requested by MERANT
technical support. Valid values include YES and
NO. The default is NO.

Table 9-8. IBM TCP/IP Parameters (OS/390) (cont.)

ETCSERVICES This specifies the dataset name of the
ETC.SERVICES dataset, which contains port
mappings of common services, such as Telnet.
SequeLink uses the hlq.ETC.SERVICES dataset to
determine the port number on which the service
will run if the service entry in the SYSINI file
does not contain a PORT parameter.
LAUNCH This starts the listener at initialization. Valid
values include YES and NO. The default is YES. If
you do not want to use TCP/IP, specify NO.
MAXIMUMSESSIO This specifies the maximum number of
NS simultaneous connection requests that the
listener can handle. You can specify any value in
the range 8 to 2048. Once the value you specify
is reached, the listener will not accept any more
connection requests. The default is 128.
SOSLIMIT SOSLIMIT (short on storage limit) specifies the
number of kilobytes of private storage that must
be available in the address space to accept
further connections. The maximum value you
can specify is 2048 KB. The default is 512 KB.
If this amount of storage is not available,
incoming connections will be rejected. This
value is compared to the total storage available
above and below the 16 MB line. There is an
additional check for storage below the 16 MB
line only. If there is less than 64 KB available,
incoming connections will be rejected. If you
specify 0, this feature is turned off.
TRACE This puts the listener in tracing mode. Only
specify this parameter if requested by MERANT
technical support. Valid values include YES and
NO. The default is NO.

Table 9-8. IBM TCP/IP Parameters (OS/390) (cont.)

USERID This specifies the name of the started procedure
used to start the TCP/IP address space. You can
find the value in the hlq.TCPIP.DATA dataset as
the value of TCPIPUSERID. The default is
TCPIP.
Note: Users of IBM TCP/IP V3R1 can find the
value in dataset hlq.TCPPARMS(TCPDATA) as the
value of TCPIPJOBNAME.
Modifying the ASCII-to-EBCDIC Tables

(Optional)
The members of the ASM dataset, ATOETRT and ETOATRT,
contain ASCII-to-EBCDIC conversion tables you can alter. These
default tables include a table of 256 characters for
ASCII-to-EBCDIC conversion (ATOETRT member) and another
table for EBCDIC-to-ASCII conversion (ETOATRT member).
Default ASCII-to-EBCDIC Table (ATOETRT):

VAILATOE CSECT
*
* ASCII TO EBCDIC conversion
*
ATOESIZE DC AL2(ATOEEND-ATOESTRT Size
ATOESTRT EQU *
DC X'0040404040402E40' **CUSTOM**
DC X'40402540400D4040' **CUSTOM**
DC X'40404040403D4040' **CUSTOM**
DC X'4040404040404040' **CUSTOM**
DC X'405A7F7B5B6C507D' **CUSTOM**
DC X'4D5D5C4E6B604B61' **CUSTOM**
DC X'F0F1F2F3F4F5F6F7' **CUSTOM**

DC X'F8F97A5E4C7E6E6F' **CUSTOM**
DC X'7CC1C2C3C4C5C6C7' **CUSTOM**
DC X'C8C9D1D2D3D4D5D6' **CUSTOM**
DC X'D7D8D9E2E3E4E5E6' **CUSTOM**
DC X'E7E8E9BAE0BBB06D' **CUSTOM**
DC X'7981828384858687' **CUSTOM**
DC X'8889919293949596' **CUSTOM**
DC X'979899A2A3A4A5A6' **CUSTOM**
DC X'A7A8A9C04FD0A140' **CUSTOM**
DC X'68DC516243444748' **CUSTOM**
DC X'5253547776786367' **CUSTOM**
DC X'719C9ECBCCCDDBDD' **CUSTOM**
DC X'DFECFC70B180BF40' **CUSTOM**
DC X'6555CEDE4969469A' **CUSTOM**
DC X'AB405FB8B7AA8A8B' **CUSTOM**
DC X'4040404040404040' **CUSTOM**
DC X'4040404040404040' **CUSTOM**
DC X'4040404040404040' **CUSTOM**
DC X'4040404040404040' **CUSTOM**
DC X'8C40404040404040' **CUSTOM**
DC X'4040404040404040' **CUSTOM**
DC X'EE59EBED4040A040' **CUSTOM**
DC X'40FEFBFD40404040' **CUSTOM**
DC X'40404040B6B5E140' **CUSTOM**
DC X'4040404040404040' **CUSTOM**
ATOEEND EQU *
END
Default EBCDIC-to-ASCII Table (ETOATRT):

VAILETOA CSECT
*
* EBCDIC TO ASCII CONVERSION
*
ETOASIZE DC AL2(ETOAEND-ETOASTRT) SIZE
ETOASTRT EQU *
DC X'0020202020202020' **CUSTOM**
DC X'20202020200D2020' **CUSTOM**
DC X'2020202020202020' **CUSTOM**
DC X'2020202020202020' **CUSTOM**
DC X'20202020200A2020' **CUSTOM**

DC X'2020202020200620' **CUSTOM**
DC X'2020202020202020' **CUSTOM**
DC X'2020202020152020' **CUSTOM**
DC X'2020838485A0A686' **CUSTOM**
DC X'87A4202E3C282B7C' **CUSTOM**
DC X'268288898AA18C8B' **CUSTOM**
DC X'8DE121242A293BAA' **CUSTOM**
DC X'2D2F838E85A0A78F' **CUSTOM**
DC X'80A57C2C255F3E3F' **CUSTOM**
DC X'9B9088898AA18C8B' **CUSTOM**
DC X'8D603A2340273D22' **CUSTOM**
DC X'9D61626364656667' **CUSTOM**
DC X'6869AEAFD0EC20F1' **CUSTOM**
DC X'F86A6B6C6D6E6F70' **CUSTOM**
DC X'7172A7A7912092CF' **CUSTOM**
DC X'E67E737475767778' **CUSTOM**
DC X'797AADA8205B2020' **CUSTOM**
DC X'5E9CBE2020F5F4AC' **CUSTOM**
DC X'AB205B5D205D279E' **CUSTOM**
DC X'7B41424344454647' **CUSTOM**
DC X'48492D939495A2A7' **CUSTOM**
DC X'7D4A4B4C4D4E4F50' **CUSTOM**
DC X'515220968197A398' **CUSTOM**
DC X'5CF6535455565758' **CUSTOM**
DC X'595AFDE299E3E0A7' **CUSTOM**
DC X'3031323334353637' **CUSTOM**
DC X'383920EA9AEBE920' **CUSTOM**
ETOAEND EQU *
END
To customize the ASCII-EBCDIC tables:

1 Copy the XTABLES procedure.
2 Edit the copied procedure.
a Change ATOETRT and ETOATRT to ATOETRTx and

ETOATRTx, respectively.
b Change the loadmodule names from VAILATOE to

VAILATEx and VAILETOA to VAILETAx.

3 Copy ATOETRT and ETOATRT to ATOETRTx and ETOATRTx,

respectively, in your ASM library.
4 Change the CSECT names from VAILATOE to VAILATEx and

VAILETOA to VAILETAx, respectively.
5 Edit your ASCII/EBCDIC tables ATOETRTx and ETOATRTx in the

ASM dataset.
6 Run the assembly and link.
7 Add ATOETRT=VAILATEx and ETOATRT=VAILETAx in the

SYSINI file (your service section).
8 Start up the server.
Automatic Execution of Commands at Startup

SequeLink Server opens the SYSCMDS dataset and executes the
SequeLink Server operator commands it finds in this dataset.
SYSCMDS can be a sequential file or member of a PDS with
RECFM set to FB, LRECL set to 80, and BLKSIZE set to a multiple of
80. If the SYSCMDS dataset does not exist, no startup commands
are executed.
Specifying the Authorized Applications List

statement, the client application must identify themselves to the
service with their application ID.
This configuration option specifies which application IDs will be

accepted and is controlled by the access control\Appld key in the
database configuration file (SRVCDB2 file). The SRVCDB2 file

Logging Information 339
resides in the CNTL library and contains database-specific

parameters that control client connections to the server. For
more information about DB2 database configuration
information, see “SequeLink Server Configuration Resource
(DB2)” on page 198.
Specify application IDs as a list of strings, separated by

semicolons (;) in your SequeLink configuration file. For example:
[access control]
AppId=myOrderEntry;theBossesReport
The list cannot contain any spaces or trailing blanks after the last
specified application ID. An empty value for this key indicates
that any application can access the service.

Logging Information
For troubleshooting, you can log information using one, or both,
of the following methods:
■ NETSRV.LOG file (packet log file)

■ Primary and secondary log files (server log files)
NETSRV.LOG File
The NETSRV.LOG file is created on the server after trace logging
has been turned on using the LOGR ALTER command. A
NETSRV.LOG file is created for each workstation that makes a
connection request after the command has been issued. Log
messages are written to the specific workstation log file.

Each workstation log file name has the following format:
USERID.NETSRV.LOG.t#xxxxxx
where:
USERID is the value specified in the LOGHLQ parameter in the

[SERVICE] section of the SYSINI.
xxxxxx is the thread identifier that is linked to a specific LU
(workstation).
You can find the thread ID for a particular workstation using the
operator commands. Tracing is controlled by the
connection\Logging subkey in the database configuration file
(SRVCDB2 file). The SRVCDB2 file resides in the CNTL library and
contains database-specific parameters that control client
connections to the server. For more information about DB2
database configuration information, see “SequeLink Server
Configuration Resource (DB2)” on page 198.
Valid values for the connection\Logging subkey include:
No The LOGR command is disabled; no logging will be

performed.
Yes The LOGR command is enabled; for tracing, issue
LOGR operator command.

processing, it is recommended that you turn on the logging
option only when you are troubleshooting. After creating the log
file, turn off logging.
Each NETSRV.LOG file exists until you delete it. For more
information about the LOGR ALTER command, see “Using
Operator Commands” on page 343.

Logging Information 341
Primary and Secondary Log Files

SequeLink Server uses a primary and secondary log file, VAILOGP
and VAILOGS, respectively. All messages are logged. They are
sent to the primary log first, and when this is almost full, the
SequeLink Server sends a message to the operator's console to
alert you to switch to the secondary log file.
Each message starts with the string VAI. The last digit indicates
one of the following levels of severity:
Severity Meaning
I Information
W Warning
T Trace
E Error
S Severe
F Fatal
For more information about error codes and messages, refer to

SequeLink Error Codes and Messages Reference.

Running Multiple SequeLink Servers

SequeLink Server is designed to support a maximum of two
network platforms (APPC and IBM TCP/IP) within the same
address space. Often, a site will operate two or more systems
simultaneously—for example, a test system and a production
system.
To provide access to multiple systems, you must run multiple

SequeLink Servers. For example, to spread the processing load
among address spaces, you may want to run a separate
SequeLink Server for each different network platform.
To run multiple SequeLink Servers:

1 Configure multiple SYSINIs and multiple SequeLink startup
jobs. There can be only one startup job for each SYSINI.
2 Start the SequeLink Servers. If you want to run multiple

SequeLink Servers (to balance network activity, for example),
follow the instructions for configuring SequeLink Server for
each network you want to run, as described in the SequeLink
Server Installation Guide. The SYSINIs could contain the same
DB2_ifid information, but different network and base
information.
If you want to run more than one copy of SequeLink Server with
APPC, make sure that the value of the VTTAMAPPLNAME of the
[APPC] section is unique for each server. The server's APPC NIM
(APPCNIM) uses VTAMAPPLNAME to register itself in the SNA
network. If you specify a value already being used, the
initialization of the APPCNIM will fail.
The default value for the VTAMAPPLNAME parameter is SRS01ACB;

therefore, a second server using APPC may have a VTAMAPPLNAME
parameter with the value SRS11ACB.
Important: The value SRS02ACB is reserved for the server’s

installation verification procedure (IVP) and must not be used.

Using Operator Commands 343
Using Operator Commands

There are some operator commands you may find useful for your
administration tasks. You may need to issue these during your
day-to-day tasks or as a result of user queries. These commands
can be issued from an OS/390 operator's console or any
3270-type workstation logged on the server's II. How you issue
the commands varies, depending on whether you use an
operator's console or a 3270-type workstation.
From an Operator's Console

From an operator’s console, enter the command:
F jobname,compid command parms
where:
jobname is the job name or started task name of the server.

compid is the ID of the server component to which the
command is directed. Valid component IDs include:
■ APPC - APPCNIM
■ CNTL - Server Controller Task
■ LOGR - Message Logging Tasks
■ XTCP - IBM TCP/IP NIM
■ DB2 - DB2 Application Support Package

command is the command name.
parms are the parameters of the command.
For example:
F MVSDB2,APPC STATUS
activates the APPC STATUS command.

Operator commands also can be issued using the SequeLink

command recognition character. For example, from an operator
console, enter:
!compid command parms
where:
! is the unique command recognition character

defined in the [ASSORTED_PARMS] section of the
SYSINI.
■ APPC - APPCNIM
■ CNTL - Server Controller Task
■ LOGR - Message Logging Tasks
■ XTCP - IBM TCP/IP NIM

For example:
!APPC STATUS
activates the APPC STATUS command.
From the Instrumentation Interface

From a 3270-type workstation, enter the following command:
compid command parms
For example, to activate the same APPC STATUS command, use

the following command:
APPC STATUS

Note: All commands issued from the II workstation are checked

against your security system to make sure that the user issuing
the server commands has authority to do so.
The following sections list the commands available for the

different components of the server. The examples for the
commands are given as though they are issued from an II
workstation. They do not contain an F jobname string.
Repeating Operator Commands

Use the REFRESH command to repeat operator commands:
Table 9-9. Refresh Command
Command: REFRESH
Purpose: To repeat the next command.
Parameter: nnn Is the number of seconds between
each refresh interval. The next
SequeLink command entered
from the II command line will be
repeated (refreshed) every nnn
seconds. Valid values are in the
range 1-999.
OFF Deactivates the screen refresh.
Example: REFRESH 10 repeats the next command every 10
seconds.
REFRESH OFF deactivates the screen refresh option.

APPC NIM Commands

Table 9-10 lists APPC NIM commands, their purposes, their
parameters, and examples of how they can be used.
Table 9-10. APPC NIM Commands
Command: ABORT
Purpose: To force the end of a session between the server and a
specific client.
Parameter: LU=: A specific LU name. This is the network
name of the client whose session will be
terminated. This parameter is required.
Example: APPC ABORT,LU=CLIENTLU ends all conversations
between the server and the client (LU) named
CLIENTLU.
Command: ALTER
Purpose: To change selected APPC NIM runtime parameters.
Parameter: SESSIONS= The maximum number of sessions
supported.
WAITTIME= The number of heartbeat timer ticks
that can occur before a conversation is
reported as inactive.
Both parameters are required.
Example: APPC ALTER SESSIONS=20 resets the
MAXIMUMSESSIONS parameter to 20.
APPC ALTER WAITTIME=10 resets the inactivity
time to 10 heartbeat ticks. (The heartbeat parameter
is set in the SYSINI by the TIMERINTERVAL parameter.)

Table 9-10. APPC NIM Commands (cont.)
Command: COUNTS
Purpose: To display APPC NIM status and, optionally, the status
of one or more specific APPC LUs.
Parameter: LU= A specific LU name or a generic LU
PARTNER= mask. If the name supplied is 8
characters, the status is displayed for
the specific LU only. If the name is less
than 8 characters (a mask), the status is
displayed for each LU with an LU name
beginning with that mask.
Both parameters are optional.
Example: APPC COUNTS returns a single line providing the
general status of the APPC NIM.
APPC COUNTS,LU=T01 returns a general APPC NIM
status line and a status line for each LU with an LU
name beginning with the string “T01.”
Command: STATUS
Purpose: To display APPC NIM status and, optionally, the status
of one or more specific APPC LUs.
Parameter: LU= A specific LU name or a generic LU
PARTNER= mask. If the name supplied is 8
characters, the status is displayed for
the specific LU only. If the name is less
than 8 characters (a mask), the status is
displayed for each LU with an LU name
beginning with that mask.
Both parameters are optional.
Example: APPC STATUS returns a single line providing the
general status of the APPC NIM.
APPC STATUS,LU=T01 returns a general APPC NIM
status line and a status line for each LU with an LU
name beginning with the string “T01.”

Server Controller Task (CNTL)

Commands
Table 9-11. Server Controller Task (CNTL) Commands
Command: ABORT
Purpose: To instruct the server controller task to remove a
service thread from the OS/390 server.
Parameter: USERID= The user ID of the thread to be
removed.
THRDID= The server thread ID of the
thread to be removed.
These parameters can be used singly or together to
identify the service thread to be removed.
Example: CNTL ABORT USERID=M126305
Command: ALTER
Purpose: To dynamically change the service definitions used by
SequeLink Server. Use this command to alter a single
or a combination of values for a specific service.
Parameter: SERVICE= The service name must appear
as a service name in the
[SERVICES] section of the
SYSINI. Use any of the following
parameters to alter the values
for the service entry.
TIMEOUT= Changes the idle time-out value
of the service (see the
IDLETIME parameter). The
value specified must be a
decimal in the range 0 to 9999.
MAXSESS= Changes the maximum number
of sessions available for the
service. The value specified
must be in the range 0 to
9999.

Table 9-11. Server Controller Task (CNTL) Commands (cont.)
AVAIL= Indicates whether the service is

available, for example, to
accept connection requests.
Valid values include Y (Yes) and
N (No).
Example: CNTL ALTER SERVICE=CONNECT MAXSESS=10,
AVAIL=Y sets the maximum number of sessions to 10,
and indicates that this service can accept connection
requests.
Command: CLOSE
Purpose: To shut down the SequeLink Server system.
Parameter: TYPE=immed Shuts down the system
immediately.
TYPE=norm Shuts down the system after
making all conversations
inactive.
This parameter is required.
Example: CNTL CLOSE TYPE=immed shuts down the server
immediately.
Command: LIST
Purpose: To list a cached SYSINI.
Note: If the SequeLink configuration file is listed, the
lines containing the keyword AppID (see the [access
control] section) are not listed for security reasons.
Parameter: DDN Is the ddname of the file you
want to list.
Example: CNTL LIST DDN = RLDIAG
Command: REFRESH
Purpose: To refresh cached files.
Parameter: TYPE=CACHE Refreshes the cached files.
Example: CNTL REFRESH TYPE=CACHE will refresh the
cached files.

Table 9-11. Server Controller Task (CNTL) Commands (cont.)
Command: STATUS
Purpose: To display the general status of the SequeLink Server
system.
Parameter: SHOW=all Displays a list of and shows the
status of all active tasks (server
core tasks and service tasks). All
services known to the server are
listed.
SHOW=services Displays a list of active
application service tasks known
to the server.
This parameter is optional.
Example: CNTL STATUS displays the status of each attached
component. The output appears on the operator’s
console.
CNTL STATUS SHOW=all displays all known active
tasks and services. The output appears on the
operator’s console.
CNTL STATUS SHOW=services lists active
application service tasks. The output appears on the
operator’s console.

Messaging Component (LOGR)

Commands
Table 9-12. Messaging Component (LOGR) Commands
Command: ALTER
Purpose: To start or stop logging of trace messages.
Parameter: TRACE=ON|OFF Turns on or off logging for
specific components and
workstations.
COMPNT= Specifies which components will
have messages logged. This can
be set to ALL (messages from all
system components) or to a
single-character, component ID
(messages for that component
only). Valid component IDs
include:
■ A - APPCNIM component
■ C - Common or shared
components (operator
interface, for example)
■ D - DB2 component
■ H - CSHELL component
■ I - II component
■ S - Server controller
component
■ X - TCP/IP component

Table 9-12. Messaging Component (LOGR) Commands (cont.)
TERMID= Determines which connections to

the server will have messages
logged. This can be set to ALL
(all new connections) or to a
specific terminal (client) ID
(messages for that client only).
Existing connections are not
affected by this parameter.
The terminal ID format depends
on your network type:
■ If APPC VTAM, the ID is the
VTAM LU name of the client
workstation (maximum of 8
characters).
■ If TCP/IP, the ID is the IP

address of the client
workstation (maximum of 15
characters)
This parameter is optional, unless
the command does not include
the TERMID or COMPNT
parameter.
USERID= Determines which users are
logging messages. This can be set
to ALL (all users have messages
logged) or to a specific user ID
(only messages for the associated
user will be logged).

Example: LOGR ALTER TRACE=ON COMPNT=ALL logs the

messages of all server components.
TERMID=TGT0D100 logs the messages of all
components of the server and the workstation
identified by TGT0D100.
LOGR ALTER TRACE=OFF COMPNT=A stops the
tracing facility for the APPCNIM component of the server.
No messages associated with the APPC NIM are logged.
LOGR ALTER TRACE=ON USERID=M126305 logs all
messages associated with the user whose ID is M126305.
Command: PRINT
Purpose: To print one of the SequeLink Server system logs.
Parameter: LOG= Prints the primary log, VAILOGP,
or the secondary log, VAILOGS.
The default is the inactive log.
CLASS= Indicates which SYSOUT class to
which to spool the printout. The
default is A.
HOLD= Indicates whether the output is
to be held on the output queue
(y or n). The default is n.
These parameters are optional.
Example: LOGR PRINT CLASS=L spools the inactive log to the
JES2 output class L; the output is not held in the output
queue.
Command: STATUS
Purpose: To display the status of the message logging component
(LOGR).
Parameter: None
Example: LOGR STATUS returns a single line, providing the
general status of the logging component.
Command: SWITCH
Purpose: To change the active log. This command switches to the
alternate log, making the current log available for
printing or archiving.

Parameter: None
Example: LOGR SWITCH If the primary log (VAILOGP) is active
when this command is issued, the secondary log
(VAILOGS) becomes the active log. Issuing the command
again makes VAILOGP the active log again.
IBM TCP/IP NIM Commands

Table 9-13. IBM TCP/IP NIM Commands
Command: CLOSE
Purpose: To close a TCP/IP connection.
Parameter: NAME= A unique name assigned to a task
associated with a TCP/IP
connection.
Example: XTCP CLOSE NAME=T#000102 closes the connection
with the taskid of T#000102.
Command: DISPLAY
Purpose: To display the connection status of one or all subtasks.
Parameter: NAME=tasknam Displays the connection status of a
e specific subtask identified by the
unique name assigned to it.
NAME=ALL Displays the connection status of
all subtasks.
Example: XTCP DISPLAY NAME=T#000102 displays the status
of the connection with the taskid of T#000102.
XTCP DISPLAY NAME=ALL displays the status of all
connections between the server and its clients.
Command: LGNSTART
Purpose: To resume the NIM logons.
Parameter: None

Table 9-13. IBM TCP/IP NIM Commands (cont.)
Example: XTCP LGNSTART allows users to log on using TCP/IP.

Command: LGNQSTAT
Purpose: To display the status of the NIM logon queue.
Parameter: None
Example: XTCP LGNQSTAT displays the status of the NIM logon
queue.
Command: LGNSTOP
Purpose: To suspend NIM logons.
Parameter: None
Example: XTCP LGNSTOP prevents any user from logging on
using TCP/IP.
Command: SHUTDOWN
Purpose: To shut down all NIM sessions between the server and
its clients.
Parameter: TYPE=immed Shuts down sessions immediately.
TYPE=normal Shuts down sessions after
completing the current process.
Example: XTCP SHUTDOWN TYPE=immed shuts down the
sessions immediately.
XTCP SHUTDOWN TYPE=normal shuts down the
sessions after performing the current process.
Command: STATE
Purpose: To display the service state of the NIM.
Parameter: None
Example: XTCP STATE displays the service state of the NIM.
Command: STATUS
Purpose: To display the general status of the NIM and a list of all
active connections.
Parameters: None.
Examples: XTCP STATUS displays the general status of the NIM.

Table 9-13. IBM TCP/IP NIM Commands (cont.)
Command: TRACE
Purpose: To turn on and off tracing facility on and off, and to
check whether tracing is turned on or off.
Parameter: SET=on|off Turns on and off tracing.
SET=? Indicates whether tracing is
turned on or off.
Example: XTCP TRACE SET=on turns on tracing.
XTCP TRACE SET=off turns off tracing.
XTCP TRACE SET=? returns a status, indicating
whether tracing facility is turned on or off.
DB2 Application Support Package

Commands
Table 9-14. DB2 Application Support Package Commands
Command: SHOW
Purpose: To display active DB2 interfaces
Parameter: None
Example: DB2 SHOW displays all active DB2 interfaces.
Command: STATUS ID=ifid
Purpose: To display the status of SequeLink Server DB2 sessions.
Parameter: None.
Example: DB2 STATUS ID=DSNG displays the status of all
SequeLink Server DB2 sessions for DB2 interface DSNG.
Command: CONNECT ID=ifid
Purpose: To explicitly connect a DB2 interface to the DB2
address space.

Table 9-14. DB2 Application Support Package Commands
Parameter: None.
Example: DB2 CONNECT ID=DSNG connects the DB2 interface
DSN4 to the SequeLink Server address space.
Command: DISCONN ID=ifid
Purpose: To explicitly disconnect a DB2 interface from the DB2
address space. This command does not allow any new
connections to the DB2 interface.
Parameter: None
Example: DB2 DISCONN ID=DSNG disconnects the DB2
interface DSNG from the SequeLink Server address
space.
Command: ALTER ID=ifid
Purpose: To alter the number of SequeLink Server concurrent
DB2 threads.
Note: This command is only accepted if the Thread
Management Facility was activated at startup by a
nonzero value for the parameter MAXIMUMTHREADS in
the [DB2_ifid] section of the SYSINI.
Parameter: THREADS= A decimal number in the range of 1 to
255.
Example: DB2 ALTER ID=DSNG THREADS=15 alters the
number of SequeLink Server concurrent DB2 threads
to 15 for the DB2 interface DSNG.

SMF Accounting
If you have an OS/390 ESA system, you can use SequeLink Server
to post accounting records to the SMF dataset. These records
contain statistical data which can be used to track information
for charge-back systems. The following data is provided for each
database session:
■ Client logon ID
■ Internal thread ID assigned by SequeLink Server
■ Session start/end times
■ Number of packets received/sent
■ Number of bytes transferred
■ Total CPU consumption
■ Service name
■ Application name or loadmodule name
■ Network node name of the client
■ Total number of DB2 calls
■ Total number of DB2 reconnects (thread management)
■ Total number of DB2 checkpoints (thread management)
■ Total SQL call CPU consumption
The records are written to the active SMF dataset using the SMF
record ID in the SYSINI. The format of the record ID is determined
by your own standards. If you do not want to use the accounting
facility, you can turn it off by specifying a zero (0) as the SMF
record ID.
The following example shows a typical SMF record:
*****************************************************************
SMF RECORD HEADER
*****************************************************************
SMFRECORD DS OF
SMFRECLEN DS H Record length
SMFDESC DS H Descriptor (must be zero)
SMFSYS DS X System indicator (set to zero)
SMFTYPE DS X Record type (set from SYSINI)

SMF Accounting 359
SMFTIME DS AL4 Current time

SMFDATE DS AL4 Current date
SMFSID DS CL4 Host system ID
SMFSUBS DS CL4 Server subsystem ID (set from SYSINI)
SMFSUBTYP DS OX Start of subtype field(s)
*****************************************************************
SUBTYPE X'0001' - SESSION ACCOUNTING RECORD
*****************************************************************
@ACCTLEN DS XL2 Accounting record length
@ACCTTYP DS XL2 Accounting record subtype (X'0001')
@ACCTUID DS CL8 Client logon (user) ID
@ACCTTID DS CL8 Thread ID
@ACCTAPL DS CL8 Application name (or loadmodule)
@ACCTSVC DS CL64 Service name
@ACCTCPU DS F CPU time in hundredths/second
@ACCTCNT DS F Message count
@ACCTBIN DS F Input packet byte count
@ACCTBOT DS F Input packet byte count
@ACCTDBC DS F Database calls
@ACCTBEG DS F Session start time (hhmmssth)
@ACCTEND DS F Session stop time (hhmmssth)
@ACCTNOD DS CL16 Client node name
@ACCTDBO DS F DB2 reconnects (thread management)
@ACCTCKP DS F DB2 checkpoints (thread management)
@ACCTSQC DS F Total SQL call CPU time (in microseconds)
Note: The following fields are DB2-specific and are not used for
Oracle services:
@ACCTDBO DS F DB2 reconnects (thread management)

@ACCTCKP DS F DB2 checkpoints (thread management)


361
Part 4: SequeLink ODBC

Edition Client Administration
ODBC Edition Client. It contains the following chapters:

and Windows NT”

Windows 3.1”

362 Part 4: SequeLink ODBC Edition Client Administration

363
10 SequeLink ODBC Edition Client

for Windows 9x and
Windows NT

perform for SequeLink ODBC Edition Client for Windows 9x and
Windows NT.

Stored
The SequeLink ODBC Edition Client preferences are stored in the
Windows 9x or Windows NT Registry in the key:
HKEY_LOCAL_MACHINE\SOFTWARE\INTERSOLV\SequeLink\
Client\sqlnkdll
This key is referred to as the Client Preferences Resource. All

other files required for SequeLink are stored in the SequeLink
ODBC Edition Client directory specified during installation. This
is a local directory on your workstation unless you are using the
SequeLink Client network installation. In this case, the directory
is a shared network directory.

364 Chapter 10 SequeLink ODBC Edition Client for Windows 9x and Windows NT
The Client Preferences Resource is divided into sections identified

by a section heading and followed by a set of key=value pairs.
Table 10-1 lists the sections in the Client Preferences Resource and
describes their purpose.
Table 10-1. Client Preferences Resource Sections (Windows 9x

and Windows NT)
Section Description
[general] General SequeLink information.
[sspmodules] Internal mappings used by SequeLink.
These values should not be changed.
[sqlnkcat] Internal mappings used by the SequeLink
CAT. These values should not be changed.
[encryption modules] List of installed encryption modules.
[compression modules] List of installed compression modules.
[ssptcpe] Settings for SequeLink TCP/IP services.
[tcp_services] Mappings between symbolic service names
and TCP ports.

Configuring SequeLink ODBC Edition Client 365
Configuring SequeLink ODBC Edition Client

■ “Changing the TCP Port” on page 365
■ “Changing the TCP/IP Connection Time-Out” on page 366
Note: Use the Registration Editor program, REGEDT32.EXE, to

change parameter values.
Changing the TCP Port

TCP/IP services are identified by a unique TCP port number.
Alternatively, you can assign a symbolic name for each service.
The symbolic name is mapped to the TCP port number in the
tcp_services section of the Client Preferences Resource.
Table 3-1, “Default Symbolic Names and TCP Port Numbers for
SequeLink Server Services” on page 108 shows the default
symbolic names, service types, and TCP ports for SequeLink
ODBC Edition Client.
To change the TCP port number, enter a new value for the port
number by editing the tcp_services section of your Client
Preferences Resource. Also, you can enter additional
servicename=portnumber pairs to the section for any new
services you want to add.
Note the following guidelines for changing port numbers:
■ Before you change a TCP port number, make sure that the
port number is not being used by another service. TCP port
Telnet) and cannot be used.

■ The port number on the client and server must match. For
platform-specific information about changing the TCP port
number on your server, see:
• Chapter 6, “SequeLink Server for Windows NT”
• Chapter 7, “SequeLink Server for UNIX”
• Chapter 8, “SequeLink Server for AS/400”
• Chapter 9, “SequeLink Server for OS/390”
Changing the TCP/IP Connection

Time-Out
When connecting to SequeLink Server using TCP/IP, the
connection attempt is discontinued if a reply is not received from
the server within a specified time. The default value for this
time-out period is 45 seconds.
To change the connection time-out:

1 In the Client Preferences Resource, locate the ssptcpe
section for TCP/IP services.
2 Edit the following line:
ConnectionTimeOut=45
changing the time-out value to another value between 1 and
600 seconds.

Quick Install Images 367
Quick Install Images

A Quick Install Image is a predefined, customized installation
image that you can use to install the same SequeLink ODBC
Edition Client configuration, including data source definitions,
on multiple workstations. It helps ensure that all SequeLink
clients in your organization or workgroup are installed and
configured in the same way. Minimal user interaction is required
to install the Quick Install Image.
You can configure a Quick Install Image with the following

options:
■ Workstation or Network Installation. You can configure a

workstation install or network install of the Quick Install
Image. If you configure:
• A workstation install, the SequeLink ODBC Edition Client

must be installed on each workstation.
• A network install, the SequeLink ODBC Edition Client will

be installed at a network location and each workstation
can share this network version. Before the network
version can be used, the Quick Install Image must be run
on each workstation.
■ Installation Directory. You can specify the directory where

SequeLink ODBC Edition Client will be installed. The default
directory is c:\Program Files\SequeLink ODBC Edition.
■ SequeLink Components. The SequeLink ODBC Driver and the

SequeLink CAT are required components that are
automatically installed when you create a Quick Install
image. Additionally, you can configure the Quick Install
image to install optional components. You must install at
least one network module. The SequeLink ODBC Data Source
SyncTool Administrator and the SequeLink Dictionary
Manager should be made available only to administrators.

Note: The SequeLink ODBC Driver is always installed in the

SequeLink ODBC Edition Client directory.
■ Interactive or Batch Mode. You can choose to run the Quick

Install image in Interactive or Batch mode. In Interactive
mode, a window appears at the end of the installation to
indicate whether the installation was completed successfully.
In Batch mode, no user interaction is required. At the end of
the installation, the INSTALL.LOG log file is created in one of
the following directories:
• The path specified by the TMP environment variable
• If TMP is not defined, the path specified by the TEMP
environment variable
• If neither TMP or TEMP is defined, the WINDOWS directory
Examine this file to determine whether the installation was

successful (see “Examining the INSTALL.LOG File” on
page 371).
■ Program Folder. You can specify whether a Program Folder

will be created. To hide the SequeLink ODBC Edition Client
software from the end user, you can choose not to create a
program folder.
■ Default Data Sources. Your Quick Install image can create a

set of default data sources. First, you must create a data
source file (.DSF) using the SequeLink Data Source SyncTool
Administrator. For instructions on creating data source files,
see “Using the SequeLink Data Source SyncTool” on page 95.
Note: Quick Install images only support data source files that
specify import in Merge or Overwrite mode.

Creating Quick Install Images

To create Quick Install images
■ From a CD, see the following section“From a CD,”
■ From files downloaded from the Web, see “From Files

Downloaded From the Web” on page 370
From a CD
1 Insert the CD into the CD-ROM drive. If you have a local
CD-ROM drive, this typically is drive D. If the CD-ROM drive is
on a network, mount the CD and create a mapping to the
CD-ROM drive.
2 Start the Product Setup:
a If AutoPlay for CDs is turned on, the CD starts

automatically.
b If AutoPlay for CDs is turned off, navigate to the root

directory on the CD, and click setupw32.exe.
3 Select SequeLink ODBC Edition for Windows 9x/NT from the

drop-down list.
4 Click Run Setup.
5 Enter your Serial Number and Key. You can find them on the
Product Registration Information card that is shipped with
the product.
6 Click the Create Quick Install image installation icon.
7 Follow the instructions that appear on your screen.
8 Select the directory to which the Quick Install image will be

saved. For network installations, this also is the directory that
will contain the SequeLink components. This directory can be
on a file server accessible to all users within a workgroup.

Note: To prevent users from deleting files from the Quick

Install image, we recommend that administrators grant users
read access only to the directory containing the Quick Install
Image.
9 Review the settings you specified for the Quick Install image.
When all settings are correct, click Next to build the image.
10 When the Quick Install Image as been built, click Finish. The
Product Setup window appears. You are now ready to run the
Quick Install Image on multiple workstations.
From Files Downloaded From the Web

1 Download the appropriate self-extracting ZIP file. Download
instructions are available on the Web site.
2 Open the contents of the ZIP file into a directory. For

example:
c:\temp\
3 Navigate to the directory to which you unzipped the files and
double-click on the setup.exe file to start the installation
program.
4 Follow the instructions on the Web page to register an

evaluation version of the SequeLink ODBC Edition Client
software. Then, click Next. A Serial Number and Key will be
mailed to you.




Image.
9 When the Quick Install Image as been built, click Finish. You
are now ready to run the Quick Install Image on multiple
workstations.
Installing a Quick Install Image

1 Go to the directory where the Quick Install image resides.
2 Double-click setup.exe.
3 If the Quick Install image was configured in Interactive mode,

click Finish when the installation is complete. If the Quick
Install image was configured in Batch mode, you will need to
examine the INSTALL.LOG file.
Examining the INSTALL.LOG File

After running a Quick Install image in batch mode, check the
INSTALL.LOG file to determine whether the installation was
successful. This file is located in one of the following directories:
■ The path specified by the TMP environment variable
■ If TMP is not defined, the path specified by the TEMP

■ If neither TMP or TEMP is defined, the WINDOWS directory

If the installation:
■ Is successful and no further action is required, the file will

contain OK
■ Is successful and your Windows 9x or Windows NT machine

needs to be restarted, the file will contain RESTART
■ Failed, the file will contain details about the failure’s cause

373

for Windows 3.1

perform for SequeLink ODBC Edition Client for Windows 3.1.

Stored
SQLNKDLL.INI file in the Windows directory. This file is also
called the Client Preferences Resource. All other files that are
needed for SequeLink are stored in the SequeLink ODBC Edition
Client directory specified during installation. This is a local
directory on your workstation unless you are using the
SequeLink Client network installation. In this case, the directory
The Client Preferences Resource is a standard text file that uses

an initialization (INI) file structure. It is divided into sections
identified by a heading and followed by a set of key=value pairs.
The section headings and key=value pairs are not case-sensitive.
A typical section may look like this:
[general]
sqlnkdir=c:\sqlnkwin\
logfile=c:\sqlnkwin\sqlnk.log

374 Chapter 11 SequeLink ODBC Edition Client for Windows 3.1
Table 11-1. Client Preferences Resource Sections (Windows 3.1)
Section Description
[sspmssna] Settings for SequeLink Microsoft SNA
Server services.
[ssprumba] Settings for SequeLink Rumba services.
[sspattm] Settings for SequeLink Attachmate
services.
[ssppcs] Settings for SequeLink Client Access/400
services.
and TCP ports.


The following table lists configuration tasks and points you to
the appropriate procedure:
■ “Specifying Yielding Behavior for TCP/IP” on page 377
■ “Specifying Yielding Behavior for APPC” on page 377
Note: You can change parameter values using a standard text

editor, such as Notepad.

TCP/IP services are identified by a unique TCP port number. In the
SequeLink data source definition, you can specify the TCP port in
the service name field of the database settings section.
tcp_services section of the Client Preferences Resource. Table
3-1, “Default Symbolic Names and TCP Port Numbers for
symbolic names, service types, and TCP ports.

platform-specific information about changing the port

Time-Out
When connecting using TCP/IP, the connection attempt is
discontinued if a reply is not received from the server within a
specified time. The default value for this time-out period is 45
seconds.

changing the current time-out value to another value
between 1 and 600 seconds.

Specifying Yielding Behavior for TCP/IP

You can specify whether your client can switch to other
applications while SequeLink waits for a reply from the server.
Add the following line to the ssptcpe section in the Client
Preferences Resource:
Yield=n
n can be 0 or 1.
Setting the value to 0 prevents application switching; setting it

to 1 allows application switching. Because switching does not
work with many Windows applications and can cause your
system to become unstable, yielding should be enabled only for
applications that prevent multiple reentries.
Specifying Yielding Behavior for APPC

You can specify whether your client can switch to other
applications while SequeLink waits for a reply from the server.
Add the following line to the appropriate section in the Client
Preferences Resource (see Table 11-1, “Client Preferences
Resource Sections (Windows 3.1)” on page 374 for a list of
sections):
Yield=n
n can be 0 or 1.
Setting the value to 0 prevents application switching; setting it

to 1 allows application switching. Because switching does not
work with many Windows applications and can cause your
system to become unstable, yielding should be enabled only for
applications that prevent multiple reentries.


image that you can use to install the same SequeLink ODBC
Edition Client configuration, including data source definitions, on
multiple workstations. It helps ensure that all SequeLink clients in
your organization or workgroup are installed and configured in
the same way. Minimal user interaction is required to install the
Quick Install Image.

options:

• A workstation install, the SequeLink ODBC Edition Client

must be installed on each workstation.
• A network install, the SequeLink ODBC Edition Client will

be installed at a network location and each workstation
can share this network version. Before the network
version can be used, the Quick Install Image must be run
on each workstation.

SequeLink ODBC Edition Client will be installed. The default
directory is c:\sqlnkwin.
■ SequeLink Components. The SequeLink ODBC Driver and the

SequeLink CAT are required components that are
automatically installed when you create a Quick Install image.
Additionally, you can configure the Quick Install image to
install optional components. You must install at least one
network module. The SequeLink ODBC Data Source SyncTool
Administrator and the SequeLink Dictionary Manager should
be made available only to administrators.

■ System Directory Installation. By default, the SequeLink

ODBC Driver will be installed in the Windows System
directory. You also can configure the quick install image to
install the SequeLink ODBC Driver in the SequeLink directory.
For network installations, the SequeLink ODBC Driver is
installed in the SequeLink directory.
Note: If you choose to install the SequeLink ODBC Driver in

the SequeLink directory, the PATH environment variable must
be modified during the installation and you may need to
restart the machine after installation.



page 382).

will be created. To hide the SequeLink ODBC Edition Client
program folder.

set of default data sources. You first must create a data
source file (.DSF) using the SequeLink ODBC Data Source
SyncTool Administrator. For instructions on creating data

source files, see “Using the SequeLink Data Source SyncTool”

on page 95.

To create Quick Install images:
■ From a CD, see the following section “From a CD”

From a CD
CD-ROM drive.
2 Start the Product Setup. Navigate to the root directory on the

CD, and click setupw16.exe.
3 Select SequeLink ODBC Edition for Windows 3.1 from the

drop-down list.
4 Click Run Setup.
the product.

saved. For network installations, use the directory that

contains the SequeLink components. This directory can be on

a file server accessible to all users within a workgroup.

image.
Product Setup window appears. You are now ready to run
the Quick Install Image on multiple workstations.

1 Download the self-extracting 16-bit ZIP file. Download

example:
c:\temp\
3 Navigate to the directory to which you unzipped the files
and double-click on the setup.exe file to start the installation
program.

evaluation version of the SequeLink ODBC Edition Client
mailed to you.



image.
9 When the Quick Install Image has been built, click Finish. You
workstations.



successful. This files is located in one of the following directories:



contain OK
■ Is successful and your machine needs to be restarted, the file

will contain RESTART


385

for Macintosh

perform for SequeLink ODBC Edition Client for Macintosh.

Stored
SQLNKDLL file in the SequeLink folder in the Preferences folder.
This file is also called the Client Preferences Resource. The
SequeLink folder also contains all other files needed for
SequeLink.

an initialization (INI) file structure. It is divided into sections that
are identified by a heading followed by a set of key=value pairs.
The section headings and key=value pairs are not case-sensitive.
A typical section may look like this:
[tcp_services]
SLORACLE=4003

386 Chapter 12 SequeLink ODBC Edition Client for Macintosh
Table 12-1 identifies the sections in the Client Preferences

Resource and describes their purpose.
Table 12-1. Client Preferences Resource Sections (Macintosh)
Section Description
[general] General information
[encryption modules] List of installed encryption modules
[compression modules] List of installed compression modules
[ssptcpe] Settings for SequeLink ODBC Edition Client
for TCP/IP services
and TCP ports


The only configuration task you may need to perform is
changing the TCP port.

the Service Name field of the Database Settings section.
This symbolic name is mapped to the TCP port number in the
tcp_services section of the Client Preferences Resource.
Table 3-1, “Default Symbolic Names and TCP Port Numbers for
symbolic names, service types, and TCP ports.

388 Chapter 12 SequeLink ODBC Edition Client for Macintosh

389

for UNIX

perform for SequeLink ODBC Edition Client for UNIX.

Stored
hidden file .sqlnkdll.ini, which can be found in the INI
subdirectory of your SequeLink ODBC Edition Client directory.
This file is referred to as the Client Preferences Resource.

an INI file structure. It is divided into sections identified by a
heading and followed by a set of key=value pairs. The section
headings and key=value pairs are not case-sensitive. A typical
section may look like this
[general]
sqlnkdir=/users/smith/slclient

390 Chapter 13 SequeLink ODBC Edition Client for UNIX
Table 13-1 identifies the sections in the Client Preferences

Resource and describes their purpose.
Table 13-1. Client Preferences Resource Sections (UNIX)
Section Description
[general] General information.
[sqlnkcat] Internal mappings used by SequeLink CAT
software. These values should not be
changed.
[ssptcpe] Settings for TCP/IP services.
[tcp_services] Mappings between symbolic service
names and TCP ports.


Note: You can change parameter values using a standard text

editor, such as vi or emacs.

the service name field of the database settings section.
SequeLink Server looks in the /etc/services file for the symbolic
name. If it is not found in this file, it is mapped to the TCP port
number in the tcp_services section of the Client Preferences
Resource. Table 3-1, “Default Symbolic Names and TCP Port
Numbers for SequeLink Server Services” on page 108 shows the
default symbolic names, service types, and TCP ports.

392 Chapter 13 SequeLink ODBC Edition Client for UNIX

Time-Out
When connecting using TCP/IP, the connection attempt is
discontinued if a reply is not received from the server within a
specified time. The default value for this time-out period is
45 seconds.

section.
600 seconds.

393
Part 5: SequeLink OLE DB

Edition Client Administration
OLE DB Edition Client. It contains the following chapters:


394 Part 5: SequeLink OLE DB Edition Client Administration

395
14 SequeLink OLE DB Edition

Client for Windows 9x and
Windows NT

perform for SequeLink OLE DB Edition Client for Windows 9x
and Windows NT.

Stored
The SequeLink OLE DB Edition Client preferences are stored in
the Windows 9x or Windows NT Registry in the key:
HKEY_LOCAL_MACHINE\SOFTWARE\INTERSOLV\SequeLink\
Client\sqlnkdll
This key is referred to as the Client Preferences Resource. All

other files required for SequeLink are stored in the SequeLink
OLE DB Edition Client directory specified during installation. This
is a local directory on your workstation unless you are using the
SequeLink client network installation. In this case, the directory

396 Chapter 14 SequeLink OLE DB Edition Client for Windows 9x and Windows NT
The Client Preferences Resource is divided into sections identified

by a section heading and followed by a set of key=value pairs.
Table 14-1. Client Preferences Resource Sections (Windows 9x

and Windows NT)
Section Description
and TCP ports.

Configuring SequeLink OLE DB Edition Client 397
Configuring SequeLink OLE DB Edition Client

Note: You can change parameter values using the Registration

Editor program, REGEDT32.EXE.

TCP/IP services are identified by a unique TCP port number.
tcp_services section of the Client Preferences Resource. Table
3-1, “Default Symbolic Names and TCP Port Numbers for
symbolic names, service types, and TCP ports for SequeLink
OLE DB Edition Client.

platform-specific information about changing the TCP port

Time-Out
When connecting to SequeLink Server using TCP/IP, the
connection attempt is discontinued if a reply is not received from
the server within a specified time. The default value for this
time-out period is 45 seconds.

600 seconds.


image that you can use to install the same SequeLink OLE DB
Edition Client configuration, including data source definitions,
on multiple workstations. It helps ensure that all SequeLink
clients in your organization or workgroup are installed and
configured in the same way. Minimal user interaction is required
to install the Quick Install Image.

options:

• A workstation install, the SequeLink OLE DB Edition

Client must be installed on each workstation.
• A network install, the SequeLink OLE DB Edition Client

will be installed at a network location and each
workstation can share this network version. Before the
network version can be used, the Quick Install Image
must be run on each workstation.

SequeLink OLE DB Edition Client will be installed. The default
directory is c:\Program Files\SequeLink OLE DB Edition.
■ SequeLink Components. The SequeLink OLE DB Provider and

the SequeLink CAT are required components that are
automatically installed when you create a Quick Install
image. Additionally, you can configure the Quick Install
image to install optional components. You must install at
least one network module. The SequeLink OLE DB Data
Source SyncTool Administrator should be made available only
to administrators.

Note: The SequeLink OLE DB Provider is always installed in the

SequeLink OLE DB Edition Client directory.


page 403).

will be created. To hide the SequeLink OLE DB Edition Client
program folder.

set of default data sources. First, you must create a data
source file (.OSF) using the SequeLink OLE DB Data Source
SyncTool Administrator. For instructions on creating data
source files, see “Using the SequeLink Data Source SyncTool”
on page 95.


To create Quick Install images:
■ From a CD, see the following section“From a CD”

From a CD
CD-ROM drive.
2 Start the Product Setup:
a If AutoPlay for CDs is turned on, the CD starts

automatically.
b If AutoPlay for CDs is turned off, navigate to the root

directory on the CD, and click setupw32.exe.
3 Select SequeLink OLE DB Edition for Windows 9x/NT from

the drop-down list.
4 Click Run Setup.
the product.


Note: We recommend that administrators only give users read

access to the directory containing the Quick Install Image to
prevents users from deleting files from the Quick Install
Image.
Product Setup window appears. You are now ready to run the
Quick Install Image on multiple workstations.

1 Download the appropriate self-extracting ZIP file. Download

example:
c:\temp\
3 Navigate to the directory to which you unzipped the files and
double-click on the setup.exe file to start the installation
program.

evaluation version of the SequeLink OLE DB Edition Client
mailed to you.




Image.
9 When the Quick Install Image as been built, click Finish. You
workstations.



successful. This file is located in one of the following directories:


contain OK

■ Is successful and your Windows 9x or Windows NT machine

needs to be restarted, the file will contain RESTART

405
Part 6: Appendix
This part provides provides additional information about
SequeLink. It contains the following appendix:
■ Appendix A, “TCP/IP (UDP) Communication (OS/390)”

contains specific administration information for customers
that use TCP/IP (UDP) communication on OS/390.

406 Part 6: Appendix

407
A TCP/IP (UDP) Communication

(OS/390)
OS/390 SequeLink Server for OS/390 4.51 is the last version of SequeLink
Server that will provide TCP/IP (UDP) support. Use it only to
upgrade any existing SequeLink Server for DB2 installations to
use TCP/IP communication.
Note: SequeLink Server for Oracle7 does not provide

TCP/IP (UDP) support.
Because TCP/IP (UDP) support is the only network support

provided for Interlink TCP/IP, this version of SequeLink Server for
OS/390 is also the last version that will support Interlink TCP/IP.
This appendix contains specific administration information for

customers that use TCP/IP (UDP) communication on OS/390.
About TCP/IP (UDP) Support

TCP/IP (UDP) support is provided by the TCP/IP (UDP) NIM. The
TCP/IP (UDP) NIM starts a task that uses the TCP/IP (UDP) network
layer. This task monitors a specific UDP port for connection
requests from clients. These connection requests include a
service name that corresponds to a section in the SYSINI file.
The task waits for an incoming TCP connection request from a

client on a particular TCP port. On receiving a request, the
TCP/IP (UDP) NIM sends the client a UDP message naming this
TCP port. The client then sets up a TCP connection to the
service task.

408 Appendix A TCP/IP (UDP) Communication (OS/390)
The default UDP port used by the TCP/IP (UDP) NIM is 2000. For
more information about changing UDP ports:
■ On the OS/390 server, see “Modifying IBM TCP/IP (UDP)

Parameters” on page 408 and “Modifying Interlink TCP/IP
(UDP) Parameters” on page 411
■ On the client, see “Changing UDP Ports on the SequeLink

Client” on page 414
Modifying IBM TCP/IP (UDP) Parameters

The [IBM_TCP/IP] section contains parameters required by the
IBM TCP/IP (UDP) NIM. Table 14-2 lists the IBM TCP/IP (UDP)
parameters you can customize and provides a description and
valid values for each parameter.
Table 14-2. IBM TCP/IP (UDP) Parameters (OS/390)

[IBM_TCP/IP] DEBUG This puts the NIM in debugging mode. Only
specify this parameter if requested by
MERANT technical support.
HOSTNAME This specifies the name of the server/host
running SequeLink Server. Consult your
TCP/IP administrator for this information. It
should match the name specified by the
HOSTNAME parameter in the hlq.TCPIP.DATA
or hlq.TCPPARMS(TCPDATA) configuration
dataset.
KEEPALIVE This specifies whether the TCPKeepAlive
option is turned on. Valid values include ON
and OFF. The default is OFF. The interval
used by the KeepAlive mechanism to cancel a
session is specified in the KEEPALIVEOPTIONS
statement in the TCP/IP configuration
dataset.

Modifying IBM TCP/IP (UDP) Parameters 409
Table 14-2. IBM TCP/IP (UDP) Parameters (OS/390) (cont.)

LAUNCH This starts the NIM at initialization. Valid
values include YES and NO. The default is
YES. If you do not want to use TCP/IP (UDP),
specify NO.
MAXIMUMPACKETSIZE This specifies the maximum network
input/output buffer size, in bytes. You can
specify a nonzero value lower than or equal
to 32000. If the lrg-env-size value of the
LARGEENVELOPEPOOLSIZE parameter in the
TCP/IP configuration dataset is lower than
the MAXIMUMPACKETSIZE, the lrg-env-size
will be used. If the MAXIMUMPACKETSIZE is
lower than the lrg-env-size, the
MAXIMUMPACKETSIZE will be used. If there is
no TCPCONFG DD name in the server startup,
the default of 8192 will be used; this can be
overridden if the MAXIMUMPACKETSIZE
contains a lower value.
simultaneous connection requests that
SequeLink Server can handle. You can specify
any nonzero value. Once this value is
reached, the NIM will not accept any
NOAPI This specifies the action to be performed by
the NIM if TCP/IP is unavailable when the NIM
initializes or when it is down. Valid values
include ABEND and SLEEP. If set to ABEND,
TCPIPNIM terminates abnormally. If set to
SLEEP, the NIM suspends TCP/IP operations.
When TCP/IP comes back online, the NIM
automatically restarts. The default is ABEND.

Table 14-2. IBM TCP/IP (UDP) Parameters (OS/390) (cont.)

PORT This specifies the 4-character service port
number that client applications use to
establish connections and request a list of
services offered by the server. The default is
2000. This value should not be changed,
unless it conflicts with the port number of
another TCP/IP service.
TIMEOUT This specifies a time-out interval (in seconds)
for TCP/IP requests to the TCP/IP address
space. The default is 5. If TCP/IP does not
respond to a request within this interval, the
thread (session) is terminated after issuing
VAIT048E and VAIT006E messages. If set to 0,
TCP/IP requests are not timed. For example,
the NIM will wait until it receives a response
from the TCP/IP address space.
TRACE This turns on or off logging of trace messages
for specific components and workstations.
USERID This specifies the name of the started
procedure used to start the TCPIP address
space. You can find the value in the
hlq.TCPIP.DATA dataset as the value of
TCPIPUSERID. The default is TCPIP.

Modifying Interlink TCP/IP (UDP) Parameters 411
Modifying Interlink TCP/IP (UDP) Parameters

The [Interlink_TCP/IP] section contains parameters required by
the Interlink TCP/IP (UDP) NIM. Table 14-3 lists the Interlink
TCP/IP (UDP) parameters you can customize and provides a
description and valid values for each parameter.
Table 14-3. Interlink TCP/IP (UDP) Parameters (OS/390)

[INTERLINK_TCP/IP] DEBUG This puts the NIM in debugging mode. Only
specify this parameter if requested by
MERANT technical support.
DNRSERVICE This specifies whether the NIM will issue a
Domain Name Resolver (DNR) call to translate
the client’s local protocol address to a
DNS-style name. This name appears in the
HOSTNAME column of any status message
displayed for a connection. Valid values
include ON and OFF. The default is ON.
KEEPALIVE This specifies whether the TCPKeepAlive
option is enabled. The value may be ON or
OFF. The default is OFF.
KEEPALIVETIME This specifies the time (in minutes) for which
a client is allowed to be idle before the
TCPKeepAlive mechanism cancels the session.
This parameter is required only when
KEEPALIVE=ON. The default is 120. The
TCP/IP lower limit of KEEPALIVETIME is 30.
LAUNCH This starts the NIM at initialization. Valid
values include YES and NO. The default is
YES. To use TCP/IP (UDP), specify NO.

Table 14-3. Interlink TCP/IP (UDP) Parameters (OS/390) (cont.)

MAXIMUMPACKETSIZE This specifies the maximum network
input/output buffer size, in bytes. You can
specify a value between 256 and 32000. If
the MAXIMUMPACKETSIZE in the SYSINI is
greater than the packet size Interlink TCP/IP
can handle and automatic override is
performed, the packet size will be lower than
that specified in the SYSINI. The
MAXIMUMPACKETSIZE in the SYSINI must not
exceed the maximum limits established in the
Interlink Transport Service Information Block
(TIBLTSND and TIBLTRCV).
simultaneous connection requests the server
can handle. Specify any value in the range of
8 to 2048. Once the value you specified is
reached, the NIM will not accept any more
NAGLEOPTION This specifies whether the TCP/IP Nagle
algorithm is enabled. The Nagle algorithm
optimizes performance by gathering
outbound data into maximal packets. We
recommend that you disable the Nagle
algorithm, so that outbound packets are
transmitted when they are received. Valid
values include:
■ ON enables the Nagle algorithm option.
■ OFF disables the Nagle algorithm option.
■ UNA indicates that the Nagle algorithm
option is not available for this TCP/IP
implementation.
The default is OFF.

Modifying Interlink TCP/IP (UDP) Parameters 413

NOAPI This specifies the action to be taken by the
NIM when:
■ SNS/API is unavailable when the NIM
initializes
■ SNS/API signals that it is ready to shut

down
Valid values include ABEND and SLEEP. If set
to ABEND, the NIM terminates abnormally. If
set to SLEEP, the NIM suspends TCP/IP
operations. When the SNS/API comes back
online, the NIM automatically restarts. The
default is ABEND.
PORT This specifies the 4-character service port that
client applications use to establish
connections and request a list of server
services. The default is 2000 and should not
be changed, unless it conflicts with the port
number of another TCP/IP service.
SESSTERMTYPE This specifies the type of session termination
supported by the NIM. Valid values include
ORDERLY and IMMEDIATE.
If set to ORDERLY, the NIM attempts an
orderly shutdown of the session after the
service has completed its work. If the client
does not support or acknowledge orderly
shutdown, the session will not terminate on
its own and the operator must use the
ABORT command. This is the default.
If set to IMMEDIATE, the orderly shutdown
logic is bypassed and the session is closed
immediately. If you use this value and the
client does support orderly shutdown, the
client will receive an error when an orderly
shutdown request is made. This situation only
will occur if the client initiates the shutdown.


SUBSYSID This parameter specifies the subsystem name
used by the NIM to establish communication
with the Interlink SNS/API. This can be any 1-
to 4-character name. The default is ACSS.
TRACE Turns on or off logging of trace messages for
specific components and workstations.
Changing UDP Ports on the SequeLink Client

UDP port numbers must match on the client and the server. This
section contains instructions on changing the UDP port number
on your SequeLink client.
On Windows 9x and Windows NT

The default UDP port number used for TCP/IP (UDP) services is
2000. If another service is using port 2000, you will need to
change the port number to an unused port number in the range
1024 to 32767. Port numbers lower than 1024 are reserved.
To change a UDP port number:

1 Locate the ssptcp32 section in the Client Preferences
Resource.
2 Change the port number found in the PortNumber key, so

that it identifies a new unused port number in the range 1024
to 32,767. The default is 2000. For example:
Original Key: PortNumber=2000 (the default)

Changed Key: PortNumber=3999

Changing UDP Ports on the SequeLink Client 415
Notes:
■ The UDP port number also can be specified on a per

connection basis by specifying the port number and the
service name, separated by a period (.) in the SequeLink CAT
data source definition. For example:
3023.SLOracle
■ The port number on the client and server must match.
On Windows 3.1
The default UDP port number used for SequeLink is 2000. If
another service is using port 2000, you will need to change the
SequeLink port number to an unused port number in the range
1024 to 5000. Port numbers lower than 1024 are reserved.
To change the UDP port number:

1 Locate the ssptcpw section in the Client Preferences
Resource.
2 Change the port number found in the PortNumber key, so

that it identifies a new unused port number in the range
1024 to 32767. The default is 2000. For example:
Original Key: PortNumber=2000 (the default)

Changed Key: PortNumber=3999
Notes:
■ The UDP port number also can be specified on a per

connection basis by specifying the port number and the
service name, separated by a period (.) in the SequeLink CAT
data source definition. For example:
3023.SLOracle
■ The port number on the client and server must match.

Running Multiple SequeLink Servers

If you are using TCP/IP (UDP) and want to run multiple SequeLink
Servers, each SequeLink Server may use the IBM TCP/IP (UDP) NIM
or the Interlink TCP/IP (UDP) NIM. This means several SequeLink
TCP/IP (UDP) NIMs may be running at the same time. In addition,
the following requirements apply:
■ Each TCP/IP (UDP) NIM must use a unique IP address and PORT
value.
■ The IP address space for each TCP/IP (UDP) NIM must be

specified in the SUBSYSID or USERID value.
Each TCP/IP (UDP) NIM services communication requests on a

particular IP address and port number. The IP address/port
number combination used for each TCP/IP (UDP) NIM must be
unique. For example, you may want to use a different IP address
for each TCP/IP (UDP) NIM and the same port for every IP address,
or a different port for each TCP/IP (UDP) NIM and the same
IP address for each port.
Note:
■ Even if you are running a single SequeLink Server with a

single TCP/IP (UDP) NIM, you may need to change the PORT
value in the [IBM_TCP/IP] or [INTERLINK_TCP/IP] section, if
another application on the same OS/390 server is already
using port 2000.
■ The port number used by your clients must match the port
number in the SYSINI. If all your SequeLink Server services use
the same port number or if you have only one service, set the
default port number at your clients.
If you are using multiple port numbers, specify the correct port
number at connection or when you configure the SequeLink data
source using the SequeLink CAT.

IP addresses are determined by the number of TCP/IP address

spaces running on your OS/390 server. For Interlink TCP/IP (UDP),
the TCP/IP address space is identified by its OS/390 subsystem
name (the SUBSYSID parameter in the [INTERLINK_TCP/IP]
section of the SYSINI). For IBM TCP/IP (UDP), the TCP/IP address
space is identified by name (the USERID parameter in the
[IBM_TCP/IP] section of the SYSINI).
Active port numbers for an IP address are determined by

SequeLink Server. The PORT parameter in the [INTERLINK_TCP/IP]
or [IBM_TCP/IP] section of the SYSINI will show you which port
number to use.
Using Operator Commands

From an operator’s console, enter the command:
F jobname,compid command parms
where:
jobname is the job name or started task name of the server.

■ TCP - IBM TCP/IP (UDP) NIM
■ ICS - Interlink TCP/IP (UDP) NIM


IBM TCP/IP (UDP) NIM Commands

Table 14-4. IBM TCP/IP (UDP) NIM Commands
Command: ABORT
specific client.
Parameter: NAME= A specific NIM-assigned connection
name, which can be obtained by
issuing a DISPLAY NAME=ALL
command. This parameter is
required.
Example: TCP ABORT NAME=TCP00110 aborts all
conversations between the server and the client
named TCP00110.
Command: CLOSE
Purpose: To close a TCP/IP (UDP) connection.
required.
Example: TCP CLOSE NAME=TCP00111 closes the connection
with the NIM-assigned name of TCP00111.

Table 14-4. IBM TCP/IP (UDP) NIM Commands (cont.)
Command: DISPLAY or SHOW

Purpose: To display a TCP/IP (UDP) connection.
Parameter: NAME= A specific taskname or ALL. If a
specific taskname is stated, the
display is shown for that connection
only. If ALL is specified, all
connections are displayed. This
parameter is required.
Example: TCP DISPLAY NAME=TCP00123 displays the
connection with the NIM-assigned name TCP00123.
TCP SHOW NAME=TCP00123 displays the connection
with the NIM-assigned name TCP00123.
TCP DISPLAY NAME=ALL displays a list of all
TCP SHOW NAME=ALL displays a list of all
Command: KEEPALIV
Purpose: To enable/disable the TCPKeepAlive facility.
Parameter: SET=on|off Turns on and off the TCPKeepAlive
facility.
This command results in the message
VAIT1521I, which displays the
current status of the TCPKeepAlive
facility.
Example: TCP KEEPALIV SET=on turns on the TCPKeepAlive
facility for all connections made after the command is
issued. Current connections are not affected.
TCP KEEPALIV SET=off turns off the
TCPKeepAlive facility for all connections made after
the command is issued. Current connections are not
affected.

Command: LGNSTART
Parameter: None
Example: TCP LGNSTART allows users to log on using TCP/IP
(UDP).
Command: LGNQSTAT
Parameter: None
Example: TCP LGNQSTAT displays the status of the NIM logon
queue.
Command: LGNSTOP
Parameter: None
Example: TCP LGNSTOP prevents any user from logging on
using TCP/IP (UDP).
Command: RESTART
Purpose: To restart the NIM. This command does not give a
warning to users who are logged on. All active sessions
are terminated immediately.
Parameter: None
Example: TCP RESTART restarts the NIM.
Command: SHUTDOWN
its clients.
Example: TCP SHUTDOWN TYPE=immed shuts down the
TCP SHUTDOWN TYPE=normal shuts down the

Command: STATUS
Purpose: To display the general status of the NIM.
Parameters: None.
Examples: TCP STATUS displays the general status of the NIM.
Command: TRACE
Purpose: To turn on and off tracing, and to check whether
tracing is turned on or off.
SET=? Indicates whether tracing is turned
on or off.
Example: TCP TRACE SET=on turns on tracing.
TCP TRACE SET=off turns off tracing.
TCP TRACE SET=? returns a status, indicating

Interlink TCP/IP (UDP) NIM Commands

Table 14-5. Interlink TCP/IP (UDP) NIM Commands
Command: ABORT
specific client. When the NIM processes an ABORT
command, it attempts to contact the service to alert it
of the session abort condition and give the application
a chance to perform its own cleanup before the session
is terminated.
The NIM defers its final session cleanup until it is
notified that the service has acknowledged the abort
signal and has completed its cleanup process. If the
application does not acknowledge the abort signal,
the NIM does not complete its cleanup task. However,
the NIM will detect a second ABORT command for the
session, so that it can unconditionally perform cleanup
tasks for a session.
required.
Example: ICS ABORT NAME=TCP00110 aborts all
conversations between the server and the client
named TCP00110.
Command: CLOSE
Purpose: To close a TCP/IP (UDP) connection.
required.
Example: ICS CLOSE NAME=TCP00111 closes the connection
with the NIM-assigned name of TCP00111.

Table 14-5. Interlink TCP/IP (UDP) NIM Commands (cont.)
Command: DISPLAY or SHOW

Purpose: To display a TCP/IP (UDP) connection.
Parameter: NAME= A specific taskname or ALL. If a
specific taskname is stated, the
display is shown for that connection
only. If ALL is specified, all
connections are displayed. This
parameter is required.
Example: TCP DISPLAY NAME=TCP00123 displays the
connection with the NIM-assigned name TCP00123.
TCP SHOW NAME=TCP00123 displays the connection
with the NIM-assigned name TCP00123.
TCP DISPLAY NAME=ALL displays a list of all
TCP SHOW NAME=ALL displays a list of all
Command: KEEPALIV
Purpose: To enable/disable the TCPKeepAlive facility. This
command results in the message VAIK052I, which
displays the status of the TCPKeepAlive facility.
Parameter: SET=on|off Turns on and off the TCPKeepAlive
facility. This parameter is required.
Example: ICS KEEPALIV SET=on turns on the TCPKeepAlive
facility for all connections made after the command is
issued. Current connections are not affected.
ICS KEEPALIV SET=off turns off the
TCPKeepAlive facility for all connections made after
the command is issued. Current connections are not
affected.
Command: LGNSTART
Parameter: None
Example: ICS LGNSTART allows users to log on using TCP/IP
(UDP).

Command: LGNQSTAT
Parameter: None
Example: ICS LGNQSTAT displays the status of the NIM logon
queue.
Command: LGNSTOP
Parameter: None
Example: ICS LGNSTOP prevents any user from logging on
using TCP/IP (UDP).
Command: RESTART
Purpose: To restart the NIM. This command does not give a
warning to users who are logged on. All active sessions
are terminated immediately.
Parameter: None
Example: ICS RESTART restarts the NIM.
Command: SHUTDOWN
its clients.
Example: ICS SHUTDOWN TYPE=immed shuts down the
ICS SHUTDOWN TYPE=normal shuts down the
Command: STATUS
Purpose: To display the general status of the NIM.
Parameters: None.
Examples: ICS STATUS displays the general status of the NIM.

Command: TRACE
Purpose: To turn on and off tracing facility on and off, and
check whether tracing is turned on or off.
SET=? Indicates whether tracing is turned
on or off.
Example: ICS TRACE SET=on turns on tracing.
ICS TRACE SET=off turns off tracing.
ICS TRACE SET=? returns a status, indicating


427
Index
A Attachmate (CPIC), configuring SNA

networks 138
Attachmate, SequeLink data source network
about, SequeLink parameters 90
ODBC Socket 34, 93 Authorized applications list, specifying
Access to services, limiting 125 AS/400 283
Activating services OS/390 338
UNIX 267 UNIX 270
Windows NT 247 Windows NT 250
Adding services Automatic execution of commands at
UNIX 261 startup (OS/390) 338
Windows NT 242 Autostart, setting (Windows NT) 253
Administrator tools 36
Aliases (OS/390) 178
APPC
Parameters (OS/390) 332
SNA network 109
B
Windows 3.1x 377
Base component parameters (OS/390) 301
APPC NIM commands 346
Binary support, turning on and off
Application IDs, using 125
(AS/400) 285
Architecture, SequeLink 39
Binding DBRMs to DB2 (OS/390) 170
AS/400
ASCII- to-EBCDIC conversion 281
Authorized applications list 283
Calling initialization programs 289
Changing the default isolation level 286
C
Creating and deleting user defined
services 287 Changing
Default class description, changing 285 Connection time-out
EBCDIC-to-ASCII conversion 282 UNIX 392
Fine-tuning system performance 179 Windows 9x/NT 366, 398
Logging option, turning on and off 284 Default class description (AS/400) 285
Multimember support 291 Default isolation level (AS/400) 286
Network parameters 136 TCP port numbers
OS/400 commands 290 UNIX 271, 391
Translation options, changing 279 Windows 3.1x 375
Turning binary support on and off 285 Windows NT 251
ASCII-to-EBCDIC conversion 281 Translation options (AS/400) 279
UDP ports 414, 416

428 Index
Class description, AS/400 285 SequeLink data sources (Macintosh and

Client Access/400 Windows)
Configuring SNA networks 145 From an existing data source 59
SequeLink data source network From scratch 54
parameters 90 SequeLink data sources (UNIX) 63
Client configuration file location SSDD tables (OS/390) 169
Macintosh 385 SSDDs 164
UNIX 389 User-defined services (AS/400) 287
Windows 3.1x 373 Cross-database settings 183
Windows 9x/Windows NT 363, 395 Cross-platform configuration 112
CNTL Cursor behavior at Commit/Rollback
Commands 348 DB2 198
Input record usage 171 Informix 7 203
Compression 72, 128 Informix 9 207
Concurrent active SQL statements
Informix 7 203
Informix 9 207
Oracle8 222 D
Configuration mode, SequeLink Server
Administrator (Windows NT) 241 Data
Configuring Compression 128
Cursor behavior at Commit/Rollback Encryption 128
DB2 198 Data dictionary information, extracting 154
Informix 7 203 Data source name 55
Informix 9 207 Data sources
Data dictionary extraction 156 Exporting 96, 101
SNA networks 135 Importing 98, 103
Connection ODBC 49
Management (UNIX) 264 ODBC 3.0 file data source 99
Refusal details SequeLink 47
UNIX 124, 269 Synchronizing 51
Windows NT 118, 249 Database
Time-out, changing Data dictionary filters
UNIX 392 DB2 for OS/390 200
Windows 9x/Windows NT 366, 398 Specifying 186
contacting Technical Support 28 Using 161
Conventions used in this book 25 Diagnostic formats 183
Creating Extracting data dictionary
Quick Install images information 185
Windows 3.1 369, 380 Meta-information, retrieving 151
Windows 9x and Windows NT 369 Open transactions at logoff 183
Read-only services 184
Database user authentication (Microsoft SQL
Server) 119

Index 429
Database-specific information 182 Displaying host names and IP addresses

DataDictionary parameter, setting 156 (Windows NT) 246
DataDirect Connect ODBC Drivers Domain name, setting
(ODBC Driver Pack) 35 (Windows NT) 118, 250
DB2
Configuring cursor behavior at Com-
mit/Rollback 198
Graphic data types 198 E
DB2 for AS/400, SequeLink functionality 191
DB2 for OS/390 EBCDIC-to-ASCII conversion 282
Application support package Encryption 72, 128
commands 356 Example
DB2 filter settings 200 Creating a new SequeLink data source
Fine-tuning system performance 179 (UNIX ) 64
Multiple DB2 interface parameters, Modifying a SequeLink data source
modifying 308 (UNIX) 66
SequeLink functionality 195 SSDD 154
Service parameters 326, 328 SYSIN input record 173
Settings 199 SYSINI 294
Using stored procedures 196 Testing a data source (UNIX) 69
DB2 on AS/400, SequeLink data source Testing a SequeLink data source (UNIX) 69
service parameters 75 Existing services list (UNIX) 264
DB2 on NT, service parameters 77 Exporting data sources 96, 101
DB2 on OS/390, service parameters 78 Extracting data dictionary
DB2 on UNIX, service parameters 78 information 154, 185
Deactivating services
UNIX 267
Windows NT 247
Default F
Class description (AS/400) 285
Isolation level, changing (AS/400) 286 Features, SequeLink 42
Deleting FILECACHE parameters (OS/390) 329
SequeLink data sources (Macintosh and Fine-tuning system performance
Windows) 61 DB2 for AS/400 179
Services DB2 for OS/390 179
UNIX 263 Informix 7 and 9 180
Windows NT 243 Oracle 179
User-defined services (AS/400) 287 Sybase System 10 and 11 180
Description, SequeLink data source 56 Firewalls 130
Details, connection refusal Functional overview, SequeLink 41
(Windows NT) 118
Diagnostic formats 183

430 Index
G J
Graphic data types (DB2) 198 JDBC
Preparing for client access
UNIX 273
Windows NT 254
H
Host user definitions 149
L
Limiting access to services 125
I Log file directory, specifying
(Windows NT) 252
IBM Personal Communications Logging option, turning on and off
Configuring SNA network 139 AS/400 284
SequeLink data source network OS/390 339
parameters 91 UNIX 272
Importing data sources 98, 103 Windows NT 252
Informix 7 LOGR commands 351
Concurrent active statements 203
Cursor behavior at Commit/Rollback 203
SequeLink functionality 201
Informix 9 M
Concurrent active SQL statements 207
Cursor behavior at Commit/Rollback 207 Macintosh
SequeLink functionality 205 Client configuration file location 385
Informix on Windows NT, SequeLink data Deleting SequeLink data sources 61
source service parameters 79 Starting SequeLink CAT 53
Informix, fine-tuning system Testing SequeLink data sources 61
performance 180 Managing
Initialization programs, AS/400 289 Different SSDD versions 168
Internet Retrieval of database
Security 132 meta-information 151
System performance 132 Meta-information, managing
IP addresses, displaying (Windows NT) 246 retrieval of 151
Isolation level, changing (AS/400) 286 Microsoft SNA Server, configuring SNA
networks 141
Microsoft SQL Server
Database user authentication 119
SequeLink data source service
parameters 80

Index 431
Modifying Open transactions at logoff 183

ASCII-to-EBCDIC tables 335 OpenINGRES
Multiple DB2 interface parameters SequeLink data source service
(OS/390) 308 parameters 86
SequeLink data source example (UNIX) 66 SequeLink functionality 210
SequeLink data sources (Macintosh and Operator commands (OS/390) 343
Windows) 61 Oracle
Multimember support, AS/400 291 Fine-tuning system performance 179
SequeLink functionality 215, 220
Oracle8, concurrent active statements 222
OS/390
N Aliases 178
APPC NIM commands 346
Name, data source 55 APPC parameters 332
NETSRV.LOG 339 Automatic execution of commands at
Nonrelational database support, SequeLink startup 338
ODBC Socket 34 Base component parameters 301
Binding DBRMs to DB2 170
CNTL commands 348
Configuring SNA networks 137
O Creating SSDD tables 169
DB2 application support package
ODBC commands 356
Data dictionary extraction 155 DB2 service parameters 326, 328
Data sources 49 FILECACHE parameters 329
DataDirect ODBC Connect (Driver Pack) 35 IBM TCP/IP (UDP) NIM commands 418
Driver, SequeLink 31 IBM TCP/IP (UDP) parameters 408
ODBC 3.0 file data sources 99 IBM TCP/IP NIM commands 354
Preparing for client access InterLink TCP/IP (UDP) NIM commands 422
UNIX 273 Logging option 339
Windows NT 254 LOGR commands 351
SequeLink data source service parameters Modifying
Btrieve 81 IBM TCP/IP parameters 333
dBASE 82 InterLink TCP/IP (UDP) parameters 411
Excel 82 TCP/IP service parameters 328
FoxPro 83 Multiple DB2 interfaces 308
Microsoft Access 83 NETSRV.LOG 339
Paradox 84 Network parameters 137
Socket 84 Operator commands 343
Text 86 Return codes, working with SSDDs 174
SequeLink ODBC Socket 34 Running multiple SequeLink Servers 342
Socket, predefined service types 93 Service parameters, modifying 314
ODBC Socket Specifying the authorized applications
about 34, 93 list 338

432 Index
User ID mapping 329

Using
R
Batch procedures with SSDDs 169
Batch program 170 Read-Only services 184
Previous versions of SSDDs 178 Retrieving database meta-information 151
OS/390 ESA, SMF accounting 358 Return codes, working with SSDDs
OS/400 commands 290 (OS/390) 174
Overview Rumba Office
Functional 41 Configuring SNA networks 143
SequeLink 31 SequeLink data source network
SequeLink Server 33 parameters 92
Running
Multiple SequeLink Servers (OS/390) 342
SequeLink Server 3.5 and 4.x on the same
P server (UNIX) 274
SequeLink Server 3.5 and 4.x on the same
server (Windows NT) 255
Parameters
SequeLink CAT 71
SequeLink data source network 90
SequeLink data source service 75
Setting (UNIX) 267
S
Predefined service types for SequeLink ODBC
Socket 93 Security
Preparing services for SequeLink client access Configuring master account
UNIX 273 (Windows NT, UNIX) 41
Windows NT 254 Internet 132
Process, SequeLink 42 SequeLink architecture 39
SequeLink CAT
Creating data sources 54
Parameters 71
Q Using on UNIX 63
Value placeholder 71
SequeLink data source network parameters
Quick Install images
Attachmate 90
Creating
Client Access/400 90
Windows 3.1 369, 380
Windows 9x and Windows NT 369
Rumba Office 92
Using 38
TCP/IP 92
SequeLink data source service parameters
DB2 on AS/400 75
DB2 on NT 77
DB2 on OS/390 78
DB2 on UNIX 78
Informix on Windows NT 79

Index 433
Microsoft SQL Server 80 Oracle 215, 220

ODBC Sybase 231
Btrieve 81 SequeLink JDBC Driver, configuring SSDDs
dBASE 82 for 160
Excel 82 SequeLink ODBC Driver
FoxPro 83 About 31
Microsoft Access 83 Configuring SSDDs 159, 160
Paradox 84 SequeLink ODBC Socket
Socket 84 about 34, 93
Text 86 Connecting with 93
OpenINGRES 86 Predefined service types 93
Sybase 88 Service parameters 84
SequeLink Data Source SyncTool, using 95 using 93
SequeLink data sources SequeLink process 42
Creating SequeLink Server Administrator (UNIX),
From an existing data source (Macintosh starting 258
and Windows) 59 SequeLink Server Administrator
From scratch (Macintosh (Windows NT)
and Windows) 54 Configuration mode 241
On UNIX 64 Status mode 241
Deleting (Macintosh and Windows) 61 SequeLink Server, overview 33
Description 56 SequeLink Shadow Data Dictionaries (SSDDs)
Information stored in 47 About 152
Modifying configuration, example Advantages of 152
(UNIX) 66 Catalog and schema names 153
Testing Configuring
Example (UNIX) 69 Using the SequeLink JDBC Driver 160
Macintosh and Windows 61 Using the SequeLink ODBC
SequeLink Dictionary Manager Driver 159, 160
Creating SSDDs 164 Creating 164
Extracting Data Dictionary Editing the SequeLink Server
information 154 configuration resource 157
SSDDs, about 152 Managing different versions of 168
Supported services and configurations 166 ODBC 3.0 data sources 158
Using 162 ODBC.INI file 161
SequeLink functional overview 41 Updating 166
SequeLink functionality Using batch procedures (OS/390) 169
DB2 for AS/400 191 SequeLink, overview 31
DB2 for OS/390 195 Server-defined host user definitions 149
DB2 V5 189 Service
Informix 7 201 Attributes, displaying (UNIX) 266
Informix 9 205 Configuration sections, editing (UNIX) 266
Microsoft SQL Server 226 TCP/IP Parameters, modifying (OS/390) 328
OpenINGRES 210

434 Index
Service levels (DB2 for AS/400) Starting

SQLNKALL 191 SequeLink CAT (Macintosh
SQLNKNONE 191 and Windows) 53
Service parameters SequeLink Server Administrator
DB2 on NT 77 (UNIX) 258
DB2 on OS/390 78 Services (Windows NT) 245
DB2 on UNIX 78 Status mode, SequeLink Server
Modifying (OS/390) 314 Administrator (Windows NT) 241
Setting Stopping services (Windows NT) 245
Connection refusal details Stored procedures (DB2 for OS/390) 196
UNIX 124, 269 SupportNet 28
Windows NT 249 Sybase
DataDictionary parameter 156 Fine-tuning system performance 180
Default domain name (Windows NT) 118 SequeLink data source service
Settings parameters 88
Cross-database 183 SequeLink functionality 231
DB2 for OS/390-specific 199 Specific settings 234
Informix 7 on Windows NT-specific 203 Synchronizing
Informix 9 on Windows NT-specific 207 Data sources 51
Microsoft SQL Server-specific 228 ODBC 3.0 file data sources 99
OpenINGRES-specific 212 SyncTool
Oracle7-specific 218 Using 95
Oracle8-specific 223 SYSIN input record usage 172
Sybase-specific 234 SYSINI 293
Shutdown grace period, setting Example 294
(Windows NT) 253 Sections 300
SMF accounting 358 System performance
SNA Fine-tuning
APPC 109 Informix 7 and 9 180
Attachmate (CPIC) 138 Sybase System 10 and 11 180
Client Access/400 145 Internet 132
Configuring for SequeLink 135
Microsoft SNA Server 141
Rumba 143 T
Specifying the authorized applications list
(OS/390) 338 TCP ports, changing
SQL Server UNIX 271, 391
SequeLink functionality 226 Windows 3.1x 375
SQLNKALL service level (AS/400) 191 Windows 9x/Windows NT 365, 397
SQLNKNONE service level (AS/400) 191 Windows NT 251

Index 435
TCP/IP Connection refusal details,

IBM TCP/IP (UDP) NIM commands setting 124, 269
(OS/390) 418 Deleting services 263
IBM TCP/IP NIM commands (OS/390) 354 Displaying service attributes 266
IBM TCP/IP parameters, modifying Existing services list 264
(OS/390) 333 Logging option, turning on and off 272
IBM TCP/IP UDP parameters (OS/390) 408 Parameters 267
InterLink TCP/IP (UDP) NIM commands Preparing services for SequeLink client
(OS/390) 422 access 273
InterLink TCP/IP UDP parameters, Service configuration sections 266
modifying (OS/390) 411 Starting SequeLink Server
SequeLink data source network Administrator 258
parameters 92 User authentication 268
Service parameters, modifying Using
(OS/390) 328 SequeLink CAT 63
Technical Support, contacting 28 SequeLink Server Administrator 258
Testing Valid configuration actions 263
SequeLink data sources 61 Updating SSDDs 166
Macintosh and Windows 61 Upgrading
UNIX 69 SequeLink 4.0 services 244
Tools, administrator 36 SequeLink Server 3.5 services to 4.x
Translation options, changing (AS/400) 279 (Windows NT) 256
Turning on and off User authentication
Binary support (AS/400) 285 About 117
Logging option Setting
AS/400 284 UNIX 268
UNIX 272 Windows NT 248
Windows NT 252 User ID mapping (OS/390) 329
User-defined services, creating and deleting
(AS/400) 287
Using
U Applications IDs 125
Batch program (OS/390) 170
UDP ports, changing 414 Data compression 128
UNIX Database data dictionary filters 161
Activating and deactivating services 267 Firewalls 130
Adding services 261 Previous versions of SSDDs (OS/390) 178
Authorized applications list 270 Quick Install images 38
Changing SequeLink CAT
Connection time-out 392 Macintosh 52
TCP ports 271, 391 UNIX 63
Client configuration file location 389 Windows 52
Connection management 264 SequeLink Data Source SyncTool 95
SequeLink Dictionary Manager 162

436 Index
SequeLink Server Administrator Client configuration file location 363, 395

UNIX 258 Connection refusal details, setting 249
Windows NT 240 Default TCP port numbers 251
SequeLink with the Internet 130 Deleting services 243
Server-defined host user definitions 149 Displaying host names and IP
Stored procedures (DB2 for OS/390) 196 addresses 246
SyncTool with different versions of the Informix data source service parameters 79
Sequelink ODBC Driver 100 Logging option, turning on and off 252
Preparing services for SequeLink client
access 254
Running SequeLink Server 3.5 and 4.x on
V the same server 255
Setting
Valid configuration actions (UNIX) 263 Autostart 253
Value placeholder for SequeLink CAT 71 Default domain name 250
Shutdown grace period 253
User authentication 248
Specifying
W Authorized applications list 250
Log file directory 252
Windows Starting services 245
Deleting SequeLink data sources 61 Stopping services 245
Starting SequeLink CAT 53 UDP port, changing 416
Testing SequeLink data sources 61 Upgrading SequeLink Server 3.5 services
Windows 3.1x to 4.x 256
Changing TCP ports 375 Using the SequeLink Server
Client configuration file location 373 Administrator 240
Creating Quick Install images 369, 380 WWW, using to contact technical support 28
Yielding behavior 377
Windows 9x
Changing
Connection time-out 366, 398
TCP ports (client) 365, 397
Client configuration file location 363, 395
UDP port, changing 416
Windows 9x/Windows NT 416
Windows NT
Activating and deactivating services 247
Adding services 242
Administrator window toolbar 242
Changing
Connection time-out 366, 398
TCP ports 365, 397
TCP ports (server) 251

Admin

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Admin

Uploaded by

Copyright:

Available Formats

ODBC Edition 4.

INTERSOLV, DataDirect, APS, Maintenance Workbench, PVCS, TechGnosis,

Licensees may duplicate the software product user documentation contained

U.S. GOVERNMENT RESTRICTED RIGHTS. It is acknowledged that the Software

Using This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . 28

SequeLink Administrator’s Guide

SequeLink’s n-Tier Architecture . . . . . . . . . . . . . . . . . . . . . . . . 39

Part 1: Data Sources

2 Using Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . 47

SequeLink CAT Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Connecting With the SequeLink ODBC Socket. . . . . . . . . . . . 93

Part 2: Network Considerations

3 SequeLink and Your Network. . . . . . . . . . . . . . . . . . 107

SequeLink Administrator’s Guide

Cross-Platform Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Using SequeLink with the Internet. . . . . . . . . . . . . . . . . . . . . . 130

4 Configuring Your SNA Network for SequeLink. . . . 135

Part 3: SequeLink Server Administration

5 Using SequeLink With Your Database . . . . . . . . . . . 149

Using the SequeLink Dictionary Manager . . . . . . . . . . . . . . . . 162

SequeLink Administrator’s Guide

Updating SSDDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Using OS/390 Batch Procedures with SSDDs . . . . . . . . . . . . . . 169

Fine-Tuning System Performance . . . . . . . . . . . . . . . . . . . . . . 179

Database-Specific Information . . . . . . . . . . . . . . . . . . . . . . . . 182

6 SequeLink Server for Windows NT . . . . . . . . . . . . . 239

SequeLink Administrator’s Guide

Stopping a Service Process for a Specific User . . . . . . . . . . 245

Configuring SequeLink Server . . . . . . . . . . . . . . . . . . . . . . . . . 247

Preparing Services for SequeLink Client Access . . . . . . . . . . . . 254

7 SequeLink Server for UNIX . . . . . . . . . . . . . . . . . . . . 257

Configuring SequeLink Server . . . . . . . . . . . . . . . . . . . . . . . . . 261

SequeLink Administrator’s Guide

Editing Service Configuration Sections . . . . . . . . . . . . . . . 266

Preparing Services for SequeLink Client Access . . . . . . . . . . . 273

8 SequeLink Server for AS/400 . . . . . . . . . . . . . . . . . . 277

Calling Initialization Programs . . . . . . . . . . . . . . . . . . . . . . . . 289

9 SequeLink Server for OS/390 . . . . . . . . . . . . . . . . . . 293

SequeLink Administrator’s Guide

Modifying FILECACHE Parameters . . . . . . . . . . . . . . . . . . . 329

Automatic Execution of Commands at Startup . . . . . . . . . . . . 338

SMF Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Part 4: SequeLink ODBC Edition Client Administration

10 SequeLink ODBC Edition Client for Windows 9x

Quick Install Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

SequeLink Administrator’s Guide

11 SequeLink ODBC Edition Client for Windows 3.1 . . 373

Quick Install Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

12 SequeLink ODBC Edition Client for Macintosh . . . . 385

13 SequeLink ODBC Edition Client for UNIX. . . . . . . . . 389

Part 5: SequeLink OLE DB Edition Client Administration

14 SequeLink OLE DB Edition Client for Windows 9x

SequeLink Administrator’s Guide

Quick Install Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

A TCP/IP (UDP) Communication (OS/390) . . . . . . . . . . 407

Running Multiple SequeLink Servers . . . . . . . . . . . . . . . . . . . . 416

SequeLink Administrator’s Guide

SequeLink Administrator’s Guide

Table 1-1. Administrator Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

SequeLink Administrator’s Guide

Table 5-7. Data Types (DB2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

SequeLink Administrator’s Guide

Table 8-5. Defaults for the SEQCLS Class (AS/400) . . . . . . . . . . . . . . . . . . . . . . . . 285