Oracle Network Products Getting Started for Windows Platforms Go to Product Documentation Library
Library		 Go to books for this product
Product		 Go to Contents for this book
Contents		 Go to Index
Index


Go to previous file in sequence Go to next file in sequence

Verifying Parameters and Vendor Adapters for Windows 3.1x

Verifying File Parameters

Verify that the CONFIG.SYS file and AUTOEXEC.BAT file correctly list the parameter for each Oracle Protocol Adapter. If you must modify these files manually, use a text editor, such as Windows Notepad or MS-DOS Editor. Reboot your computer after making edits to ensure that Windows recognizes changes to these system files.

This appendix also describes additional AUTOEXEC.BAT changes that you can make for several Oracle Protocol Adapters.

Verifying CONFIG.SYS File Contents

Verify that your CONFIG.SYS file contains the appropriate settings for the BUFFERS and FILES parameters. The minimum requirements for each are:

BUFFERS=16

FILES=60
Verify that the following command is in the CONFIG.SYS file:

BREAK=ON
If you modify your CONFIG.SYS file, you must reboot your machine before continuing.

Verifying WIN.INI File Contents

Verify the following information is written to the WIN.INI file to there is a pointer to the ORACLE.INI file for Oracle configuration information.

[ORACLE]

ORA_CONFIG=C:\WINDOWS\ORACLE.INI

Including a DOS Oracle Home Directory in the AUTOEXEC.BAT File

 Some third-party products and version 6 tools for Windows can be located in a DOS Oracle home directory, but require DLLs located in your Windows Oracle home directory. If you are using these products, ensure that the PATH in your AUTOEXEC.BAT file contains the following line:

PATH=C:\ORAWIN\BIN;<DOS_Oracle_home>
If your Windows Oracle home directory is not called ORAWIN, substitute the appropriate name.

If you modify your AUTOEXEC.BAT file, you must reboot your system before the changes take effect.

Verifying TCP/IP Protocol Adapter Setup

Follow the procedures described below before using the Oracle TCP/IP Protocol Adapter:

Loading TSR Transports for TCP/IP

 The following implementations of TCP/IP are Terminate and Stay Resident (TSR) transports.

Load the appropriate TCP/IP executables from the DOS command line before starting Windows or alter your AUTOEXEC.BAT file to load them when starting your workstation. If you plan to run these applications frequently and want to load the required executables automatically, modify your AUTOEXEC.BAT to include the required commands. Refer to the following instructions for the program names and loading sequence for your specific transport.

3Com 3+Open TCP (Versions 1.1 and 1.2)

To load the required executables automatically (for versions 1.1 and 1.2 only), verify that the following lines are in your AUTOEXEC.BAT file:

path\TCPTSR

path\DNRTSR

path\NMTSR

path\SOCKTSR

ORAWIN\BIN\M3OPEN

Beame and Whiteside TCP/IP

 To load the required executables automatically, verify that the following line is in your AUTOEXEC.BAT file:

\ORAWIN\BIN\MBW.EXE
Note
 To use the Beame and Whiteside TCP/IP transport, add the following line to your CONFIG.SYS file:

where path is the location of the device driver.

FTP PC/TCP

To load the required executables automatically, determine which network interface card you are using, and alter your AUTOEXEC.BAT as follows. For example, if you are using a 3COM 3C503 card and installed your FTP 2.1 software in the \PCTCP directory, enter:

\PCTCP\3C503

\PCTCP\ETHDRV

\ORAWIN\BIN\MFTP
In addition, verify that the following lines are in your Windows SYSTEM.INI file:

[boot]

network.drv=pctcpnet.drv

[386 Enhanced]

device=vpctcp.386

Microsoft LAN Manager TCP/IP

 To load the required executables automatically, add the following lines to your AUTOEXEC.BAT file:

path\net start workstation

path\load tcpip

path\sockets 






 Note


Set NUMSOCKETS (in the [SOCKETS] section of TCP UTILS.INI) to the required maximum concurrent number of connections. UTILS.INI is located in the directory where LAN Manager for DOS is installed.
In addition, verify that the following lines are in your Windows SYSTEM.INI file:

