1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
|
==================================
SOLID Server version 2.20.0007
Release Notes
Last update 11-02-1997
==================================
NEW FEATURES COMPARED TO 2.10
-----------------------------
7.1 Ease-of-Deployment Features
7.1.1 Several Solid Installations within One Computer
All SOLID driver, interface, and communication library files are
named according to the Solid version. This means that when a new
Partner application that has SOLID Inside is installed onto a
computer that already has Solid installed as part of other
Partners applications, all the SOLID DBMSs can happily co-exist
without problems within the same computer.
7.1.2 Create Database and Exit
New SOLID Server command line options allow starting SOLID Server to
only create the database and/or to execute some SQL script to create
tables, indices etc. and exiting immediately after that.
This feature is useful, for example, in an embedded setup utility,
where the database needs to be created and closed first before
SOLID Server can be started in the background as an NT service
process. For details, see SOLID Server Administrator's Guide:
Appendix G.
7.1.3 Logical Data Source Names
By using Logical Data Source Names, SOLID Server databases
can be referred to and accessed from clients also by using a
Logical Data Source Name, i.e., any user-specified character
string. Now the data source names can be made self-documenting
instead of using the network names, which tend to be rather
cryptic on certain protocols.
Clients can still use the SOLID Server network name consisting
of the communication protocol name and the unique identifier of
the server. The logical name is translated to a network name
according to the entries in either solid.ini, odbc.ini, or the
Windows registry.
Using Logical Data Source Names means that SOLID databases can
be named so that the name makes sense to the end user, e.g.,
"Enterprise Intelligence Database" instead of "tcp serverX 1234".
This makes using SOLID databases more convenient to the power
users of ODBC tools like Excel. Also, it will be easier for
application developers to write portable applications and setup
programs.
Please see SOLID Server Administrator's Guide for details.
7.1.4 Shrink Initial Databases
Based on Partner feedback, we have further developed SOLID Tools
in order to make it straight-forward to export all data from a
SOLID database and to reinsert the data into a new database.
The result is a database with the desired contents and a minimal
size in bytes.
The SOLID Server Administrator's Guide contains detailed
instructions on how to perform the database compression using the
soldd, solexp, and solload utilities.
We suggest compressing the initial databases that are mass
distributed with Partner applications always when preparing
evaluation or product packages, whatever the delivery media may
be: diskette, CD-ROM, FTP, or Web.
7.1.5 Reset Database Age for Evaluation Databases
This is a service provided to our Partners who are distributing
evaluation copies of their software with a SOLID Server database.
Partners can preset the contents of a SOLID Server database and
have Solid erase the database creation time stamp after that. This
way, the limited evaluation time starts only after the evaluator
opens the database.
7.1.6 CD-ROM Support
In addition to the evaluation database creation and database
compression utilities mentioned above, version 2.2 provides the
following new features that support CD-ROM distribution:
read-only flag in server startup
read-only license option
Using the read-only startup option allows the database to reside
on a CD-ROM device. This feature is useful when implementing
tutorial applications that are run directly from CD-ROM and that
need a demo database.
The read-only license option is mainly targeted for the
information providers who wish to sell and distribute
non-alterable data, even if the database is copied from
CD-ROM to a hard disk.
7.2 SQL Functionality Enhancements
7.2.1 Schema Support
Table schemas allow several logical databases to reside in the
same physical database. A typical use could be to have a similar
table structure for each customer in the database of an
accounting firm. All the data would still be stored in a single
physical database, which allows sharing the common parameter
information. Please note that indices still have to be named
uniquely.
For schema usage instructions and syntax details, please refer to
SOLID Server Administrator's Guide.
7.2.2. Returning Result Sets from Database Procedures
In version 2.2, SOLID Server can return multiple row result sets
from database procedures. This enables application designers to
have all database operations performed through database procedures
when appropriate in order to hide the physical table structures
from client applications or to solve data protection or network
congestion problems.
7.2.3. Row Number in Result Sets
The ROWNUM attribute may be used in SELECT and UPDATE statements
to limit the number of rows in the result set that are returned to
the client or processed. The ROWNUM semantics are similar to
Oracle's ROWNUM.
Please take note on the following points:
- Only conditions in like ROWNUM < n (with no surrounding
NOs or like that) are allowed. All other conditions would
be meaningless and are therefore prohibited.
(e.g. ROWNUM > 1 would always return zero rows).
- New SQL error 86 "illegal ROWNUM constraint" is added.
- The trick how to retrieve the specified row numbers
from a query can be done with a view. To get every other
row from table AA, do as follows:
CREATE VIEWS AAV (RN,...) AS SELECT ROWNUM,* FROM AA;
SELECT * FROM AAV WHERE RN / 2 * 2 = RN;
- Also the following kind of UPDATE statements work:
UPDATE T SET F = ROWNUM
- ROWNUM is a new reserved word.
7.2.4. WHENEVER SQLERROR Supported
The syntax
EXEC SQL WHENEVER SQLERROR [ROLLBACK [WORK] ,] ABORT;
has been added to decrease the need for IF NOT SQLSUCCESS THEN ...
tests after every executed SQL statement in a procedure.
7.2.5 SET STATEMENT MAXTIME Supported
The new SQL statement SET STATEMENT MAXTIME <minutes> sets
connection-specific statement maximum execution time in seconds.
The setting is effective until a new maximum time is given. A zero
value means no maximum time, which is also the default. When a
statement fails due to a timeout expiration, the SQL error code
14529 is returned to the application.
7.2.6 EXCEPT and INTERSECT Supported
Now the EXCEPT and INTERSECT statements are allowed in SELECT
criteria. For details on the syntax, please see SOLID Server
Administrator's Guide.
7.2.7 Table Name Shorthand Aliases Allowed
The syntax <table id> AS <identifier> was added as a new feature.
The reserved word AS cannot be used as an identifier without double
quotes.
7.2.8 UPDATE <table>.<column> Supported
Support for the following syntax was added:
UPDATE <table>.<column>
For details, please refer to SOLID Server Administrator's Guide.
7.2.9 "INTO" Optional in "INSERT INTO"
In the "INSERT INTO" statement, the word "INTO" is now optional.
Therefore, the reserved word "INTO" cannot be used any more as an
identifier name.
7.2.10 Accurate Data Type Mapping in Database Procedures
Now all the data type length and precision information
are exploited also in database procedures. All data types
behave in produres exactly as in the SQL API.
7.2.11 CASE Control Structure Allowed in Database Procedures
Support for the following syntax was added:
CASE WHEN ... THEN ... ELSE ... END
For details, please refer to SOLID Server Administrator's Guide.
7.2.12 Identifier Name Length Restriction Removed
Now the SQL identifier name length is unlimited.
7.2.13 SQL Info Logging Enhancements
Some new parameters to configure the SQL Info facility were added:
[SQL]SQLInfo SQL-specific info level. Only SQL
info output, no table level info.
If not set, default taken from the
[SQL]Info parameter.
[SQL]InfoFileName Default global info file name.
[SQL]InfoFileSize Max info file size, used only for user
given info files or if InfoFileName is
specified.
[SQL]InfoFileFlush Default yes, flushes info file after
every write operation.
7.2.14 Several SQL Performance Enhancements
The SQL operations performance has been further improved by:
- adding single-row subqueries optimization
- adding DISTINCT-statement optimization in conjunction
with ANY or ALL
- improving range constraint's cost estimation
- adjusting estimator parameter default values
- using external sorter, when appropriate, to save central memory
- optimizing ORDER processing to avoid redundant searches
- introducing new, improved join path algorithm
7.3 Server Functionality Enhancements
7.3.1 More Efficient Group Commit
The log write in multithread environments has been improved
to automatically execute group commit for write operations.
This is done by queueing the write operations both before and
after the logical log write operation. The grouping increases
adaptively and prevents the log file flushing from becoming a
bottleneck to the server performance.
The new group commit method is independent of the write mode
and usually the default LogWriteMode is the best alternative.
Note that the configuration parameter setting
[Logging]
CommitMaxWait=n
has now become obsolete and should be removed from solid.ini.
Also the LogWriteMode=3 (lazy) is now obsolete and is implicitly
replaced by Logwritemode=2 (overwrite last block mode)
7.3.2 Cursor Read Level Changed
The cursor read level has been changed. Previously the cursor was
able to see changes that were made in the same transaction after the
cursor was opened. For example, if the cursor was positioned onto
row 2 and a new row was added in position 5, the new row was visible
in following fetch calls. This caused some problems because the
cursor behaved differently if the set was ordered using external
sorter or index leaf buffering.
The new changed behaviour fixes the cursor read level to the point
when the cursor was opened. Later changes in the same transaction
are not visible to the cursor. At transaction commit or rollback
the cursor read level is updated to the point of the start of the
transaction.
7.3.3 Windows Info... Display
On Windows platforms (3.1x, 95, NT) the SOLID Server icon menu has
the new option 'Info...'. It displays server startup messages
including license and listening details in a message box.
This helps to identify separate SOLID Server processes that are
running on the same workstation.
7.3.4 ADMIN COMMAND Accepts Arguments that Contain Spaces
Server-internal command line argument parsing, which is used to
process, e.g., ADMIN COMMAND staments now accepts double quoting to
give arguments that contain spaces.
Double quotes can be included in the command string by preceding
them with a backslash (i.e. \").
7.3.5 Enhancements to the ADMIN COMMAND 'Userlist'
The ADMIN COMMAND userlist output has been changed. Instead of
dividing users to control and normal users, it now displays the user
type (e.g., SQL, SA, rcon, or solcon user).
Also, there are new arguments for the userlist command. The new
extended syntax is:
ul [-l] [name|id]
Option -l prints the long list including more info such as user
login time and current SQL statement details. The optional name or
id argument requests the info for that one user only.
7.3.6 Configuration File Shorthand Syntax for Numeric Values
Numeric values in solid.ini (e.g., CacheSize) can now be given with
the suffix k, K, m, or M. The letter K stands for kilobytes (value
* 1024) and the letter M for megabytes (value * 1024 * 1024). The
parameter type must be long; this mechanism does not work for
parameters of the type double.
7.3.7 Ability to Configure No Timeouts
Negative or zero value for the solid.ini configuration parameters
[Srv]ConnectTimeOut and [Srv]AbortTimeOut mean infinite timeout.
7.3.8 Error Log File Size Limited
The error log file solerror.out size is limited to 1 MB. When the
file grows over this limit it is renamed to solerror.bak, and a new
solerror.out is started.
7.3.9 Minimum Cache Size Increased
The minimum size of the database cache in central memory has been
increased from 10*blocksize to 20*blocksize.
7.3.10 Several Server Performance Improvements
Several performance optimizations have been implemented in the:
- I/O Manager
- Log Manager
- Merge process
- Backup process
- Multi-thread operation
- Aggregate functions execution
- Large table index creation optimization
7.4 Communication Functionality Enhancements
7.4.1 UNIX Pipes Support
Now SOLID Server and the client applications can communicate
locally within a UNIX host by using the UNIX Pipes protocol. The
shorthand for the UNIX Pipes protocol is 'upipe' or 'unp'. E.g.:
[Com]
Listen = unp MySOLID
This means that Desktop licenses can now be controlled also
on UNIX platforms by allowing only UNIX Pipes connections.
UNIX Pipes are implemented on AIX, Clix, HP-UX, IRIX, Linux,
and Solaris platforms.
7.4.2 Unlimited Amount of Listening Sessions
The previous limitation of 10 concurrent listening
sessions was removed. Now any number of listening sessions or
asynchronous client connections is possible.
7.4.3 NetBIOS Multiadapter Connection
When NetBIOS listening is started in Windows NT without specifying
the adapter identifier (i.e., the lana number), the default now is
"listen to all available lanas" instead of just lana 0, which often
is not the wanted one or may even be unusable. The lana number
containing the "Nbf" on the top level is used first.
Also, the client using the NetBIOS protocol without specifying any
adapter tries first to connect to the server using the lana bound to
"Nbf". If the connection is not established, all the available
lanas are tried one at a time.
7.5 Tools Functionality Enhancements
7.5.1 Streamlined Operation; Command Line Options
The co-operations between soldd, solexp, and solload has been
streamlined. Also, the command line options have been changed to
be as consistent as possible between executables. For details,
please see SOLID Server Administrator's Guide or run tool programs
with the option: '-?'.
7.5.2 Long File Names in Solexp and Soldd
Solexp and soldd no longer truncate file names generated from table
names to 8 characters except in Windows 3.x versions.
7.5.3 BLOb Support for solexp
Solexp now also supports binary fields of unlimited length.
7.5.4 Inserting Enclose Characters
SpeedLoader accepts the special characters CR and LF in enclosed
formats and within fixed length fields. Enclose characters can be
included in strings by typing two consequtive enclose characters
(e.g., 'can''t'). Solexp now outputs two quote characters in
strings that contain quote characters (').
7.5.5 SOLID SpeedLoader Commit Interval Configurable
The SOLID SpeedLoader commit batch size can be changed using the
command line option -b or the control file option COMMITBATCH. If
the commit batch size is specified, data is committed at commit
batch intervals. If the commit batch value is zero, all data is
loaded before commit. The default commit batch value is one, which
is the same as the autocommit mode.
7.5.6 SOLID SpeedLoader TIME and TIMESTAMP Format Keywords
In the SOLID SpeedLoader control file it is possible to also specify
default TIME and TIMESTAMP formats for columns in addition to the
DATE format. The syntax is the following:
DATE 'format-str'
TIME 'format-str'
TIMESTAMP 'format-str'
Any or all of the default formats may be missing, but the existing
ones must be given in the above order, e.g., DATE must always be
specified before TIME. The keywords TIME and TIMESTAMP work in the
same way as the keyword DATE.
7.5.7 'Quit' also from Solcon & Solinst
For consistency reasons, solcon now acceps the quit command, which
is equivalent to the exit command. Solinst accepts the 'Q' command,
which is equivalent to 'X'.
7.6 Changes to Supported Platforms
7.6.1 Silicon Graphics IRIX
IRIX was provided as a 2.1 beta release. Now, with SOLID Server
version 2.2, IRIX v. 6.2 becomes a supported platform.
7.6.2 Windows NT 4.0 (Intel)
SOLID Server 2.1 for NT could be run without problems on Windows
NT 4.0, although it was not an officially supported platform.
Now, both NT 3.51 and NT 4.0 are officially supported on the
Intel hardware.
On Digital Alpha hardware, NT 3.51 continues to be the supported
NT version.
SOLID Server 2.2 supports the following platforms and protocols:
----------------------------------------------------------------
DOS : NetBIOS*, IPX/SPX*
(Client only)
MS Windows 3.1x : ShMem, NmPipe*, NetBIOS*, IPX/SPX*,
(Desktop & : DECnet*, TCP/IP*
Client only)
Windows 95 4.00 : ShMem, NmPipe, NetBIOS, IPX/SPX*, TCP/IP
Windows NT 4.0 (Intel): ShMem, NmPipe, NetBIOS, IPX/SPX*,
: TCP/IP
Windows NT 3.51(Alpha): ShMem, NmPipe, NetBIOS, TCP/IP
OS/2 2.1, 3.0 Warp: ShMem, NmPipe, NetBIOS, IPX/SPX*,
: DECnet*, TCP/IP
Novell Netware 3.12, 4.10: IPX/SPX
SCO Unix 3.2: : TCP/IP
Linux 1.2.13 : UPipe, TCP/IP
AIX 3.2, 4.1 : UPipe, TCP/IP
HP-UX 9.05: : UPipe, TCP/IP
Intergraph CLIX System V R3.1 v.7.1.3: UPipe, TCP/IP
Silicon Graphics IRIX v.6.2: UPipe, TCP/IP
SUN Solaris 2.5 : UPipe, TCP/IP
VAX/VMS 5.5 : DECnet, TCP/IP
Open VMS AXP 6.1: DECnet, TCP/IP
Note for SOLID Server 2.1 users
-------------------------------
Upgrading to 2.2 does not require any special actions. Stop any
running SOLID Servers; install and start using SOLID Server 2.2.
Older versions of SOLID Client 2.x software are compatible with
the new 2.2 server. However, upgrading the client software
simultaneously with server software is advisable in general.
Note for UNIX SQL API users
---------------------------
We recommend that you change the character set used in your UNIX
client application to ANSI, i.e., ISO LATIN-1. This ensures
maximum interoperability of your database from applications on
different platforms. The default character set in UNIX clients
of SOLID will change in the future from the current 7-bit to
ISO LATIN-1.
Example:
<...connection established, handle hdbc...>
SQLSetConnectOption(
hdbc, SQL_TRANSLATE_OPTION, SQL_SOLID_XLATOPT_ANSI
);
==================================
Solid v.2.20 list of product files
==================================
This document lists all files that are part of a Solid product.
NOTE! All products do not necessarily contain all these files.
Contents:
---------
SOLID Server
SOLID SQL Editor (Windows ODBC)
SOLID SQL Editor (Windows CLI DLL)
SOLID SQL Editor (Teletype)
SOLID Remote Control (Windows)
SOLID Remote Control (Teletype)
SOLID SpeedLoader
SOLID Data Dictionary
SOLID Export
CLI/ODBC development
SA development
Communication DLLs (Windows, Windows95, OS/2, NT)
SOLID Server
------------
SOLID database server.
Name: solid.exe (Windows, Windows95, OS/2, NT, VMS)
solid.nlm (Novell)
solid (Unix)
Requires: Communication DLL (Windows, Windows95, OS/2, NT)
SOLID SQL Editor (Windows ODBC)
-------------------------------
Graphical SQL Editor for Windows 3.x using ODBC.
Name: ssql.exe
Requires: ODBC 16-bit installed
sclw1622.dll (Windows 3.x)
Communication DLL
ODBC 32-bit installed
sclw3222.dll (Windows95, NT)
Communication DLL
Commonview DLLs
glcv31mw.dll
glfs31mw.dll
bwcc.dll
pstuirw.dll
gldg31mw.dll
SOLID SQL Editor (Windows CLI DLL)
----------------------------------
Graphical SQL Editor for Windows 3.x using SOLID CLI DLL directly,
no ODBC needed.
Name: ssqlw.exe
Requires: sclw1622.dll
Communication DLL
Commonview DLLs
glcv31mw.dll
glfs31mw.dll
bwcc.dll
pstuirw.dll
gldg31mw.dll
SOLID SQL Editor (Teletype)
---------------------------
The teletype version of SOLID SQL Editor.
Name: solsql.exe (Windows95, OS/2, NT, VMS)
solsql.nlm (Novell)
solsql (Unix)
Requires: Communication DLL (Windows95, OS/2, NT)
SOLID Remote Control (Windows)
------------------------------
Graphical remote administration program for Windows 3.x.
Name: rcon.exe
Requires: Communication DLL
Commonview DLLs:
glcv31mw.dll
glfs31mw.dll
bwcc.dll
pstuirw.dll
gldg31mw.dll
SOLID Remote Control (Teletype)
-------------------------------
The teletype version of the remote administration program.
Name: solcon.exe (Windows95, OS/2, NT, VMS)
solcon.nlm (Novell)
solcon (Unix)
Requires: Communication DLL (Windows95, OS/2, NT)
SOLID SpeedLoader
------------------
Program for importing ASCII data into a SOLID database.
Name: Standalone
----------
solloads.exe (Windows, Windows95, OS/2, NT, VMS)
solloads.nlm (Novell)
solloads (Unix)
Network
-------
solload.exe (Windows, Windows95, OS/2, NT, VMS)
solload.nlm (Novell)
solload (Unix)
Requires: Standalone
----------
- no other files needed -
Network
-------
Communication DLL (Windows, Windows95, OS/2, NT)
SOLID Data Dictionary
---------------------
Creates SQL Data Definition Language script file containg the
data dictionary of a SOLID database.
Name: solddls.exe (Windows, Windows95, OS/2, NT, VMS)
solddls.nlm (Novell)
solddls (Unix)
Requires: Communication DLL (Windows, Windows95, OS/2, NT)
SOLID Export
------------
Exports data from a table to a format loadable by SOLID SpeedLoader.
Also creates a control file for SpeedLoader.
Name: solexp.exe (Windows, Windows95, OS/2, NT, VMS)
solexp.nlm (Novell)
solexp (Unix)
Requires: Communication DLL (Windows, Windows95, OS/2, NT)
SOLID SQL API and ODBC development
----------------------------------
SOLID SQL API and ODBC development libraries and headers.
Headers: cli0core.h (all)
cli0defs.h (all)
cli0env.h (all)
cli0ext1.h (all)
Libraries: SclOOOVv.{ext}
where: S = constant prefix
cl = constant for CLI/ODBC
OOO = operating system
Vv = major version, minor version (22)
ext = file extension (lib, olb, a, ...)
sclw1622.dll (Windows)
sclw3222.dll (Windows95, NT Intel)
sclnta22.dll (NT Alpha)
sclo1622.dll (OS/2 1.x)
sclo3222.dll (OS/2 2.x, Warp 3.x)
Requires: Communication DLL (Windows, Windows95, OS/2, NT)
SA development
--------------
Solid API development libraries and headers.
Headers: sa.h (all)
Libraries: SsaOOOVv.{ext}
where: S = constant prefix
sa = constant for SA
OOO = operating system
Vv = major version, minor version (22)
ext = file extension (lib, olb, a, ...)
ssaw1622.dll (Windows)
ssaw3222.dll (Windows95, NT Intel)
ssanta22.dll (NT Alpha)
ssao1622.dll (OS/2 1.x)
ssao3222.dll (OS/2 2.x, Warp 3.x)
Requires: Communication DLL (Windows, Windows95, OS/2, NT)
Communication DLLs (Windows, Windows95, OS/2, NT)
-------------------------------------------------
Communication files for DLL environments. In other environments
communication code is linked to the executable or included in the
client library.
Name: SPPOOOVv.dll
where: S = constant prefix
PP = protocol
OOO = operating system
Vv = major version, minor version (22)
Protocol
--------
sm = Shared Memory
np = Named Pipes
nb = NetBIOS
tc = TCP/IP
sx = Novell IPX/SPX
dn = DECnet
Operating system
----------------
w16 = Windows 3.x
w32 = Windows95, NT Intel
nta = NT Alpha
o16 = OS/2 1.x
o32 = OS/2 2.x, Warp 3.x
Example
-------
ssmw1622.dll (Shared Memory for Windows 3.x,
SOLID version 2.2)
Available combinations Jan 27, 1997
-----------------------------------
ssmw1622.dll
ssmw3222.dll
ssmnta22.dll
ssmo1622.dll
ssmo3222.dll
snpw1622.dll
snpw3222.dll
snpnta22.dll
snpo1622.dll
snpo3222.dll
snbw1622.dll
snbw3222.dll
snbnta22.dll
snbo1622.dll
snbo3222.dll
stcw1622.dll
stcw3222.dll
stcnta22.dll
stco1622.dll
stco3222.dll
ssxw1622.dll
ssxw3222.dll
ssxo1622.dll (also used in OS/2 2.x, Warp 3.x)
sdnw1622.dll
sdno1622.dll (also used in OS/2 2.x, Warp 3.x)
Required system software for communication to work
--------------------------------------------------
npw16 Windows for Workgroups
tcw16 Windows Sockets
tcw32 Windows Sockets (included in NT and 95)
tco16 IBM TCP/IP
tco32 IBM TCP/IP
sxw16 NetWare Client
sxw32 NetWare Client 32
dnw16 Digital Pathworks
dno16 Digital Pathworks
|
