Oracle Network Products Getting Started for Windows Platforms

Library

Product

Contents

Index

Verifying Parameters and Vendor Adapters for Windows 3.1x

• Verifying File Parameters
• Verifying TCP/IP Protocol Adapter Setup
• Verifying SPX Protocol Adapter Setup
• Verifying NetBIOS Protocol Adapter Setup
• Verifying LU6.2 Protocol Adapter for IBM NS/WIN Setup
• Configuring Oracle Version 6 Tools

Verifying File Parameters

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

Verifying CONFIG.SYS File Contents

BUFFERS=16

FILES=60

BREAK=ON

Verifying WIN.INI File Contents

[ORACLE]

ORA_CONFIG=C:\WINDOWS\ORACLE.INI

PATH=C:\ORAWIN\BIN;<DOS_Oracle_home> 

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

Verifying TCP/IP Protocol Adapter Setup

• Loading TSR Transports for TCP/IP

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

• Verifying ORACLE.INI File Contents

• Using Windows Sockets Vendors

• Verifying TCP/IP Vendor File Installation

• Loading the TCP/IP Network Software

• Enabling Ctrl+C

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)

path\TCPTSR

path\DNRTSR

path\NMTSR

path\SOCKTSR

ORAWIN\BIN\M3OPEN

\ORAWIN\BIN\MBW.EXE

FTP PC/TCP

\PCTCP\3C503

\PCTCP\ETHDRV

\ORAWIN\BIN\MFTP

[boot]

network.drv=pctcpnet.drv

[386 Enhanced]

device=vpctcp.386

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.

[boot]

network.drv=lanman21.drv

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)

path\TCPTSR

path\DNRTSR

path\NMTSR

path\SOCKTSR

HP ARPA Services for DOS

path\TCPTSR

path\SOCKTSR

path\DNRTSR

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

[386 Enhanced]

device=vtil.386

device=vbapi.386

device=vsockets.386

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

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

[boot]

network.drv=netware.drv

[386 Enhanced]

device=vtcpip.386

path\NET INIT

path\RTM

path\[RNMNIS|RNMFILE]

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

[boot]

network.drv=pcnfs.drv

[386 Enhanced]

device=pcnfs.386

path\RNDIS <parameters>

path\NETBIND

call path\STARTNET.BAT

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

[386 Enhanced]

device=vsockets.386

path\PWCONFIG

path\3C503 parameters

path\PWTCP  		(the actual kernel stack)

Verifying ORACLE.INI File Contents

Verify that this parameter is set in the following format:

TCP_VENDOR = vendor_key

Using Windows Sockets Vendors

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 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

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

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

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: [TCPGLOBAL] HOSTNAME=local_name 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

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

DIR MSOCKLIB.DLL 

COPY G:\MSOCKLIB.DLL 

Verifying JSB Executable File Installation

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

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

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

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

Using the Domain Name Service

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

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

Enabling Ctrl+C

 [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] 

 . 

 . 

 . 

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.

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

• IBM LAN Support Program--make sure that the following files are loaded in your CONFIG.SYS file:
  • PROTMAN.DOS

  • ELNK3.DOS (the driver for your network adapter [3COM's EtherLink III in this case])

  • DXMA0MOD.SYS

  • DXME0MOD.SYS

  • DXMT0MOD.SYS

• Microsoft NetBEUI--set Microsoft NetBEUI as the default protocol using the network setup in Microsoft Windows for Workgroups.

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

Table B¯6 LU6.2 Connection Types

Editing the NSD.INI File

[IUO]

DontYield=TRUE

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:
   • APPC Networking Services for Windows

   • Local Area Network Support Program

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,

The parameters are described below:

Where...	Specifies the...
DLCTYPE	type of communications adapter being used.
STARTPROGRAMLAUNCHER	value for executing the program (TRUE).
EHNAPPCNONBLOCKING	value for enabling or disabling APPC nonblocking.
LANGUAGE	language in which to display messages and help screens.
LOCALLUNAME	local logical unit (LU) name for your workstation.
NODEID	node identifier carried in the XID exchange at the data link control layer when links are connected.
DIRECTORY	directory location of the NSD.INI file.
TRLD1	name used by only your workstation to refer to the link between your workstation and the remote computer.
SDDI	interrupt number used by the real-mode device driver.
SNASVCMG BLANK BATCH INTER QPCSUPP ORAPLU62	mode names to which you assign a maximum request unit (RU) size, receive pacing window size, maximum negotiable sessions value, and minimum negotiable session contention winners value.
SERVER DB VM	symbolic destination names to which you assign a partner LU name, mode name, transaction program name, security type, user identifier, and password.
APINGD ATELLD	transaction program (TP) names to which you assign a file specification name, accept/conversion time-out, incoming attach time-out, TP operation value, and parameter string

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.

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.

Prev Next

Copyright © 1996 Oracle Corporation. All Rights Reserved.

Library

Product

Contents

Index