[boot]

network.drv=lanman21.drv

Loading TCP/IP Kernel-Specific Code Before Running Windows TCP/IP Transports

 If your TCP/IP transport is implemented as a DLL program, the appropriate JSB DLL loads automatically when SQL*Net calls the TCP/IP transport. No additional files are required before beginning SQL*Net operation.

Before starting Windows, however, you must load the TCP/IP kernel-specific code for your TCP/IP version. This section provides a brief summary of the files that must be loaded by each of the DLL-implemented TCP/IP transports.

3Com 3+Open TCP (Version 2.0)

Verify that the following executables are loaded before you run Windows. Run them from the DOS command line or load them from your AUTOEXEC.BAT file.

path\TCPTSR

path\DNRTSR

path\NMTSR

path\SOCKTSR
where path is the location of the executable.

HP ARPA Services for DOS

Verify that the following executables are loaded before you run Windows. Run them from the DOS command line or load them from your AUTOEXEC.BAT file.

path\TCPTSR

path\SOCKTSR

path\DNRTSR
where path is the location of the executable.

Verify also that the following lines are in your Windows SYSTEM.INI file:

[386 Enhanced]

device=vtil.386

device=vbapi.386

device=vsockets.386

Novell LAN WorkPlace for DOS

 Verify that the following executables are loaded before you run Windows. Run them from the DOS command line or load them from your AUTOEXEC.BAT file.

path\LSL

path\3C503

path\IPXODI		  (optional; load only if you require TCP/IP compatibility with NetWare)			 

path\NETX		  (optional; load only if you require TCP/IP compatibility with NetWare)

\XLN\BIN40\TCPIP
where path is the location of the executable.

Verify also that the following lines are in your Windows SYSTEM.INI file:

[boot]

network.drv=netware.drv

[386 Enhanced]

device=vtcpip.386

Sun PC-NFS

Verify that the following executables are loaded before you run Windows. Run them from the DOS command line or load them from your AUTOEXEC.BAT file.

path\NET INIT

path\RTM

path\[RNMNIS|RNMFILE]
where path is the location of the executable.

Verify also that the following lines are in your Windows SYSTEM.INI file:

[boot]

network.drv=pcnfs.drv

[386 Enhanced]

device=pcnfs.386

Walker Richer & Quinn Reflection Network Series

 Verify that the following executables are loaded before you run Windows. Run them from the DOS command line or load them from your AUTOEXEC.BAT file.

path\RNDIS <parameters>

path\NETBIND

call path\STARTNET.BAT
where path is the location of the executable and parameters are configuration-specific options documented in your Walker Richer & Quinn Reflection Network Series documentation.

Verify also that the following lines are in your Windows SYSTEM.INI file:

[386 Enhanced]

device=vsockets.386

Wollongong Pathway Access for DOS

 Verify that the following executables are loaded before you run Windows. Run them from the DOS command line or load them from your AUTOEXEC.BAT file.

path\PWCONFIG

path\3C503 parameters

path\PWTCP  		(the actual kernel stack)
where path is the location of the executable and parameters are configuration-specific options documented in your Wollongong Pathway Access documentation.

Verifying ORACLE.INI File Contents

During installation of the Oracle TCP/IP Protocol Adapter, the ORAINST or SETUP program may prompt you for the name of the vendor whose TCP/IP transport you want to use with the JSB Virtual Socket Library (VSL) software. This occurs only in the exceptional case in which the Oracle Installer cannot unambiguously determine the vendor. This is the case for FTP/TCP. After entering the name of the vendor, ORAINST or SETUP changes the value of the TCP_VENDOR parameter in your ORACLE.INI file.

Verify that this parameter is set in the following format:

TCP_VENDOR = vendor_key
where vendor_key is one of the values defined in the tables in "Verifying TCP/IP Vendor File Installation" of this appendix.

Using Windows Sockets Vendors

The Oracle TCP/IP Protocol Adapter for Windows is certified to work with the Windows Sockets' vendors and versions specified in this chapter. Ensure that your network software is from a Windows Sockets supplier. This ensures that the Oracle TCP/IP Protocol Adapter for Windows and your network software are compatible.

