Microsoft KB Archive/64608

-

The information in this article applies to:


 * Microsoft SQL Server for OS/2, version 4.2

-

The following questions and answers provide information about NetWare named pipes:

1. Q. Is it true that NetWare names all named pipes servers alike, regardless of what named pipes process they are running?

A. Novell supports extended LAN Manager API calls [NetServerEnum, NetUserEnum, and so forth] in versions 1.2 and later of the OS/2 requester (OS/2 version 1.1 returns a null     list). With this software, you can indeed query the network for named pipes servers.

Servers are named in CONFIG.SYS by passing a &quot;computername&quot; parameter when the named pipes daemon is loaded (this is     documented in the comments in the CONFIG.PST file created by the      requester install program).

The DBNMPIPE TSR (terminate-and-stay-resident) program is a     component of the SQL Server 1.1, 1.11, and 4.2 client software for MS-DOS. We have made DB-Library (DB-Lib) protocol independent--this TSR program is an interface layer for named pipes. This interface IS NOT the protocol stack itself--it must be resident as part of the network software. The OS/2 and Windows implementations of this are DLLs (dynamic-link     libraries).

2. Q. Can you have more than one OS/2 SQL Server on a single NetWare LAN?

A. Yes, you can have as many SQL Servers on a NetWare LAN as you have OS/2 requester software installed. The &quot;computername&quot; parameters should be unique. Incidentally, the computername is     what is prefixed as the root of the SQL Server pipe, as in the following example:

\\MYCOMPUTER\PIPE\SQL\QUERY Additional query words: dblib

Keywords         : kbnetwork SSrvLAN Version          : 4.2 Platform         : OS/2 Issue type       : Last Reviewed: March 9, 1999