Network software adhering to the Windows Sockets standard is referred to as Windows Sockets Compliant. Suppliers of Windows Sockets Compliant software are referred to as Windows Sockets Suppliers. A vendor must implement 100% of the Windows Sockets standard to be Windows Sockets Compliant.

The Windows Sockets standard is a network programming interface for Microsoft Windows based on a "socket" paradigm popularized by Berkeley Software Distribution (BSD) from the University of California at Berkeley.

The Windows Sockets standard provides a single API used by application programmers and confirmed by multiple network software vendors. For each Microsoft Windows version, the Windows Sockets standard defines library calls and associated semantics. This enables applications written to the Windows Sockets API to work with a conforming protocol from any network software vendor. Most current TCP/IP network vendors interface with Windows sockets through the WINSOCK.DLL file.

Windows Sockets include both Berkeley socket-style routines and Windows-specific extensions that let programmers use a Windows message-driven design. All Windows Sockets implementations support both TCP and User Datagram Protocol (UDP) sockets.

Unlike a TSR program, which stays in memory until you reboot your computer, a Windows Sockets DLL file dynamically loads into memory and automatically unloads when you exit the application.

Applications operating with any Windows Sockets Compliant protocol implementation are referred to as having a Windows Sockets interface and are known as Windows Sockets applications.

Verifying TCP/IP Vendor File Installation

If you are using the Oracle TCP/IP Adapter for Windows, verify that the JSB DLL or TSR files listed in the tables in this section exist. All necessary JSB Virtual Socket Library (VSL) software for your vendor's TCP/IP transport is installed.

If any of the files listed in the following sections are absent, it can mean that the Oracle TCP/IP Protocol Adapter and/or SQL*Net version 2 products were not installed correctly. Refer to the CD-ROM insert for instructions on re-installing any of these Oracle network products for Windows.

Verifying JSB VSL Support for TCP/IP

The Oracle TCP/IP Protocol Adapter for Windows version 2.1.4 or later supports JSB VSL version 3.0.11 for SQL*Net 2.3. JSB VSL is an API that supports multiple TCP/IP transports.

Depending on the TCP/IP transport used, the specific JSB component for that transport can require some special configuration, loading, and unloading procedures.

The Window Sockets' vendors and versions supported in this release of the Oracle TCP/IP Protocol Adapter for Windows are shown in the Table B-1. This table is subject to change.

Table B¯1 Window Socket Vendors

Product Name (Windows Sockets) Release/Version Number(s) Supported
3Com 3+Open TCP 2.1
Digital PATHWORKS for DOS (TCP/IP) 5.0a
Distinct TCP/IP 3.1
Esker Tun TCP 7.1, 7.2, 7.3
Frontier Technologies Super-TCP for Windows 3.0, 4.0, 4.0R2, 4.15
FTP PC/TCP1 & 2 2.2, 2.3, 3.0, 3.1
FTP PC/TCP OnNet VxD 1.1, 1.2, 2.0
Hummingbird NFS Maestro TCP/IP for DOS & Windows 5.0 5.0
IBM TCP/IP for DOS3 2.1.1
IBM TCP/IP for DOS/Windows Access Kit 2.0
Ipswitch PIPER/IP 1.001, 2.0
Microsoft Windows for Workgroups TCP/IP (VxD) 3.11
Microsoft Windows NT TCP/IP 3.1, 3.5, 3.51
NetManage Chameleon TCP/IP 3.11, 4.0, 4.01
Persoft SmarTCP 3.0, 4.0
Sun PC-NFS 5.1.5
Sun PC-NFS Pro 1.1, 2.0
Walker Richer & Quinn Reflection Network Series

 2.1, 4.0, 4.02, 5.0
Wollongong PathWay Access Runtime

 2.0, 3.0
  1. Using DNS with FTP PC/TCP 2.2 results in the SQL*Net connect error:

    ORA-12203: TNS: unable to connect to host
  2. Oracle Corporation recommends that you use a local host file for host name resolution. You must use FTP's WINSOCK.DLL file release 1.0.6. if you use PC/TCP 2.2. Please contact FTP Software, Inc. to obtain a copy of this file. Attempting to open a network definition stored in a database returns an Application Error when using WINSOCK.DLL release 1.13 (shipped with PC/TCP 3.0 and OnNet 1.1). Update to FTP WINSOCK.DLL release 1.15 (shipped with PC/TCP 3.1 and OnNet 1.1) to resolve this problem.

  3. If you use the TCP/IP Protocol Adapter for Windows and FTP PC/TCP release 2.3 Winsock on a PC that is not 100% compatible with IBM or Compaq equipment, the TCP/IP adapter may fail during connect. If this happens, Oracle recommends that you use the native (or non-Winsock) FTP PC/TCP release 2.3 interface by reinstalling and selecting FTP as your vendor. When we better understand this problem, we provides a patch, if necessary.

  4. You must use IBM TCP/IP for DOS release 2.1.0.2 with IBM's WINSOCK.DLL file. Please contact IBM to obtain a copy of this file. IBM TCP/IP for DOS releases 2.1.1 and 2.1.1.2 may cause SQL*Net to hang. If you experience this problem, contact IBM to get the latest patch.

The other socket vendors and versions supported in this release of the Oracle TCP/IP Protocol Adapter for Windows are shown in Table B-2

Table B¯2 Other Socket Vendors

Product Name (Other Sockets) Release/Version Number(s) Supported
3Com 3+Open TCP 1.1, 1.2, 2.0, 2.1
Beame & Whiteside TCP/IP 3.0, 3.1
Digital PATHWORKS for DOS (TCP/IP) 4.1, 5.0
Firefox NOV*IX 2.21
FTP PC/TCP 2.1, 2.2, 2.3, 3.0, 3.1
HP ARPA Services for DOS 2.1
Microsoft LAN Manager TCP/IP 2.1a, 2.2
Microsoft Windows for Workgroups TCP/IP (16 bit) 3.11
Novell LAN WorkPlace for DOS 4.0, 4.01, 4.1, 4.12, 4.2, 5.0
Sun PC-NFS 4.0a, 5.0, 5.1.5
Ungermann-Bass Net/One TCP/IP1 16.5, 16.6
Wollongong PathWay Access 1.2, 2.0, 3.0
  1. The current configuration only provides support through the Ungermann-Bass protocol stack.

:

In addition to the above listed transports, the JSB VSL supports transports that comply with the Windows Sockets version 1.1 specifications.
Note
 Users of 3Com 3+Open TCP, Microsoft LAN Manager TCP/IP, Digital Pathworks TCP/IP, and HP ARPA Services for DOS must ensure that their local PROTOCOL.INI file contains the correct name of their local workstation. The entry for the workstation name is in the TCPGLOBAL section of the PROTOCOL.INI file as follows: where local_name is the name of the local workstation and is the same name found in the local HOSTS file or in the Domain Name Server's HOSTS file.

Verifying MSOCKLIB.DLL File Installation

When you install the Oracle TCP/IP Protocol Adapter for Windows, the Oracle Installer installs the MSOCKLIB.DLL file and several other VSL files under the ORAWIN\BIN directory. These VSL files enable the SQL*Net driver to communicate with the vendor's TCP/IP.

If multiple copies of MSOCKLIB.DLL exist on your PC, be sure the most recent version is in the ORAWIN\BIN directory.

To verify that you are using the most recent version of MSOCKLIB.DLL, compare the creation date of this file on your CD-ROM containing the Oracle TCP/IP Protocol Adapter for Windows with the values shown for MSOCKLIB.DLL in your ORAWIN\BIN directory.

To compare the file creation dates, change directories to your ORAWIN\BIN directory and insert CD-ROM contains the Oracle TCP/IP Protocol Adapter for Windows. If the CD-ROM is mapped to the G: drive, for example, enter:

DIR G:\MSOCKLIB.DLL
followed by:

DIR MSOCKLIB.DLL
If the version on the Oracle TCP/IP Protocol Adapter for Windows CD-ROM is more recent, type:

COPY G:\MSOCKLIB.DLL

Verifying VSL.INI File Installation

 Verify that the VSL.INI file is in the \WINDOWS directory. The VSL.INI file maps JSB calls to each vendor's API.

Verifying JSB Executable File Installation

Verify that the DLL file specified for your vendor and the TSR executable appears in your ORAWIN\BIN directory. The TCP_VENDOR parameter is described in "Verifying ORACLE.INI File Contents."

Some TCP/IP transports are implemented as a DLL that loads automatically when SQL*Net initiates calls to the transport. Other TCP/IP products are implemented as TSR programs. These programs must be executed before SQL*Net can operate.

The Window Socket vendors, the DLLs installed by the Oracle Installer and TSR executables, and the TCP_VENDOR parameter are shown in Table B-3:

Table B¯3 Windows Sockets Installation

Product Name (Windows Sockets) JSB DLLs or TSRs Vendor Key for TCP_VENDOR
3Com 3+Open TCP 2.1 MWINSOCK.DLL WINSOCK
Digital PATHWORKS for DOS (TCP/IP) 5.0a MWINSOCK.DLL WINSOCK
Distinct TCP/IP 3.1 MWINSOCK.DLL WINSOCK
Esker Tun TCP 7.1, 7.2, 7.3 MWINSOCK.DLL WINSOCK
Frontier Technologies Super-TCP for Windows 3.0, 4.0, 4.0R2, 4.15 MWINSOCK.DLL WINSOCK
FTP PC/TCP 2.2, 2.3, 3.0, 3.1 MWINSOCK.DLL WINSOCK
FTP PC/TCP OnNet VxD 1.1, 1.2, 2.0 MWINSOCK.DLL WINSOCK
IBM TCP/IP for DOS 2.1.1 MWINSOCK.DLL WINSOCK
IBM TCP/IP for DOS/Windows Access Kit 2.0 MWINSOCK.DLL WINSOCK
lpswitch PIPER/IP 1.001, 2.0 MWINSOCK.DLL WINSOCK
Microsoft Windows for Workgroups TCP/IP (VxD) 3.11 MWINSOCK.DLL WINSOCK
Microsoft Windows NT TCP/IP 3.1, 3.5, 3.51 MWINSOCK.DLL WINSOCK
NetManage Chameleon TCP/IP 3.11, 4.0, 4.01, 4.51, 4.6 MWINSOCK.DLL WINSOCK
Persoft SmarTCP 3.0, 4.0 MWINSOCK.DLL WINSOCK
Sun PC-NFS 5.1.5 MWINSOCK.DLL WINSOCK
Sun PC-NFS Pro 1.1 MWINSOCK.DLL WINSOCK
Walker Richer & Quinn Reflection Network Series 2.1, 4.0, 4.02, 5.0, 5.6 MWINSOCK.DLL WINSOCK
Wollongong PathWay Access Runtime 2.0, 3.0, 4.0 MWINSOCK.DLL WINSOCK
  1. Opening a network definition stored in a database may fail as described above. Users should update to the WINSOCK.DLL shipped with Chameleon release 4.5 or later. Before a SQL*Net connection or disconnection is established, NetManage Chameleon loads or unloads its TCP module in Windows. On some slower PCs; for example, a 386/25Mhz or below, loading and unloading of the NetManage module may cause SQL*Net to hang, especially when it is running during a connect or disconnect from a batch file. If the SQL*Net connection hangs, do a warm start by pressing [Ctrl]+[Alt]+[Delete].

The other socket vendors, the DLLs installed by the Oracle Installer and TSR executables, and the TCP_VENDOR parameter are shown in Table B-4:

Table B¯4 Other Sockets Installation

Product Name (Other Sockets) JSB DLLs or TSRs Vendor Key for TCP_VENDOR
3Com 3+Open TCP 2.0, 2.1 M3OPEN2.DLL 3OPEN
3Com 3+Open TCP 1.1, 1.2 M3OPEN.EXE 3OPEN
Beame & Whiteside TCP/IP 3.0, 3.1 MBW.EXE BW
Digital PATHWORKS for DOS (TCP/IP) 4.1, 5.0a M3OPEN.EXE PWORKS
Firefox NOV*IX 2.21 MNOVLWP.DLL NOVLWP
FTP PC/TCP 2.1, 2.2, 2.3, 3.0, 3.1 MFTP.EXE FTP
HP ARPA Services for DOS 2.1 MHPARPA.DLL HPARPA
Microsoft LAN Manager TCP/IP 2.1a, 2.2 MHPARPA.DLL LANMAN2
Novell LAN WorkPlace for DOS 4.0, 4.01, 4.1, 4.12, 4.21 MNOVLWP.DLL NOVLWP
Sun PC-NFS 4.0a, 5.0, 5.1.5 MPCNFS4.DLL PCNFS4
Ungermann-Bass Net/One TCP/IP 16.5, 16.6 MNETONE.EXE NETONE
Wollongong PathWay Access 1.2, 2.0, 3.0 MPATHWAY.DLL PATHWAY
  1. If you use Novell LAN Workplace Version 4.2, you must choose the non-WINSOCK interface. This is because Novell's WINSOCK implementation does not support OS_LINGER in their setsockopt() which is required for SQL*Net to perform non-blocking SQL.

Many of the vendors use the generic Windows Socket DLL, MWINSOCK.DLL. Windows Sockets is an emerging standard interface for TCP/IP under Windows.

The listed transports load automatically when called. However, ensure that the TCP/IP core code is loaded before starting Windows. These steps are described in the next section, "Loading the TCP/IP Network Software."
Note
 If you install the After Dark software after loading the JSB vendor-specific TSR file, the JSB vendor-specific TSR file unloads, and error message ORA-12533 appears. Oracle recommends that you install the After Dark software before you load the JSB vendor-specific TSR file.

Loading the TCP/IP Network Software

Before your workstation can load the correct JSB transport, your TCP/IP software must be installed and working properly. After installation, use the PING command to test your software, as described in "Verifying TCP/IP Network Connections". If you cannot successfully PING another workstation, you cannot use the TCP/IP Protocol Adapter for Windows.

If your software uses DLL transports, the transport loads automatically. If your vendor uses a TSR transport, the transport loads when you turn on your computer if the transport has been properly installed in your AUTOEXEC.BAT file. See the section "Verifying TCP/IP Vendor File Installation" to determine if your software uses a DLL transport or TSR transport and to verify that your transport is installed correctly.

Identifying the Destination Address for TCP/IP

With the Oracle TCP/IP Protocol Adapter for Windows, you must specify the destination host's Internet Protocol (IP) address in order to make a SQL*Net connection. If you do not specify the IP address of your host, you can instead specify a host name.

Using the Domain Name Service

Most TCP/IP transports attempt to use the Domain Name Service (DNS) to translate the host name into the host address. If a Domain Name Server is present on your network and the TCP/IP vendor supports DNS, the host name is successfully translated to the host address.

Each of the JSB-supported transports also identify the available servers on your network by referring to a HOSTS file. Transports refer to a HOSTS file only if they do not detect the presence of DNS or do not support DNS at all.
Additional Information
 See your network documentation for information on your network's DNS. Microsoft LAN Manager TCP does not support DNS.

Locating the HOSTS File

The HOSTS file is a text file that contains an entry for each host with the host name "mapped" to its corresponding Internet address on the network. There must be an entry in the HOSTS file for each server you intend to use.

SQL*Net uses the name lookup services provided by JSB (which in turn are implemented using third-party vendors' APIs). Because of this, SQL*Net uses the same HOSTS file resident in the directory expected by the native TCP/IP vendor.

For the JSB virtual socket library, the HOSTS file location is transport dependent. Each JSB-supported transport expects its HOSTS file to reside in a specific directory, as described in Table B-5:

Table B¯5 HOSTS File Location

This transport... Looks for the HOSTS file...
3Com 3+Open TCP In the directory specified by the "NETFILES=" parameter of the TCPGLOBAL section of PROTOCOL.INI, which is located in the home directory of the transport.
Beame and Whiteside TCP/IP In the transport's home directory. By default, this is \BWTCP.
Digital PATHWORKS for DOS In the transport's home directory. By default, this is \PW.
Frontier Technologies Super-TCP/IP for Windows In the transport's home directory. By default, this is \SUPERTCP
FTP PC/TCP In the location specified using the IPCONFIG utility. By default, this is \PCTCP.
HP ARPA Services for DOS In the directory specified by the "NETFILES=" parameter of the TCPGLOBAL section of PROTOCOL.INI, which is located in the home directory of the transport.
IBM TCP/IP for DOS In the ETC subdirectory of the transport's home directory. By default, this is \TCPDOS\ETC.
Microsoft LAN Manager TCP/IP In the transport's home directory. By default, this is \LANMAN.DOS\ETC.
Microsoft Windows for Workgroups TCP/IP In the Windows for Workgroups home directory. By default, this is \WINDOWS or \WFW.
NetManage TCP/IP In the transport's home directory. By default, this is \NETMANAG
Novell LAN WorkPlace for DOS In the TCP subdirectory of the transport's home directory. By default, this is \XLN\TCP.
Sun PC-NFS In the directory specified by the NFSPATH environment variable of AUTOEXEC.BAT. If no HOSTS file is found there, PC-NFS looks in the NFS home directory.
Wollongong Pathway Access In the transport's home directory, which defaults to \PATHWAY. (Use the CUSTOM.EXE utility to configure the HOSTS file. Refer to your Wollongong documentation for information.)

Enabling Ctrl+C

The use of [Ctrl] + [C] to terminate 16-bit applications is enabled with the YIELD parameter in ORACLE.INI file, under the [ORACLE] section:

 [Oracle] 

 ORACLE_HOME=C:\ORAWIN 

 CUSTOMER=Oracle Corporation 

 NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1 

 ORAINST=E:\ORA73WIN\233\dbs 

 MSHELP=E:\ORA73WIN\233\mshelp 

 YIELD=YES 

 [orainst] 

 . 

 . 

 .

Verifying SPX Protocol Adapter Setup

Editing the AUTOEXEC.BAT File

 If you are using the SPX Protocol Adapter for Windows, there are additional lines you must include in your AUTOEXEC.BAT file. This is because the Open Data-Link Interface (ODI) enables you to run more than one network protocol simultaneously. These lines are:

lsl (the driver for your network interface card)

3c503 (if using a 3COM 3C503 network interface card)

ipxodi

vlm (or netx) 






 Note


 vlm is required with SQL*Net releases 2.1 through 2.3. netx is OK with SQL*Net release 1.1 or 2.0.x.
The SPX Protocol Adapter for Windows accesses the NetWare DLL files to make the SQL*Net connection. Make sure that your Windows home directory contains the DLLs required by Novell NetWare. These files are available from the Novell NetWare Workstation Kit for DOS and Windows. If these DLLs are missing or the SPX Protocol Adapter for Windows cannot detect their location, you receive an error message during login.

If you installed these DLLs manually, make sure their location appears on the DOS PATH.
Additional Information
 See "Oracle Protocol Adapters" for the supported version of the Novell NetWare Workstation Kit for DOS and Windows.

Verifying NetBIOS Protocol Adapter Setup

Editing the CONFIG.SYS File or Setting a Default Protocol

 If you are using the NetBIOS Protocol Adapter for Windows to support:

Verifying LU6.2 Protocol Adapter for IBM NS/WIN Setup

Editing the AUTOEXEC.BAT AND SYSTEM.INI Files

 For NS/WIN, the user's path in the AUTOEXEC.BAT must include the directory in which the NS/WIN drivers and utilities are located, which is typically "NSW" on the root directory. The drivers are specified in the SYSTEM.INI file.

Table B-6 shows the drivers for each connection type:

Table B¯6 LU6.2 Connection Types

Connection Type Drivers
asynchronous vnswutil.386
local area network vnswutil.386
vd802.386
synchronous vnswutil.386
twinaxial vnswutil.386
vdnswq.386
vdtwinx.386

Editing the NSD.INI File

For NS/WIN, all parameters are contained in the NSD.INI file, which must be located in your Windows directory. Make the following changes to your NSD.INI file. Use the exact upper case/lower case combination shown below: 
[IUO]

DontYield=TRUE
Reboot your machine after making these changes.

Follow the additional steps described below to ensure successful vendor configuration of IBM NS/WIN on your computer or workstation.

This section provides an overview of NSD.INI file parameter requirements. For a complete description of parameters and how to change them, refer to Configuration Parameters Reference for Administrators and Application Programmers Version 1.0. Most parameters can be changed with the Configure utility icon located in the IBM APPC Networking Services program group. Some of the optional parameters can only be modified by editing NSD.INI with a text editor.
Note
 The parameters and examples are subject to changes in the IBM NS/WIN software and IBM documentation. Consult the IBM documentation provided with NS/WIN version 1.0.

To verify successful vendor installation:

  1. Install the IBM NS/WIN Version 1.0 software:

  2. Verify that the user's path includes the directory in which the NS/WIN drivers are located. (See the Table B-6 table on the previous page)

  3. Choose the Configure icon in the IBM APPC Networking Services program group to configure the NSD.INI file, which contains the CONFIG.NSD, DEFINETP.NSD, MODE.NSD, and SIDEINFO.NSD files that were previously configured separately with NS/DOS.

  4. Modify the NDS.INI file as described below. This example describes how to connect a Windows client to an OS/2 host:

    [Configuration]
    DLCTYPE=LAN
     
    STARTPROGRAMLAUNCHER=TRUE
     
    EHNAPPCNONBLOCKING=FALSE
     
    LANGUAGE=2924
     
    LOCALLUNAME=ORACLE.CLIENT
     
    NODEID=07500000
     
    DIRECTORY=C:\NSW\
     
    
    

    [LAN]
    
    

    TRLD1=COMPAQ, 10005A747AAF
    
    

    
    

    [REMOTE]
    
    

    SDDI=66
    
    

    
    

    [MODES]
    
    

    SNASVCMG= 512, 7, 2, 1
    
    

    BLANK= , 3, 8, 4
    
    

    #BATCH= , 3, 8, 4
    
    

    #INTER= , 7, 8, 4
    
    

    QPCSUPP= 1024, 2, 32, 16
    
    

    ORAPLU62= 4096, 1, 20, 10
    
    

    
    

    [SIDEINFO]
    
    

    SERVER= SERVER, ORAPLU62, MYDB, NONE, ,
    
    

    DB= SERVER, ORAPLU62, MYDB, NONE, ,
    
    

    VM= ORAVTAMA, ORAPLU62, ORTNMST, NONE, ,
    
    

    
    

    [DEFINETP]
    
    

    APINGD=C:\NSW\SAMPLES\APINGD.EXE, 120, 30, am_started,
    
    

    
    

    ATELLD=C:\NSW\SAMPLES\ATELLD.EXE, 120, 30, am_started,
    






    


  1. Reboot Windows for your changes to take effect.
    


  2. Start NS/WIN by choosing the Autostart Networking Services icon in the IBM APPC Networking Services group. 

    


    

     Additional Information
    
    
See your IBM documentation.



    


    

    

    

    




 Configuring Oracle Version 6 Tools 


SQL*Net for Windows uses the Oracle Installer Version 3.1x Windows directory structure. In this directory structure, SQL*Net for Windows looks at the ORACLE.INI file for configuration parameters.


To use Version 6 Tools with SQL*Net for Windows, you must make two changes:


    


  1. Add the following path statement to your AUTOEXEC.BAT file:
    

    PATH=C:\ORAWIN\BIN

    


  2. Modify the ORACLE.INI file
    

Enter the CONFIG.ORA parameters into the ORACLE.INI file to ensure that all Version 6 Tools parameters are located by SQL*Net. 
    


















Go to previous file in sequence
Go to next file in sequence

Prev 
Next		
















Oracle

Copyright © 1996 Oracle Corporation.


All Rights Reserved.		















Go to Product Documentation Library

Library		





Go to books for this product

Product		





Go to Contents for this book

Contents		






Go to Index

Index