home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
lsnata40.zip
/
LS40NAR1.INF
(
.txt
)
next >
Wrap
OS/2 Help File
|
1995-04-20
|
737KB
|
22,719 lines
ΓòÉΓòÉΓòÉ 1. We'd Like to Hear from You ΓòÉΓòÉΓòÉ
Please let us know how you feel about the books for this product by placing a
check mark in one of the columns following each question below:
Note that IBM may use or distribute the responses to this form without
obligation.
To return this form, print it, write your comments, and:
o Mail it to:
International Business Machines Corporation
Department 452, internal zip 9151
Austin, TX 78758 USA
o Send a FAX (U.S. only) to:
(512) 838-0666
For postage-paid mailing, please give your form to your IBM representative.
Please check off the online (O/L) or hardcopy (H/C) book you are commenting
about:
O/L H/C
___ ___Easy Start
___ ___Up and Running!
___ ___NARV1: Planning, Installation and Configuration
___ ___NARV2: Performance Tuning
___ ___NARV3: Network Administrator Tasks
___ ___OS/2 LAN Requester User's Guide
___ ___DLS and Windows User's Guide
___ ___Problem Determination Guide
___ ___Programming Guide and Reference
___ ___Commands and Utilities
n/a ___Guide to LAN Server Books
___ ___MPTS Configuration Guide
___ ___LAN CID Utility Guide
Overall, how satisfied are you with the book?
Very Very
Satisfied Dissatisfied
1 2 3 4
Overall
Satisfaction ___ ___ ___ ___
Are you satisfied that the book is:
Accurate ___ ___ ___ ___
Complete ___ ___ ___ ___
Easy to find ___ ___ ___ ___
Easy to understand ___ ___ ___ ___
Well organized ___ ___ ___ ___
Applicable to your
tasks ___ ___ ___ ___
Please tell us how we can improve the information:
_________________________________________________________
_________________________________________________________
_________________________________________________________
_________________________________________________________
Thank you! May we contact you to discuss your responses? ___Yes ___No
Name:
_________________________________________________________
Title:
_________________________________________________________
Company or Organization:
_________________________________________________________
Address:
_________________________________________________________
_________________________________________________________
_________________________________________________________
Phone:
(___)__________________________________________
Fax
(___)__________________________________________
Do not use this form to request IBM publications. Please direct any requests
for copies of publications or for assistance in using your IBM system, to your
IBM representative or to the IBM branch office serving your locality.
ΓòÉΓòÉΓòÉ 2. Version Notice ΓòÉΓòÉΓòÉ
First Edition
The following paragraph does not apply to the United Kingdom or any country
where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS
MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states
do not allow disclaimer of express or implied warranties in certain
transactions; therefore, this statement may not apply to you.
This publication could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time.
It is possible that this publication may contain reference to, or information
about, IBM products (machines and programs), programming, or services that are
not announced in your country. Such references or information must not be
construed to mean that IBM intends to announce such IBM products, programming,
or services in your country.
Requests for copies of this publication and for technical information about IBM
products should be made to your IBM Authorized Dealer or your IBM Marketing
Representative.
(C) Copyright International Business Machines Corp. 1991, 1994. All Rights
Reserved.
(C) Copyright Microsoft Corp. 1988, 1991.
Note to US Government Users - Documentation and programs related to restricted
rights - Use, duplication or disclosure is subject to restrictions set forth in
GSA ADP Schedule Contract with IBM Corp.
ΓòÉΓòÉΓòÉ 3. Notices ΓòÉΓòÉΓòÉ
References in this publication to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended
to state or imply that only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe
upon any of IBM's intellectual property rights or other legally protectible
rights may be used instead of the IBM product, program, or service. Evaluation
and verification of operation in conjunction with other products, programs, or
services, except those expressly designated by IBM, are the user's
responsibility.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any rights to
these patents. You can inquire, in writing, to the IBM Director of Licensing
Services, IBM Corporation, 500 Columbus Ave., Thornwood, NY 10594, USA.
Asia-Pacific users can inquire, in writing, to Intellectual Property &
Licensing, IBM World Trade Asia Corporation 2-31, Roppongi 3-chome, Minato-ku,
Tokyo 106, Japan.
For online versions of this book, we authorize you to:
o Copy, modify, and print the documentation contained on the media, for use
within your enterprise, provided you reproduce the copyright notice, all
warning statements, and other required statements on each copy or partial
copy.
o Transfer the original unaltered copy of the documentation when you transfer
the related IBM product (which may be either machines you own, or programs,
if the program's license terms permit a transfer). You must, at the same
time, destroy all other copies of the documentation.
You are responsible for payment of any taxes, including personal property
taxes, resulting from this authorization.
THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow the exclusion of implied warranties, so the
above exclusion may not apply to you.
Your failure to comply with the terms above terminates this authorization. Upon
termination, you must destroy your machine readable documentation.
ΓòÉΓòÉΓòÉ 3.1. Trademarks ΓòÉΓòÉΓòÉ
The following terms, denoted by an asterisk (*) in this book, are trademarks of
the IBM Corporation in the United States, other countries, or both:
LAN Server OS/2 LAN Server
AT Personal Computer AT
XT Personal Computer XT
FFST/2 First Failure Support Technology/2
IBM Communications Manager/2
WIN-OS/2 DATABASE 2 OS/2
OS/2 Operating System/2
PS/2 Personal System/2
PS/55 Personal System/55
NetView Presentation Manager
The following terms, denoted by a double asterisk (**) in this book, are
trademarks of other companies:
3Com 3Com Corporation
BootWare Lanworks Technologies Inc.
EtherCard PLUS Standard Microsystems Corporation
EtherLink 3Com Corporation
Intel Intel Corporation
Pentium Intel Corporation
Microsoft Microsoft Corporation
MS-DOS Microsoft Corporation
NIU Ungermann-Bass Corporation
Novell Novell, Inc.
RIPL CTA Incorporated
Ungermann-Bass Ungermann-Bass Corporation
Weitek Weitek Corporation
Windows Microsoft Corporation
ΓòÉΓòÉΓòÉ 4. About This Book ΓòÉΓòÉΓòÉ
This book introduces the IBM* Operating System/2* (OS/2*) LAN Server*
Version 4.0 program, briefly discusses its main features, gives information
about planning your network, and provides step-by-step instructions for
installation and configuration. The LAN Server product includes LAN Server,
OS/2 LAN Requester, MPTS (which includes LAN Adapter and Protocol Support), and
DOS LAN Services.
This book is the first volume of the IBM OS/2 LAN Server Version 4.0 Network
Administrator Reference (hereafter referred to as the LAN Server Network
Administrator Reference). The LAN Server Network Administrator Reference
Volume 2: Performance Tuning provides information about configuration
parameters and performance. The LAN Server Network Administrator Reference
Volume 3: Network Administrator Tasks provides information about setting up and
using LAN Server. All three volumes are included in the LAN Server product
package.
Note:
The program that installs and configures the OS/2 LAN Server and OS/2
LAN Requester components of LAN Server is called the LAN Services
installation/configuration program. For consistency, the term LAN
Services (instead of LAN Server) is used throughout this book in
contexts dealing with installation and configuration tasks and their
results. The terms OS/2 LAN Server and OS/2 LAN Requester are used in
contexts where a distinction needs to be made between the two
components. In all other cases, the term LAN Server is used to refer to
the product.
ΓòÉΓòÉΓòÉ 4.1. Who Should Use This Book ΓòÉΓòÉΓòÉ
This book is intended for network administrators and technical support
personnel who are familiar with OS/2 2.1 or higher and DOS.
Network administrators are responsible for the installation, management,
control, and configuration of a network. The network administrator defines the
resources to be shared and determines who can use those resources.
The network administrator is also responsible for ensuring that all or part of
any program available on the network is shared according to the appropriate
program license agreement or conditions of use.
Technical support personnel can use this book as an introduction to the LAN
Server product.
This book assists the network administrator or user in the following tasks:
o Planning a network
o Installing or reinstalling the OS/2 LAN Server or OS/2 LAN Requester
component of the LAN Server 4.0 product
o Upgrading the OS/2 LAN Server 2.0 or 3.0 product
o Upgrading an IBM PC LAN Program Version 1.3 (or later) server (SBCS systems
only)
Note:
For upgrading PC LAN Program servers, refer to Migrating PCLP to an
IBM OS/2 LAN Server Environment.
o Upgrading OS/2 LAN Requester Version 2.0 or 3.0
o Upgrading the requester component of LAN Enabler 2.0
o Installing DOS LAN Services, upgrading an IBM PC LAN Program Version 1.3 (or
later) requester to DOS LAN Services (SBCS systems only), and upgrading DOS
LAN Services from OS/2 LAN Server 2.0 (or later) to DOS LAN Services from
OS/2 LAN Server 4.0.
o Configuring DOS LAN Services Windows (with Microsoft** Windows** 3.1)
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: DOS LAN Services Windows is Γöé
Γöé available on: Γöé
Γöé Γöé
Γöé o IBM DOS 5.0/V Γöé
Γöé o MS DOS 6.2/V Γöé
Γöé o PC DOS 6.1/V or 6.3/V Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
o Running DOS LAN Services on OS/2 2.0 or 2.1
o Creating 386-HPFS boot diskettes
Refer as needed to the conceptual and planning information in Chapters 1 and 2
before, during, and after installation and configuration.
Some complex networks may require editing of the LAN configuration files. For
detailed information, refer to the LAN Server Network Administrator Reference
Volume 2: Performance Tuning.
ΓòÉΓòÉΓòÉ 4.2. LAN Server Highlights ΓòÉΓòÉΓòÉ
The LAN Server 4.0 product provides the following enhancements:
o The LAN Server Administration graphical user interface (GUI) replaces the
full-screen interface (FSI). The LAN Server Administration GUI is a
selectable component. The object-oriented GUI allows you to configure and
use the network by manipulating visual objects. The LAN Server
Administration GUI is similar in appearance to the OS/2 Workplace Shell.
o For DOS requesters, the FSI has been replaced with a GUI that supports DBCS
and mouse input, as well as all the current FSI functions. This GUI can be
used with or without Windows.
o Network DDE and Clipboard allows application programs or users to copy text
from one workstation to another through the clipboard. You can also create
dynamic data links between different workstations. Dynamic data links are
copies of data that are automatically updated across the network when changes
are made to the original data. To use Network DDE and Clipboard, you must use
applications that support the clipboard and dynamic data linking functions.
You can use Network DDE and Clipboard with DOS LAN Services if you are using
the Windows interface.
o Network Messaging provides a messaging function for sending messages to and
receiving messages from other users on the network. The network messaging
function uses the Messenger service.
o 32-bit application programming interfaces (APIs) allow you to develop 32-bit
applications to take advantage of the 32-bit capabilities of OS/2 2.0 and
higher.
o You can limit the size of 386-HPFS directories. LAN Server 4.0 stores the
limits within the file system and enforces the disk-space limits by
generating alert messages when you approach the limits and by returning an
alert message when you reach the limit.
o The LAN Server Applications Development Toolkit includes the API structures
(.H and .LIB files) and sample programs. The LAN Server APIs have been
enhanced to provide better 32-bit support and extend their functionality. The
toolkit is selectable for OS/2 clients, additional servers, and domain
controllers.
o DOS LAN Services includes Peer support for DOS requesters, which allows users
to share printers and directories with other LAN Server DOS clients, OS/2 LAN
Requesters, and other SMB-based network products. Peer functions can be
invoked from either the graphical user interface or the command line. Peer
services for DOS clients has the same single-session restriction that the
OS/2 client has. For more information, refer to the IBM OS/2 LAN Server
Version 4.0 DOS LAN Services and Windows User's Guide or the LAN Server
Commands and Utilities.
o Network applications, both public and private, as well as DOS OS/2 client
applications assigned to the user, now reside in a single Network
Applications folder. The program objects for these applications are based on
the OS/2 program object. Therefore, the actual icon for the application is
displayed, and the application program settings are available.
o The advanced server has been enabled to take advantage of unique features of
the Pentium** processor to improve performance.
o LAN Server 4.0 provides REXX callable routines that extend the REXX language
to take advantage of the new RIPL APIs. The definitions and profiles of RIPL
clients on LAN Server can now be managed using the REXX programming language.
o LAN Server 4.0 enables DOS LAN Services to be installed through the DOS
Configuration, Installation, and Distribution (CID) environment, using
NetView* Distribution Manager/2 2.0.
o LAN Server 4.0 provides enhanced multidomain support by including the
following as part of the product:
- Cross domain aliases
- Multi-domain administration
- Network sign-on coordinator
- Multi-domain browse and connect
o The OS/2 transport services included in LAN Server 4.0 introduce a transport
independent programming framework based on the Multi-Protocol Transport
Services (MPTS) architecture for distributed OS/2 applications. LAN Server
4.0 includes the TCP/IP and NetBIOS protocol stacks, access to NetBIOS
through traditional NetBIOS programming interfaces, and an improved
implementation of NetBIOS for TCP/IP called TCPBEUI.
ΓòÉΓòÉΓòÉ 4.3. How This Book Is Organized ΓòÉΓòÉΓòÉ
This book contains the following chapters and appendixes:
o Overview of the LAN Server Product includes conceptual information about
local area networks (LANs) and introduces LAN Server.
o Planning Your Network helps you plan your network.
o LAN Services Installation and Configuration helps you install, reinstall, and
configure the OS/2 LAN Server and OS/2 LAN Requester components of LAN
Server, and upgrade a previous version of OS/2 LAN Server, PC LAN Program
Version 1.3 (or later), and OS/2 LAN Requester.
o Remote Installation provides information on how to set up and start a remote
installation. Three modes of remote installation are described: unattended,
lightly attended, and attended.
o Installing and Optimizing DOS LAN Services helps you install DOS LAN
Services, change your DOS LAN Services configuration, and upgrade DOS LAN
Requester by installing DOS LAN Services remotely. Installing and Optimizing
DOS LAN Services also describes how to configure DOS LAN Services Windows and
provides example configuration files.
o Installing and Running DOS LAN Services on OS/2 helps you install DOS LAN
Services on OS/2 on a specific DOS session started from either a primary
partition or an image file. This chapter also provides tips on setting up
multiple DOS LAN Services workstations.
o Planning for the LAN Support Program describes some planning considerations
for the LAN Support Program.
o Customizing the LAN Support Program Device Driver Parameters describes the
LAN Support Program device driver parameter values and tells you how to edit
the parameter values in the CONFIG.SYS file.
o Worksheets contains worksheets to assist in planning your network.
o Migrating PCLP to an IBM OS/2 LAN Server Environment helps you upgrade from a
PC LAN Program (PCLP) 1.3 or later environment to a LAN Server 4.0
environment.
o Configuration Considerations helps you calculate server resources and modify
capacity-related parameters.
o Language Support and Code Page Considerations discusses available languages
and code page considerations.
o Upgrading LAN Server 2.0 or 3.0 helps you upgrade a LAN Server 2.0 or 3.0
domain. It guides you through a server upgrade and helps you run various
migration utilities.
o Upgrading or Reinstalling on 386-HPFS Servers describes how to upgrade or
reinstall on a 386-HPFS workstation. It provides step-by-step instructions
to help you run the PREPACL and THIN386 utilities during a diskette-based
installation of OS/2.
o Upgrading LAN Server 2.0 or 3.0 Using the LAN CID Utility helps you upgrade
the LAN Server 2.0 or 3.0 product using the LAN CID Utility. It provides
example sections of a REXX command file used to remotely upgrade a 386-HPFS
workstation to OS/2 and LAN Server.
o Creating 386-HPFS Startup Diskettes describes how to create 386-HPFS boot
diskettes and how to start a workstation with those diskettes.
o Response File Keywords Used in Remote Installation provides descriptions and
default values for response file keywords used in remote installation.
Examples of response files are also provided.
o LAN Support Program Messages and Problem Solving lists all the messages that
the LAN Support Program device driver files can display when being loaded
into memory. This chapter also contains recommendations to help you prevent
or handle problems you may have while using the LAN Support Program. Finally,
the chapter outlines guidelines for adjusting the NetBIOS parameter values
when using DXMT0MOD.SYS.
o NetBIOS Over TCP/IP discusses NetBIOS over TCP/IP and explains how to
configure LAN Server 4.0 on a wide-area network.
o LAN Manager 1.0 NetBIOS Interface describes the LAN Manager 1.0 (LM10)
interface.
ΓòÉΓòÉΓòÉ 4.4. Conventions ΓòÉΓòÉΓòÉ
Throughout this book, the following highlighting conventions are used.
Note:
Highlighting may vary online depending on the type of display you have.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 1. Highlighting Conventions Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé HIGHLIGHTING Γöé USED TO IDENTIFY Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CAPITAL LETTERS Γöé o Commands Γöé
Γöé Γöé o Directory names Γöé
Γöé Γöé o File names Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé BOLD Γöé Controls (when used in procedures), for example: Γöé
Γöé Γöé Γöé
Γöé Γöé o Menu bar choices Γöé
Γöé Γöé o Radio buttons Γöé
Γöé Γöé o Push buttons Γöé
Γöé Γöé o List boxes Γöé
Γöé Γöé o Check boxes Γöé
Γöé Γöé o Entry fields Γöé
Γöé Γöé o Read-only entry fields Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Italics Γöé o Book and diskette titles Γöé
Γöé Γöé o Variable names and values Γöé
Γöé Γöé o Technical terms when introduced Γöé
Γöé Γöé o Words of emphasis Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé "Monospace" Γöé o Coding examples Γöé
Γöé Γöé o Special characters Γöé
Γöé Γöé o Text the reader must type Γöé
Γöé Γöé o Text displayed on the computer screen Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 4.5. Double-Byte Character Set (DBCS) Users ΓòÉΓòÉΓòÉ
LAN Server runs on both single-byte character set (SBCS) and double-byte
character set (DBCS) systems. SBCS is a graphic character set in which each
character occupies one byte. DBCS systems use a set of characters in which each
character occupies two bytes. Languages, such as Japanese, Chinese, and
Korean, that contain more symbols than can be represented by 256 code
combinations, require double-byte character sets.
Throughout this book are notes to DBCS users. These notes are shaded and
contain information applicable to DBCS systems. Entering, displaying, and
printing DBCS characters require special hardware and software support, and
these special requirements are explained in the notes.
Restrictions for DBCS systems are indicated by the following:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 4.6. Related Books ΓòÉΓòÉΓòÉ
The following is a list of books that you may find helpful. For information on
ordering these publications, contact your authorized IBM sales representative.
o Coexistence Guide for OS/2 LAN Server and NetWare from IBM
o IBM AT Technical Reference
o IBM LAN Configuration, Installation, and Distribution Utility Guide
o IBM LAN Technical Reference
o IBM Multi-Protocol Transport Services - AnyNet for OS/2: Configuration Guide
o IBM Multi-Protocol Transport Services - AnyNet for OS/2 NetBIOS Guide
o IBM Multi-Protocol Transport Services - AnyNet for OS/2: Programmer's
Reference
o IBM OS/2 LAN Server Version 4.0 Commands and Utilities
o IBM OS/2 LAN Server Version 4.0 DOS LAN Services and Windows User's Guide
o IBM OS/2 LAN Server Version 4.0 Network Administrator Reference Volume 2:
Performance Tuning
o IBM OS/2 LAN Server Version 4.0 Network Administrator Reference Volume 3:
Network Administrator Tasks
o IBM OS/2 LAN Server Version 4.0 OS/2 LAN Requester User's Guide
o IBM OS/2 LAN Server Version 4.0 Problem Determination Guide
o IBM OS/2 LAN Server Version 4.0 Programming Guide and Reference
o IBM OS/2 LAN Server Version 4.0 Up and Running!
o IBM PC Network Hardware Maintenance and Service Manual
o IBM Token-Ring Network Administrator's Guide
o IBM Token-Ring Network Introduction and Planning Guide
o IBM Token-Ring Network PC Adapter Hardware Maintenance and Service
o IBM Token-Ring Network Problem Determination Guide
o IBM Token-Ring Network Technical Reference
o OS/2 Technical Library
ΓòÉΓòÉΓòÉ 4.7. Training ΓòÉΓòÉΓòÉ
IBM offers classroom courses to assist customers in properly setting up and
using LAN Server. For tuition information, schedule availability, and IBM
education center locations, contact an IBM representative or call IBM
Direct-Education toll free at the following number (in the U.S. only):
1-800-IBM-8322
ΓòÉΓòÉΓòÉ 5. Overview of the LAN Server Product ΓòÉΓòÉΓòÉ
This chapter provides conceptual information about local area networks (LANs)
and briefly discusses the various features of the LAN Server product.
A LAN is a group of workstations connected by adapters and cables. When a
workstation is part of a LAN, its users can communicate with other
workstations. Communications on a LAN are limited to a moderately sized
geographic area, such as a single office building, warehouse, or campus.
Because the geographic area is limited, however, communication on a LAN is very
high speed and has very high quality. The figure titled A Local Area Network
illustrates a LAN.
A Local Area Network
ΓòÉΓòÉΓòÉ 5.1. The OS/2 LAN Server Product ΓòÉΓòÉΓòÉ
The LAN Server product is a LAN program providing OS/2 LAN Server, OS/2 LAN
Requester, and DOS LAN Services. In addition, the installation package includes
Multi-Protocol Transport Services (MPTS), the LAN Support Program, and various
utilities.
OS/2 LAN Server provides resource sharing for directories, printers, and serial
devices across a LAN. OS/2 LAN Requester and DOS LAN Services access the shared
network resources by redirecting a request from an application program or user
onto the network. (DOS LAN Services enables DOS users to use resources on a
network.) OS/2 LAN Server provides the shared resources and passes the response
back to OS/2 LAN Requester or DOS LAN Services. This process is transparent to
the application; it seems as though the request is fulfilled locally.
OS/2 LAN Server and OS/2 LAN Requester run on OS/2 2.1 or later and must be
installed on either a 386- or 486-based workstation. LAN Adapter and Protocol
Support (LAPS), which is component of IBM Multi-Protocol Transport Services -
AnyNet for OS/2, is installed during the OS/2 LAN Server or OS/2 LAN Requester
installation.
Notes:
1. Refer to the discussion of the MPTS product in this section for
information on LAPS.
2. The LAN Server product is compatible with the Communications Manager/2*
and DATABASE 2 OS/2* programs.
DOS LAN Services must be installed on a 286-based (or higher) workstation and
requires:
o IBM DOS or MS-DOS** 3.3
o IBM DOS or MS-DOS 5.0
o MS DOS 6.0 or 6.2
o PC DOS 6.1 or 6.3
o Asian versions of IBM DOS 5.0 or 5.0/V
o Asian versions of PC DOS 6.1/V or later
o Asian versions of MS DOS 6.2/V
The LAN Server product is available in two separately sold installation
packages:
o IBM OS/2 LAN Server Version 4.0-Entry (hereafter referred to as LAN
Server-Entry)
o IBM OS/2 LAN Server Version 4.0-Advanced (hereafter referred to as LAN
Server-Advanced).
LAN Server-Advanced supports all functions available in the LAN Server-Entry
package as well as the 386 high performance file system (386 HPFS)
server-related functions, such as Fault Tolerance and Local Security.
For a brief discussion of each installable function, see Supported Functions.
For a list of the components installed with each package, see Installation
Package.
For a discussion of the functions provided by DOS LAN Services, see the IBM
OS/2 LAN Server Version 4.0 DOS LAN Services and Windows User's Guide.
The IBM Multi-Protocol Transport Services - AnyNet for OS/2 product is shipped
with the LAN Server product and includes the following:
o LAN Adapter and Protocol Support (LAPS)
The LAPS component of MPTS provides adapter, NetBIOS protocol, LAN Virtual
Device Driver (VDD), and IEEE802.2 support. By conforming to the
3Com**/Microsoft LAN Manager Network Device Driver Interface Specification
(NDIS) Version 2.01, LAPS provides support for a broad range of adapters and
protocols made by IBM, original equipment manufacturers (OEMs), and non-IBM
manufacturers. LAPS is installed with the LAN Server product. For more
information about LAPS, refer to the IBM Multi-Protocol Transport Services -
AnyNet for OS/2: Configuration Guide (hereafter referred to as the MPTS -
AnyNet for OS/2: Configuration Guide).
o Socket/MPTS
The Socket/MPTS component provides a transport framework that lets Socket
applications communicate using TCP/IP, NetBIOS, or Local IPC. Socket/MPTS
allows TCP/IP applications to run over NetBIOS and NetBIOS applications to
run over TCP/IP, using the non-native networking feature of Socket/MPTS. For
more information about Socket/MPTS, refer to the MPTS - AnyNet for OS/2:
Configuration Guide and the MPTS - AnyNet for OS/2: Programmer's Reference.
Note:
In the previous release of the LAN Server product (LAN Server 3.0), LAPS
was a separate product provided with MPTS. In the present release,
Socket/MPTS and LAPS are included as part of the LAN Server product.
ΓòÉΓòÉΓòÉ 5.2. LAN Connectivity ΓòÉΓòÉΓòÉ
The LAN Server product provides comprehensive LAN capabilities to
interconnected OS/2 and DOS workstations on the following networks:
o IBM Token-Ring Network
o IBM PC Network (SBCS systems only)
o IBM ETHERAND Network (IBM-supported Ethernet [DIX Version 2.0 specifications]
and IEEE 802.3 protocols)
o Any network supported by MPTS
o ETHERAND networks and workstations attached to 3174 control units by coaxial
cable
The LAN Server product allows up to four network adapter cards in an OS/2 LAN
Server or OS/2 LAN Requester workstation. For a list of supported adapter
cards, see Supported Network Adapters.
The LAN Server product servers and requesters can coexist and function together
with IBM LAN server and requester products at different version levels on the
same LAN. See Compatibility among Servers and Requesters.
The LAN Server product and TCP/IP can run on the same machine, if properly
configured. See the MPTS - AnyNet for OS/2: Configuration Guide.
ΓòÉΓòÉΓòÉ 5.3. User Interface ΓòÉΓòÉΓòÉ
After the LAN Server product has been installed, LAN tasks can be done from
either the command-line interface or, if installed, the LAN Server
Administration graphical user interface (GUI). In addition, a number of LAN
Server functions are available through the Network folder on the OS/2 desktop.
DOS LAN Services also provides both a command-line interface and, if installed,
a graphical user interface.
The command-line interface supports a set of commands that are used to invoke
system functions. The LAN Server Administration GUI is a menu system that
invokes the same functions.
For more information about the network commands, see the online LAN Server
Commands and Utilities. For information about the LAN Server Administration
GUI and the Network folder on the OS/2 desktop, see the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
ΓòÉΓòÉΓòÉ 5.4. Administering the Network ΓòÉΓòÉΓòÉ
The network administrator is a person who organizes LAN servers into groups
called domains. A domain consists of one or more servers that allocate
resources as a single logical system. The network administrator defines,
redefines, and deletes resources and users within a domain, and carries out
administrative tasks, such as managing print queues. Network administrators
perform services for network users and define access control to valuable (and
confidential) data and applications.
The administrator of a domain can log on at any OS/2 workstation within the
domain and, once logged on, access any resource in the domain.
ΓòÉΓòÉΓòÉ 5.5. Workstation Types ΓòÉΓòÉΓòÉ
The LAN Server product supports the following workstation types:
o Server
- Domain controller
- Backup domain controller
- Additional server
o Requester
- OS/2
- OS/2 remote IPL
- DOS (with or without Windows)
- DOS remote IPL (with or without Windows)
- Peer server
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: DOS LAN Services Windows is Γöé
Γöé supported by DOS 5.0/V and 6.1/V or later. DOS remote IPL is sup- Γöé
Γöé ported only on PC DOS 6.3/V. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 5.5.1. Server ΓòÉΓòÉΓòÉ
A server is a workstation that provides resources (such as directories,
printers, plotters, serial devices, and remote computing) to users on the LAN.
Access permissions to a resource are defined through the use of access control
profiles (ACPs). Access control information is stored on the server on which
the resources reside. For information on access permissions, see the LAN Server
Network Administrator Reference Volume 3: Network Administrator Tasks.
A server with the LAN Server product installed can also function as a
requester.
ΓòÉΓòÉΓòÉ 5.5.1.1. Domain Controller ΓòÉΓòÉΓòÉ
The network administrator designates one network server within each domain as
the domain controller. A domain controller is a server that is designated to
manage a domain; that is, to coordinate communication between servers and
requesters.
Each domain must have a domain controller. Definitions for network resources
reside at the domain controller in the domain control database (DCDB). The
DCDB contains information such as logon assignments, application selector
information, and resources to be shared. In addition, the domain controller
maintains the master user and group definitions file (NET.ACC). Updates to the
file are made at the domain controller and then copied to all servers on the
domain.
A physical LAN can be divided into several logical domains, with each domain
independently managed by a domain controller. Each domain has only one domain
controller; if a domain has only one server, that server is also the domain
controller.
ΓòÉΓòÉΓòÉ 5.5.1.2. Backup Domain Controller ΓòÉΓòÉΓòÉ
A backup domain controller maintains a copy of the DCDB. When a backup domain
controller is defined and started, users can log on to and use the domain, even
if the domain controller has failed or is busy retrieving information stored in
the DCDB.
The administrator can define (during LAN Services installation and
configuration) one or more backup domain controllers to receive DCDB
information. Any existing server in the domain (including the domain
controller) can be redefined as a backup domain controller.
In order for replication of the DCDB information to occur, the DCDB Replicator
service must be started on both the domain controller and backup domain
controller (using the autostart feature or the NET START DCDBREPL command). The
DCDB Replicator service is not related to the Replicator service, and both can
be active at the same time on the domain controller or backup domain
controllers.
After the DCDB Replicator service is started, information in the DCDB on the
domain controller is automatically copied to the backup domain controllers
whenever updates occur. The replicated DCDB information includes all files in
the \IBMLAN\DCDB subdirectory (except remote IPL files).
ΓòÉΓòÉΓòÉ 5.5.1.3. Additional Server ΓòÉΓòÉΓòÉ
A domain can have one or more additional servers. Additional servers receive
user and group information from the domain controller. Any additional server
in the network can be redefined as a backup domain controller.
ΓòÉΓòÉΓòÉ 5.5.2. Requester ΓòÉΓòÉΓòÉ
A requester is a workstation that allows users both to access shared resources
and to use the processing capability of the server. A requester has either
OS/2 LAN Requester or DOS LAN Services installed. A DOS application running in
DOS compatibility mode at an OS/2 LAN Requester workstation can access disk and
printer resources on an OS/2 LAN Server. The LAN Server product provides
network support of DOS LAN Services in a DOS environment (with or without
Windows). For more information, refer to the DOS LAN Services and Windows
User's Guide.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: Windows is available on DOS Γöé
Γöé 5.0/V and 6.1/V or later. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
A user (or network administrator) at an OS/2 or DOS requester on a LAN can
access any domain in which the appropriate access control profiles have been
defined. Only an administrator can create an access control profile. The
administrator should give the "P" permission to operators who will manage this
resource.
A user can log on to only one domain at a time; however, a single user ID can
log on to multiple requesters at a time.
A requester with the appropriately configured hardware can use remote initial
program load (remote IPL), which allows the workstation to receive the initial
program image from a LAN Server instead of from a local hard disk, CD-ROM, or
diskette. The LAN Server product supports remote IPL for DOS LAN Services and
OS/2 LAN Requester. To make use of remote IPL, a requester must have supported
adapters.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: DOS remote IPL is supported Γöé
Γöé only on DOS 6.3/V. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
A DOS LAN Services workstation without a hard disk can also be started from
diskette if the workstation has a diskette drive.
Compatibility among Servers and Requesters provides detailed information about
the coexistence and interoperability of various server and requester products
at different version levels.
A LAN Server or DOS LAN Services requester with the Peer service installed can
act as a peer workstation. Like a server, a peer workstation provides
resources to users on a LAN. A peer services workstation is, however, limited
to providing resources to one user at a time.
ΓòÉΓòÉΓòÉ 5.6. Example of a LAN Server Network ΓòÉΓòÉΓòÉ
A LAN can have more than one domain. For example, in an office building, a LAN
can have a domain for each department or floor of the building. A domain can
consist of one or more servers. A server can be active in only one domain at a
time.
On a physical LAN divided into more than one domain, workstation users can log
on to either domain. Once they are logged on and have been granted access,
users can access resources on any server in any domain. Both administrators and
users must be identified to the domain to which they log on.
ΓòÉΓòÉΓòÉ 5.7. Resource Sharing ΓòÉΓòÉΓòÉ
The directories, printers, and serial devices attached to or residing on a
server are called resources. Generally, users have access to resources on their
domain. They can also have access to resources in other domains if the network
administrators of the other domains grant the users access to those resources.
For a user to use a resource, the resource must be shared, and the user must be
assigned the proper access permissions.
ΓòÉΓòÉΓòÉ 5.7.1. Names of Shared Resources ΓòÉΓòÉΓòÉ
Users refer to a shared resource by either its alias or its netname. Aliases
and netnames are assigned by the network administrator sharing the resource.
Aliases and netnames can be used in both the LAN Requester graphical user
interface and the command-line interface.
ΓòÉΓòÉΓòÉ 5.7.1.1. Alias ΓòÉΓòÉΓòÉ
An alias is a nickname that enables easy reference to a resource. For example,
the network administrator could create the alias MAYDATA to refer to a
directory on SERVER1 called C:\MAY\DATASET. You can then connect to that
directory simply as MAYDATA. When an alias has been assigned to a resource,
you need not specify the path to the resource or its location when you connect
to it.
An alias can point to any LAN Server resource outside your domain. Since alias
definitions include the server and the path to a resource, an alias can be
redefined to point to a different resource or a different server without
affecting the procedures you use to connect to their resources.
ΓòÉΓòÉΓòÉ 5.7.1.2. Netname ΓòÉΓòÉΓòÉ
A netname identifies a shared resource on a server. All shared resources are
assigned a netname, even if they have been shared from an alias definition. A
shared resource must have a netname, but can be shared without an alias. When
you use a netname to connect to a shared resource, you must also specify the
server name. To use such a resource, the user must refer to it by its netname
and specify the server where the resource is located.
A resource shared via its alias definition is also given a netname, while it is
shared, that is equal to the alias name (in the case of a directory).
The server name and the netname are combined into a universal naming convention
(UNC) name that identifies a resource in the domain. A UNC name has the
following format:
\\servername\netname\path
where \path is optional.
Not all DOS or OS/2 commands are LAN-aware and support UNC names. For a list
of DOS and OS/2 commands that do not work with UNC names, refer to the LAN
Server Network Administrator Reference Volume 3: Network Administrator Tasks.
ΓòÉΓòÉΓòÉ 5.7.2. Types of Network Resources ΓòÉΓòÉΓòÉ
The three types of network resources are directory resources, printer
resources, and serial device resources.
ΓòÉΓòÉΓòÉ 5.7.2.1. Directories ΓòÉΓòÉΓòÉ
A directory resource is a directory that contains data files or programs. The
network administrator or the end user can share a directory resource to a local
drive letter (D through Z) to make that directory and its files available for
use. For example, to share the C:\PUBLIC directory, type:
NET SHARE PUBLIC=C:\PUBLIC
The network administrator can also assign a directory resource to one or more
users. Such a directory resource is called a home directory. A home directory
is assigned when a user logs on; this directory serves as personal storage
space.
After a local drive letter (for example, K) has been assigned to a directory
resource, the user can use the directory resource as if it resided on drive K
at the workstation. This is possible even though there is no physical drive K
on the workstation. For example, drive K could be assigned to a remote
directory resource identified by the alias DATASET. The files in DATASET could
then be used as if DATASET were the root directory of a disk in drive K.
When the user accesses drive K and requests a directory listing, a list of the
files in the alias DATASET is displayed (if the network administrator has given
the user permission to view that directory).
ΓòÉΓòÉΓòÉ 5.7.2.2. Printers ΓòÉΓòÉΓòÉ
Printers are another type of network resource that can be shared. For example,
to share a printer named LASER, type:
NET SHARE LASER /PRINT
The LAN Server product shares OS/2 print queues. OS/2 supports printing with
print queues so that different applications can print at the same time without
conflict. The LAN Server product extends the print queue support to other
machines on the network.
A spooler queue is an ordered list of print jobs waiting to be printed.
Network printers are accessed through shared spooler queues. A spooler queue
can be serviced by one printer or by a group of several printers called a
printer pool. A print job waiting in a spooler queue serviced by a printer
pool is processed by the first available printer in the pool (unless another
queue for that printer pool has a higher priority).
For example, suppose that a user has permission to use a shared network spooler
queue identified by the alias PRINTQ1 and that PRINTQ1 has been assigned to a
local device name, such as LPT2. Suppose also that PRINTQ1 is serviced by a
printer pool consisting of two printers. If the user sends a print job to
LPT2, the output will be printed at one of the two printers in the printer
pool. Because there could be other print jobs ahead of the one just sent, the
output might not be printed immediately. While the print job waits in the
queue, the user can continue with other tasks.
When the print job is completed, the network sends a message to the user's
workstation indicating that the print job is finished. If the Messenger service
is active, this message is displayed automatically on the workstation. The
Alerter service must be started on the print server for the message to be sent.
Sometimes a network administrator arranges for more than one spooler queue to
be serviced by a particular printer or a printer pool. For example, the
network administrator can create a spooler queue for the majority of users and
another queue for users who need to have their printer requests handled
quickly. In each case, the printer definition on the OS/2 requester must match
the remote printer definition.
ΓòÉΓòÉΓòÉ 5.7.2.3. Serial Devices ΓòÉΓòÉΓòÉ
A third type of shared resource is the serial device. Examples are modems,
plotters, and serial printers. Such devices are assigned either to COM ports
for direct input/output (I/O) use or to COM ports that are redirected from LPT
ports for output only.
Note:
DOS LAN Services does not provide access to shared serial devices.
For example, to share a modem connected to the COM1 port, type
NET SHARE MODEM=COM1: /COMM
To manage multiple serial devices, the network administrator can create serial
device queues and serial device pools where requests are automatically routed
to the first available device.
A serial device queue is an ordered list of user requests waiting to use a
shared serial device. A serial device pool is a group of similar serial
devices that services a serial device queue.
A serial device can service more than one queue, each possibly having a
different priority. The network administrator can create a serial device queue
for the majority of users and another queue for users who need to have their
serial device requests handled quickly. A serial device request waits in a
serial device queue until one of the serial devices in its pool becomes
available. While the serial device request waits in a queue, the user cannot
proceed with a task that requires the serial device. However, the user can
perform other OS/2 tasks in other OS/2 sessions.
The network administrator can create an alias for a serial device queue that
can be used in place of the full path to that queue. The user can use a shared
queue by assigning a local device name (COM1 through COM9 or LPT1 through LPT9)
to the serial device queue.
ΓòÉΓòÉΓòÉ 5.7.3. Connecting to Shared Resources ΓòÉΓòÉΓòÉ
To access a shared resource, assign it a local device name. A local device
name is either a local drive letter (such as K) or a local port name (such as
LPT2 or COM2). For example, local drive K could be assigned to a directory
resource (a shared directory), and LPT2 could be assigned to a shared spooler
queue to access a network printer. When the local device names K and LPT2 are
associated with shared resources (that is, associated with a netname), they are
said to be redirected device names.
Redirected device names can be used with DOS or OS/2 applications that are
designed to work across a network. However, not all DOS or OS/2 commands work
across a network and support redirected drives. For a list of DOS and OS/2
commands that do not work with redirected drives, refer to the LAN Server
Network Administrator Reference Volume 3: Network Administrator Tasks.
ΓòÉΓòÉΓòÉ 5.7.4. Network Applications ΓòÉΓòÉΓòÉ
A network application is a program, or a combination of a program and data,
that is defined to the domain because it uses network resources. For example,
a network application can be stored in a directory on a requester or in a
shared directory on a server. However, the program runs on the requester. If
the application's files are stored on a server, the files are accessed at the
requester from the server, as required.
Network applications can be either public or private. A public application is
one that is defined and managed by the network administrator for users on the
network. A private application is one that a user defines for personal use so
that network resources can be assigned automatically when the private
application is run. Public applications must reside on the server; private
applications can reside on either a server or a requester.
The program objects for these applications are based on the OS/2 program
object, which means that the real icon for the application is displayed, and
the application settings are available from an OS/2 client.
For example, a word processing program that resides on a requester could be
defined as a private network application, allowing output to be sent
automatically to a network printer. A shared directory containing, for
example, documents to be edited could be made current when the private
application is started.
Each time a user logs on to the domain, OS/2 LAN Server adds all OS/2
applications assigned to that user ID to the user's OS/2 desktop. Public and
private applications are listed in the Network Applications folder. A combined
total of 64 public and private applications can be listed.
ΓòÉΓòÉΓòÉ 5.8. Access Control ΓòÉΓòÉΓòÉ
Access to resources on a LAN is governed in two ways. First, User Profile
Management (UPM) provides validation for a user ID and password at logon, if
required. Second, OS/2 LAN Server's own access control system provides a set
of permissions that allow the network administrator to grant users various
levels of access to shared resources.
ΓòÉΓòÉΓòÉ 5.8.1. User Profile Management ΓòÉΓòÉΓòÉ
User Profile Management (UPM) provides a set of user and group validation and
management functions that help control access to information. (All user
management functions are also available from the LAN Server Administration
graphical user interface (GUI).) User IDs and optional passwords are used to
validate user identity. These user IDs and passwords are assigned by a user
with administrative authority. UPM operates within a Presentation Manager*
window environment; its tasks are completed through a menu interface. Online
help is available to assist both the user and the administrator.
Note:
Up to 16000 user IDs can be defined through UPM, but the full list
cannot be displayed in the Presentation Manager window environment.
UPM is installed by the LAN Services installation/configuration program. Each
installation of UPM is local to the particular workstation where it is
installed and validates users accessing data or using programs residing on that
particular workstation.
Note:
UPM can also be installed during Communications Manager/2 or DATABASE 2
OS/2 installation.
Each machine has a NET.ACC file, which stores user IDs, group IDs, and
passwords. Servers in a domain maintain synchrony in NET.ACC files; that is,
an identical copy of the NET.ACC file resides on each server. These local
NET.ACC files allow resources to be accessed even when the domain controller
fails, since user identity is always checked locally. UPM provides three levels
of authority: user, local administrator, and administrator.
ΓòÉΓòÉΓòÉ 5.8.1.1. User ΓòÉΓòÉΓòÉ
Users can perform the following tasks:
o Log on
o View the user profile
o Change their own passwords
o Add comments to the user profile
o Log off
ΓòÉΓòÉΓòÉ 5.8.1.2. Local Administrator ΓòÉΓòÉΓòÉ
For LAN access control, local administrative authority does not differ from
user authority. For Database Manager, the person with local administrator
authority has the same authority as the administrator, but the authority
extends to local databases only. A local administrator does not have
administrative authority for UPM.
ΓòÉΓòÉΓòÉ 5.8.1.3. Administrator ΓòÉΓòÉΓòÉ
In addition to being able to perform all user tasks, the person with
administrative authority can perform the following additional tasks:
o Administration of users:
- Add or delete users (including other administrators)
- Specify user authority (either user or administrator)
- Specify password options (optional or required)
- Specify user status (access allowed or denied)
o Administration for groups of users:
- Create or delete groups
- Add users to or remove users from groups
An administrator can establish groups so that access to protected objects can
be granted to all members of a department or to all persons performing
similar tasks. Access can then be granted to the group as a whole. The
members of the group can be changed through UPM. If a user ID is deleted, it
is removed from all groups.
UPM is a shared user-validation function. A user with administrator privilege
has that level of privilege for all OS/2 subsystems to utilize the UPM user
database.
ΓòÉΓòÉΓòÉ 5.8.1.4. Standalone Logon ΓòÉΓòÉΓòÉ
The LAN Server product supports the standalone logon feature, which allows a
user to log on without being verified by the domain controller. The LAN Server
product saves the ID and password specified by the user when logging on at the
client, and user validation takes place when access to a server's resource is
requested. The user ID and password are validated by the specified server
before access is granted. The standalone logon feature allows a requester to
continue to access servers (including peer workstations) outside the domain,
even if no logon server in the domain is active.
ΓòÉΓòÉΓòÉ 5.8.2. LAN Server Access Control System ΓòÉΓòÉΓòÉ
The network administrator can grant, restrict, or deny access to a shared
resource by creating an access control profile (ACP). An ACP defines resource
users and the level of access. The network administrator can also grant
permission to a user to create an access control profile (ACP) or change an
existing profile.
Each directory in a files type resource can have an ACP. Each file in a files
type resource can have an ACP. A profile is not required, but if one does not
exist, users cannot access the resource because the default permission is none.
Each type of resource can be accessed protected by rules in the root profile,
even if the resource does not have an individual ACP. If no root profile
exists, access is denied. For more information on access control, refer to the
LAN Server Network Administrator Reference Volume 3: Network Administrator
Tasks.
An access control profile can contain a user access list and a group access
list. A user access list is a list of user IDs and the permissions assigned to
them. A group access list is a list of group IDs and the permissions assigned
to them. (A group is a set of user IDs that can be referred to by a single
name, or group ID.)
The number of entries in the combined user and group lists for each access
control profile is limited to 64. Use a group list if you have a large number
of users with common needs.
The network administrator can assign access permissions that enable a user to
perform the following functions:
o Read files and run .EXE, .COM, .BAT, and .CMD files
o Write to files
o Create subdirectories and files
o Delete subdirectories and files
o Change file attributes
o Create, change, and delete access control profiles
Access permissions are described in detail in the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
The user IDs, group IDs, and passwords for all users within a server's domain
are stored in a UPM user accounts database (NET.ACC) on the server. On a LAN
Server-Entry workstation with either the FAT or HPFS file system, the access
control profile information is stored in the NET.ACC file. On a LAN
Server-Advanced workstation with the 386 HPFS installed, the access control
profiles for the 386-HPFS files and directories are stored within the file
system data structures for the corresponding partition.
The access control profiles for all other resources (for example, FAT files,
print spooler queues, and serial device queues) and drive-level access control
profiles for 386-HPFS drives are stored in the NET.ACC file. Up to 15000 access
control profiles can be stored in the NET.ACC file. A 386-HPFS workstation
stores an unlimited number of access control profiles for directories and files
residing on the 386 HPFS drives.
ΓòÉΓòÉΓòÉ 5.8.2.1. PREPACL and THIN386 Utilities ΓòÉΓòÉΓòÉ
The PREPACL and THIN386 utilities help you bypass the inability of OS/2's HPFS
file system's read files that are protected by 386-HPFS access control profiles
when you are upgrading OS/2 and OS/2 LAN Server 4.0-Advanced on a 386-HPFS
workstation.
The PREPACL utility helps you back up, remove, and restore 386-HPFS access
control profiles applied to any subdirectories or files that are required to
install OS/2.
The THIN386 utility creates a modified 386 HPFS that enables OS/2 to access
files that are protected by 386-HPFS access control profiles during the
following:
o A LAN Server-Advanced installation that follows a CD-ROM or diskette-based
OS/2 installation
o A LAN CID Utility-initiated OS/2 and LAN Server-Advanced installation
You must run one or both of these utilities when doing the following:
o Upgrading LAN Server 2.0 or 3.0-Advanced to LAN Server 4.0-Advanced (which
may include installing OS/2)
o Reinstalling OS/2 on a LAN Server 4.0-Advanced workstation
o Installing a new OS/2 release on a LAN Server 4.0-Advanced workstation
The PREPACL and THIN386 utilities are provided on Server - Disk 1. For
step-by-step information about when and how to run these utilities during the
installation cycle, see Upgrading or Reinstalling on 386-HPFS Servers.
Note:
Though PREPACL is intended for use on only 386-HPFS access control
profiles, it also removes and restores access control profiles on FAT
and OS/2 HPFS files that are kept in the NET.ACC file.
ΓòÉΓòÉΓòÉ 5.8.2.2. BACKACC and RESTACC Utilities ΓòÉΓòÉΓòÉ
The BACKACC and RESTACC utilities allow the backing up and restoring of FAT,
OS/2 HPFS, and 386-HPFS access control profile information associated with
server resources while the server is running. You must run these utilities to
save access control profile information when doing the following:
o Backing up and restoring data on a LAN Server server
o Installing LAN Server-Advanced over LAN Server-Entry
o Upgrading the LAN Server 2.0 or 3.0 product to the LAN Server 4.0 product
running on a different file system; for example, upgrading from the HPFS of
the LAN Server 2.0 product to the 386 HPFS of LAN Server 4.0-Advanced
o Replacing a file system from FAT to 386 HPFS on an Advanced server
The BACKACC and RESTACC utilities are located on Requester - Disk 1. For more
information on these utilities, see the LAN Server Commands and Utilities or
the LAN Server Network Administrator Reference Volume 3: Network Administrator
Tasks.
ΓòÉΓòÉΓòÉ 5.9. Operator Privileges ΓòÉΓòÉΓòÉ
A network administrator can give a user operator privileges if the user needs
to perform certain administrative tasks, such as print management or group
management. Four types of operator privilege are available:
o Accounts
o Print
o Comm
o Server
A user can be given more than one type of operator privilege. Users with
operator privileges are still bound by access control and other security
measures not associated with their privileges.
ΓòÉΓòÉΓòÉ 5.9.1. Accounts Operator Privilege ΓòÉΓòÉΓòÉ
A user with accounts operator privilege can manage users and groups within the
domain. The user can add, modify, or delete users and groups but cannot create
or modify user accounts with administrative or operator privilege. The user
with accounts operator privilege can manage user and group accounts from UPM or
from the command line.
ΓòÉΓòÉΓòÉ 5.9.2. Print Operator Privilege ΓòÉΓòÉΓòÉ
A user with print operator privilege can manage print queues and print jobs.
The user can create, modify, or delete print jobs or queues on servers within
the domain and can share print queues and manage remote jobs on shared queues.
The user with print operator privilege can manage queues and print jobs from
either Print Manager or the command line.
ΓòÉΓòÉΓòÉ 5.9.3. Comm Operator Privilege ΓòÉΓòÉΓòÉ
A user with comm operator privilege can manage serial devices. The user can
share serial devices and manage remote jobs on shared serial devices from the
command line.
ΓòÉΓòÉΓòÉ 5.9.4. Server Operator Privilege ΓòÉΓòÉΓòÉ
A user with server operator privilege can manage aliases and other shared
resources and view network status within the domain. The user can create,
modify, or delete aliases or other shared resources. The user with server
operator privilege can manage shared resources and view network status from the
command line.
Operator privileges can be defined from the command-line interface. For more
information, see the LAN Server Network Administrator Reference Volume 3:
Network Administrator Tasks and the online LAN Server Commands and Utilities.
ΓòÉΓòÉΓòÉ 5.10. Supported Functions ΓòÉΓòÉΓòÉ
The following sections provide a brief overview of the various functions and
installable components of OS/2 LAN Server, OS/2 LAN Requester, and DOS LAN
Services. For information on how to use and manage these functions, see the LAN
Server Network Administrator Reference Volume 3: Network Administrator Tasks.
The supported functions are:
o User Profile Management (UPM)
o First Failure Support Technology/2* (FAST.*)
o Graphical User Interface (GUI)
o Network DDE and Clipboard
o Migration Import Utility
o Network Messaging
o Loop-Back Driver
o LAN Server Applications Development Toolkit
o Virtual DOS LAN API Support
o OS/2 LAN Services Installation/Configuration Program
o 386 High Performance File System (386 HPFS)
o Local Security for the 386 HPFS
o Fault Tolerance for Hard Disk
o IBM Multi-Protocol Transport Services - AnyNet for OS/2
o Network Services
ΓòÉΓòÉΓòÉ 5.10.1. User Profile Management ΓòÉΓòÉΓòÉ
This access-control function provides validation for a user ID and password at
logon. For a more detailed description, see User Profile Management.
UPM is automatically installed if you follow the Easy installation path during
an initial server or requester installation. If the Communications Manager/2
or DATABASE 2 OS/2 program is already installed, UPM is reinstalled
automatically only if the installed code is at a lower level. To install UPM
during a Tailored installation, select User Profile Management in the Install
and Remove window.
ΓòÉΓòÉΓòÉ 5.10.2. First Failure Support Technology/2 ΓòÉΓòÉΓòÉ
First Failure Support Technology/2 (FFST/2) provides the following reliability,
availability, and serviceability (RAS) functions for use by OS/2 LAN Server,
OS/2 LAN Requester, Communications Manager/2, DATABASE 2 OS/2, and other
applications that are written to make use of FFST/2:
o Error logging
Constructs a symptom record that uniquely identifies the detected error and
places the record in the OS/2 error log (SYSLOG).
o Message logging
Retrieves and logs application-specific messages from national language
support (NLS) message files.
o Selective dump capability
Collects and dumps storage areas, files, or both, selected by the calling
application.
o Generic alert build and routing capability
Creates and forwards a software generic alert describing the detected error
condition. If error logging is selected, key segments from the symptom
record are included in the alert.
o Presentation Manager message console facility
Maintains a scrollable copy of all messages logged or displayed by FFST/2.
Messages from any type of process (including detached processes) are
displayed. This function allows a user to quickly obtain a record of
recently displayed or logged messages.
FFST/2 can be installed on server and requester workstations. You must select
it if you want to install the Generic Alerter service. Also, OS/2
Serviceability and Diagnostics Aids must have been selected during OS/2
installation.
To install FFST/2 during LAN Services installation and configuration, select
First Failure Support Technology/2 in the Install and Remove window.
During configuration, you can do the following:
o Specify if you want FFST/2 to be autostarted and, if so, where you want the
alerts routed.
o Specify if you want messages to be displayed on the FFST/2 message console.
o Specify the maximum system and application dumps, the system and application
dump paths, and the application message log.
o Provide the following vital product data: workstation type, serial number,
and ID of the workstation.
Note:
This data enables the host to identify error information about the
workstation.
ΓòÉΓòÉΓòÉ 5.10.3. LAN Server Administration GUI ΓòÉΓòÉΓòÉ
The LAN Server Administration graphical user interface (GUI), which can be
installed on both servers and requesters, is a menu system that provides access
to many system functions. In addition, the LAN Server Administration GUI
provides online help windows. Depending on your needs, you can consider not
installing the GUI; it is selectable.
The LAN Server Administration GUI is automatically installed when you follow
the Easy or Tailored installation path during an initial server or requester
installation.
The XPG4.DLL and LOCALE.DLL device drivers are installed in the \IBMLAN\NETLIB
directory when the LAN Server Administration GUI is installed. The LOCPATH
environment variable is set to the \IBMLAN\NETLIB directory. The LANG
environment variable defaults to EN_US, but takes the value specified by the
IBMLANOP.PRF file for other countries.
ΓòÉΓòÉΓòÉ 5.10.4. Network DDE and Clipboard ΓòÉΓòÉΓòÉ
Network DDE and Clipboard allows application programs or users to copy text
from one workstation to another through the clipboard. You can also create
dynamic data links between different workstations. Dynamic data links are
copies of data that are automatically updated across the network when changes
are made to the original data. To use Network DDE and Clipboard, you must use
applications that support the clipboard and dynamic data linking functions. You
can use Network DDE and Clipboard with DOS LAN Services if you are using the
Windows interface.
OS/2 provides many applications (stored in your Productivity folder) that
support clipboard copy and paste functions. You can use Network DDE and
Clipboard to do simple copy and paste tasks between workstations. The simple
copy function can be useful when you want to share information with others on
your network but do not have time to distribute the information manually.
For example, if you have several meetings that everyone must attend scheduled
for a particular day, you can copy your schedule from your Daily Planner to
your clipboard and send a message to other users that tells them to copy your
clipboard for the meeting schedule. Other users can copy the information from
your clipboard and paste it into their own Daily Planner. Everyone now knows
when the meetings are scheduled, and all you had to do was copy the information
to your clipboard and send out a simple note using Network Messaging.
To create dynamic data links, you must be using applications that support
linking. (Most of them have a Paste Link menu option in their Edit menu.) If
linking is not supported by an application, you can copy information, but it
will not be updated automatically if it is changed. Links can be created
either through the clipboard or through published resources.
A published resource is a file created by using an application and Network DDE
and Clipboard. This file contains data that can be either copied or used to
create a link. When you link to a published resource, the link points to the
data that was used to create the published resource. You cannot change the
published resource. However, the data to which the link points can be changed
and the changes are updated across the network for all users linked to that
data.
For details on using Network DDE and Clipboard, refer to the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks or IBM OS/2 LAN
Server Version 4.0 Up and Running!.
ΓòÉΓòÉΓòÉ 5.10.5. Migration Import Utility ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: The migration import Γöé
Γöé utility is not available to DBCS users. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The migration import utility provides the support to migrate a domain control
database (DCDB) of a PC LAN Program Version 1.3 (or later) domain controller.
Note:
The DCDB contains the definitions for network resources. The contents
of the DCDB are described in detail in Domain Controller.
The migration import utility uses the export and import functions to move and
process the domain definitions from the current domain to the new one.
To install the migration import utility during LAN Services installation and
configuration, select Migration Import Utility in the Install and Remove
window.
Note:
This item can be selected only if you are installing a domain
controller.
The LAN Services installation/configuration program installs the migration
import utility but does not run it. The migration import utility must be run to
restore a DCDB saved by the migration export utility. For detailed information
about migration, see Migration of Data and Migrating PCLP to an IBM OS/2 LAN
Server Environment.
ΓòÉΓòÉΓòÉ 5.10.6. Network Messaging ΓòÉΓòÉΓòÉ
Network messaging enables users to perform the following functions:
o Send and receive messages
o View, reply to, and delete messages
o Save messages in the log file
o Add and delete messaging names
o Forward messages to another requester
You must be logged on to send and receive messages using network messaging.
The network messaging function uses the Messenger service to accomplish these
tasks. When a new message arrives on your workstation, the Messenger service
adds it to the list of messages waiting to be read and, if you have configured
the Pop-up option, informs you of its arrival through a pop-up window.
Messages can be sent to users who are logged on to workstations that are
started and running the Messenger service. If you have defined users and groups
on the domain, they will be listed as possible recipients of your messages in
the List Users and List Groups windows when you send a new message. All
messages you receive are saved in a message log on your workstation until you
delete them.
ΓòÉΓòÉΓòÉ 5.10.7. Loop-Back Driver ΓòÉΓòÉΓòÉ
The loop-back driver enables a single server to emulate network operation
without actually being connected to a network; that is, no network adapter card
needs to be installed in the server. The loop-back driver sends requests to
the local machine as if it were remote. This process simulates what would
normally occur on a real network.
For these reasons, the loop-back driver is suitable for training, testing, or
planning purposes where a simulated LAN environment is needed. The loop-back
driver does not provide true LAN connectivity or function.
Note:
You cannot use the loop-back driver to interact with DOS LAN Services
running in a DOS session on the server.
If you installed the loop-back driver and did not select any configured NetBIOS
adapters for use with the LAN Server product during LAN Services installation
and configuration, the loop-back driver is automatically enabled to start.
Warning:
Do not select to install the loop-back driver and also select one or
more configured NetBIOS adapters for use with the LAN Server product.
If you do so, unpredictable network errors can occur because the NetBIOS
protocol attempts to duplicate activity that the loop-back driver is
performing. If you decide to install NetBIOS adapters and the loop-back
driver is running, disable the loop-back driver first.
ΓòÉΓòÉΓòÉ 5.10.8. LAN Server Applications Development Toolkit ΓòÉΓòÉΓòÉ
The LAN Server Applications Development Toolkit enables application programs to
interact with network operations and resources. The toolkit provides access to
network functions through a well-defined interface for high-level languages.
The LAN Server Applications Development Toolkit includes the application
programming interface (API) reference, sample programs, and the API structures
(.H and .LIB files). If installed as a standalone product, the LAN Server
Applications Development Toolkit also includes the online LAN Server
Programming Guide and Reference. The toolkit is selectable for OS/2 clients,
additional servers, and domain controllers.
The API structures, which are the data structures required to write an
application that uses the network, are automatically installed if you follow
the Easy installation path during an initial server installation. If selected
in the Install and Remove window, they are installed during a Tailored server
or requester installation.
All OS/2 LAN API functions can be run on a local server. Many functions can
also be run on a remote server or a local requester. Certain functions require
administrator or operator privilege or are restricted to only running locally
or against a server. Most of the OS/2 LAN API functions are available to DOS
LAN Services users.
For more information, refer to the LAN Server Programming Guide and Reference.
Thirty-four categories of API functions perform various LAN Server network
tasks. For example, the Serial Device category contains all functions used to
control shared serial devices. The following is a list of the function
categories, including a brief description of each.
Function Category Task
Access Permission Examines and modifies user or group access
control lists for server resources.
Alert Provides a system for notifying network
service programs and applications of network
events.
Alias Manages alias definitions.
Application Manages public and private application
definitions.
Auditing Controls the audit log file, which contains
an audit log of operations that occur on a
server.
Configuration Retrieves network configuration information
from the IBMLAN.INI file.
Connection Lists all connections made to a server by a
requester or all connections made to the
shared resource of a server.
DLS-Specific APIs Task
Error Logging Controls the error log file.
File Provides a system for monitoring the files,
device, and pipe resources that are opened
on a server, and for closing these resources
if necessary.
Group Controls user groups in the user accounts
database.
Handle Obtains and sets information on a per-handle
basis.
Mailslot Provides one-way interprocess communication
locally and between networked machines.
Message Sends, logs, and forwards messages.
Named Pipe Controls interprocess communication for
named pipes. The functions in this category
are provided by the base operating system
and supported by OS/2 LAN Server across the
network.
NetBIOS Provides direct access to network device
drivers, using the "submit" interface. An
alternative IBM NetBIOS API is documented in
the IBM LAN Technical Reference.
Print Destination Controls the printers that receive spooled
print jobs on a server for DOS requesters
and 16-bit application. See also the spooler
category.
Print Job Controls the print jobs in a printer queue
on a server for DOS requesters and 16-bit
application. See also the spooler category.
Printer Queue Controls the printer queues on a server for
DOS requesters and 16-bit application. See
also the spooler category.
Remote Utility Enables applications to copy and move remote
files, remotely run a program, and access
the time-of-day information on a remote
server.
Requester Controls the operation of requesters.
Serial Device Controls shared serial devices and their
associated queues.
Server Enumerates and manages local and remote
servers.
Services Starts and controls network service
programs.
Session Controls network sessions established
between requesters and servers.
Share Controls shared resources.
Spooler Provides OS/2 applications access to print
spooler operations. The functions in this
category are provided by the base operating
system and supported by OS/2 LAN Server
across the network.
Statistics Retrieves and clears the operating
statistics for requesters and servers.
Use Examines or controls connections (uses)
between requesters and servers.
User Controls a user's account in the user
accounts database.
User Profile Management (UPM) Provides log-on and log-off services.
ΓòÉΓòÉΓòÉ 5.10.9. Virtual DOS LAN API Support ΓòÉΓòÉΓòÉ
The LAN Server product provides Virtual DOS LAN API support to enable DOS
applications that are running in the virtual DOS machine environment of OS/2
2.1 to call the following APIs without having to load DOS LAN Services:
o OS/2 LAN APIs
o PC LAN Program Version 1.3 compatibility APIs
o Specified DOS function calls
The virtual DOS machine environment supports Windows (running in a specific DOS
session), WIN-OS/2*, emulated DOS, and VM DOS startup (in a specific DOS
session).
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: For DBCS users, the virtual Γöé
Γöé DOS machine environment supports WIN-OS/2 and emulated DOS. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The supported OS/2 LAN APIs are listed in LAN Server Applications Development
Toolkit. For more information, refer to the LAN Server Programming Guide and
Reference.
PCLP Compatibility APIs lists the PC LAN Program Version 1.3 compatibility
APIs.
Note:
The hex name and interrupt levels are added before the APIs.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 2. PCLP Compatibility APIs Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé API Γöé HEX NAME Γöé INTERRUPT LEVEL Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Installation check Γöé 0000H Γöé (INT 2AH) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Get user ID and logon Γöé 7802H Γöé (INT 2AH) Γöé
Γöé status Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS LAN Services Γöé B800H Γöé (INT 2FH) Γöé
Γöé installation check Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Network version check Γöé B809H Γöé (INT 2FH) Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
For more information, refer to the LAN Server Programming Guide and Reference.
Supported DOS Function Calls lists the supported DOS function calls.
Note:
The hex name and interrupt levels are added before the APIs.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 3. Supported DOS Function Calls Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé API Γöé HEX NAME Γöé INTERRUPT LEVEL Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Get machine name Γöé 5E00H Γöé (INT 21H) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Get redirection list Γöé 5F02H Γöé (INT 21H) Γöé
Γöé entry Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Redirect device Γöé 5F03H Γöé (INT 21H) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Cancel redirection Γöé 5F04H Γöé (INT 21H) Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
For more information, refer to the DOS 5.0 Technical Reference.
The APIs supported locally by Virtual DOS LAN API support are limited to the
ones normally provided by DOS LAN Services. They are:
o DosDeleteMailslot
o DosMailslotInfo
o DosMakeMailslot
o DosPeekMailslot
o DosReadMailslot
o DosWriteMailslot
o NetMessageBufferSend
o NetRemoteCopy
o NetRemoteMove
o NetServiceControl
o NetServiceEnum
o NetUseAdd
o NetUseDel
o NetUseEnum
o NetUseGetInfo
o NetWkstaGetInfo
o NetWkstaSetInfo
Note:
All other LAN Server APIs are supported only when run remotely.
For the APIs to work in a virtual DOS machine environment, Virtual DOS LAN API
support must be installed, and OS/2 LAN Requester must be started. Note that
the command-line interface and graphical user interface of DOS LAN Services
running from a virtual DOS machine are not supported.
To install Virtual DOS LAN API support during LAN Services installation and
configuration, select Virtual DOS LAN API Support in the Install and Remove
window.
ΓòÉΓòÉΓòÉ 5.10.10. OS/2 LAN Services Installation/Configuration Program ΓòÉΓòÉΓòÉ
If you select OS/2 LAN Services Installation/Configuration Program in the
Install and Remove window during LAN Services installation and configuration,
the LAN Services installation/configuration program is installed on your
workstation. If the workstation has more than one hard disk, the program is
installed on the hard disk you specified for LAN Services installation in the
Hard Disk window.
A different program is installed during the installation and configuration of
OS/2 LAN Server than during the installation and configuration of OS/2 LAN
Requester. If installed, the LAN Services installation/configuration program
can be run from the hard disk when you want to reinstall or reconfigure OS/2
LAN Server or OS/2 LAN Requester at a later time. To reinstall from a CD-ROM,
the reinstallation must be started from the CD-ROM. To do this, open the LAN
Services folder on the OS/2 desktop, and select OS/2 LAN Services
Installation/Configuration.
Once the LAN Server product is installed, the IBM LAN Server 4.0 Performance
Tuning Assistant is available to improve performance and tune your
configuration.
ΓòÉΓòÉΓòÉ 5.10.11. 386 High Performance File System (386 HPFS) ΓòÉΓòÉΓòÉ
The 386 high performance file system (386 HPFS) provides extremely fast access
to very large disk volumes and optimizes performance in a server environment in
which many files are open simultaneously. The 386 HPFS is a network-optimized
file system. It supports the HPFS file system; that is, existing HPFS
partitions need not be reformatted when the 386 HPFS is installed. Note that
shared network file systems are expected but not required to be on HPFS
volumes. Non-HPFS resources, such as the FAT file system, remain accessible on
a 386-HPFS server.
The \IBM386FS\HPFS386.INI file defines the operation of the file system, and,
therefore, should be on an accessible drive (the startup drive) at system
startup. If the file cannot be read, the default parameters for the file
system are used.
The 386 HPFS is available only with LAN Server-Advanced. The file system is
automatically installed when you follow the Easy or Tailored path during an
initial installation.
Warning:
If you install the 386 HPFS and you make your startup partition
386 HPFS, you need to create an 386-HPFS startup diskette to use in the
event the hard disk fails to start the workstation in the future.
Otherwise, you might have to reformat the hard disk and reinstall the
base operating system and the LAN Server product. You can create the
386-HPFS startup diskette during the LAN Server installation. If you do
not create the startup diskette during the LAN Server installation, you
should create the startup diskette immediately after completing
installation. For more information, see Creating 386-HPFS Startup
Diskettes.
ΓòÉΓòÉΓòÉ 5.10.11.1. Features ΓòÉΓòÉΓòÉ
In addition to taking advantage of the Intel** 80386 instruction set and
addressing modes, the 386 HPFS provides a number of additional features not
found in the OS/2 version of HPFS.
Features marked with an asterisk (*) in the following list are exclusive to the
386 HPFS. All other features are common to the OS/2 and the Advanced server
version of HPFS:
o * 32-bit assembler code
o * Exploitation of Pentium-specific features
o * Server component for processing network requests
o * Access and audit control in the file system
o * Local security
o * Selective caching of large files
o * Support for cache size greater than 2MB
o * Utilization of memory above 16MB
o * Support for adapter card memory above 16MB
o * Support for directory limits
o * Support for alerts for directory limits
o * Support for fault-tolerant, enhanced disk drivers
o Extended attribute support
o File names up to 254 characters
o Strategic allocation of directory structures
o Highly contiguous file allocation
o Caching of directories, data, and file system structures
o Use of file-access-based heuristics
o Multithreaded I/O
o Read-ahead and lazy-write processes
o Optional write-through
o Ability to be used on the startup partition
o Enhanced recoverability
o Support for hard disks greater than 4 gigabytes (maximum 64GB)
o Support for files up to 2GB
o Hotfix defect mapping
Note:
A bad disk sector is hotfixed when the 386 HPFS allocates a new
sector for it from a buffer of sectors available for hotfixes. Future
requests are rerouted to the new, good sector.
ΓòÉΓòÉΓòÉ 5.10.11.2. Directory Limits and Alerts ΓòÉΓòÉΓòÉ
Directory limits allow disk space to be managed at the directory level, in much
the same manner as the space on a hard disk is managed. By setting a limit on
a particular directory, the administrator enforces a maximum size for the
directory. Directory limits are managed like a logical drive; they cannot be
overridden except by administrators. In addition to enforcing a maximum size,
directory limits have alerting capabilities. Administrators, or other specified
users, can be notified when a directory is full. Users can also be notified
when a directory size crosses the set threshold. Thresholds are set by
administrators.
For finer granularity in monitoring directory sizes, incremental thresholds are
provided. To avoid "alert storms," delay windows are provided so that
administrators can filter out redundant alerts. The following information
describes the two kinds of directory limits: threshold alerts and directory
full alerts.
ΓòÉΓòÉΓòÉ 5.10.11.2.1. Threshold Alerts ΓòÉΓòÉΓòÉ
Threshold alerts are posted when the size of a directory increases beyond a
threshold value. Directory full alerts are posted when a directory tree is
full; that is, when a request for disk space cannot be satisfied because of
lack of space. Associated with a threshold are incremental thresholds that
function as mini-thresholds.
There is only one threshold with a set of incremental limits, or
mini-thresholds, defined between the threshold and the actual limit. The
incremental limits are spaced apart at equal intervals. As the directory size
increases, it crosses the threshold and generates an alert. A threshold delay
defines the minimum amount of time that must elapse before another crossing of
the same or lesser threshold will again generate an alert.
The threshold delay is overridden when the directory size crosses a higher
threshold. Every time an alert is generated, the threshold delay window is
reset to 0. Note that threshold alerts cannot be posted unless a threshold is
set. For procedural information on setting threshold alerts, refer to the LAN
Server Network Administrator Reference Volume 3: Network Administrator Tasks.
ΓòÉΓòÉΓòÉ 5.10.11.2.2. Directory Full Alerts ΓòÉΓòÉΓòÉ
Since a user cannot cross the directory limit, alerts are only generated when a
directory full condition is encountered. A directory full condition occurs
when a write request is denied because of insufficient space within the
directory tree. Like threshold alerts, directory full alerts have a delay
window that allows administrators to control alert notification. Posting of
directory full alerts depends on parameters found in the HPFS386.INI file. For
procedural information on setting directory full alerts, refer to the LAN
Server Network Administrator Reference Volume 3: Network Administrator Tasks.
Warning:
To use directory limits and alerts, you must install fixes to OS/2. For
details, refer to the README.DOC file in the \IBMLAN subdirectory.
ΓòÉΓòÉΓòÉ 5.10.11.3. File-System Caching ΓòÉΓòÉΓòÉ
The high performance file system manages a cache of memory divided into blocks
of 2KB. Data that is read from and written to the disk is transferred through
this cache so that the data can be used in future read requests.
In most cases, when a write request is received, it is not necessary to write
the data immediately to disk. The 386 HPFS takes this data and copies it into
its cache without actually performing the costly write-to-disk operation. Once
the data is in the cache, it is written to disk as a background activity during
disk-idle time.
This operation is called lazy write. It allows a typical write operation
submitted by a user process to occur with a much faster response time than in
file systems where all write operations are synchronous. In addition, because
lazy-write operations are performed during idle time, incoming requests need
not wait for large, synchronous write operations to be completed, thus
optimizing overall server throughput and response time for all requesting
processes. It is recommended that if you enable lazy write, you also install
uninterruptible power supply (UPS) hardware.
If you follow the Tailored installation path, you have the opportunity to
configure:
o 386-HPFS cache size (the amount of memory to be used by the workstation for
file-system buffer storage)
o Location of the cache (above/below 16MB)
o Lazy-write options (maximum cache age and minimum buffer-idle time). Lazy
write is optional.
o 386-HPFS heap size (the amount of memory to be used for dynamic memory
allocation)
If you follow the Easy installation path, IBM-supplied default values are used.
For information on how the values of these parameters affect performance, refer
to the LAN Server Network Administrator Reference Volume 2: Performance Tuning.
ΓòÉΓòÉΓòÉ 5.10.12. Local Security for the 386 HPFS ΓòÉΓòÉΓòÉ
The Local Security for the 386-HPFS feature allows the network administrator to
restrict access to local files on the 386-HPFS partitions of a server. Servers
with Local Security installed protect their 386-HPFS partitions from local
access in addition to the standard remote access control protection. In
addition, Local Security restricts calls to APIs based on user authority.
Note:
If the Local Security for the 386-HPFS option is installed, the
command-line interface and the graphical user interface will become more
restrictive for users at the server. For detailed information, see the
LAN Server Network Administrator Reference Volume 3: Network
Administrator Tasks.
The Local Security for the 386-HPFS option is available only with LAN
Server-Advanced. To install Local Security for the 386 HPFS during LAN
Services installation and configuration, you must ensure that 386 HPFS is
selected in the Install and Remove window (installed by default); then select
Local Security for 386 HPFS.
ΓòÉΓòÉΓòÉ 5.10.13. Fault Tolerance for Hard Disk ΓòÉΓòÉΓòÉ
The Fault Tolerance for Hard-Disk feature (hereafter called Fault Tolerance)
provides a computer system with the capability to handle disk hardware problems
without interrupting the system's performance or losing system data.
Fault Tolerance allows drive mirroring and duplexing as well as error logging,
alerting, and monitoring of disk activity.
Drive mirroring and drive duplexing provide duplication of data stored on disk,
thereby improving data integrity. Drive mirroring is the duplication of a
single logical drive or volume on two partitions that do not reside on the same
physical disk. If the data on the two partitions differs, the drives are
synchronized through drive verification, which ensures that the mirrored or
duplexed drives are identical.
Drive duplexing is a special type of drive mirroring, with the additional
advantage that the two disks on which the two partitions reside are controlled
by two different disk controllers. Drive duplexing provides protection against
errors caused by a faulty controller and improves read performance. Each
mirrored or duplexed pair of partitions must reside on disks handled by the
same disk device driver.
Fault Tolerance works together with a compatible disk device driver and the
file systems to detect and correct disk faults. When a fault is detected, it
is logged. Errors and critical errors resulting from a fault can also cause an
alert. Two administrator utilities, FTSETUP and FTADMIN, are provided to set up
Fault Tolerance, view the log, and correct errors.
Drive fault monitoring is possible regardless of the number of disks in the
system and whether they are mirrored or duplexed. If no disks are mirrored, the
number of different error log entries and alerts that can be produced is
limited.
If you plan to install Fault Tolerance, make sure you have sufficient disk
space. Refer to Disk Requirements for Fault Tolerance.
The Fault Tolerance feature is available only with LAN Server-Advanced. To
install Fault Tolerance during LAN Services installation and configuration, you
must ensure that 386 HPFS is selected in the Install and Remove window
(installed by default); then select Fault Tolerance for Hard Disk. For detailed
information on administering Fault Tolerance, refer to the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
A server with Fault Tolerance installed can use the FTREMOTE utility to
administer FTSETUP and FTADMIN for a remote server. A network administrator is
not required to be at the remote server. A history of commands and actions
taken by the FTREMOTE utility, as well as any errors encountered during
execution of these commands, are logged to a history file. The configuration
of the computer upon completion of the commands is logged to a status file.
For more information, refer to the LAN Server Network Administrator Reference
Volume 3: Network Administrator Tasks and the LAN CID Utility Guide. Even if
Fault Tolerance is installed, hard disks should be backed up regularly. Fault
Tolerance protects against a single disk failure, but not against multiple
failures.
ΓòÉΓòÉΓòÉ 5.10.14. IBM Multi-Protocol Transport Services - AnyNet for OS/2 ΓòÉΓòÉΓòÉ
The OS/2 transport services included in LAN Server 4.0 introduce a transport
independent programming framework based on the Multi-Protocol Transport
Services (MPTS) architecture for distributed OS/2 applications. This transport
supports sockets programs written to the BSD 4.3 sockets interface standard and
enables them to communicate using any protocol implemented to the transport
framework. LAN Server 4.0 includes the TCP/IP and NetBIOS protocol stacks
implemented in this fashion.
The OS/2 transport also includes access to NetBIOS through traditional NetBIOS
programming interfaces.
Additionally, the OS/2 transport included in LAN Server 4.0 provides an
improved implementation of NetBIOS for TCP/IP called TCPBEUI. Previously, the
TCP/IP protocol was accessible from NetBIOS applications but the implementation
was inefficient because of transitions through the code paths between the
kernel level and the application level. TCPBEUI provides a kernel level NetBIOS
programming interface that accesses the TCP/IP protocol stack at the same
kernel level. With this implementation, TCPBEUI provides a more efficient
NetBIOS access to TCP/IP than NetBIOS. For more information on how NetBIOS
relates to TCP/IP, refer to NetBIOS Over TCP/IP. For details on IBM
Multi-Protocol Transport Services - AnyNet for OS/2, refer to MPTS - AnyNet for
OS/2: Configuration Guide.
ΓòÉΓòÉΓòÉ 5.11. Network Services ΓòÉΓòÉΓòÉ
Network services are the programs that perform primary functions of OS/2 LAN
Server or OS/2 LAN Requester and related software. The LAN Server product
provides the following network services:
o Alerter
o DCDB Replicator
o Generic Alerter
o LSserver
o Messenger
o Netlogon
o Netrun
o Peer (Requester only)
o Remote Initial Program Load (remote IPL)
o Replicator
o Requester
o Server
o Timesource
o Uninterruptible Power Supply (UPM)
ΓòÉΓòÉΓòÉ 5.11.1. Alerter Service ΓòÉΓòÉΓòÉ
The Alerter service is a server service that generates alert
messages whenever a system event occurs. You can set up
thresholds for various server parameters in the IBMLAN.INI file to
determine when an alert is generated. You can also specify in the
IBMLAN.INI file where the alerts should be sent.
The Alerter service is automatically installed on servers during LAN Services
installation and configuration. To configure the Alerter service to start
automatically, select Alerter and On in the Server Services window during
installation and configuration.
If the Alerter service has not been configured to start automatically, it can
be started from the Network Services window on the LAN Server Administration
GUI or from the command-line interface with the NET START command. (See LAN
Server Commands and Utilities and the LAN Server Network Administrator
Reference Volume 3: Network Administrator Tasks.)
ΓòÉΓòÉΓòÉ 5.11.2. DCDB Replicator Service ΓòÉΓòÉΓòÉ
The DCDB Replicator service replicates the \IBMLAN\DCDB
subdirectory (except remote IPL images) from a domain controller
to other servers defined as backup domain controllers. When used
with the Netlogon service, the DCDB Replicator service ensures
that users can always log on to a domain, even if the domain
controller fails or is busy. The DCDB Replicator service is
separate from the Replicator service, and both can reside and
function independently of each other on the domain controller or
backup domain controllers.
The DCDB Replicator service is automatically installed on domain controllers
and backup domain controllers during LAN Services installation and
configuration. The LAN Services installation/configuration program default is
for the DCDB Replicator service to start automatically on a backup domain
controller. If you do not want to start the service automatically, select DCDB
Replicator and Off in the Server Services window during installation and
configuration.
If the DCDB Replicator service has not been configured to start automatically,
it can be started from the Network Services window on the LAN Server
Administration GUI or from the command-line interface with the NET START
command. (See LAN Server Commands and Utilities and the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.)
ΓòÉΓòÉΓòÉ 5.11.3. Generic Alerter Service ΓòÉΓòÉΓòÉ
The Generic Alerter service enables the server to build and send
Systems Network Architecture (SNA) alerts. The Generic Alerter
service is notified by the Alerter service (see Alerter Service)
when certain LAN alerts occur. The Generic Alerter service then
uses the FFST/2 program to build software generic alerts that
conform to the SNA format and sends them either to the NetView
program or to IBM LAN Network Manager using the FFST/2 router. LAN
alerts are documented in the IBM OS/2 LAN Server Version 4.0
Problem Determination Guide.
Note:
If a server is configured to forward generic alerts to IBM LAN Network
Manager, IEEE 802.2 must be installed on the server.
To install the Generic Alerter service during LAN Services installation and
configuration, select Generic Alerter Service in the Install and Remove window.
Note:
You must select First Failure Support Technology/2 first.
To configure the Generic Alerter service to start automatically, select Generic
Alerter and On in the Server Services window during installation and
configuration. You can configure the Generic Alerter service to start
automatically only if FFST/2 has been selected to autostart as well.
If the Generic Alerter service is not configured to start automatically, it can
be started from the Network Services window on the LAN Server Administration
GUI or from the command-line interface with the NET START command. (See LAN
Server Commands and Utilities and the LAN Server Network Administrator
Reference Volume 3: Network Administrator Tasks.)
ΓòÉΓòÉΓòÉ 5.11.4. LSserver ΓòÉΓòÉΓòÉ
The LSserver service provides DOS LAN Services support and logical
server functions. The logical server supports remote requests
from requesters for activities such as spooling, querying users,
logon, and logoff. The LSserver service is started and stopped by
the Server service.
ΓòÉΓòÉΓòÉ 5.11.5. Messenger Service ΓòÉΓòÉΓòÉ
The Messenger service is a requester service that enables users to
perform the following actions:
o Send and receive messages
o Save messages in the log file
o Add and delete messaging names
o Forward messages to another requester
Messenger service is automatically installed on servers and requesters during
LAN Services installation and configuration. To configure the Messenger Service
to start automatically, select Messenger and On in either the Server Services
window or Requester Services window during installation and configuration.
If the Messenger Service has not been configured to start automatically, you
can start it in one of the following ways:
o From the Network Services window on the LAN Server Administration graphical
user interface (GUI). (See the LAN Server Network Administrator Reference
Volume 3: Network Administrator Tasks.)
o From the command-line interface with the NET START command. (See LAN Server
Commands and Utilities and the LAN Server Network Administrator Reference
Volume 3: Network Administrator Tasks.)
ΓòÉΓòÉΓòÉ 5.11.6. Netlogon Service ΓòÉΓòÉΓòÉ
The Netlogon service allows servers in a domain to maintain
identical copies of the user and group definitions file (NET.ACC),
which is maintained on the domain controller, by receiving the
changes that occur to the database. The Netlogon service also
enables domain controllers and additional servers that function as
a domain controller backup to satisfy the user validation step of
logon requests.
The Netlogon service is automatically installed on servers during LAN Services
installation and configuration. The LAN Services installation/configuration
program default is for the service to start automatically. If you do not want
to start the Netlogon service automatically, select Netlogon and Off in the
Server Services window during installation and configuration.
If the Netlogon service has not been configured to start automatically, it can
be started from the Network Services window on the LAN Server Administration
GUI or from the command-line interface with the NET START command. (See LAN
Server Commands and Utilities and the LAN Server Network Administrator
Reference Volume 3: Network Administrator Tasks.)
ΓòÉΓòÉΓòÉ 5.11.7. Netrun Service ΓòÉΓòÉΓòÉ
The Netrun service runs on a server and handles requests for
remote execution of programs. The purpose of using the Netrun
service is to use the server's resources to run a program.
The Netrun service is automatically installed on servers during LAN Services
installation and configuration. To configure the Netrun service to start
automatically, select Netrun and On in the Server Services window during
installation and configuration.
If the Netrun service has not been configured to start automatically, it can be
started from the Network Services window on the LAN Server Administration GUI
or from the command-line interface with the NET START command. (See LAN Server
Commands and Utilities and the LAN Server Network Administrator Reference
Volume 3: Network Administrator Tasks.)
ΓòÉΓòÉΓòÉ 5.11.8. Peer Service ΓòÉΓòÉΓòÉ
The Peer service gives a requester some of the capabilities of a
server. A requester with the Peer service installed is called a
peer workstation. Just as a network administrator creates shared
resources for a server, the owner of a requester with the Peer
service installed creates shared resources for a peer workstation.
The Peer service allows the owner of the requester to share
resources (such as directories, one print queue, and one
communication-device queue) with other users on the network.
Only one user at a time is allowed to connect to the peer workstation. In
addition, the peer workstation owner can always connect to the peer workstation
if the Peer service uses user-level security. (See Types of Security.) This
differs from an OS/2 LAN Server machine, which allows sessions with multiple
requesters. The peer workstation's interprocess communication resource can,
however, be used by multiple users.
Peer workstations are not started from the domain. They are administered by
the owner of the peer workstation, rather than the network administrator, who
has no control over the resources at a peer workstation.
Because peer workstations are not part of the domain, they can be administered
only from the command line and do not support alias names.
To install the Peer service during LAN Services installation and configuration,
select Peer service in the Install and Remove window. To configure the Peer
service to start automatically, select Peer service and On in the Requester
Services window during installation and configuration. If the Peer service has
not been configured to start automatically, it can be started from the Network
Services window on the LAN Server Administration GUI or from the command-line
interface with the NET START command. (See LAN Server Commands and Utilities
and the LAN Server Network Administrator Reference Volume 3: Network
Administrator Tasks.)
ΓòÉΓòÉΓòÉ 5.11.8.1. Types of Security ΓòÉΓòÉΓòÉ
During configuration, you can specify one of the following types of security to
be used by the Peer service:
o User-level security (identical to LAN Server security)
Access to shared resources is controlled by user ID and password
identification. User-level security allows the owner of the peer workstation
to define specific access rights to a resource for an individual owner or a
group of users.
o Share-level security
Access to resources is controlled by identification of a password valid for
the entire shared resource. Share-level security allows the owner of the
peer workstation to specify both the password and the permissions associated
with a shared resource.
ΓòÉΓòÉΓòÉ 5.11.9. Remote Initial Program Load Service ΓòÉΓòÉΓòÉ
The remote initial program load (remote IPL) server function
supports both DOS and OS/2 2.0 or higher requesters. Remote IPL
supports requesters without local media (CD-ROM, hard disk, or
diskette drives). An OS/2 remote IPL requester can be enabled to
switch between DOS and OS/2 operating systems. The remote IPL
server function also allows you to share the same resource
multiple times with different passwords that give different levels
of privilege.
To install the Remote IPL service (also called the Remoteboot service), select
DOS Remote IPL Service, OS/2 Remote IPL Service, or both in the Install and
Remove window during LAN Services installation and configuration. Note that
when you install (or reinstall) the Remote IPL service, you must run the
RIPLINST (OS/2 only) and GETRPL (DOS and OS/2) utilities after restarting the
server upon completion of the LAN Services installation/configuration program.
For more information about these utilities, refer to the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
The Remote IPL service can be run only on servers with the Server service
started. The server must have at least one network adapter card configured for
the IEEE 802.2 protocol. The machine requesting remote IPL must be a requester
workstation equipped with an adapter that supports remote IPL. Remote IPL
machines can be managed through the LAN Server Administration GUI. For more
information, see the LAN Server Network Administrator Reference Volume 3:
Network Administrator Tasks.
To configure the Remote IPL service to start automatically, select Remote IPL
and On in the Server Services window during installation and configuration. If
the Remote IPL service has not been configured to start automatically, it can
be started from the Network Services window on the LAN Server Administration
GUI or from the command-line interface with the NET START REMOTEBOOT command.
(See LAN Server Commands and Utilities and the LAN Server Network Administrator
Reference Volume 3: Network Administrator Tasks.)
When receiving a remote IPL request, the Remote IPL service locates the files
to send to the requester. To download the files, the Remote IPL service uses
the RPL network interface API.
The server maintains an RPL.MAP file containing one or more workstation records
for each remote IPL requester. Workstation records determine the parameters
used when a specific workstation is started. Although multiple records can be
defined for a workstation, only one can be enabled at any given time. The
CHGBOOT utility allows a user at a remote IPL requester to select temporarily
an alternative workstation record. The selection goes into effect the next time
the workstation is remote-IPLed. The default record is restored with the next
remote IPL.
For example, users of OS/2 requesters for which OS/2 and DOS workstation
records are listed in the RPL.MAP file can select the operating system of their
choice. This might be useful for running a DOS application that would otherwise
not run in the DOS compatibility mode. Also, users at DOS workstations or users
at OS/2 workstations who selected to remote IPL with DOS can select a
particular DOS image from the DOS images available on the server. This
capability is useful when starting a diagnostics function.
Note:
Only one DOS workstation record is required to enable users to select
from all DOS images available on the server. For an explanation of
startup image, see DOS Remote IPL.
The LAN Server product provides the Presentation Manager-based MKRDPM utility
to create remote IPL startup diskettes that can be used to start DOS or OS/2
workstations on the PC Network (SBCS systems only), Token-Ring, and ETHERAND
networks.
The startup diskettes initialize the adapter and start the remote IPL process.
For detailed information about the MKRDPM utility, refer to the LAN Server
Network Administrator Reference Volume 3: Network Administrator Tasks.
ΓòÉΓòÉΓòÉ 5.11.9.1. DOS Remote IPL ΓòÉΓòÉΓòÉ
DOS remote IPL mimics the normal process of a personal computer starting DOS,
with several slight variations that allow the information to come from the
network, rather than from the workstation's CD-ROM, hard-disk, or diskette
drive.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: DOS remote IPL is supported Γöé
Γöé only on DOS 6.3/V. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
To start a workstation running DOS remotely, the network adapter card initially
locates a remote IPL server, which delivers drivers that are loaded into
memory. Next, a more sophisticated program, the loader, redirects accesses to
the workstation's A: drive across the network. The usual startup files, such
as IBMBIO.COM, IBMDOS.COM, COMMAND.COM, CONFIG.SYS, and AUTOEXEC.BAT, are
loaded into the workstation's memory from a remotely accessed startup image.
A startup image is a file on the server that looks like a diskette to the
workstation. After the loading of this image, the redirection to drive A: is
ended. The DOS LAN Services software, which is partially present in the image
and started by the AUTOEXEC.BAT file, can then be used to establish a user
session with a server. For a procedure to create DOS images, refer to the LAN
Server Network Administrator Reference Volume 3: Network Administrator Tasks.
A server requires the following programs to create a DOS image:
o DOS LAN Services 4.0
o LAN Support Program 1.35
and one of the following versions of DOS:
o IBM DOS or MS-DOS 3.3
o IBM DOS or MS-DOS 5.0
o MS DOS 6.0 or 6.2
o PC DOS 6.1 or 6.3
o Asian versions of PC DOS 6.3/V
These products can be selected from the Copy Programs window during LAN
Services installation and configuration.
ΓòÉΓòÉΓòÉ 5.11.9.2. OS/2 Remote IPL ΓòÉΓòÉΓòÉ
OS/2 remote IPL is similar to DOS remote IPL in the early stages, and shares
some common server components. OS/2 remote IPL deviates from DOS in that it
uses a mini-file-system driver to load base device drivers, dynamic link
libraries, the CONFIG.SYS file, network device drivers, and the remote IPL
redirector. This approach eliminates image file requirements and physical
sector dependencies. A server supporting OS/2 remote IPL requires LAN Support
Program 1.35. This product can be selected from the Copy Programs window during
LAN Services installation and configuration.
Note:
The LAN Server product does not support the remote IPL of OS/2 1.3
requesters. A LAN Server 2.0 machine with the ability to remote-IPL
OS/2 1.3requesters on the domain does not retain this capability when
upgraded to the LAN Server 4.0 product.
ΓòÉΓòÉΓòÉ 5.11.10. Replicator Service ΓòÉΓòÉΓòÉ
The Replicator service copies subdirectories from a server to
another server or requester so that an information base can be
maintained simultaneously on two or more workstations. The
Replicator service ensures that any update to the information base
is sent to all workstations receiving copies. The server sending
the data is called the exporter. The requesters or servers
receiving the data are called importers.
The Replicator service is automatically installed on servers during LAN
Services installation and configuration. To configure the Replicator service to
start automatically, select Replicator and On in the Server Services window
during installation and configuration.
If the Replicator service has not been configured to start automatically, it
can be started from the Network Services window on the LAN Server
Administration GUI or from the command-line interface with the NET START
command. (See LAN Server Commands and Utilities and the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.)
ΓòÉΓòÉΓòÉ 5.11.11. Requester ΓòÉΓòÉΓòÉ
The Requester service sends requests for files, printers, and
serial devices from one workstation to another workstation. The
workstation that receives the request must be a server or a peer
workstation. The server or peer workstation either sends data
back to the workstation that sent the request or indicates that
access to the requested resource is denied.
ΓòÉΓòÉΓòÉ 5.11.12. Server ΓòÉΓòÉΓòÉ
The Server service allows the server to share its resources with
users on the network. It receives and answers network requests
for files, printers, and serial devices.
ΓòÉΓòÉΓòÉ 5.11.13. Timesource Service ΓòÉΓòÉΓòÉ
The Timesource service designates a domain controller as the
domain time server with which other workstations in the same
domain or other domains can synchronize. The Timesource service
does not keep time. It only provides the means for other
workstations on the network to identify a reliable clock, which
must be maintained by special hardware or software, or both.
The Timesource service is automatically installed on domain controllers during
LAN Services installation and configuration. It is not available on additional
servers.
To configure the Timesource service to start automatically on a domain
controller, select Timesource and On in the Server Services window during
installation and configuration.
If the Timesource service has not been configured to start automatically, it
can be started from the Network Services window on the LAN Server
Administration GUI or from the command-line interface with the NET START
command. (See LAN Server Commands and Utilities and the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.)
ΓòÉΓòÉΓòÉ 5.11.14. Uninterruptible Power Supply Service ΓòÉΓòÉΓòÉ
The Uninterruptible Power Supply (UPS) service is a server
function providing protection against loss of data during power
failures. When a power interruption occurs at a server, users who
have active sessions with the affected server are notified of an
impending shutdown. They have the opportunity to save and close
open files on their workstations before the server shuts down.
To install UPS support during LAN Services installation and configuration,
select Uninterruptible Power Supply Support in the Install and Remove window.
To configure the UPS service to start automatically, select Uninterruptible
Power Supply Support and On in the Server Services window during installation
and configuration. To have the UPS service start automatically, UPS hardware
must be installed in the server.
UPS support is compatible with any UPS hardware with contact closure or
voltage-level signaling. The UPS hardware is connected to the server through a
dedicated industry-standard serial port. During LAN Services installation and
configuration, you can select the port to be used by the UPS hardware.
Note:
If you have a COM.SYS device driver in CONFIG.SYS, make sure it is
placed after the UPSDRV.OS2 statement in the CONFIG.SYS file.
Otherwise, the UPS service will not start successfully.
If the UPS service is not configured to start automatically, you can start it
from the Network Services window on the LAN Server Administration GUI or from
the command-line interface with the NET START command. (See LAN Server Commands
and Utilities and the LAN Server Network Administrator Reference Volume 3:
Network Administrator Tasks.)
ΓòÉΓòÉΓòÉ 5.12. DOS LAN Services and Windows ΓòÉΓòÉΓòÉ
DOS LAN Services is the component of the LAN Server product that provides LAN
connectivity for users of workstations running DOS. You can use DOS LAN
Services in a DOS environment with or without Windows.
When you use DOS LAN Services with Windows, you can access network resources
(such as directories, printers, applications, and other services) through the
Windows graphical user interface. When you use DOS LAN Services without
Windows, you can access the network resources through the DOS LAN Services
graphical user interface. During the DOS LAN Services installation process,
you set up DOS LAN Services to function with or without Windows. If you want
to access network resources through the Windows interface, you must also
install Windows.
Note:
Windows must be purchased separately.
DOS LAN Services (with or without Windows) enables you to:
o Log on and log off an OS/2 LAN Server domain
o Change logon assignments
o Change your logon password
o Change your user comment
o List logged-on users
o Send messages to other network users
o Broadcast messages to a specified domain
o Broadcast messages to the network
o Receive messages from other network users
o Queue messages for later viewing
o Log the messages in a file
o Log the messages to a printer
o View your message log file
o Change your message logging status
o View, connect, and disconnect shared directory aliases
o View, install, and use LAN Server shared applications
o Manage print jobs in shared print queues
o View, connect, and disconnect shared printers
o View directory-limit information for a shared directory (Windows only)
o Share local directories and printers with other network users
o View, connect, and disconnect any LAN Server shared serial printer that is
configured as a shared printer rather than as a serial device.
The LAN Server product grants access to the shared resource using the same User
Profile Management and access control system that is used for OS/2 LAN
Requester. For more information, refer to Access Control.
ΓòÉΓòÉΓòÉ 5.13. Online Information ΓòÉΓòÉΓòÉ
The following online LAN information can be installed:
o DOS LAN Services and Windows User's Guide
o IBM OS/2 LAN Server Version 4.0 Up and Running!
o LAN Server Network Administrator Reference Volume 1: Planning, Installation,
and Configuration
o LAN Server Network Administrator Reference Volume 2: Performance Tuning
o LAN Server Network Administrator Reference Volume 3: Network Administrator
Tasks
o LAN Server Problem Determination Guide
o MPTS - AnyNet for OS/2: Configuration Guide
o LAN CID Utility Guide
o OS/2 LAN Server Online Error Message Reference
o OS/2 LAN Requester User's Guide
For information on how to install the online books or how to order printed
copies of the online books, refer to IBM OS/2 LAN Server Version 4.0 Up and
Running!
Notes:
1. Help windows are automatically installed if the LAN Server
Administration GUI is selected to be installed. (See LAN Server
Administration GUI.) If you follow the Easy path for an initial
installation, the graphical user interface and the help windows are
always installed.
2. DOS LAN Services Windows online help is available, but it is not a
selectable item during LAN Services installation and configuration.
You can access online LAN help information (if installed) from the LAN Services
folder on the desktop, from the graphical user interface, or from the OS/2
command-line interface, as follows.
To Access Online Information:
o From the LAN Services folder, open LAN Server Books, and then select the
reference you want to consult.
o From the LAN Server Administration GUI, select F1=Help to receive help
information about the function or window you are currently using.
o From the command-line interface, do one of the following:
- For information about a specific command, type NET HELP followed by the
command name. For example, for information about the NET COPY command,
type:
NET HELP COPY
- To view information about the command options, type NET HELP and the
command name followed by the /OPTIONS parameter. For example, to
display a description of the parameters available for the NET COPY
command, type:
NET HELP COPY /OPTIONS
- To display a list of the network commands for which help information is
available, type NET HELP without a command name.
- For information about a network error message received at the command
line, type HELP and the message number. For example, for cause and
recovery information about the following error message:
NET2103: The server cannot be located.
type:
HELP NET2103
In addition to message information available online, see the
\IBMLAN.\ERROR.TXT file for descriptions of other error messages.
Notes:
1. Online help for DOS LAN Services Windows is available from the menu bar.
2. OS/2 and DOS commands are described in the online LAN Server Commands
and Utilities.
ΓòÉΓòÉΓòÉ 5.14. Language Support for Different Countries ΓòÉΓòÉΓòÉ
The LAN Server product is available in the following languages:
o Canadian French
o French
o German
o Italian
o Japanese
o Korean
o Norwegian
o Spanish
o Swedish (only DOS LAN Services and the DOS LAN Services and Windows User's
Guide)
o Taiwanese (Traditional Chinese)
o U.K. English
o U.S. English
For information on code page considerations, refer to Language Support and Code
Page Considerations.
ΓòÉΓòÉΓòÉ 6. Planning Your Network ΓòÉΓòÉΓòÉ
To ensure a that your network will function properly, you must plan for each
domain and server in the network. Planning for a domain means identifying the
domain controller and any additional servers in the domain. This chapter lists
general hardware and software requirements and outlines the network planning
tasks. Worksheets provides worksheets to assist you in network planning.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: The PC LAN Program is not Γöé
Γöé available in DBCS countries. Any reference in this book to the PC Γöé
Γöé LAN Program does not apply to DBCS systems. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
If you want to upgrade a domain running the PC LAN Program Version 1.3 (or
later), refer to Migrating PCLP to an IBM OS/2 LAN Server Environment. If you
want to upgrade a domain running a previous version of OS/2 LAN Server, read
Migration of Data. For an example procedure, refer to Upgrading LAN Server 2.0
or 3.0.
If you are administering a LAN with server and requester products at different
version levels, read Compatibility among Servers and Requesters.
ΓòÉΓòÉΓòÉ 6.1. Software Requirements and Compatibility ΓòÉΓòÉΓòÉ
Before installing the LAN Server product, make sure the following software
requirements are met. As indicated in the following list, most of these
products are included with the LAN Server product.
o The LAN Server product requires OS/2 2.1 or higher or an equivalent base
operating system (separately sold products).
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: The following DBCS versions Γöé
Γöé of OS/2, DOS, and Windows are supported by LAN Server Version 4.0: Γöé
Γöé Γöé
Γöé o OS/2: Γöé
Γöé - 2.1+Service Pak (XR06200 level or higher) Γöé
Γöé - 2.11 Γöé
Γöé o DOS: Γöé
Γöé - IBM DOS 5.0 or 5.0/V Γöé
Γöé - PC DOS 6.1/V or 6.3/V Γöé
Γöé - MS DOS 6.2/V Γöé
Γöé o Windows: Γöé
Γöé - IBM 3.1 or MS 3.1 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
o The LAN Server product requires LAN Adapter and Protocol Support (LAPS),
which is part of the IBM Multi-Protocol Transport Services - AnyNet for OS/2
product (provided with the LAN Server product).
o DOS LAN Services requires the following additional products:
- DOS version:
o IBM DOS or MS-DOS 3.3
o IBM DOS or MS-DOS 5.0
o MS-DOS 6.0 or 6.2
o PC DOS 6.1 or 6.3
(DOS is sold separately.)
These products are installed by the LAN Services installation/configuration
program.
o Servers supporting the DOS Remote IPL service require the following
additional products:
- DOS LAN Services 3.0 (provided with the LAN Server product)
- LAN Support Program 1.35 (provided with the LAN Server product)
- DOS version:
o IBM DOS or MS-DOS 3.3
o IBM DOS or MS-DOS 5.0
o MS-DOS 6.0 or 6.2
o PC DOS 6.1 or 6.3
o Asian versions of PC DOS 6.1/V or 6.3/VJ
(DOS is sold separately.)
These products can be installed by the LAN Services
installation/configuration program.
o Servers supporting the OS/2 Remote IPL service require the following
additional product:
- LAN Support Program 1.35 (provided with the LAN Server product). This
product can be installed by the LAN Services installation/configuration
program.
o The LAN Server product is compatible with Communications Manager/2 and
DATABASE 2 OS/2 and can run on the same workstation.
ΓòÉΓòÉΓòÉ 6.1.1. Current Corrective Service Diskette (CSD) Levels ΓòÉΓòÉΓòÉ
The following table provides the latest maintenance release levels for OS/2
products. To order, contact your authorized IBM sales representative.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: The following table con- Γöé
Γöé tains information for SBCS systems only. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
A problem management record number (PMR) will be assigned for you.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 4. Maintenance Release Levels Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PRODUCT/COMPONENT Γöé RELEASE Γöé CSD LEVEL Γöé PTF NUMBER Γöé DATE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OS/2 Toolkit Γöé 2.1 Γöé XR06110 Γöé XR06110 Γöé 09/01/93 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OS/2 LAN Server/Requester Γöé 3.00 Γöé IP07045 Γöé IP07040 Γöé 3/94 Γöé
Γöé ServicePak: Γöé Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé Γöé
Γöé o Server/Requester Γöé Γöé Γöé Γöé Γöé
Γöé o Fault Tolerance Γöé Γöé Γöé Γöé Γöé
Γöé o User Profile Management Γöé Γöé Γöé Γöé Γöé
Γöé o HPFS/NetView Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ConvieniencePak for LAN NetView Γöé 3.00 Γöé IPX7006 Γöé IPX7006 Γöé 11/93 Γöé
Γöé Prerequisites Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LAN Server/DOS LAN Services Γöé 3.00 Γöé IP07041 Γöé IP07041 Γöé 3/94 Γöé
Γöé SelectPak Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LAN Server/DOS LAN Services Γöé 3.00 Γöé IP07003 Γöé IP07003 Γöé 7/93 Γöé
Γöé SelectPak Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NTS/2 SelectPak Γöé 1.0 Γöé WR07040 Γöé WR07040 Γöé 3/94 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CSET/2 Compiler Γöé 1.00 Γöé Γöé XR06150 Γöé 6/93 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Workstation Program (WSP) Γöé 1.12 Γöé Γöé UR23217 Γöé 1/89 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Note:
WR06050 can be ordered on diskette and will be forwarded to the
Communications Manager/2 Group for orders. IBM internal users can
request this information through OS2PROD.
ΓòÉΓòÉΓòÉ 6.2. Hardware, Memory, and Hard-Disk Requirements ΓòÉΓòÉΓòÉ
The LAN Server product runs on the following appropriately configured hardware:
o IBM Personal System/2* (PS/2)* and Personal System/55* (PS/55)* products
supported by OS/2 2.1 or higher
o IBM personal computer products supported by OS/2 2.1 or higher
Refer to the OS/2 license information booklet for a complete list of IBM
hardware supported by OS/2 2.1 or higher.
o All non-IBM workstations supported by a base operating system that is
equivalent to OS/2 2.1 or higher
DOS LAN Services requires workstations that support:
o IBM DOS or MS-DOS 3.3
o IBM DOS or MS-DOS 5.0
o MS-DOS 6.0 or 6.2
o PC DOS 6.1 or 6.3
o Asian versions of IBM DOS 5.0 or 5.0/V
o Asian versions of PC DOS 6.1/V or 6.3/VJ
o Asian versions of MS DOS 6.2/V
Ensure that each workstation is installed with sufficient hard-disk space and
memory. Choose hardware that meets or exceeds the minimum requirements. For
help in calculating the memory and hard disk needs for each workstation,
consult Memory and Hard-Disk Estimating Worksheets. Consider memory and
hard-disk requirements for the operating system, applications, and data. For
memory considerations specifically concerning servers, see Designating Servers
in Each Domain. Plan for growth in hard-disk space, especially for the domain
controller. As much memory as possible should be allocated to cache on an
Advanced server. Other areas in which to plan for growth include applications,
home directories, and spooler usage.
Note:
During LAN Services installation and configuration, the amount of
required disk space is calculated. If this amount exceeds the available
space, the Insufficient Disk Space window is displayed. You can then
take appropriate action to make more disk space available or end the LAN
Services installation/configuration program.
Because of the limited RAM available to applications after DOS LAN Services is
loaded, it may be necessary to relocate parts of the DOS LAN Services code into
one of the available DOS memory extenders. If a workstation is configured with
expanded or extended memory above 1MB, parts of the DOS LAN Services code can
be loaded there, reducing the usage to approximately 45KB of the lowest 640KB
memory. For more information, refer to DOS LAN Services Memory Management.
ΓòÉΓòÉΓòÉ 6.2.1. Disk Requirements for Fault Tolerance ΓòÉΓòÉΓòÉ
If you plan to install Fault Tolerance on your server workstation and want to
use drive mirroring or drive duplexing, you must have a minimum of two physical
disks on the workstation. The following additonal constraints must be
addressed:
o There must be enough contiguous free space for FTSETUP to create the
secondary, or back-up, drive.
o You can only mirror into an extended partition.
o Recovery is a special case of mirroring, so you can't recover into a primary
partition.
o Therefore, if you want a recoverable operating system, you must install it
into an extended partition by using Boot Manager.
Note:
The disks used for mirroring must have the same geometry. Disks with the
same geometry have the same number of sectors per track and the same
number of tracks per cylinder.
Drive duplexing also requires that these disks be on two different controllers.
Each mirrored or duplexed pair of partitions must reside on disks handled by
the same disk device driver.
When planning the hard-disk requirements for your server, determine the type of
applications and data used on the server. Install applications and data that
are critical to your environment on mirrored drives.
You can mirror drives on disks of different physical sizes on the condition
that there is enough contiguous-free space available. For example, you can
mirror a logical drive located on a 320MB disk to a 160MB disk as long as the
logical drive is less than 160MB. You cannot mirror a 200MB logical drive to a
160MB disk.
If the workstation on which you plan to install Fault Tolerance has only two
hard disks, you must, at installation time, specify a primary HPFS partition
size on the disk containing the boot drive. To specify a primary partition,
follow the instructions in the OS/2 2.1 installation documentation. Make sure
you select Specify your own primary partition at the start of OS/2 2.1
installation.
When prompted, enter the size, in MB, of the primary partition you want to
create. Any remaining space can be used to create extended partitions.
Therefore, when you specify the primary partition size, you should be sure to
leave enough space available on the hard disk for mirrored (or duplexed) drives
to hold the applications and data you want to be mirrored (or duplexed).
Note:
Both Boot Manager and the boot drive can be located on the first disk.
To be able to use Boot Manager successfully and mirror the boot drive,
proceed as follows during OS/2 2.1 installation:
1. When prompted by the OS/2 2.1 installation program, specify your
partition size for the boot drive.
If you plan to mirror the boot drive, remember to create it as a logical
drive and not as a primary drive.
2. When the installation program is running the FDISK utility, select
Install Boot Manager.
The maximum size of a mirrored drive is 1MB less than the maximum size of its
hard disk (1MB is required for system use). Mirrored drives use twice as much
disk space as non-mirrored drives.
It is strongly recommended that you create extended partitions on both the hard
disk containing the boot drive and your other hard disks, before LAN Services
installation and configuration (using the FDISKPM command). If the drives are
not set up correctly before installation, you may not be able to mirror, in
addition to which you may have to reinstall the LAN Server product. Refer to
the base operating system documentation for information on this command. The
size of the partitions depends on the applications you plan to install and the
data you plan to store. Fault Tolerance makes extensive use of extended
partitions, particularly when creating mirrored partitions.
The figure titled Server Configuration with Mirrored and Duplexed Drives
illustrates a server configuration with five physical disks. Because of
mirroring, the actual storage capacity is three disks. Drives C: and E: are
duplexed drives; F: is a mirrored drive.
Server Configuration with Mirrored and Duplexed Drives
For a brief description of the Fault Tolerance function, see Upgrading an
Attended Server; for detailed information, see the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
ΓòÉΓòÉΓòÉ 6.2.2. Network Adapters ΓòÉΓòÉΓòÉ
Network adapters (also referred to as network adapter cards) are hardware units
in a workstation that perform the interface between a workstation and the
network.
The LAN Server product supports network adapters that can handle the following
networks:
o IBM Token-Ring Network
o IBM PC Network (SBCS systems only)
o IBM ETHERAND Network
o Any other networks supported by MPTS
For each of these LANs, a variety of adapters is available to support different
communication capabilities, different data-handling resources, and the
following different types of workstations:
o IBM Personal Computer AT (DOS LAN Services and DOS workstations only)
o Compatible OEM workstations
o IBM PS/2 and PS/55
ΓòÉΓòÉΓòÉ 6.2.2.1. Supported Network Adapters ΓòÉΓòÉΓòÉ
The following information describes the network adapters that LAPS supports. A
distinction is made between network adapters supported by drivers provided with
LAPS and network adapters supported by drivers not provided with LAPS.
For a complete list of supported adapter cards and information on obtaining the
current driver, refer to the READMAC.TXT file located in the IBMCOM\MACS
subdirectory.
ΓòÉΓòÉΓòÉ 6.2.2.2. Network Adapter Cards-Drivers Shipped with LAPS ΓòÉΓòÉΓòÉ
3Com** EtherLink** II (3C503)
3Com EtherLink II-16 (3C503-16)
3Com EtherLink II-16-TP (3C503-16-TP)
3Com EtherLink/MC (3C523B)
3Com EtherLink/MC-TP (3C523B-TP)
3Com EtherLink III (3C509)
3Com EtherLink III-Combo (3C509-COMBO)
3Com EtherLink III-TP (3C509-TP)
3Com EtherLink III-TPO (3C509-TPO)
3Com EtherLink III-EISA (3C579)
3Com EtherLink III-EISA-TP (3C579-TP)
3Com EtherLink III-MCA (3C529)
3Com EtherLink III-MCA-TP (3C529-TP)
3Com TokenLink III (3C619)
3Com TokenLink III EISA (3C679)
3Com TokenLink III MCA (3C629)
Cabletron Ethernet DNI Adapter (E1112)
Cabletron Ethernet DNI Adapter (E1119)
Cabletron Ethernet DNI Adapter (E2112)
Cabletron Ethernet DNI Adapter (E2119)
Cabletron Ethernet DNI Adapter (E3112)
Cabletron Ethernet DNI Adapter (E3119)
Cabletron Token-Ring DNI Adapter (T2015)
Cabletron Token-Ring DNI Adapter (T3015)
Cray Communications ScaNet Network Interface Adapter-ISA
Cray Communications ScaNet Network Interface Adapter-MCA
DCA ClassicBlue MC 4/16 Token-Ring Adapter
IBM Adapter/A for Ethernet Networks
IBM Adapter/A for Ethernet Twisted-Pair Networks
IBM LAN Adapter for Ethernet
IBM LAN Adapter for Ethernet CX
IBM LAN Adapter for Ethernet TP
IBM LAN Adapter/A for Ethernet
IBM EtherStreamer* MC 32 Adapter
IBM IBM Credit Card Adapter for Ethernet-10B2
IBM IBM Credit Card Adapter II for Ethernet-10BT
IBM Token-Ring Network Adapter
IBM Token-Ring Network Adapter II
IBM Token-Ring Network 16/4 Adapter
IBM Token-Ring Network 16/4 ISA-16 Adapter
IBM Token-Ring Network 16/4 Adapter II
IBM 16/4 Busmaster EISA Adapter
IBM Token-Ring 16/4 Credit Card Adapter II
IBM Token-Ring Network Adapter/A
IBM Token-Ring Network 16/4 Adapter/A (16F1163)
IBM Token-Ring Network 16/4 Adapter/A (75F9410)
IBM 16/4 Busmaster Server Adapter/A
IBM LANStreamer* MC 16 Adapter
IBM LANStreamer MC 32 Adapter
IBM Auto LANStreamer MC 32 Adapter
IBM PC Network Adapter II-Frequency 2
IBM PC Network Adapter II-Frequency 3
IBM PC Network Baseband Adapter
IBM PC Network Broadband Adapter II
IBM PC Network Adapter II/A-Frequency 2
IBM PC Network Adapter II/A-Frequency 3
IBM PC Network Baseband Adapter/A
IBM PC Network Broadband Adapter II/A
IBM Advanced 3278/79 Emulation Adapter
IBM 3270 Connection, DFT
Intel EtherExpress 16C (PCLA8100)
Intel EtherExpress FlashC (PCLA8105)
Intel EtherExpress 16 (PCLA8110)
Intel EtherExpress Flash (PCLA8115)
Intel EtherExpress 16TP (PCLA8120)
Intel EtherExpress FlashTP (PCLA8125)
Intel EtherExpress MCA (MCLA8110)
Intel EtherExpress MCATP (MCLA8120)
Intel TokenExpress ISA/16S (PCLA8130A)
Intel TokenExpress 16/4 LAN Adapter for EISA (EILA8235)
Intel TokenExpress EISA/32 LAN Adapter (EILA8245)
Madge Straight Blue 16/4 ISA (62-01)
Madge Straight Blue ISA Plus Blue Box (62-02)
Madge Straight Blue MC Blue Box (64-01)
SMC EtherCard PLUS** (8003EB)
SMC EtherCard PLUS/A (8003E/A)
Thomas-Conrad Tropic 16/4 Token-Ring Adapter/AT (TC4043)
Ungermann-Bass** NIUpc** Adapter
Ungermann-Bass NIUps Adapter
Notes:
1. The Cray Communications ScaNet adapter cards are also called Dowty
ScaNet adapter cards.
2. Standard Microsystems EtherCard PLUS Adapter was formerly called
Western-Digital EtherCard PLUS Adapter
3. Standard Microsystems EtherCard PLUS/A Network Adapter was formerly
called Western-Digital EtherCard PLUS/A Network Adapter
ΓòÉΓòÉΓòÉ 6.2.2.3. Network Adapter Cards-Drivers not Shipped with LAPS ΓòÉΓòÉΓòÉ
3Com EtherLink 16 (3C507)
3Com EtherLink 16-TP (3C507-TP)
3Com EtherLink MC-32 (3C527B)
Accton EtherCombo-16 (EN1650)
Accton EtherPair-16 (EN1651)
Accton EtherCoax-16 (EN1652)
Accton EtherCombo-32 (EN1200)
Artisoft NodeRunner/SI 2000/C
Artisoft NodeRunner/SI 2000/T
Artisoft NodeRunner/SI 2000/A
Artisoft NodeRunner/SI 2000M/TC
Artisoft LANTastic NodeRunner 2000/C
Artisoft LANTastic NodeRunner 2000/T
Artisoft LANTastic NodeRunner 2000/A
Artisoft LANTastic NodeRunner 2000M/TC
Asante EtherPaC 2000+3
Asante EtherPaC 2000+N
Asante EtherPaC 2000+T
DCA IRMAtrac EISA
DCA IRMAtrac Token-Ring Adapter/Convertible
D-Link Ethernet Interface Card for the PC XT*/AT* (DE-220C)
D-Link Ethernet Interface Card for the PC XT/AT (DE-220CAT)
D-Link Ethernet Interface Card for the PC XT/AT (DE-220CT)
D-Link Ethernet Interface Card for the PC XT/AT (DE-220T)
D-Link Ethernet Card for EISA-Bus PC (DE-400)*
D-Link Ethernet VESA Combo Card (DE-500CAT)
Eagle EtherXpert EP2000plus
Eagle EtherXpert EP2000Tplus
Eagle EtherXpert EP3210
Eagle Novell NE2000
Eagle Novell NE2000T
Eagle Novell NE2000plus
Eagle Novell NE2000Tplus
Eagle Novell NE2000plus-3
Eagle Novell NE3210
Hewlett-Packard 27247
IBM Dual EtherStreamer MC 32 Adapter
IBM Dual LANStreamer MC 32 Adapter
Madge Smart 16/4 AT PLUS Ringnode (52-03)
Madge Smart 16/4 EISA Ringnode (52-08)
Madge Smart 16/4 MC Ringnode (54-08)
Madge Smart 16/4 MC32 Ringnode (54-09)
NCR WaveLAN Adapter
Olicom USA, Inc. ISA 16/4 Adapter (OC-3117)
Olicom USA, Inc. MCA 16/4 Adapter (OC-3129)
Olicom USA, Inc. EISA 16/4 Adapter (OC-3133)
Olicom USA, Inc. EISA/32 Adapter (OC-3135)
Olicom USA, Inc. Pocket Token-Ring Adapter (OC-3210)
Olicom USA, Inc. Token-Ring PCMCIA Card (OC-3220)
Proteon p1392plus
Proteon p1892plus
Proteon p1992plus
Racal-InterLan EtherBlaster TP-8INT (163-3184)
Racal-InterLan NI5210-16 (163-0610)
Racal-InterLan ES3210-TP (163-3160)
Racal-InterLan InterLAN MCA (163-3142)
Racal-InterLan InterLAN MCA-TP (163-3143)
Racal-InterLan InterLAN Token-Ring 16/4 ISA (163-3193)
Racal-InterLan InterLAN Token-Ring 16/4 MCA (163-3137)
SMC EtherCard PLUS Elite (8003EP)
SMC EtherCard PLUS Elite 10T (8003WC)
SMC EtherCard PLUS Elite 16 (8013EPC)
SMC EtherCard PLUS Elite 16T (8013WC)
SMC EtherCard PLUS Elite 16 Combo (8013EWC)
SMC EtherCard PLUS Elite/A (8013EP/A)
SMC EtherCard PLUS Elite 10T/A (8013WP/A)
SMC EtherCard Elite 16 Ultra (8216)
SMC EtherCard Elite 16C Ultra (8216C)
SMC EtherCard Elite 16T Ultra (8216T)
SMC EtherCard Elite 32C Ultra (82M32C)
SMC TokenCard Elite/A (8115T/A)
SMC TokenCard Elite Master 32 (83M32)
Thomas-Conrad 16/4 Token-Ring Adapter/AT (TC4045)
Thomas-Conrad 16/4 Token-Ring Adapter/MC (TC4046)
Xircom External Token-Ring Adapter (ET16BU)
Xircom Pocket Token Ring Adapter III (PT3-16CTP)
Xircom CreditCard Token Ring Adapter (CT-16CTP)
Xircom Pocket Ethernet Adapter III (PE3-10BT)
Xircom Pocket Ethernet Adapter III (PE3-10BC)
Xircom Pocket Ethernet Adapter III (PE3-10BX)
Xircom CreditCard Ethernet Adapter (CE-10BC)
Xircom PS-CreditCard Ethernet Adapter (PS-CE2-10BT)
ΓòÉΓòÉΓòÉ 6.2.2.4. Multiple Adapter Considerations ΓòÉΓòÉΓòÉ
Because an OS/2 LAN Server or OS/2 LAN Requester workstation can support up to
four network adapters at a time, it can be attached to multiple networks. If
you plan to install more than one network adapter, consult the MPTS - AnyNet
for OS/2: Configuration Guide for information about restrictions on particular
adapter combinations.
In addition, consider the following:
o For each network adapter used by OS/2 LAN Server or OS/2 LAN Requester, a
netx statement must be present in the IBMLAN.INI file. Logical adapter 0
corresponds to the net1 statement, logical adapter 1 to the net2 statement,
and so on. The LAN Services installation/configuration program automatically
generates the appropriate netx statements.
If you follow the Easy installation path, only one network adapter is
configured for use with OS/2 LAN Server or OS/2 LAN Requester. Follow the
Tailored installation path if you want to select more than one network
adapter for use with OS/2 LAN Server or OS/2 LAN Requester. Select LAN
Services Adapters in the Configure window and make your adapter selections in
the LAN Adapters window.
For detailed information about the netx statement and about how to modify the
IBMLAN.INI file with an ASCII text editor, refer to the LAN Server Network
Administrator Reference Volume 2: Performance Tuning.
o The total RAM used by your network adapters, including other hardware
adapters (for example, displays or SCSI drives) must not exceed 64KB for
802.2 and 64KB for NetBIOS (128KB total). If this limit is exceeded, the
network may not be able to start. To calculate the RAM usage of adapters
supported by the LAN Server product, refer to the MPTS - AnyNet for OS/2:
Configuration Guide. To this total, add any RAM used by other hardware as
indicated by the manufacturer's documentation.
o If two or more nonbridged networks have workstations (servers or requesters)
configured for multiple adapters, the computernameparameter in the IBMLAN.INI
file of each workstation residing on those networks must be unique to ensure
valid connections to the workstations. Normally the NetBIOS protocol ensures
that machine names are unique; however, in certain nonbridged topologies,
name uniqueness must be manually maintained.
For example, if a server with two adapters tries to connect to a requester
named REQ1, but two workstations named REQ1 reside on two networks to which
the server is attached, only the requester on the network associated with the
net1 statement in the server IBMLAN.INI file establishes a connection.
Because the server stops polling when a session begins, it cannot access the
other REQ1 workstation.
A similar problem occurs for a requester with two adapters trying to connect
to a duplicate server name that exists on two separate networks. The
requester cannot access data on the server connected to the network
associated with the net2 statement, because a successful connection to the
server associated with the net1 statement is always made first.
For more information about the netx statement, see the LAN Server Network
Administrator Reference Volume 2: Performance Tuning.
For nonbridged networks, the LAN Server product does not provide checking or
error messages for duplicate computername parameters. Therefore, keep a log
of the names used when setting up workstations on a domain. See Worksheets
for worksheets to use in tracking server and requester names.
Note:
The computername parameter is set when you provide a server name or a
requester name during LAN Services installation and configuration.
You can use an ASCII editor to change the computername parameter in
the IBMLAN.INI file after installation.
ΓòÉΓòÉΓòÉ 6.2.2.5. DOS LAN Services Supported Network Adapter Cards ΓòÉΓòÉΓòÉ
The following list identifies the network adapter cards you can use with DOS
LAN Services:
o 3Com EtherLink
o 3Com EtherLink 16
o 3Com EtherLink II or IITP (8 or 16-bit)
o 3Com EtherLink III
o 3Com EtherLink/MC
o 3Com EtherLink Plus
o 3Com TokenLink
o Advanced Micro Devices AM2100/PCnet
o Amplicard AC 210/XT
o Amplicard AC 210/AT
o ARCNET Compatible
o Artisoft AE-1
o Artisoft AE-2 or AE-3
o Artisoft A E-2 (MCA) or AE-3 (MCA)
o Artisoft AE-3
o Cabletron E2000 Series DNI
o Cabletron E2100 Series DNI
o Data Systems Z-Note
o DEC Ethernet (All Types)
o DEC DEPCA
o DEC EE101 (Built-In)
o DEC EtherWorks LC
o DEC EtherWorks LC/TP
o DEC EtherWorks LC/TP_BNC
o DEC EtherWorks MC
o DEC EtherWorks MC/TP
o DEC EtherWorks MC/TP_BNC
o DEC EtherWorks Turbo
o DEC EtherWorks Turbo/TP
o DEC EtherWorks Turbo/TP_BNC
o DECpc 433 WS (Built-In)
o IBM Token Ring (All Types)
o IBM Token Ring
o IBM Token Ring (MCA)
o IBM Token Ring II
o IBM Token Ring II/Short
o IBM Token Ring 4/16Mbs
o IBM Token Ring 4/16Mbs (MCA)
o Intel EtherExpress 16 or 16TP
o Intel TokenExpress EISA 16/4
o Intel TokenExpress 16/4
o Intel TokenExpress MCA 16/4
o National Semiconductor Ethernode *16AT
o National Semiconductor AT/LANTIC EtherNODE 16-AT3
o NCR Token-Ring 4 Mbs ISA
o NCR Token-Ring 16/4 Mbs ISA
o NCR Token-Ring 16/4 Mbs MCA
o NE1000 Compatible
o NE2000 Compatible
o Novell**/Anthem NE1000
o Novell/Anthem NE2000
o Novell/Anthem NE1500T
o Novell/Anthem NE2100
o Novell/Anthem NE/2
o Olicom 16/4 Token-Ring Adapter
o Proteon ISA Token Ring (1340)
o Proteon ISA Token Ring (1342)
o Proteon ISA Token Ring (1346)
o Proteon ISA Token Ring (1347)
o Proteon MCA Token Ring (1840)
o Proteon Token Ring (P1390)
o Proteon Token Ring (P1392)
o Pure Data PDI508+ (ArcNet)
o Pure Data PDI516+ (ArcNet)
o Pure Data PDI9025-32 (Token Ring)
o Pure Data PDuC9025 (Token Ring)
o Racal NI6510
o RadiSys EXM-10
o SMC ARCNETPC
o SMC ARCNET PC100, PC200
o SMC ARCNET PC110, PC210, PS110, PS210, PC250
o SMC ARCNET PC130/E
o SMC ARCNET PC120,PC220, PC260
o SMC ARCNET PC270/E
o SMC ARCNET PC600W, PC650W
o SMC (WD) EtherCard (All Types except 8013/A)
o SMC (WD) EtherCard PLUS (WD/8003E)
o SMC (WD) EtherCard PLUS 10T/A (MCA) (WD 8003W/A)
o SMC (WD) EtherCard PLUS 16 With Boot ROM Socket (WD/8013EBT)
o SMC (WD) EtherCard PLUS/A (MCA) (WD 8003E/A or 8003ET/A)
o SMC (WD) EtherCard PLUS TP (WD/8003WT)
o SMC (WD) EtherCard PLUS With Boot ROM Socket (WD/8003EB)
o SMC (WD) EtherCard PLUS With Boot ROM Socket (WD/8003EBT)
o SMC (WD) EtherCard PLUS Elite (WD/8003EP)
o SMC (WD) EtherCard PLUS 10T (WD/8003W)
o SMC (WD) EtherCard PLUS Elite 16 (WD/8013EP)
o SMC (WD) EtherCard PLUS Elite 16T (WD/8013W)
o SMC (WD) EtherCard PLUS Elite 16 Combo (WD/8013EW or 8013EWC)
o SMC (WD) StarCard PLUS (WD/8003S)
o SMC (WD) StarCard PLUS/A (MCA) (WD 8003ST/A)
o SMC (WD) StarCard PLUS With On Board Hub (WD/8003SH)
ΓòÉΓòÉΓòÉ 6.2.2.6. 3174 Peer Communications ΓòÉΓòÉΓòÉ
The 3174 Peer Communications function provides peer-to-peer communication for
programmable workstations connected to an IBM 3174 Control Unit by means of IBM
3270 communication adapters using coaxial cable or telephone twisted-pair wire.
An OS/2 LAN Server or OS/2 LAN Requester workstation can support up to two 3270
communication adapters configured for 3174 Peer Communications at a time.
The 3174 Peer Communications function is useful for users who currently have
coaxial cabling or telephone twisted-pair wiring with IBM 3270 adapters in
their network but who want to migrate to a LAN Server network. The 3174 Peer
Communications function allows these users to take advantage of LAN Server
features with their coaxial or twisted-pair connections until the hardware for
an IBM Token-Ring, ETHERAND, or PC Network (SBCS systems only) topology is
installed.
If you use 3174 Peer Communications on a network with heavy traffic (a high
volume of broadcast frames), logging on to the network by establishing NetBIOS
sessions using broadcast frames can be difficult. Since the IBM 3174 Control
Unit attempts to send all token-ring broadcast frames to each coax-connected
workstation, the control unit can become flooded, causing discard of a
broadcast frame required to establish a session.
In certain situations, this problem can be avoided by increasing the values of
the NETBIOSRETRIES and NETBIOSTIMEOUT parameters. However, in networks that
experience very heavy traffic, this adjustment might not prevent logon
failures.
For more information about these parameters, see the LAN Server Network
Administrator Reference Volume 2: Performance Tuning.
ΓòÉΓòÉΓòÉ 6.2.2.7. Remote IPL Support ΓòÉΓòÉΓòÉ
Servers providing the Remote IPL service can be equipped with any adapter
supported by the LAN Server product.
Remote IPL requesters must be equipped with at least one of the following
network adapter types:
ΓòÉΓòÉΓòÉ 6.2.2.7.1. ISA Adapters ΓòÉΓòÉΓòÉ
o 3Com EtherLink 16(3C507)
o 3Com EtherLink II(3C503)
o 3Com EtherLink III(3C509)
o IBM LAN Adapter for Ethernet
o IBM LAN Adapter for Ethernet CX
o IBM LAN Adapter for Ethernet TP
o IBM PC Network baseband adapter
o IBM PC Network broadband adapter II
o IBM PS/2 Adapter for BNC/UTP Ethernet Networks
o IBM Token Ring Network Adapter
o IBM Token Ring Network 16/4 Adapter
o IBM Token Ring Network 16/4 Adapter II
o Standard Microsystems EtherCard PLUS Elite 16 (formerly Western-Digital)
ΓòÉΓòÉΓòÉ 6.2.2.7.2. Micro-Channel Adapters ΓòÉΓòÉΓòÉ
o 3Com EtherLink/MC adapter
o IBM LAN Adapter/A for Ethernet
o IBM LANStreamer MC 32 Adapter
o IBM PC Network baseband adapter/A
o IBM PC Network broadband adapter II/A
o IBM PS/2 Adapter/A for Ethernet Networks
o IBM Token Ring Network Adapter/A
o IBM Token Ring Network 16/4 Adapter/A
Note:
If your adapter is not on this list, contact your authorized IBM sales
representative.
The IBM adapters must support remote IPL and could require a RIPL** computer
chip. A bootable remote IPL diskette is also available. The 3Com adapters
require BootWare** RIPL ROM for LAN Manager from Lanworks Technologies Inc. The
Standard Microsystems adapter requires a RIPL ROM available from Standard
Microsystems.
If two adapters of the same type are installed in a remote IPL requester, only
the primary adapter can be configured for the remote IPL service.
ΓòÉΓòÉΓòÉ 6.2.2.8. Network Bridges ΓòÉΓòÉΓòÉ
If you are running a server with multiple adapters, the server determines which
of the adapters are on the same LAN at startup time. If the LAN topology
changes because of bridges starting up or failing between the adapters, the
server can react by failing intermittently. If you have bridges that fail
frequently and you are running a server with multiple adapters, ensure that no
two adapters in the server are connected by a bridge. Adapters in the server
should be connected either to the same LAN segment or to different LAN segments
that are not bridged together.
If you intend to run a bridge program on a slow workstation, ensure that the
parameter server value in the bridge configuration program is set to No. If the
parameter server value is set to Yes, a slow or congested bridge machine cannot
respond quickly enough to workstations on the network, preventing the
workstations' adapters from opening. Workstations that cannot enter the LAN
display an Error opening adapter message.
ΓòÉΓòÉΓòÉ 6.3. Planning Domains ΓòÉΓòÉΓòÉ
When planning the network, consider your organization's needs and workload.
Then decide how to arrange the network into domains. For example, you might
define a domain for each department in your organization.
Setting up a domain involves defining elements such as servers, resources,
users, groups, and access control profiles. For specific information about
defining these network elements, see the LAN Server Network Administrator
Reference Volume 3: Network Administrator Tasks. Consider the following:
o Which server will be the domain controller in each domain
o The number of additional servers (if any) in each domain
o Which servers (if any) will be backup domain controllers in the domain
o Which resources to share and how to distribute them among the servers
o The amount of random access memory (RAM) and hard-disk space required for the
shared resources
o The number of OS/2 and DOS LAN Services users that can log on to the domain
Networks become large and complex as the number of requesters, servers, and
resources increases. Use the Network Setup Worksheets in Network Setup
Worksheets to record network information as you designate servers, plan
resources and access control, select requesters, and identify users. Use the
Memory and Hard-Disk Estimating Worksheets provided in Memory and Hard-Disk
Estimating Worksheets to record memory and hard-disk requirements.
Draw a map of your network to help visualize it for planning and maintenance
purposes. The following information is useful on a network map:
o Requesters and servers
- Include machine IDs and messaging names.
- Show OS/2 LAN Requester workstations and DOS LAN Services workstations.
Indicate which workstations are remote IPL requesters. Indicate which
OS/2 LAN Requester or DOS requester workstations have the Peer service
installed.
o Resources connected to each server
- Show netnames and aliases.
- Identify cross-domain aliases.
o Domain names, domain controllers, and backup domain controllers
- Include domain membership for each server.
ΓòÉΓòÉΓòÉ 6.3.1. Designating Servers in Each Domain ΓòÉΓòÉΓòÉ
The selection of workstations to act as servers on each domain depends on
network performance requirements, the number of resources to share on each
domain, and server security. When designating the servers, do the following:
1. Consider the RAM and hard-disk space that each server requires, in addition
to the base operating system requirements.
2. Consider the adapter RAM space and the number of requesters the server must
support at the same time. Generally, a server with an 8KB adapter can
support up to 24 requesters. If more than 24 requesters will be frequently
using server resources, a 32-bit BusMaster adapter is recommended.
3. Consider which applications and files will be shared and the amount of
workstation RAM and hard-disk space these require. Also, consider the
printers and serial devices to be shared and the hardware needed to connect
these to a server. Allocate as much memory as possible to cache on an
Advanced server.
Add up all the RAM and hard-disk space requirements to determine the number
of servers you need and the amount of RAM and hard-disk space each server
requires. Server performance is affected by the number and types of
resource requests the server receives. For example, running a remote
program places a greater demand on a server's memory than running a private
application.
Server performance can be adjusted by changing parameters in the IBMLAN.INI
file and the PROTOCOL.INI file. For more information, see the LAN Server
Network Administrator Reference Volume 2: Performance Tuning.
4. Remote access of a server by a requester is restricted by OS/2 LAN Server.
To restrict local access to a server, you might want to install the Local
Security option. (See Local Security for the 386 HPFS.)
Note:
This option can be installed only on 386-HPFS servers and protects
386-HPFS partitions.
To provide further protection, consider restricting physical access to all
servers on your domain. In addition, be sure that those authorized to use
the server understand the effects that actions such as deleting files or
turning off server power can have on the network.
5. Determine the number of remote-IPL requesters per server. Make sure that at
least one adapter is configured for the IEEE 802.2 protocol on the remote
IPL server.
6. For servers that remote IPL more than 20 requesters, use the Advanced
server and the high performance file system (HPFS). The hard-disk partition
or partitions that will contain the OS/2 programs to be shared by the
remote-IPL requesters should be formatted for the HPFS. Also, specify a
large cache in the IFS statement in the CONFIG.SYS file of the remote IPL
server. For detailed information, refer to the LAN Server Network
Administrator Reference Volume 2: Performance Tuning.
Use the OS/2 LAN Server Installation Worksheet to help you install each server
workstation on your network. For each server supporting remote IPL, fill out a
copy of the Remote IPL Server Worksheet. To calculate memory and hard-disk
requirements for each server workstation, use the Memory Estimating Worksheet
for OS/2 LAN Server Workstations and the Hard-Disk Estimating Worksheet for
OS/2 LAN Server Workstations.
To calculate the value of some configuration parameters, refer to Calculating
IEEE 802.2 and NetBIOS Resources for OS/2 LAN Servers and Calculating Resources
for OS/2 Remote IPL Servers.
Note:
You can also consider installing the Peer service on one or more OS/2
and DOS Requester workstations to provide them with some server
capabilities. For more information, see Peer Service.
ΓòÉΓòÉΓòÉ 6.3.2. Planning Resources and Access Control ΓòÉΓòÉΓòÉ
To plan for resources, consider the following:
o Server on which a resource is to reside
o Resources to be shared
o User access permissions to a shared resource
Access to shared resources is controlled through access control profiles. An
access control profile for a resource defines the users who can use a resource
and their access permissions.
Note:
When planning for applications, check how many licenses were purchased
for the applications.
To help plan for the resources on each server, use the Server Summary
Worksheet. To help plan access control for each resource, use the Directory
Resource Worksheet, the Printer Resource Worksheet, and the Serial Device
Resource Worksheet.
For information about sharing resources, access control profiles, and access
permissions, see LAN Server Access Control System and the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
If you have set up printers, installed applications, or copied data to hard
disks on a server, you should define your resources in this order:
o Workstations (other servers)
o Alias names (resource definitions)
o Public applications
o User access lists
o Group access lists
o Access control for resources
ΓòÉΓòÉΓòÉ 6.3.3. Selecting Requesters ΓòÉΓòÉΓòÉ
Select OS/2 requesters and DOS requesters. Decide which workstations will be
remote IPL requesters. Decide which OS/2 LAN Requester or DOS requester will
be peer workstations.
ΓòÉΓòÉΓòÉ 6.3.3.1. OS/2 LAN Requester ΓòÉΓòÉΓòÉ
Use the OS/2 LAN Requester Installation Worksheet for each OS/2 requester
workstation you want to install on your network. To calculate memory and
hard-disk requirements for each OS/2 requester workstation, use the Memory
Estimating Worksheet for OS/2 LAN Requester Workstations and the Hard-Disk
Estimating Worksheet for OS/2 LAN Requester Workstations. As an administrator,
you might want to provide your users with a custom installation diskette to
simplify OS/2 LAN Requester installation. See Creating a Requester Custom
Diskette and Using a Requester Custom Diskette.
The LAN Server product supports remote initial program load (remote IPL) for
OS/2 requester workstations through the OS/2 Remote IPL service. Determine
which OS/2 requesters will be remote IPL requesters. To make use of remote IPL,
you must install the OS/2 Remote IPL service on the server supporting remote
IPL.
ΓòÉΓòÉΓòÉ 6.3.3.2. DOS LAN Services ΓòÉΓòÉΓòÉ
Users at DOS workstations with or without Windows can install DOS LAN Services
from CD-ROM or diskette. Refer to Installing DOS LAN Services from CD-ROM or
Diskettes. The DOS LAN Services Installation Worksheet assists you or the
workstation user in preparing to install DOS LAN Services from diskettes.
To calculate memory and hard-disk requirements for each DOS LAN Services
workstation, use the Memory Estimating Worksheet for DOS LAN Services
Workstations and the Hard-Disk Estimating Worksheet for DOS LAN Services
Workstations. See topic Hardware, Memory, and Hard-Disk Requirements for memory
considerations regarding DOS LAN Services. To improve the normal operation of a
DOS LAN Services workstation, refer to DOS LAN Services Memory Management.
DOS LAN Services workstations without hard disks can receive DOS LAN Services
IPL images either by diskette or by remote IPL through the server's DOS Remote
IPL service.
An image is a binary file used to load LAN software onto DOS requesters that
are not initialized from a hard disk or diskette. Images are created in two
ways:
o From image definition files
o From diskettes
You can store images on specified servers or diskettes, and you can use them to
IPL a DOS workstation when it is turned on or restarted.
An image definition identifies an image to the domain. Defining an image does
not create it.
An image definition file is an ASCII file that contains the items used to
generate an image. With this file, you can:
o Modify image details (by editing the image definition file).
o View, create, maintain, and delete the image definition (but not the image
itself).
o Create, copy, or store an image on a server or diskette.
A set of 20 standard image definition files is supplied with the LAN Server
product. You can select an image definition file based on diskette size,
diskette density, DOS version, and network adapter type.
Note:
There are 10 files for Ethernet requesters and 10 files for non-Ethernet
requesters.
Provide a diskette with an IPL image for each DOS LAN Services diskless
workstation you want to be started from diskette. Determine which DOS
requesters will be remote IPL requesters.
Note:
If you want to remote-IPL a DOS LAN Services workstation equipped with
IBM PS/2 Adapter/A for Ethernet Networks, reset the default adapter I/O
range from 0200-021F to 0280-029F.
To make use of remote IPL, you must install the DOS Remote IPL service on the
server supporting remote IPL.
You can create an image by using the graphical user interface or by running the
MAKEIMG utility from the command-line interface. For more information, refer
to the LAN Server Network Administrator Reference Volume 3: Network
Administrator Tasks.
For information about DOS LAN Services in general, see the DOS LAN Services and
Windows User's Guide.
ΓòÉΓòÉΓòÉ 6.3.4. Identifying Users ΓòÉΓòÉΓòÉ
Identify the set of users on each domain. Assign user IDs and passwords
(passwords are optional). Several user IDs can be referred to as a unit by
defining a group. A group is a set of user IDs that can be referred to by a
group ID. Groups provide a convenient way to refer to more than one user ID for
purposes such as sending messages or controlling access to network resources.
By default, all users in a domain (user type: USER) are assigned to a group
called USERS; all administrators (user type: ADMINISTRATOR) are assigned to a
group called ADMINS.
For example, if you define a group consisting of the users in an accounting
department, you can put the group ID in a group access list for a particular
resource, such as a department printer. If new users join the accounting
department, you can add them to the group. If users leave the department, their
access permissions to the department printer can be removed by deleting their
user IDs from the group.
Determine which users will be granted certain operator privileges. For more
information, refer to Operator Privileges.
To help plan for each user and group, use the User Worksheet and the Group
Worksheet. For information about defining users and groups, see the LAN Server
Access Control System.
ΓòÉΓòÉΓòÉ 6.4. Compatibility among Servers and Requesters ΓòÉΓòÉΓòÉ
This section describes the compatibility among various IBM server and requester
products on a LAN.
ΓòÉΓòÉΓòÉ 6.4.1. Coexistence of LAN Servers in a Single Domain ΓòÉΓòÉΓòÉ
Servers with different OS/2 LAN Server packages installed can coexist in a
single domain. For example, a domain can have an OS/2 LAN Server-Advanced
domain controller and two OS/2 LAN Server-Entry additional servers.
OS/2 LAN Server 2.0 and 3.0 servers can coexist with OS/2 LAN Server 4.0
servers on the same domain (with any as the domain controller).
ΓòÉΓòÉΓòÉ 6.4.2. Interoperability between LAN Servers and LAN Requesters ΓòÉΓòÉΓòÉ
The access capabilities of various IBM LAN Requester products to resources on
IBM LAN Server domains are described in LAN Server 4.0 Client/Server
Interoperability. The following four areas are covered:
o Logging on to a domain
o Administering a domain
o Accessing shared resources across domains
o Using domain services
The IBM LAN Server domains illustrated are:
o PC LAN Program 1.31 (or later) Communications Manager/2 or DATABASE 2 OS/2
(SBCS systems only)
o OS/2 LAN Server 1.3
o OS/2 LAN Server 2.0
o OS/2 LAN Server 3.0
o OS/2 LAN Server 4.0
The IBM LAN Requester products addressed are:
o The PC LAN Program 1.31 (or later) Base Services Requester (also requires IBM
LAN Support Program; SBCS systems only)
o The PC LAN Program 1.31 (or later) Communications Manager/2 or DATABASE 2
OS/2 Requester (also requires IBM LAN Support Program; SBCS systems only)
o OS/2 LAN Requester shipped with OS/2 Extended Edition 1.3
o OS/2 LAN Requester shipped with LAN Server 2.0, 3.0, and 4.0
o DOS LAN Requester shipped with OS/2 LAN Server 2.0 or 3.0 (also requires IBM
LAN Support Program)
o LAN Enabler 2.0 (includes OS/2 LAN Requester and DOS LAN Requester)
o DOS LAN Services shipped with IBM OS/2 LAN Server Version 4.0
ΓòÉΓòÉΓòÉ 6.4.3. LAN Server 4.0 Client/Server Interoperability ΓòÉΓòÉΓòÉ
LAN Server 4.0 Client/Server Interoperability illustrates the capabilities of
various requester products when used with various server products. The table
distinguishes the following capabilities:
Resource access Determines connectivity to file, print, and serial
device resources.
Logon services Determine validation of domain logon requests.
Domain awareness Determines the ability to connect to resources by
alias, to launch network applications, and to use
other centrally administered domain services.
Administrative capabilities Determine the ability to administer servers and
domains.
Only LAN Server servers can participate as full servers within a LAN Server
domain. Users access resources on other servers, either by referring to the
server and its resource by name, using a Universal Naming Convention (UNC) name
such as \\SERVER1\C-DRIVE, or by connecting to a cross-domain alias. A
cross-domain alias refers to a server outside the domain and is created like a
normal alias, except that the server is not defined within the domain.
A user logged on to an OS/2 or DOS LAN Requester can connect to resources on
any number of servers, whether or not the servers are within the user's domain.
However, when a server outside the domain has user-level security, the user
must either be defined on that server with the same password as in the logon
domain, or access the resource as a guest, assuming that the guest account
(usually GUEST) has access to the resource.
When passwords are assigned to shares (share-level security), the NET USE
command must be used so that the password can be specified on the command.
Note:
Abbreviations and numbers in parentheses are explained at the bottom of
the table.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 5. LAN Server 4.0 Client/Server Interoperability Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CLIENTS Γöé SERVERS Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé PCLP Γöé PCLP Γöé LAN Γöé LAN Γöé MICROSOFT Γöé LAN Γöé LAN Γöé
Γöé Γöé 1.31 OR Γöé 1.31 Γöé SERVEΓöé SERVERΓöé LAN Γöé SERVERΓöé SERVEΓöé
Γöé Γöé LATER Γöé OR Γöé 2.0 Γöé 4.0 Γöé MANAGER; Γöé 4.0 Γöé 4.0 Γöé
Γöé Γöé (BASE Γöé LATER Γöé OR Γöé Γöé WINDOWS NT Γöé PEER Γöé PEER Γöé
Γöé Γöé SER- Γöé (ES)(7Γöé 3.0 Γöé Γöé AND NTAS; Γöé SER- Γöé SER- Γöé
Γöé Γöé VICES)(7Γöé Γöé Γöé Γöé WINDOWS FOR Γöé VICES Γöé VICESΓöé
Γöé Γöé Γöé Γöé Γöé Γöé WORKGROUPS Γöé FOR Γöé FOR Γöé
Γöé Γöé Γöé Γöé Γöé Γöé Γöé OS/2 Γöé DOS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PCLP 1.31 or Γöé R Γöé R(1),LΓöé2R(1),Γöé(R(1),LΓöé2R(1) Γöé R(1,3)Γöé R(1,3Γöé
Γöé later (Base Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé Services)(7) Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PCLP 1.31 or Γöé R Γöé L,A Γöé Γöé Γöé Γöé Γöé Γöé
Γöé later (ES)(7) Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OS/2 LAN Γöé R Γöé R Γöé R,L,DΓöéAR,L,D,Γöé R Γöé R(3) Γöé R(1,3Γöé
Γöé Requester Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé (shipped with Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé LAN Server 2.0 Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé or 3.0, or LAN Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé Enabler 2.0) Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OS/2 LAN Γöé R Γöé R Γöé R,L,DΓöéAR,L,D,Γöé R Γöé R(3) Γöé R(1,3Γöé
Γöé Requester Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé (shipped with Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé LAN Server Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé 4.0) Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS LAN Γöé R Γöé R Γöé R,L,DΓöéAR,L,D,Γöé(R) Γöé R(3) Γöé R(1,3Γöé
Γöé Requester Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé (shipped with Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé LAN Server 2.0 Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé or 3.0) Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS LAN Ser- Γöé R Γöé R Γöé R,L,DΓöéAR,L,D,Γöé(R) Γöé R(3) Γöé R(1,3Γöé
Γöé vices (shipped Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé with LAN Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé Server 4.0) Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 5. LAN Server 4.0 Client/Server Interoperability Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CLIENTS Γöé SERVERS Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé PCLP Γöé PCLP Γöé LAN Γöé LAN Γöé MICROSOFT Γöé LAN Γöé LAN Γöé
Γöé Γöé 1.31 OR Γöé 1.31 Γöé SERVEΓöé SERVERΓöé LAN Γöé SERVERΓöé SERVEΓöé
Γöé Γöé LATER Γöé OR Γöé 2.0 Γöé 4.0 Γöé MANAGER; Γöé 4.0 Γöé 4.0 Γöé
Γöé Γöé (BASE Γöé LATER Γöé OR Γöé Γöé WINDOWS NT Γöé PEER Γöé PEER Γöé
Γöé Γöé SER- Γöé (ES)(7Γöé 3.0 Γöé Γöé AND NTAS; Γöé SER- Γöé SER- Γöé
Γöé Γöé VICES)(7Γöé Γöé Γöé Γöé WINDOWS FOR Γöé VICES Γöé VICESΓöé
Γöé Γöé Γöé Γöé Γöé Γöé WORKGROUPS Γöé FOR Γöé FOR Γöé
Γöé Γöé Γöé Γöé Γöé Γöé Γöé OS/2 Γöé DOS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Microsoft LAN Γöé R Γöé R Γöé R,L,AΓöé R,L,A Γöé R,L,A Γöé R(3) Γöé R(1,3Γöé
Γöé Manager; Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé Windows NT and Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé NTAS; Windows Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé for Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé Workgroups; Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé Workgroup Con- Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé nection for Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé DOS Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ABBREVIATIONS: Γöé
Γöé Γöé
Γöé o R = access to shared resources (file, print, serial) Γöé
Γöé o L = domain logon capability Γöé
Γöé o D = domain services (aliases, application definitions, etc.) Γöé
Γöé o A = administrative capabilities Γöé
Γöé o ES = Extended Services Γöé
Γöé o PCLP = PC LAN Program Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTES: Γöé
Γöé Γöé
Γöé 1. Remote access to serial devices is not supported. Γöé
Γöé 2. The network administrator defines a user ID that matches the machine Γöé
Γöé name of the PC LAN Program Base Services workstation. When the work- Γöé
Γöé station issues a NET USE command, the machine name is validated against Γöé
Γöé the defined user IDs. Γöé
Γöé 3. Peer Services for DOS and OS/2 are limited to sharing with one client at Γöé
Γöé a time (single session). Γöé
Γöé 4. Administrative capability from the DOS LAN Requester client is available Γöé
Γöé only from the LAN Server application programming interface (API). A Γöé
Γöé large number of categories that support remote network administration Γöé
Γöé are supported. For more information, refer to the LAN Server Program- Γöé
Γöé ming Guide and Reference. Γöé
Γöé 5. In addition to the API support described in the previous note, DOS LAN Γöé
Γöé Services for LAN Server 4.0 includes the NET ADMIN command, which allows Γöé
Γöé full command line administration of LAN Server. Γöé
Γöé 6. PCLP and Microsoft servers cannot be defined within a LAN Server domain; Γöé
Γöé access to those resources are cross-domain. Γöé
Γöé 7. PC LAN Program is available on SBCS systems only. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7. LAN Services Installation and Configuration ΓòÉΓòÉΓòÉ
This chapter assists you in performing the following tasks:
o Installing and configuring the OS/2 LAN Server component of the LAN Server
product for the first time
Note:
The OS/2 LAN Server component consists of a number of installable
components or functions.
o Installing and configuring the OS/2 LAN Requester component of the LAN Server
product for the first time
Note:
The OS/2 LAN Requester component consists of a number of installable
components or functions.
o Reinstalling and reconfiguring the OS/2 LAN Server or OS/2 LAN Requester
component of the LAN Server product
o Removing the OS/2 LAN Server or OS/2 LAN Requester component of the LAN
Server product or some of their functions
o Upgrading OS/2 LAN Server Version 2.0 or 3.0
o Upgrading a PC LAN Program Version 1.3 (or later) server
o Upgrading a LAN Server 2.0 or 3.0 OS/2 LAN Requester
o Upgrading the OS/2 LAN Requester component of LAN Enabler 2.0
o Creating custom installation diskettes for workstation users
o Creating a response file to be used for lightly attended and unattended
installations
Note:
If you plan to set up a remote installation of OS/2 LAN Server or
OS/2 LAN Requester, read Remote Installation.
refers to installing the OS/2 LAN Server or OS/2 LAN Requester component of the
LAN Server product on a workstation that already has either of these LAN Server
components installed.
Upgrading refers to installing the following:
o The OS/2 LAN Server component of the LAN Server product on a workstation that
has a previous version of OS/2 LAN Server or PC LAN Program Version 1.3 (or
later) installed.
o The OS/2 LAN Requester component of the LAN Server product on a workstation
that has a previous version of OS/2 LAN Requester installed.
The installation of DOS LAN Services is documented in Installing DOS LAN
Services. Also see Changing the DOS LAN Services Configuration.
The installation and configuration tasks described in this chapter can be
performed by any user.
The program that helps you install and configure the OS/2 LAN Server and OS/2
LAN Requester components of the LAN Server product is called the LAN Services
installation/configuration program. For consistency, the term LAN Services
(instead of LAN Server) is used in contexts dealing with installation and
configuration tasks and their results. The terms OS/2 LAN Server and OS/2 LAN
Requester are used when a distinction needs to be made between the two
components. For example, the OS/2 LAN Server installation path is different
from the OS/2 LAN Requester installation path.
As the name indicates, the LAN Services installation/configuration program
involves both installation and configuration. The program enables you to
configure LAN Services before actually copying the installation files to your
hard disk.
Installing OS/2 LAN Server and Installing OS/2 LAN Requester guide you through
LAN Services installation and configuration windows.
Although the LAN Services installation/configuration program handles most
configuration tasks, some tasks can require editing the LAN configuration
files. For more information, refer to the LAN Server Network Administrator
Reference Volume 2: Performance Tuning.
The Fault Tolerance function and the Remote IPL service must be configured
through separate utilities after installation or before removal. For detailed
information, refer to the LAN Server Network Administrator Reference Volume 3:
Network Administrator Tasks. Some upgrading tasks may require running migration
utilities before and after installation. For detailed procedures, see Migration
of Data and Migrating PCLP to an IBM OS/2 LAN Server Environment.
This chapter occasionally refers to configuration files and the subdirectories
where LAN Services is installed. The main configuration file is the IBMLAN.INI
file. For detailed information about configuration files, refer to the LAN
Server Network Administrator Reference Volume 2: Performance Tuning.
Note:
The LAN Adapter and Protocol Support configuration file is the
PROTOCOL.INI file. For more information, see the MPTS - AnyNet for OS/2:
Configuration Guide.
For a detailed discussion of the directory structure, refer to the LAN Server
Network Administrator Reference Volume 3: Network Administrator Tasks. For now,
note that:
o Most of LAN Services is installed in the \IBMLAN subdirectory.
o The IBM Multi-Protocol Transport Services - AnyNet for OS/2 component is
installed in the \IBMCON subdirectory.
o The User Profile Management component is installed in the \MUGLIB
subdirectory.
o Most of the 386-HPFS component is installed in the \IBM386FS subdirectory.
o The MUGLIB and IBM386FS directories are always located on the OS/2 startup
drive.
ΓòÉΓòÉΓòÉ 7.1. Before You Install ΓòÉΓòÉΓòÉ
To gain a good understanding of the installation and configuration process,
read the following sections carefully before you begin installing and
configuring LAN Services.
ΓòÉΓòÉΓòÉ 7.1.1. Installation Requirements and Restrictions ΓòÉΓòÉΓòÉ
Ensure that you understand the following requirements and restrictions, and
take the appropriate actions before you install the LAN Server product:
o OS/2 must be installed on your workstation. Refer to the documentation
provided with OS/2 for installation information.
o Before and after you install or reinstall OS/2 or the LAN Server product on a
workstation that already has a version of OS/2 LAN Server installed, you may
need to run utilities that ensure proper migration of important data. To find
out if you must run any utilities and, if so, when and how to run them, read
the section that applies to you in Migration of Data. Refer to Upgrading LAN
Server 2.0 or 3.0, for an example procedure.
If you plan to install OS/2 on a 386-HPFS workstation, read also Upgrading or
Reinstalling on 386-HPFS Servers.
o To install FFST/2 on a server or a requester, select OS/2 Serviceability and
Diagnostics Aids during OS/2 installation. If OS/2 is already installed, you
can install FFST/2 using the Selective Install. Refer to the documentation
provided with OS/2 for installation information.
o If you are installing the OS/2 LAN Server component and enabling the remote
IPL service, you must configure at least one adapter for the IEEE 802.2
protocol.
o Do not run the LAN Services and Communications Manager/2 or DATABASE 2 OS/2
installation programs at the same time. Running these programs
simultaneously leads to unpredictable results.
o Shut down and restart your workstation after each installation.
o It is strongly recommended that you either install LAN Server on drive C or
create all of your logical drives before beginning installation. If you
install the LAN Server product on a drive other than drive C, and you plan to
use FDISKPM to create new logical drives, it is important to consider the
location of any new drives you create. If a new drive created with FDISKPM
is located before the drive where the LAN Server product is installed, you
must reinstall LAN Server. If a new drive created with FDISKPM is located
after the drive where the LAN Server product is installed, you do not have to
reinstall LAN Server.
o Before you begin installation, run CHKDSK on all logical drives that you have
created. To run CHKDSK, type at the OS/2 command prompt:
CHKDSK x: /F
where x is a logical drive letter. The /F switch specifies that the CHKDSK
command fix any errors found on a disk or directory. Then press Enter.
o To install Fault Tolerance on a server with only two hard disks, ensure that
you have enough free space for mirroring. To specify a primary HPFS partition
during base operating system installation, refer to Disk Requirements for
Fault Tolerance and the OS/2 installation documentation. Ensure that you
have sufficient hard-disk storage on your primary partition. Some LAN Server
components, such as User Profile Management, are always installed on the
startup drive. To calculate hard-disk requirements, see Hard-Disk Estimating
Worksheet for OS/2 LAN Server Workstations.
o To install the Local Security function on a server workstation, specify a
primary HPFS partition on the physical hard disk containing the startup
drive. To specify a primary HPFS partition during base operating system
installation, refer to Disk Requirements for Fault Tolerance and the OS/2
installation documentation. Ensure that you have sufficient hard-disk
storage on your primary partition. Some LAN Server components, such as User
Profile Management, are always installed on the startup drive. To calculate
hard-disk requirements, see Hard-Disk Estimating Worksheet for OS/2 LAN
Server Workstations.
o The LAN Server product does not support remote IPL for OS/2 1.3 requesters.
A LAN Server 2.0 machine with the capability to remote-IPL OS/2 1.3
requesters on the domain does not maintain this capability when upgraded to
the LAN Server 4.0 product.
ΓòÉΓòÉΓòÉ 7.1.2. Installation Package ΓòÉΓòÉΓòÉ
The LAN Server product is provided in two separate packages:
o LAN Server-Entry
o LAN Server-Advanced
Each installation package consists of a CD-ROM or diskettes containing OS/2 LAN
Server, OS/2 LAN Requester, DOS LAN Services, LAN Support Program, Productivity
Aids, IBM Multi-Protocol Transport Services - AnyNet for OS/2, and online
documentation.
Each installation package also includes documentation to support installation,
configuration, and proper running of the shipped products.
When you acquire the LAN Server product, you receive all the software you need
to install and set up a LAN Server LAN. You are authorized to install the
requester and the server software on your server workstation. To set up
additional requesters, you need to install copies of the requester software on
the requester workstations. The requester function is a distributed feature.
To copy the software for additional requesters, you must acquire a license for
each requester workstation. This license allows you to copy the requester
software in your LAN Server package.
The requester functions provided by the LAN Server-Entry and LAN
Server-Advanced packages are the same. No additional CD-ROM, diskettes, or
publications are provided with the distributed feature license. You must
acquire a license for each requester (OS/2 or DOS) on your network. The
license provided with the initial LAN Server package includes a license for the
requester function installed on the server.
The following sections list the OS/2 LAN Server and OS/2 LAN Requester
functions installed by the LAN Services installation/configuration program for
each of the two packages. The DOS LAN Services component is separately
installed and is identical for both packages. OS/2 LAN Server and OS/2 LAN
Requester must be installed on either a 386- or 486-based or higher
workstation. DOS LAN Services can be installed on a 286-based (or higher)
workstation.
ΓòÉΓòÉΓòÉ 7.1.2.1. LAN Server-Entry ΓòÉΓòÉΓòÉ
LAN Server-Entry servers are designed for use as both a server and a requester.
If you use a LAN Server-Entry server locally for uses other than server
functions, network performance may be adversely affected. The workstation can
also be used as a requester.
On larger LANs, LAN Server-Entry provides the same performance level as LAN
Server-Advanced for printing and as a domain controller. If you do not need
the additional features provided by LAN Server-Advanced, LAN Server-Entry
provides a low-cost alternative.
Note:
Some of these functions are not installed by default. You may need to
add the additional functions you want to use. For more information about
the LAN Server functions, refer to Supported Functions.
LAN Server-Entry contains the OS/2 LAN Server, OS/2 LAN Requester, and DOS LAN
Services components. For a functional description of DOS LAN Services, see DOS
LAN Services and Windows or Installing and Optimizing DOS LAN Services.
The OS/2 LAN Server component supports the following functions:
o Server
Notes:
1. Requester code is standard on a server installation. The OS/2 LAN
Requester code is automatically installed with the server.
2. This function includes the Alerter, Replicator, DCDB Replicator (on
domain controllers and backup domain controllers only), Netlogon,
Netrun, Timesource, and Messenger services.
o DOS Remote IPL service
o First Failure Support Technology/2 (FFST/2)
o Generic Alerter service
o LAN Server Administration GUI
o LAN Server Applications Development Toolkit
o Loop-Back driver
o Migration Import Utility (Domain Controller only)
o Network DDE and Clipboard
o Network Messaging
o OS/2 Remote IPL service
o Server installation/configuration program
o Uninterruptible Power Supply (UPS) Support
o User Profile Management (UPM)
o Virtual DOS LAN API support
For a discussion of these functions, refer to Supported Functions.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: The migration utility is Γöé
Γöé not supported in the DBCS product. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The OS/2 LAN Requester component supports the following functions:
o Requester
Note:
This function includes the Messenger service.
o Fault Tolerance Administration
Note:
Fault Tolerance Administration is active only if the Fault Tolerance
function has been installed on the server. The Fault Tolerance
server function is available only with LAN Server-Advanced.
o First Failure Support Technology/2 (FFST/2)
o LAN Server Administration GUI
o LAN Server Applications Development Toolkit
o Network DDE and Clipboard
o Network Messaging
o User Profile Management (UPM)
o Peer service
o Requester installation/configuration program
o Virtual DOS LAN API support
ΓòÉΓòÉΓòÉ 7.1.2.2. LAN Server-Advanced ΓòÉΓòÉΓòÉ
LAN Server-Advanced provides a high-performance, high-availability file server.
The 386 high performance file system (386 HPFS) provides improved performance
over the HPFS provided with OS/2. LAN Server-Advanced also allows you to mirror
hard-drives, which allows you to quickly recover from hardware failures. You
can also put multiple network adapter cards in a single server to protect
against hardware failure on a single adapter card.
LAN Server-Advanced supports small networks to ones with up to 1000 connected
users. The requester functions are the same as those with the LAN Server-Entry
package. To decide between LAN Server-Entry and LAN Server-Advanced, consider
your network performance and reliability needs.
LAN Server-Advanced provides three server functions in addition to the
functions provided by the LAN Server-Entry package:
o 386 high performance file system (386 HPFS)
o Fault Tolerance for Hard Disk (disk mirroring and duplexing)
o Local Security for the 386 HPFS
For a discussion of these functions, refer to Overview of the LAN Server
Product.
The 386-HPFS function is installed on server workstations with HPFS partitions
along with the LAN Server-Entry server functions. If you install LAN
Server-Advanced on a server with only FAT partitions, the installation program
installs only the LAN Server-Entry server functions.
You can enhance the Entry package by purchasing the Advanced package and
installing it on top of the Entry package. The installation and configuration
program handles this situation as a reinstallation and not as a completely new
installation.
ΓòÉΓòÉΓòÉ 7.1.3. Window Layout ΓòÉΓòÉΓòÉ
Most windows that you see during installation and configuration display one or
more of the following push buttons:
OK Confirms the selections you have made in the present window and takes
you to the next window.
Cancel Cancels any selections you have made in the present window and
returns you to the previous window.
Help Displays a window that provides online help for the selected item or
field (if an item or field was selected) or help for the present
window (if no item or field was selected). If the selected item is
in a list box, the corresponding help provides general information
for the list box.
Note:
Pressing F1 has the same result as selecting the Help push button.
Retry Repeats a process after you made an attempt to correct a faulty
situation.
Exit Discards all changes you might have made during the LAN Services
installation/configuration program and exits the program. If you
select this push button on any of the windows instructing you to
insert a specific installation diskette, you exit the LAN Services
installation/configuration program, leaving the product installation
in an unknown state.
The default push button on each window is highlighted and can be selected by
either using the mouse to click on it or pressing Enter.
Grayed-out push buttons or fields indicate options that are not available.
ΓòÉΓòÉΓòÉ 7.1.4. Error Messages ΓòÉΓòÉΓòÉ
As you proceed with the LAN Services installation/configuration program, error
messages may be displayed. For example, you could be informed that an incorrect
name was entered. For information about a particular error message, select Help
or press F1.
Note:
During unattended remote installation, error messages are not displayed.
Error and history information is logged to the IBMLANER.LOG and
IBMLSHST.LOG files on the target workstation and to the remote log files
specified by the /L1 or /L2 switch in the installation command
statement. For information about remote installation, see Remote
Installation.
ΓòÉΓòÉΓòÉ 7.1.5. Error Log ΓòÉΓòÉΓòÉ
Errors encountered during LAN Services installation and configuration are
recorded in the IBMLANER.LOG file, which is an ASCII file residing in the
\OS2\INSTALL subdirectory. Each entry is preceded by a date and time stamp and
is self-explanatory.
During remote installation, errors are recorded in the IBMLANER.LOG file on the
target workstation. You can also set up a remote error log of your choosing on
the code server by specifying the /L1 switch in the installation command
statement. For more information, see Remote Installation.
ΓòÉΓòÉΓòÉ 7.1.6. Help for Installation Errors ΓòÉΓòÉΓòÉ
For help with an error, select Help when the error message is displayed. You
can also receive specific help at any time by typing the following command at
an OS/2 command prompt:
HELP error_code_number
The installation program also copies a list of error messages along with
explanations and solutions into an ASCII file, ERROR.TXT, residing in the
\OS2\INSTALL directory. You can print this file or you can view it online with
the system editor or another text editor. (With the file opened from an
editor, you can use the automatic search function to find the code number of
the error message you have encountered.)
If the installation fails before ERROR.TXT is copied to the hard disk, you must
unpack the file from the installation diskette to print or view the contents.
To unpack the file, insert Server - Disk 1 or Requester - Disk 1 into drive A
and proceed to an OS/2 command prompt (ideally in the \OS2\INSTALL directory).
Type the following command:
A:PKUNZIP2 A:ERRORSRV.ZIP
OR
A:PKUNZIP2 A:ERRORREQ.ZIP
These commands unpack the ERRORSRV.TXT or ERRORREQ.TXT file into the directory
from which you initiated the command (\OS2\INSTALL). The contents of the file
can now be accessed.
ΓòÉΓòÉΓòÉ 7.1.7. History Log ΓòÉΓòÉΓòÉ
A record of the execution of the LAN Services installation/configuration
program is maintained in the IBMLSHST.LOG file, which is an ASCII file residing
in the \OS2\INSTALL subdirectory. Each execution of the LAN Services
installation/configuration program is identified by a date and time stamp, the
name of the installation package used, and the main component (server or
requester) being installed.
During remote installation, history information is recorded in the IBMLSHST.LOG
file on the target workstation. You can also set up a remote history log of
your choosing on the code server by specifying the /L2 switch in the
installation command statement. See Remote Installation, for information.
ΓòÉΓòÉΓòÉ 7.1.8. Location of Backup Configuration Files ΓòÉΓòÉΓòÉ
As a result of running the LAN Services installation/configuration program,
changes could have been made to the configuration files. Unmodified versions
of the changed files are saved as follows:
File Name Backup Name
CONFIG.SYS x:\IBMLAN\BACKUP\CONFIG.000
IBMLAN.INI x:\IBMLAN\BACKUP\IBMLAN.000
STARTUP.CMD x:\IBMLAN\BACKUP\STARTUP.000
PRIVINIT.CMD x:\IBMLAN\BACKUP\PRIVINIT.000
SRVAUTO.PRO x:\IBMLAN\BACKUP\SRVAUTO.000
PROTOCOL.INI x:\IBMLAN\BACKUP\PROTOCOL.000
where:
o x indicates the drive where LAN Services is installed.
o The file extension .000 is the same for all backed-up files from the same
execution of the LAN Services installation/configuration program. (The first
set of backed-up files has extension .001, the second set .002, and so on.)
Note:
Only modified files are backed up.
ΓòÉΓòÉΓòÉ 7.2. Upgrading ΓòÉΓòÉΓòÉ
You can upgrade a PC LAN Program Version 1.3 (or later) server, OS/2 LAN Server
(1.3, 2.0, or 3.0), or OS/2 LAN Requester (from Extended Edition 1.3, LAN
Server 2.0 or 3.0, or LAN Enabler 2.0). The LAN Server product provides the
migration utilities necessary to upgrade a PC LAN Program Version 1.3 (or
later) server or a LAN Server 2.0 or 3.0 server.
During installation, the LAN Services installation/configuration program
modifies your current IBMLAN.INI file according to the selections you made in
the installation and configuration windows. Settings in your IBMLAN.INI file
that are not handled by the LAN Services installation/configuration program,
such as the alertnames and othdomains parameters, are preserved. For the
structure of the IBMLAN.INI file and meaning of parameter values, refer to the
LAN Server Network Administrator Reference Volume 2: Performance Tuning.
Before you begin upgrading, ensure that your server and requester files and
directories can be found by the LAN Services installation/configuration
program. For the proper directory structure for the LAN Server product, see the
LAN Server Network Administrator Reference Volume 3: Network Administrator
Tasks. If you are upgrading a server, refer to the next section, Migration of
Data. For an example procedure, refer to Upgrading LAN Server 2.0 or 3.0.
ΓòÉΓòÉΓòÉ 7.3. Migration of Data ΓòÉΓòÉΓòÉ
When you install a new version of the operating system, upgrade a previous
version of OS/2 LAN Server, or reinstall the LAN Server 4.0 product, you can
consider preserving important data, such as remote IPL images, user and group
information, or access control information.
This section briefly explains how to migrate such data. Note that it pertains
only to domain controllers, backup domain controllers, and additional servers,
since requesters do not store this data. Refer to topic LAN Services
Installation and Configuration for the difference between reinstalling and
upgrading.
ΓòÉΓòÉΓòÉ 7.3.1. Remote IPL Data ΓòÉΓòÉΓòÉ
If you are upgrading OS/2 LAN Server 2.0 or 3.0 or reinstalling the LAN Server
4.0 product, DOS remote IPL data is migrated unless you select to remove the
DOS Remote IPL service during installation and configuration. When you upgrade
LAN Server 2.0 or 3.0, or reinstall the LAN Server 4.0 product, the same is
true for OS/2 remote IPL data if you do not select to remove the OS/2 Remote
IPL service.
Remember that the LAN Server product does not support the remote IPL of OS/2
1.3 requesters. A LAN Server 2.0 workstation with the capability to remote-IPL
OS/2 1.3 requesters on the domain does not maintain this capability when
upgraded to the LAN Server 4.0 product.
Remote IPL images prepared by PC LAN Program Version 1.3 (or later) are not
compatible with the LAN Server product. Therefore, you must re-create IPL
images after upgrading a PC LAN Program Version 1.3 (or later) server. Existing
remote IPL or DOS LAN Requester image diskettes must be rebuilt whenever DOS or
DOS LAN Requester is updated on the remote IPL server.
ΓòÉΓòÉΓòÉ 7.3.2. Domain Control and Access Control Profile Information ΓòÉΓòÉΓòÉ
Domain control information, such as group and user information and the access
control profiles, can be migrated in different ways depending on the server
version you upgrade and the current and new file system of your workstation.
Note:
If you install an additional server over a domain controller, the domain
control database (DCDB) is discarded, with the exception of the user and
group information stored in the NET.ACC file (which includes the access
control profiles). The user and group information on the old domain
controller will be replaced with the user information from the new
domain.
Installing a backup domain controller over a domain controller is
handled in essentially the same way as installing an additional server
over a domain controller, with the exception that the \DCDB subdirectory
is recreated to ensure correct functioning of the DCDB Replicator
service.
ΓòÉΓòÉΓòÉ 7.3.2.1. Upgrading a PC LAN Program Version 1.3 (or Later) Server ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: Information in this section Γöé
Γöé does not apply to DBCS systems. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
You must run the migration export utility to save the DCDB of a PC LAN Program
Version 1.3 (or later) domain controller before installing a new OS/2 version
or running the LAN Services installation/configuration program. The migration
export utility is provided on the CD-ROM or Requester - Disk 1 as part of the
installation package. When you run the LAN Services installation/configuration
program, be sure to follow the Tailored path and to install the migration
import utility. Run the LAN Services installation/configuration program on all
additional servers on your domain.
When the LAN Services installation/configuration program is completed, make
sure that all additional servers are started and running. Then run the
migration import utility on the domain controller to reapply the information
saved by the migration export utility. This method migrates the access control
profiles as well as other domain control information. You do not need to run
the migration import utility for each additional server.
For more details, refer to Migrating PCLP to an IBM OS/2 LAN Server
Environment.
ΓòÉΓòÉΓòÉ 7.3.2.2. Upgrading the LAN Server 2.0 or 3.0 Product or Reinstalling ΓòÉΓòÉΓòÉ
the LAN Server 4.0 Product
Read the section that applies to you, depending on the current and new file
system of your workstation.
ΓòÉΓòÉΓòÉ 7.3.2.2.1. Preserving the same file system (either FAT or HPFS) ΓòÉΓòÉΓòÉ
To upgrade an LAN Server 2.0 or 3.0 domain controller (or to reinstall a LAN
Server domain controller), follow the Easy or Tailored path. The LAN Services
installation/configuration program offers the choice of using existing domain
control definitions (that is, not reinitializing the DCDB) or not using
existing control definitions (that is, reinitializing or erasing the DCDB).
If you choose not to reinitialize the DCDB, it is saved. This procedure takes
care of migrating the access control profiles if you are preserving either the
FAT or HPFS. If you are upgrading or reinstalling on a workstation that
already has the 386 HPFS installed and you want to preserve it, read Preserving
the 386 HPFS.
ΓòÉΓòÉΓòÉ 7.3.2.2.2. Changing the file system to 386 HPFS ΓòÉΓòÉΓòÉ
To migrate access control profiles properly when you are installing a 386 HPFS
over an HPFS or FAT file system or removing the 386 HPFS, you must run the
BACKACC and RESTACC utilities.
The BACKACC utility backs up the user accounts file (NET.ACC), the audit
information file (NET.AUD), and the access control profiles. The RESTACC
utility restores previously backed-up access control information.
Both the BACKACC and RESTACC utilities can be obtained from the CD-ROM or from
Requester - Disk 1.
For detailed upgrade information, refer to Upgrading LAN Server 2.0 or 3.0. If
you are using a software distribution manager (SDM) such as the LAN CID
Utility, refer to Upgrading LAN Server 2.0 or 3.0 Using the LAN CID Utility.
ΓòÉΓòÉΓòÉ 7.3.2.2.3. Preserving the 386 HPFS ΓòÉΓòÉΓòÉ
Before installing LAN Server 4.0-Advanced on a LAN Server 2.0-Advanced
workstation, you must upgrade the current operating system (OS/2 1.3) to OS/2
2.1 or higher.
To bypass OS/2's HPFS file system's inability to read files that are protected
by 386-HPFS access control profiles run the PREPACL and THIN386 utilities as
described in the step-by-step instructions in Attended Installation. These
instructions apply only to a CD-ROM or diskette-based installation of OS/2. If
you are using an SDM, such as the LAN CID Utility, to upgrade or reinstall, you
need to run the THIN386 utility only. Refer to Unattended Remote Installation
and REXX Command File Example.
Both the PREPACL and THIN386 utilities are provided on the CD-ROM or on Server
- Disk 1.
If you are reinstalling LAN Server 3.0-Advanced, you must run the PREPACL and
THIN386 utilities only if you are also reinstalling the operating system.
ΓòÉΓòÉΓòÉ 7.3.2.3. Upgrading or Reinstalling on a Different Hard Disk ΓòÉΓòÉΓòÉ
If you are upgrading a previous version of OS/2 LAN Server on a different hard
disk and want to migrate DCDB and access control profile information, you
should run the installation and configuration program twice.
First, follow the guidelines in Upgrading a PC LAN Program Version 1.3 (or
Later) Server or in Upgrading the LAN Server 2.0 or 3.0 Product or
Reinstalling, and install the LAN Server product on the same disk on which the
previous version was residing (for example, drive C).
When the new version has been installed on that drive, restart your system and
run the LAN Services installation/configuration program again. On the Hard
Disk window, specify the drive to which you want to move LAN Services (for
example, drive D). All files are then moved from the drive on which they
reside to the specified drive.
You might need to redefine aliases in the DCDB, since they may be pointing to
the wrong drive or path.
To migrate DCDB and access control profiles when reinstalling the LAN Server
product on a different hard disk, run the LAN Services
installation/configuration program and do not reinitialize the DCDB. You do not
need to run the LAN Services installation/configuration program twice. You may
need to redefine aliases in the DCDB, as they may be pointing to the wrong
drive.
Note:
The LAN Services installation/configuration program does not move the
current MUGLIB and IBM386FS subdirectories, if they exist, to a
different hard disk. These directories always remain on the OS/2 startup
drive.
ΓòÉΓòÉΓòÉ 7.4. Installation Paths ΓòÉΓòÉΓòÉ
The LAN Services installation/configuration program provides four paths for
installation:
o Easy
o Tailored
o Custom
o Remote
The remote installation path enables you to install LAN Services remotely from
a central server to target workstations that will be either requesters or
servers. See Remote Installation for procedures on how to set up and start
remote installation.
To install LAN Services directly on the local workstation using CD-ROM,
diskettes, or a custom diskette, continue with this chapter. The order in
which the windows are used for the Easy, Tailored, and custom installation
paths are explained in detail under Installing OS/2 LAN Serverand Installing
OS/2 LAN Requester.
ΓòÉΓòÉΓòÉ 7.4.1. Easy Installation Path ΓòÉΓòÉΓòÉ
During an initial installation, the Easy path enables you to use IBM-supplied
default values for all options except the server or requester name. You are
prompted for these names. The network adapter for use with LAN Services is
automatically selected, and you cannot change the associated NetBIOS resources.
Note:
The network adapter is automatically selected as long as it is a
supported adapter.
During an initial server installation following the Easy path, you can install
a domain controller or an additional server. You must, however, use the
Tailored path during a reinstallation to change the server type; for example,
to change an additional server to a domain controller or backup domain
controller. Remember that at least one server on the domain must be the domain
controller.
During an initial installation, the Easy installation path enables you to
install OS/2 LAN Server or OS/2 LAN Requester on any valid drive. The default
is the startup drive.
The IBM-supplied defaults are designed to meet most LAN environments. However,
consider the specific needs of the workstation on which you want to install LAN
Services, and use the Tailored installation path if it is more appropriate.
You can also reinstall or reconfigure later using the Tailored installation
path.
Note:
If you want to follow the Easy path for reinstallation, refer to
Reinstalling.
ΓòÉΓòÉΓòÉ 7.4.2. Tailored Installation Path ΓòÉΓòÉΓòÉ
You must follow the Tailored installation path to change the server type (for
example, to change an additional server to a domain controller or backup domain
controller).
Tailored installation enables you to customize your workstation. You can:
o Reinstall or upgrade, installing a different set of components than
previously installed.
o Select functions not provided on the Easy path. The following list details
the functions provided by the Tailored path that are not available through
the Easy path:
- DOS Remote IPL service
- Fault Tolerance for Hard Disk (LAN Server-Advanced)
- First Failure Support Technology/2 (FFST/2)
- Generic Alerter service
- Local Security for 386 HPFS (LAN Server-Advanced)
- Loop-Back Driver
- Migration Import Utility (Domain Controller only)
- OS/2 Remote IPL service
- Uninterruptible Power Supply (UPS) Support
- Virtual DOS LAN API Support
o Install less than the default set of components. Optional components in the
default set include:
- 386 HPFS (LAN Server-Advanced)
- LAN Server Administration GUI
- LAN Server Applications Development Toolkit
- LAN Services installation/configuration program
- Network DDE and Clipboard
- Network Messaging
o Modify IBM-supplied default installation and configuration parameters (or, if
you are reinstalling or upgrading, change previously set parameters).
o Change the hard disk on which LAN Services is installed. This change can be
made during a reinstallation.
o Select multiple network adapters for use with the LAN Server product.
o Remove OS/2 LAN Server (see Removing).
o Create a custom installation diskette (see Creating a Server Custom
Diskette).
o Create a response file for remote installation (see Creating a Response File
for an OS/2 Client).
o Copy product diskettes for remote installation (see Copying LAN Server
Product Diskettes to the Code Server).
Note:
The Easy path enables you to select the hard-disk drive only during
an initial installation.
ΓòÉΓòÉΓòÉ 7.4.3. Custom Installation Path ΓòÉΓòÉΓòÉ
Custom installation enables the network administrator to simplify installation
or reinstallation by providing individual users with a custom installation
diskette. A custom installation diskette contains installation and
configuration parameters selected by the network administrator following the
Tailored installation path.
Note:
Any user (with or without administrative authority) can create a custom
diskette for another user on the network. The term network
administrator, as used in this chapter in the context of custom
installation, helps to make a distinction between the actual creator of
the custom installation diskette and the person using the diskette.
Workstation users use the custom installation diskette (instead of Server -
Disk 1 or Requester - Disk 1) to support installation on their workstations of
the program code selected by the network administrator. They insert other
diskettes from the installation package as prompted. Custom installation
requires only limited input by the workstation user, and the network
administrator is assured that only specified code is installed.
ΓòÉΓòÉΓòÉ 7.5. Making Diskettes from CD-ROM ΓòÉΓòÉΓòÉ
To install the LAN Server product on a workstation that does not have a CD-ROM
drive, you first need to make diskettes from your LAN Server CD-ROM. Use blank,
formatted high-density (1.44 MB) diskettes.
To Make Diskettes from a CD-ROM:
1. Insert the LAN Server CD-ROM in the drive.
2. Start the CD-ROM installation program. Type d:INSTALL, where d is the
drive letter of the CD-ROM drive, and press Enter.
3. Select OK in the CD-ROM Welcome window.
4. Select Make 3.5-inch product diskettes in the CD-ROM Installation
window.
5. Select the backup diskettes you want to make:
o MPTS (3 diskettes)
o OS/2 LAN Server (2 diskettes)
o OS/2 LAN Requester (5 diskettes)
o DOS LAN Services and LAN Support Program (4 diskettes)
o Productivity Aids (3 diskettes)
You will be prompted to insert each diskette into the drive (you can
change the drive letter) and to label each diskette.
ΓòÉΓòÉΓòÉ 7.6. Installing OS/2 LAN Server ΓòÉΓòÉΓòÉ
Use the following instructions if you are installing the OS/2 LAN Server
component of the LAN Server 4.0 product for the first time, reinstalling OS/2
LAN Server, or upgrading a previous server version. You may want to use the
OS/2 LAN Server Installation Worksheet to prepare for installation and
configuration.
Note:
The installation of OS/2 LAN Server automatically includes the
installation of OS/2 LAN Requester. For requester-only installation, see
Installing OS/2 LAN Requester.
Before you run the LAN Services installation/configuration program, be
sure to read Before You Install. If this installation is not the initial
one, read also Upgrading, Migration of Data, and Reinstalling,
Reconfiguring, or Removing.
You can run the LAN Services installation/configuration program locally either
from CD-ROM or diskette (always the case for initial installation), or from
hard disk (if you installed the LAN Services installation/configuration program
on your hard disk during a previous installation of OS/2 LAN Server). For
remote installation, refer to Remote Installation.
To run the LAN Services installation/configuration program from CD-ROM or
diskette, you must be in an active OS/2 full-screen or window session.
Hint:
Make backup copies (using the DISKCOPY command) of the diskettes in your
installation package, and run the LAN Services
installation/configuration program from the backup diskettes. Make sure
that the size of the backup diskettes matches the size of the original
diskettes, and that the diskettes you back up are all from the same
installation package.
Note:
When you have FAT-formatted hard drives, the following naming
restrictions apply:
o The user directory in the domain control database (DCDB) is given the name
specified by the UserID parameter. Therefore, it will be impossible to
create the directory if the value of the UserID parameter exceeds 8 bytes.
The LAN Server product returns an error when attempting to initialize a
user ID longer than 8 characters.
o The DCDB replicator will not fully replicate user directory names longer
than 8 characters.
To Begin an Easy or Tailored Server Installation:
1. Insert the LAN Server CD-ROM or Server - Disk 1 into the appropriate
drive.
2. Start the CD-ROM installation program or the diskette installation
program. To start the CD-ROM or diskette installation program, type
d:INSTALL, where d is the drive letter of the CD-ROM drive or diskette
drive, respectively, and press Enter.
Hint:
To run the LAN Services installation/configuration program from
the hard disk, substitute the following procedure for steps 1 and
2.
o Select LAN Services Installation/Configuration from the LAN Services
folder on the OS/2 desktop.
Notes:
a. If you do not want the LAN Server product to automatically detect
your adapter, invoke the INSTALL /NS command.
b. If you install the LAN Server 4.0 product on an OS/2 2.0
workstation, use the INSTALL /20 command. Several of the LAN
Server 4.0 functions, including the LAN Server Administration GUI,
will not be available on the OS/2 2.0 workstation. However, most
of the LAN Server command line functions will be available.
3. Select OK in the Welcome window (CD-ROM installation only).
4. Select Install OS/2 LAN Server in the Installation window (CD-ROM
installation only).
The IBM logo is displayed.
5. Select OK on the logo panel.
6. The Easy or Tailored Installation/Configuration window is displayed.
Select Easy if you want to follow the Easy installation path. (See Easy
Installation.)
Refer to Installation Paths to help you decide which path to select.
Select Tailored if you want to change the server type during a
reinstallation. Also, select Tailored if you plan to perform any of the
tasks in the list in Tailored Installation Path.
Note:
For a complete list of components in the Entry and Advanced
packages, refer to Installation Package.
Note:
In the event that the LAN Services installation/configuration program
cannot be run (for example, if the current operating system is not
compatible with the program), a message is displayed.
ΓòÉΓòÉΓòÉ 7.6.1. Easy Installation ΓòÉΓòÉΓòÉ
If you follow the Easy path for an initial installation of OS/2 LAN Server,
IBM-supplied default installation and configuration values are used. However,
you must supply the name of the server.
The following default components are installed during the initial Easy
installation of LAN Server-Entry and LAN Server-Advanced. For a complete list
of components in the Entry and Advanced packages, refer to Installation
Package.
o Entry package
- Server
Notes:
1. Requester code is standard on a server installation. The OS/2 LAN
Requester code is automatically installed with the server.
2. This function includes the Alerter, Replicator, DCDB Replicator
(on domain controllers and backup domain controllers only),
Netlogon, Netrun, Timesource, and Messenger services.
- LAN Server Administration GUI (requires OS/2 2.1 or higher)
- LAN Server Applications Development Toolkit
- Server installation/configuration program
- User Profile Management (UPM)
o Advanced package
- All the Entry package components
- 386 HPFS
If you are reinstalling OS/2 LAN Server, the default values are those supplied
during the previous installation. When using the Easy installation path for
reinstalling, you can reinstall only components that are currently installed.
If you use a higher-level package when reinstalling, the additional default
component or components of that package are also installed.
Notes:
1. For the meanings of the OK, Cancel, Help, Retry, and Exit push buttons
displayed in the LAN Services installation and configuration windows,
see Window Layout.
2. Additional windows may appear to ensure that the LAN Server product
installs completely. For example, if you are installing from diskettes,
the LAN Services installation/configuration program displays windows
that prompt you to insert specific diskettes. When this occurs, follow
the instructions in the windows.
To Follow the Easy Path for a Server Installation:
1. Select Easy in the Easy or Tailored Installation/Configuration window.
2. If your workstation has more than one hard disk or more than one
partition on a single hard disk, and this is an initial installation,
the Installation Location window is displayed. Select OK to install OS/2
LAN Server on the default startup drive, or specify another drive and
then select OK.
3. If this is a reinstallation:
a. The Current MPTS Version Installed window is displayed. Select Yes
if you want to reinstall MPTS, and you may be prompted to insert MPTS
diskettes. If you do not want to reinstall MPTS, select No.
b. The Reinstallation Type window is displayed. Specify whether you want
to change server and domain names, reinstall, or do both. Then
select OK. (If you choose not to do both, some of the following
steps are skipped.)
4. In the Server Name window, type the server name and then select OK.
Notes:
a. The server and domain cannot have the same name. The server name
should not match any user ID or workstation name on the network.
The workstation name is specified by the computername parameter in
the IBMLAN.INI file.
b. The server and domain names are not case-sensitive and can be 1 to
15 characters (bytes) in length. The following characters are not
valid:
" / \ [ ] ; : , | < > + = ? *
Characters below X'21' are also not valid.
c. If you are using the full-screen interface on requesters with
earlier versions of the LAN Server product, the 8-character
restriction for user IDs, group IDs, server names, and domain
names still applies. For example, when a user at a LAN Server 3.0
requester attempts to log on through the full-screen interface,
the interface rejects the user's ID if it is longer than 8
characters and returns an error upon receiving a domain name or
server name longer than 8 characters.
5. In the Domain Name window, either accept the default domain name or type
the domain name and then select OK. The installation program uses DOMAIN
as the default. If you have only one domain, the default value is
sufficient. However, if you have more than one domain, each domain must
have a unique domain name, so accept the DOMAIN default only if it is
one of your unique domain names. For information on domain name
constraints, refer to the preceding notes.
6. In the First Server - Domain Controller window, specify whether the
workstation on which you are installing the LAN Server product is the
first or only server on the domain. If you select Yes, the Domain
Controller window is displayed. If you select No, the Additional Server
window is displayed.
7. Additional windows may appear to confirm your adapter configuration.
When this occurs, follow the instructions on the windows.
8. If there is not enough disk space available on the hard disk on which
LAN Services is to be installed, the Insufficient Disk Space window is
displayed. This window displays both the disk space required to install
LAN Services as configured and the currently available disk space. Take
one of the following actions:
o Select Retry to recalculate disk-space requirements. If sufficient disk
space is available, proceed with step 9. If sufficient disk space is
still not available, the Insufficient Disk Space window is displayed
again.
o Switch to another OS/2 session and take the appropriate action to make
enough space available. Then, return to the current session and select
Retry to recalculate disk-space requirements. You may have to repeat
this step if sufficient disk space is still not available.
o Select Exit to end the LAN Services installation/configuration program.
If LAPS was upgraded, you will have to type MPTS instead of LAPS to
start LAPS. Otherwise, no changes are made to any of the workstation's
hard disks or logical drives.
The Insufficient Disk Space window may be displayed more than once
depending on the number of hard disks or logical drives involved in LAN
Services installation. (Some components, such as User Profile
Management, are always installed on the OS/2 startup drive, which may be
different from the drive where other LAN Services components are
installed.)
9. If you are installing from CD-ROM, you will not be prompted for
diskettes. If you are installing from diskettes, you will be prompted
to insert a specific diskette from the installation package. (Drive A
is the default drive, but you can select a different one.)
Warning:
If you select Exit in any of the following windows, you will exit
the LAN Services installation/configuration program, leaving the
product installation in an unknown state. The LAN Server software
will have been partially copied to your hard disk, and your
CONFIG.SYS file will not have been changed. Your LAN will not
function. You must restart the installation program to install and
configure LAN Services to have a functioning LAN.
Insert the specified diskette into the correct drive, and select OK.
Insert any additional diskettes as prompted, and select OK. Use
diskettes from the same installation package.
The program code is copied from the CD-ROM or diskettes onto the hard
disk.
Note:
You are not prompted to insert any diskettes if you are only
changing configuration parameters during a reinstallation.
10. The Default User ID and Password window is displayed if you initially
installed a domain controller. Use the user ID and password provided
(USERID and PASSWORD, respectively) for the initial logon. These values
can be customized later for subsequent logons. Select OK.
11. The Shutdown Requirements window may be displayed if you are installing
the 386 HPFS for the first time. You are reminded to shut down your
workstation from the OS/2 desktop each time you turn off the 386 HPFS
server to avoid loss of data. Select OK to acknowledge the message.
12. The Create a Startup Diskette for Your Workstation window is displayed
if you installed the 386-HPFS component of LAN Server-Advanced. Specify
Yes or No to create startup diskettes. It is strongly recommended that
you create the 386-HPFS startup diskettes for use if the hard disk fails
to start the workstation in the future. Otherwise, you may have to
reformat the hard disk and reinstall the base operating system and the
LAN Server product. If you cannot create the startup diskettes during
the install process, you should create the startup diskettes immediately
after completing installation. For more information on manually
creating 386-HPFS startup diskettes, see Creating 386-HPFS Startup
Diskettes.
13. The LAN Server product installation is complete message is displayed,
stating that the installation and configuration procedure has completed
successfully. Select OK.
In most cases, you are instructed to shut down your workstation from the
OS/2 desktop. If you are installing from diskette, remove the last
diskette before you shut down your workstation. To shut down your
workstation:
a. Stop all running programs.
b. Move the mouse pointer to an open area on the desktop, and click the
mouse button 2 to display the desktop pop-up menu.
c. Select Shut down.
d. Select OK to confirm the shut down command.
Wait until all disk activity has stopped and a message is displayed
informing you that the shutdown has completed. To restart the system and
implement the changes made by the LAN Services
installation/configuration program, press Ctrl+Alt+Del.
Unless otherwise instructed, you must shut down and restart the
workstation in the manner described to complete proper installation and
configuration.
If this is a new installation, the next step is to define users,
resources, and access control. If this is an upgrade, the next step is
to restore the backed up information, as necessary.
OS/2 LAN Server installation and configuration is complete. You can customize
the OS/2 LAN Server code installed on this workstation at a later time by using
the Tailored installation path described in the next section.
For information about starting and logging on to the LAN Server product, see
the LAN Server Network Administrator Reference Volume 3: Network Administrator
Tasks.
ΓòÉΓòÉΓòÉ 7.6.2. Tailored Installation ΓòÉΓòÉΓòÉ
Tailored installation requires more user input than the Easy installation. The
Tailored path allows you to select the components to be installed and to modify
IBM-supplied default parameters (or, if you are reinstalling or upgrading,
change previously set parameters). Unlike the Easy installation path, the
Tailored path allows you to change the server type (additional server, domain
controller, or backup domain controller) during a reinstallation.
Notes:
1. For the meanings of the OK, Cancel, Help, Retry, and Exit push buttons
displayed in the LAN Services installation and configuration windows,
see Window Layout.
2. Additional windows may appear to ensure that the LAN Server product
installs completely. For example, if you are installing from diskettes,
the LAN Services installation/configuration program displays windows
that prompt you to insert specific diskettes. When this occurs, follow
the instructions in the windows.
To Follow the Tailored Path for a Server Installation:
1. Select Tailored in the Easy or Tailored Installation/Configuration
window.
2. The Installation Tasks window is displayed. Select OK to accept Install
or configure this workstation (default).
3. If this is an initial installation and your workstation has more than
one hard disk or more than one partition on a single hard disk, the
Installation Location window is displayed. Select OK to install OS/2 LAN
Server on the default startup drive, or specify another drive, and then
select OK.
Only the \IBMLAN and \MPTN subdirectories are installed on the drive you
specify. The MUGLIB and IBM386FS subdirectories are always installed on
the OS/2 startup drive.
Note:
Read Upgrading or Reinstalling on a Different Hard Disk if that is
what you are planning to do.
4. On the Server Type window, select one of the following:
o Domain controller (default) if you want to configure your workstation
as a domain controller
o Additional server if you want to configure your workstation as an
additional server in an existing domain
o Backup domain controller to configure or redefine your workstation as a
backup domain controller Then select OK.
5. Additional windows may be displayed to confirm your adapter
configuration and to ask if you want to reinstall MPTS. When this
occurs, follow the instructions on the windows.
6. The LAPS Configuration window is displayed, as seen in the figure titled
LAPS Configuration Window. This panel provides two lists from which to
select, one for supported network adapters and one for supported
protocols, as well as a display of the current configuration. The
current configuration parameters can be edited and changed, or the
driver can be removed. The LAPS Configuration window also provides a
means to define unsupported adapters and protocols.
LAPS Configuration Window
From the LAPS Configuration window you can add, change, or delete
network adapters and protocols.
o To change a network adapter:
a. Select an adapter in the Current Configuration list.
b. Select the adapter you want from the Network Adapters list.
c. Select the Change push button under the Network Adapters list to
switch the old adapter with the newly selected adapter.
o To delete a network adapter and its associated protocol(s):
Note:
You must remove all protocols from the adapter you wish to
delete before you delete the adapter.
a. Select a protocol in the Current Configuration list.
b. Select Remove to delete that protocol.
c. Select Yes to the Remove Protocol message.
d. Repeat the preceding steps until all protocols have been removed
from the adapter.
e. Select the adapter in the Current Configuration list.
f. Select Remove.
g. Select Yes to the Remove Network Adapter message.
o To add a network adapter:
a. Select the network adapter from the Network Adapters list.
b. Select Add under the Network Adapters list. The newly added
network adapter will appear in the Current Configuration list.
o To add a protocol:
a. Select the network adapter in the Current Configuration list to
which you will add a protocol.
b. Select the desired protocol in the Protocols list.
c. Select Add under the Protocols list. The newly added protocol
will appear under the network adapter in the Current Configuration
list.
Select OK.
For detailed information on the LAPS Configuration window, refer to "
Attended LAPS Configuration" in the MPTS - AnyNet for OS/2:
Configuration Guide.
Note:
If you are running a non-IBM version of NetBIOS/802.2, you may
receive errors during the adapter installation. You will be given
the choice to Proceed or Exit. The errors indicate an
incompatibility between IBM's NetBIOS/802.2 and the non-IBM
version, but do not imply that the installation will be corrupted
or that the LAN Server product will suffer any loss in
functionality or resources. Select Proceed.
7. If a version of OS/2 LAN Server (4.0 or earlier) has already been
installed on your workstation and the LAN Services
installation/configuration program is unable to determine which drive
contains the copy of OS/2 LAN Server that is associated with the
currently started base operating system, the LAN Services to Update
window is displayed. Select the drive where the OS/2 LAN Server copy to
be updated is located. If you want to run an initial installation of LAN
Services, select None.
Note:
If you did not choose the 802.2 protocol, the Remote IPL
Requirement message is displayed. If you need OS/2 or DOS Remote
IPL, select No to return to the LAPS Configuration window.
Otherwise, select Yes.
8. The Installation and Configuration window, which is now displayed,
allows you to move between the Install and Remove window and the
Configure window. Install or remove a component is the default when the
window is displayed for the first time. Select OK.
9. If this is an initial installation, select one or more components that
you want to install in the Install and Remove window. Because the
initial program defaults to the recommended (Easy) set of components,
you do not have to select any components unless you want to add a
nondefault component. The Action column displays Install for each
selected component.
o To accept the default set of components, select OK.
o To add components, highlight items in the component list and select
Install.
Note:
You can select more than one component in this window by using the
Spacebar or mouse.
If you decide not to install a component that says Install in the Action
column, you can undo your selection by selecting one or more components
and then selecting Cancel action. The Action column will display a blank
field for each canceled component.
For components that are required, the Action column displays Install
(required); Cancel action cannot be used for these components.
If a component has been previously installed, the Status column displays
one of the following:
o Installed
The component is at the same version level as your LAN Services
installation/configuration program.
o Later version
This status is possible only if there is a subsequent release to the
LAN Server 4.0 product.
o Earlier version
The component is at an earlier version level than your LAN Services
installation/configuration program; for example the LAN Server 3.0
product and earlier.
o Damaged
The component is at the same version level as your LAN Services
installation/configuration program, but some of the required files are
missing.
If you want to remove previously installed components, select one or
more components; then select Remove. The Action column displays Remove
for each component selected. If you select the Server component, all
components are removed. You cannot remove the Server component when
upgrading.
If you select Install for previously installed components, the Action
column displays Install or, if the previously installed code is at the
same level as your LAN Services installation/configuration program, it
displays Replace.
If a Corrective Service Diskette (CSD) has been applied to previously
installed code and you reinstall a component or install a new component,
you must reapply the CSD (or a later version) after running the LAN
Services installation/configuration program. Check your system levels
before the installation and then again after the installation. If they
are the same, no action is necessary. If they are different, install
the CSDs for the down level components only.
The figure titled Install and Remove Window on the Server Installation
Path illustrates two possible settings (Install (required) and Install)
for the Action column during an additional server installation.
Install and Remove Window on the Server Installation Path
When you finish selecting the components to be installed, select OK.
Note:
For information about the various components that can be
installed, consult Supported Functions and the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
10. In the Installation and Configuration window, select Configure a
component if you want to configure one or more of the components
selected for installation. Then select OK. If you do not want to do any
configuration, proceed with step 14.
You cannot proceed with step 14 if a component selected for installation
is required to be configured (as displayed on the Configure window in
the next step).
11. The Configure window displays the configuration status of the components
you selected. Components for which the Status column displays
Configuration required require input and must be selected. Components
for which the Status column (during an initial installation) displays
IBM defaults pending are installed with the IBM-supplied defaults.
However, you may want to select these components, review the defaults,
and change them if desired.
The figure titled Configure Window on the Server Installation Path is an
example of a Configure window illustrating the Status column during the
installation of an additional server. In this particular instance, the
configuration of the Server and the 386-HPFS components have been
completed; the Status column displays Configured.
Configure Window on the Server Installation Path
Select the components that require configuration or that you want to
configure. After selecting a component, select Configure.... One or more
configuration windows are displayed. From these, you can select or
change options.
Warning:
Change defaults with extreme care, because they can affect
performance. For information about a specific item, select that
item and select Help. Upon completion of the installation, you
can use the IBM LAN Server 4.0 Performance Tuning Assistant to
help you improve performance. For information about parameters and
how they affect performance, refer to the LAN Server Network
Administrator Reference Volume 2: Performance Tuning. It is
recommended that you do not change any default parameter that you
do not understand.
12. Following the configuration windows, select the options and fill out the
fields pertinent to your workstation. Use the online help facility for
specific information. Selecting OK in the configuration windows confirms
your selections and brings up the next window in the series or returns
you to the main Configure window. Selecting Cancel displays the previous
window. For each configured component, the Status column in the
Configure window displays Configured.
The following paragraphs describe the actions to take in the
configuration windows for each configurable component. Because you are
selecting the configurable components in the main Configure window, the
order in which you see the configuration windows can be different from
the order in which they are described.
o If you select Server in the main Configure window:
a. In the Server and Domain Names window, type the server name, and
press Tab to go to the next entry field. Type the domain name,
and then select OK.
Notes:
1. The server and domain cannot have the same name. The server
name should not match any user ID or workstation name on the
network. In this case, the workstation name is specified by
the computername parameter in the IBMLAN.INI file.
2. The server and domain names are not case-sensitive and can
be 1 to 15 characters (bytes) in length.
3. The following characters are not valid:
" / \ [ ] ; : , | < > + = ? *
Characters below X'21' are also not valid.
4. When you have FAT-formatted hard drives, the following
restrictions apply:
- The user directory in the domain control database (DCDB) is
named as UserID. Therefore, it will be impossible to create
the directory if the value of the UserID parameter exceeds
8 bytes. The LAN Server product returns an error when
attempting to initialize a user ID longer than 8
characters.
- The DCDB replicator will not fully replicate user directory
names longer than 8 characters.
5. If you are using the full-screen interface on requesters
with earlier versions of the LAN Server product, the
8-character restriction for user IDs, group IDs, server
names, and domain names still applies. For example, when a
user at a LAN Server 3.0 requester attempts to log on
through the full-screen interface, the interface rejects the
user's ID if it is longer than 8 characters and returns an
error upon receiving a domain name or server name longer
than 8 characters.
b. In the Start Server window, select Start the server automatically
if you want the server to be started automatically each time the
workstation is started. Otherwise, select Do not start the server
automatically. Then select OK.
c. Set memory access for the network adapter in the Network Adapter -
Direct Memory Access window. Select All network adapters do not
use 24-bit DMA to allow LAN Server buffers to be located above the
16MB physical memory address boundary. Before selecting this
option, do the following:
- Ensure that you have greater than 16MB of physical memory.
- Ensure that the network adapter device drivers are capable of
performing direct memory access (DMA) operations above the 16MB
boundary.
Warning:
Non-BusMaster network interface cards (NIC) are not subject
to the preceding constraints. However, if you have a
BusMaster NIC, determine whether it is capable of performing
DMA above 16MB. Contact the supplier and ask whether your
card has 24 or 32 address lines. If it has 24, it cannot
perform DMA above 16MB. If it has 32, it can. If you are in
doubt, select Network adapter uses only 24-bit DMA
Select At least one network adapter uses only 24-bit DMA if the
Redirector should lock memory below the 16MB boundary (default on
an initial installation).
If displayed, select Use target setting to use the setting from a
previous installation at the target workstation.
d. In the Server Services window, select which services you want
started when the server is started. If the default set is
acceptable, no action is necessary. Then select OK.
e. If you are upgrading or reinstalling OS/2 LAN Server and you are
configuring a domain controller, one of the configuration windows
you see is the Reinitialize Domain Control Database window. This
window provides the option to reinitialize the domain control
database (DCDB), if one exists. Reinitializing the DCDB erases its
contents.
Do not reinitialize the DCDB (default) if you intend to use
existing domain control definitions. Reinitialize the DCDB only
if you intend to completely redefine it after installation and
configuration. Make your selection, and then select OK.
For more detailed information, refer to Upgrading the LAN Server
2.0 or 3.0 Product or Reinstalling.
o If you select 386 HPFS in the main Configure window, proceed as
follows:
a. In the 386 File System Cache Configuration Options window:
- Specify the amount of memory to be used by the workstation for
file-system disk caching. If you select Workstation determines
size, 20% of available memory is used for caching. If you select
Specify size, you can specify any amount in KB with a minimum of
256KB, though a cache of at least 512KB is better.
The default value for initial installation is 512KB. If your
workstation has a large amount of physical memory, you should
specify a large cache. For example, for a workstation with 16MB
of memory, a 4096KB (4MB) or 6144KB (6MB) cache minimum is
recommended. The IBM LAN Server 4.0 Performance Tuning Assistant
can assist you in determining the best cache size for your
system. In general, you should allocate as much memory to cache
as possible. If you specify an amount greater than the 512KB
default, select Specify size. Otherwise, select Workstation
determines size.
- Specify whether you want to use the lazy-write option. If you
select Write during disk-idle time (lazy-write is on), you can
specify the maximum cache age (between 0 and 65535 microseconds),
which is the maximum time a cache block can be dirty before it is
scheduled to be written to the hard disk. The recommended value
is between 1000 and 20000 microseconds. The initial default
value is 5000 microseconds.
Note:
A cache block is dirty when it contains data that has not
been transferred to the hard disk by a lazy-write
operation.
You can also specify the minimum buffer-idle time (between 0 and
500000 microseconds), which is the minimum time a dirty cache
block must remain in the cache since the last time it was
accessed (for either a read or a write operation). The
recommended value is between 100 and 1000 microseconds. The
initial default value is 500 microseconds.
To ensure the effectiveness of lazy-write operations, make sure
that the maximum cache age is greater than the minimum
buffer-idle time. It is recommended that if you enable lazy
write, you also install uninterruptible power supply hardware.
Select OK to continue.
b. In the Disk Adapter - Direct Memory Access window, select All disk
adapters support greater than 24-bit DMA if the 386 HPFS is
allowed to allocate memory for caching above the 16MB physical
address boundary. The 386 HPFS will then allocate memory above
the 16MB boundary if it is available. Before selecting this
option:
- Ensure that you have more than 16MB of physical memory.
- Ensure that the network adapter device drivers are capable of
performing direct memory access (DMA) operations above the 16MB
boundary.
Warning:
Non-BusMaster network interface cards (NIC) are not subject
to the preceding constraints. However, if you have a
BusMaster NIC, determine whether it is capable of performing
DMA above 16MB. Contact the supplier and ask whether your
card has 24 or 32 address lines. If it has 24, it cannot
perform DMA above 16MB. If it has 32, it can. If you are in
doubt, select At least one disk adapter supports only 24-bit
DMA
Select At least one disk adapter supports only 24-bit DMA to
specify that memory must be allocated below the 16MB boundary. You
must select At least one disk adapter supports only 24-bit DMA if
you are planning to use an adapter or a driver that cannot handle
a physical address above 16MB.
Select OK to continue.
c. In the Heap Configuration Option window, specify the maximum
386-HPFS heap size if you do not want to use the maximum size
determined by the workstation (the default for an initial
installation) or the maximum size set during a previous
configuration. The heap is memory used internally by the 386 HPFS.
Defining the size of the heap too restrictively can result in less
than the maximum number of find or request operations or open
files. Memory used by the heap is not available for any other use.
If you select Workstation determines maximum size, the workstation
will use up to all the available memory when it needs to use the
heap. If you select Specify maximum size, you can specify an
amount in KB. The initial default value is 512KB. It is
recommended that you select Workstation determines maximum size.
Select OK to continue.
o If you select DOS Remote IPL Service in the main Configure window,
proceed as follows:
a. In the Copy Programs window, select to copy DOS LAN Services, LAN
Support Program, and the appropriate DOS version. Then select OK.
Note:
Your actions in the Copy Programs window override any
actions you might have taken in the Copy Programs window
during OS/2 Remote IPL service configuration if this
configuration was completed earlier.
b. If you select to copy MS-DOS product diskettes (SBCS systems
only), you are prompted to indicate the number of MS-DOS diskettes
you have. Specify the correct number and select OK.
If you select to install DOS 5.0 or 5.0/V, you must create the DOS
diskettes before they can be copied by the LAN Services
installation/configuration program. Make sure you have blank
formatted diskettes and proceed as follows:
1. Minimize the current LAN Services installation/configuration
program window.
2. Insert the DOS 5.0 Installation diskette into drive A.
3. From the Command Prompts folder, select DOS from Drive A. The
workstation begins to startup from the DOS Installation
diskette.
4. Follow the instructions on the screen until the default
settings are displayed.
5. If the default is to install to the hard disk, use the arrow
keys to select Install to.... Press Enter.
6. Select Floppy Disks and press Enter.
7. When Install to: Floppy Disks is displayed, press Enter.
8. Follow the instructions on the screen to complete the
installation of DOS 5.0 to diskettes.
9. When prompted, press Enter. Press Ctrl+Esc to return to the
OS/2 desktop.
10. Select and close DOS from Drive A in the Window List.
11. Maximize the current LAN Services installation/configuration
program window and continue with the program.
c. In the Remote IPL Subdirectory window, accept the default
subdirectory location or specify a different drive letter. Then
select OK. You can place the remote IPL subdirectory
(\IBMLAN\RPL) on any hard drive, but the drive should have a
minimum of 70MB of disk space for the directory.
Notes:
1. The drive letter you specify in the Remote IPL Subdirectory
window overrides the drive letter you may have specified in
the same window during OS/2 Remote IPL service
configuration, if that configuration was completed earlier.
You cannot specify two separate drives.
2. If you are reinstalling on a different hard disk, for
example, drive D, and your previous copy of the remote IPL
subdirectory is the default C:\IBMLAN\RPL directory, specify
a new location on the D drive.
When you install (or reinstall) the DOS Remote IPL service, you
must run the GETRPL utility upon completion of the LAN Services
installation/configuration program after restarting the server.
For information about the GETRPL utility, refer to the LAN Server
Network Administrator Reference Volume 3: Network Administrator
Tasks.
d. In the Remote IPL User Subdirectory window, specify the drive on
which the \IBMLAN\RPLUSER directory tree should reside. The window
will specify the size of the directory tree, allowing you to
select a drive with sufficient disk space. The drive should have
a minimum of 40MB of disk space for the directory. If both the
\IBMLAN\RPL and the \IBMLAN\RPLUSER directories are placed on the
same drive, the LAN Server product install checks for 110MB of
free disk space.
o If you select OS/2 Remote IPL Service in the main Configure window,
proceed as follows:
a. In the Copy Programs window, select to copy OS/2 LAN Requester and
LAN Support Program. Then select OK.
Note:
Your actions in the Copy Programs window override any
actions you may have taken on the Copy Programs window
during DOS Remote IPL service configuration, if this
configuration was completed earlier.
b. In the Remote IPL Subdirectory window, accept the default
subdirectory location or specify a different drive letter. Then
select OK. You can place the remote IPL subdirectory
(\IBMLAN\RPL) on any hard drive, but the drive should have a
minimum of 70MB of disk space for the directory.
Note:
The hard drive you specify in the Remote IPL Subdirectory
window overrides the hard drive you may have specified in
the same window during DOS Remote IPL service configuration,
if that configuration was completed earlier. You cannot
specify two separate drives.
c. In the Remote IPL User Subdirectory window, specify the drive on
which the IBMLAN/RPLUSER directory tree should reside. The window
will specify the size of the directory tree, allowing you to
select a drive with sufficient disk space. The drive should have
a minimum of 40MB of disk space for the directory. If both the
\IBMLAN\RPL and the \IBMLAN\RPLUSER directories are placed on the
same drive, the LAN Server product install checks for 110MB of
free disk space.
o If you select LAN Services Adapters in the main configure window,
proceed as follows:
a. In the LAN Adapters window, select one or more configured logical
adapters (numbered 0 through 3) for use by OS/2 LAN Server. Then
select OK.
Note:
For each selected adapter, a netx statement is generated in
the Networks section of the IBMLAN.INI file. Selecting
adapter 0 adds the net1 statement to the IBMLAN.INI file,
selecting adapter 1 adds the net2 statement, and so on. If
you are creating a response file, the LAN Services
installation/configuration program generates response-file
entries reflecting this correspondence. (See Setting
IBMLAN.INI Parameters in Response Files.)
b. For each selected adapter, a NetBIOS Resources window is
displayed. The NetBIOS Resources window lists the NetBIOS
requirements (sessions, commands, and names) for your current OS/2
LAN Server configuration as well as the NetBIOS resources
currently provided by LAPS. Do one of the following:
- If LAPS provides sufficient NetBIOS resources to satisfy the OS/2
LAN Server requirements, select OK to continue.
- If LAPS provides fewer NetBIOS resources than required by OS/2
LAN Server, do one of the following:
o Adjust the value for sessions, commands, or names required by
OS/2 LAN Server by typing a number (in the appropriate entry
field) that is less than or equal to the sessions, commands,
or names provided by LAPS. Select OK.
Note:
Although your system will run, reducing required
resources can affect OS/2 LAN Server performance.
o Select Cancel to return to the LAPS Configuration window and
reconfigure LAPS to provide sufficient NetBIOS resources. The
program will return to the NetBIOS Resources window. Select
OK.
c. In the Remote IPL Adapters window (displayed if you have selected
to install the DOS or OS/2 Remote IPL service), select one or more
configured logical adapters (numbered 0 through 3) for use by
remote IPL. Then select OK.
Note:
For each selected adapter, an rplx statement is generated in
the Remoteboot section of the IBMLAN.INI file. Selecting
adapter 0 adds the rpl1 statement to the IBMLAN.INI file,
selecting adapter 1 adds the rpl2 statement, and so on. If
you are creating a response file, the LAN Services
installation/configuration program generates response-file
entries reflecting this correspondence. (See Setting
IBMLAN.INI Parameters in Response Files.)
o If you select Uninterruptible Power Supply Support in the main
Configure window, the Uninterruptible Power Supply window is displayed.
Select the port to be used by the UPS hardware (COM1 is the default);
then select OK.
Note:
To use the Uninterruptible Power Supply service, the COM.SYS
device driver must be installed on the server. Verify that the
COM.SYS device driver resides on the server and that there is a
device statement in the CONFIG.SYS file similar to the
following:
DEVICE=C:\OS2\COM.SYS
You can install this driver during or after base operating
system installation, or you can copy the driver from any
machine that has it installed. Ensure that the COM.SYS
statement is placed before the RDRHELP.SYS statement in the
CONFIG.SYS file.
o If you select First Failure Support Technology/2 in the main Configure
window, proceed as follows:
a. In the next three FFST/2 configuration windows, do the following:
1. Specify if First Failure Support Technology/2 is to be
autostarted.
2. Specify where the alerts are to be routed if you selected
Autostart.
3. Specify if messages should be displayed on the FFST/2 message
console.
4. Specify the maximum number of system dumps and the maximum
number of application dumps. Both values must be between 8 and
99; the initial default value is 32.
5. If you want to change the default system dump path and
application dump path, you can do so now.
6. Specify the application message log.
Select OK to continue.
b. In the Hardware Vital Product Data configuration window, specify
the workstation type, workstation serial number, and workstation
ID. The type and serial number can be found on the workstation.
The workstation ID is the name by which you want the workstation
to be known; the ID can be 1 to 8 characters in length. All
characters specified on this window must be alphanumeric, and
alphabetic characters must be uppercase. The workstation ID need
not be identical to the server name you specified on the Server
and Domain Names window.
Select OK to continue.
13. When you have finished configuring components, you are ready to complete
installation. In the Configure window, select OK.
14. In the Installation and Configuration window, select Apply the changes.
Then select OK.
15. If there is not enough disk space available on the hard disk on which
LAN Services is to be installed, the Insufficient Disk Space window
displays both the disk space required to install LAN Services as
configured and the currently available disk space.
If you are reinstalling the LAN Server product or upgrading a previous
version of OS/2 LAN Server, the Insufficient Disk Space window informs
you that the LAN Services installation/configuration program determines
the amount of required hard-disk space.
Warning:
If another process allocates hard-disk space after the required
disk space has been determined, you can be forced to exit the LAN
Services installation/configuration program and lose not only your
installation and configuration parameters but also valuable data,
such as the information stored in the DCDB.
The Insufficient Disk Space window may be displayed more than once,
depending on the number of hard disks or logical drives involved in LAN
Services installation. (Some components, such as User Profile Management
(UPM), are always installed on the OS/2 startup drive, which can be
different from the drive you specified in step 3 for LAN Services
installation. Also, you might have specified a different drive for the
location of the remote IPL subdirectory in step 12.)
Do one of the following:
o Select OK to exit the installation/configuration program.
o Select Retry to recalculate disk-space requirements. If sufficient disk
space is available, proceed with step 16. If sufficient disk space is
still not available, the Insufficient Disk Space window is displayed
again.
o If not enough space is available on the hard disk or drive you
specified in the Hard-Disk window in step 3, and if your workstation
has more than one hard disk or more than one partition on a single hard
disk, select Cancel. Continue to select Cancel on subsequent windows
until you return to the Hard-Disk window. Specify another drive in the
Hard-Disk window and proceed through the LAN Services
installation/configuration program.
o If not enough space is available on the hard disk or drive you
specified for the location of the remote IPL subdirectory (step 12),
select Cancel to return to the Installation and Configuration window.
Then select Configure a component to return to the main Configure
window. Follow the instructions in step 11 to return to the Remote IPL
Subdirectory window. Specify another drive on the Remote IPL
Subdirectory window and proceed through the LAN Services
installation/configuration program.
o Switch to another OS/2 session and take the appropriate action to make
enough space available. Then return to the current session and select
Retry to recalculate disk-space requirements. You may have to repeat
this step if sufficient disk space is still not available.
16. If you are installing from CD-ROM, you will not be prompted for
diskettes. If you are installing from diskettes, you will be prompted
to insert a specific diskette from the installation package. (Drive A
is the default drive, but you can select a different one.)
Warning:
If you select Exit on any of the following windows, you exit the
LAN Services installation/configuration program, leaving the
product installation in an unknown state. You must restart the
program to install and configure LAN Services.
Be sure to insert the specified diskette into the correct drive, and
then select OK. Insert any additional diskettes as prompted and select
OK. Use diskettes from the same installation package.
The program code is copied from the diskettes onto the hard disk.
Note:
During configuration, if you selected to copy DOS programs and you
do not have the appropriate diskettes available now, you can
select Skip on the Copy Diskette window. You can continue with
the LAN Services installation/configuration program, but some
components requiring the skipped DOS programs may not function
properly. You can later rerun the LAN Services
installation/configuration program and copy the DOS diskettes you
skipped.
You are not prompted to insert any diskettes if you are only
changing configuration parameters during a reinstallation.
17. The File Backup window is displayed if any of the following files are
modified as a result of running the LAN Services
installation/configuration program:
o CONFIG.SYS
o IBMLAN.INI
o STARTUP.CMD
o PRIVINIT.CMD
o SRVAUTO.PRO
o PROTOCOL.INI
The File Name column on the File Backup window displays the names of the
configuration files that are modified. The Backup Name column gives you
the location of the unmodified versions of these files.
Select OK.
18. The Shutdown Requirements window may be displayed if you are installing
the 386 HPFS for the first time. You are reminded to shut down your
workstation from the OS/2 desktop each time you turn off the 386-HPFS
server to avoid loss of data. Select OK to acknowledge the message.
19. The Default User ID and Password window is displayed if you initially
installed a domain controller or if you reinitialized the DCDB. Use the
user ID and password provided (USERID and PASSWORD, respectively) for
the initial logon. These values can be customized later for subsequent
logons. Select OK.
20. The Define Server window is displayed if you are installing an
additional server or backup domain controller for the first time (or if
you are reinstalling either workstation with a new server name). You
are reminded that the installed server must be defined to the domain
controller before it can be used. If you do not define the server, the
NET START NETLOGON command will fail. To define the server to the
domain controller from the command line, type the following at the
domain controller's command line:
NET USER ServerName /PASSWORDREQ:NO /ADD
NET GROUP SERVERS ServerName /ADD
For instructions on defining the server using the LAN Server
Administration GUI, refer to the LAN Server Network Administrator
Reference Volume 3: Network Administrator Tasks.
Select OK to acknowledge the Define Server message.
21. The Create a Startup Diskette for Your Workstation window is displayed
if you installed 386 HPFS. Specify Yes or No to create startup
diskettes. It is strongly recommended that you create the 386-HPFS
startup diskettes for use if the hard disk fails to start the
workstation in the future. Otherwise, you may have to reformat the hard
disk and reinstall the base operating system and the LAN Server product.
If you cannot create the startup diskettes during the install process,
you should create the startup diskettes immediately after completing
installation. For more information on manually creating 386-HPFS
startup diskettes, see Creating 386-HPFS Startup Diskettes.
22. The LAN Server product installation is complete message is displayed,
stating that the installation and configuration procedure has completed
successfully. Select OK.
In most cases, you are instructed to shut down your workstation from the
OS/2 desktop. If you are installing from diskette, remove the last
diskette before you shut down your workstation. To shut down your
workstation:
a. Stop all running programs.
b. Move the mouse pointer to an open area on the desktop, and click the
mouse button 2 to display the desktop pop-up menu.
c. Select Shut down.
d. Select OK to confirm the shut down command.
Wait until all disk activity has stopped and a message is displayed
informing you that the shutdown has completed. To restart the system
and implement the changes made by the LAN Services
installation/configuration program, press Ctrl+Alt+Del.
Unless otherwise instructed, you must shut down and restart the
workstation in the manner described to complete proper installation and
configuration.
23. If you selected Local Security for 386 HPFS on the Install and Remove
window (see step 9), the configuration for a locally secure 386 HPFS is
now being completed. The following modifications are made after you
restart the system during an initial installation:
o The SETSECUR.EXE entry is removed from the STARTUP.CMD file.
o Other entries in the STARTUP.CMD file, if any, are moved to the
PRIVINIT.CMD file.
o RUNPRIV.EXE is added to the STARTUP.CMD file.
Note:
Entries in the PRIVINIT.CMD file are given administrator
authority. If you want some of these entries to be run with user
authority, move the appropriate entries from the PRIVINIT.CMD file
back to the STARTUP.CMD file. You need administrative authority
or the proper permissions to do this.
Shut down and restart the system to implement the changes.
During a reinstallation of the Local Security for the 386 HPFS function,
the Default Access Controls window is displayed. Select Yes to reset the
IBM-supplied access controls for Local Security to the default settings.
Select No to retain the current settings. For a list of the IBM-supplied
access controls and their default settings, refer to the LAN Server
Network Administrator Reference Volume 3: Network Administrator Tasks.
Upon successful completion of the configuration, the Local Security
Complete window is displayed. Shut down the workstation from the OS/2
desktop and then restart it.
24. If you installed the OS/2 Remote IPL service, you must run the RIPLINST
utility to copy OS/2 2.O to the remote IPL subdirectory. For more
information about the RIPLINST utility, refer to the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
25. If you installed (or reinstalled) the DOS or OS/2 Remote IPL service,
you must run the GETRPL utility to enable successful access from a
remote IPL requester to the directory resources at the server during
startup. For more information about the GETRPL utility, refer to the
LAN Server Network Administrator Reference Volume 3: Network
Administrator Tasks.
OS/2 LAN Server installation and configuration is complete. You can customize
the OS/2 LAN Server code installed on this workstation at a later time by using
the Tailored installation path. For more information, refer to Reinstalling,
Reconfiguring, or Removing. To calculate capacity-related parameters that may
need adjustment after installation, refer to Calculating IEEE 802.2 and NetBIOS
Resources for OS/2 LAN Servers and Calculating Resources for OS/2 Remote IPL
Servers. To improve performance, use the IBM LAN Server 4.0 Performance Tuning
Assistant.
For information about starting and logging on to the LAN Server product, see
the LAN Server Network Administrator Reference Volume 3: Network Administrator
Tasks or IBM OS/2 LAN Server Version 4.0 Up and Running!.
ΓòÉΓòÉΓòÉ 7.6.3. Installing the Loop-Back Driver ΓòÉΓòÉΓòÉ
If you install the loop-back driver and do not select any configured NetBIOS
adapters for use with the LAN Server product in the LAN Adapters window, the
loop-back driver is automatically enabled to start.
Note:
If you select to install the loop-back driver and also select one or
more configured NetBIOS adapters for use with the LAN Server product,
unpredictable network errors may occur because the NetBIOS protocol
attempts to duplicate activity that the loop-back driver is performing.
The following procedure explains how to install the loop-back driver, using the
LAN Services installation/configuration program.
To Install the Loop-Back Driver:
1. Start the LAN Services installation/configuration program.
2. Select Tailored on the Easy or Tailored Installation/Configuration
window.
3. If the Adapter window is displayed, do not select any adapters.
4. In the LAPS Configuration window, do not select any adapters in the
Network Adapters window. The Current Configuration window should be
blank. If not, remove any listed adapters. Select OK.
5. In the LAPS Requirements window, select Yes.
6. In the next window, select OK.
7. In the Installation and Configuration window, select OK.
8. In the Install and Remove window, select OK.
9. In the Installation and Configuration window, Configure a component
should be highlighted; select OK.
10. In the Configure window, select Configure. Once the Server is
configured, the Configure window is displayed again. Select OK.
11. In the Installation and Configuration window, Apply the changes should
be highlighted; select OK.
12. When the installation completes, shut down and restart your workstation.
The loop-back driver will be enabled.
To Disable the Loop-Back Driver:
1. Start the LAN Services installation/configuration program.
2. Select Tailored in the Easy or Tailored Installation/Configuration
window.
3. If the Adapter window is displayed, select the desired adapters.
4. In the LAPS Configuration window, do the following:
a. Select any additional Network adapters not already in the Current
Configuration window, and select Add. The Current Configuration
window should reflect your selections.
b. From the protocol list, highlight one or more protocols for each
adapter in the Current Configuration window, and select Add Select
OK.
5. In the Installation and Configuration window, select OK.
6. In the Install and Remove window, select to remove the loop-back driver.
7. In the Installation and Configuration window, Configure a component
should be highlighted; select OK.
8. In the Configure window, select OK.
9. In the Installation and Configuration window, Apply the changes should
be highlighted; select OK.
10. Complete the LAN Services installation/configuration program, and then
shut down and restart the workstation. The loop-back driver will now be
disabled and the adapters that you selected to configure will be
enabled.
ΓòÉΓòÉΓòÉ 7.6.4. Custom Installation ΓòÉΓòÉΓòÉ
The network administrator can provide users with a custom installation diskette
to assist installation or reinstallation of specified OS/2 LAN Server code at
their workstations. Custom installation requires only limited input from the
workstation user.
The LAN Services installation/configuration program provides a guided path to
create a server custom diskette. You can create a server custom diskette that
generates menus prompting the workstation user to provide workstation-unique
information during installation. You can create user prompts only for the
following information:
o Domain name
o Server name
o Hardware vital product data (for First Failure Support Technology/2)
Generate user prompts with the LAN Services installation/configuration program
by selecting Use target setting for any of the listed options for which you
want the user to provide information during an initial installation. If you do
not want the user prompted for information for any of the listed options, do
not select Use target setting and provide the requested information instead.
Notes:
1. If you select Use target setting and the user's workstation has settings
from a previous installation, the existing settings are used, and the
custom diskette user is not prompted to provide information.
2. To force a user to provide values even if previous target settings
exist, you must modify the LANINST.RSP file on the custom diskette with
an ASCII text editor. (See Missing Values for Keyword Entries.)
Users doing a custom installation should use the provided custom installation
diskette to replace Server - Disk 1. Then insert any other diskette from the
installation package as prompted.
Note:
Before you prepare the server custom installation diskette, read Before
You Install. If the diskette is meant to assist in reinstalling or
reconfiguring the LAN Server product, read also Upgrading, Migration of
Data, and Reinstalling, Reconfiguring, or Removing.
ΓòÉΓòÉΓòÉ 7.6.4.1. Creating a Server Custom Diskette ΓòÉΓòÉΓòÉ
Before you begin this procedure, ensure that you have a blank, formatted
high-density diskette of the same size as the diskettes in your installation
package.
Hint:
Make backup copies (using the DISKCOPY command) of the diskettes in your
installation package, and run the LAN Services
installation/configuration program from the backup diskettes. Make sure
that the size of the backup diskettes matches the size of the original
diskettes and that the diskettes you back up are all from the same
installation package.
To Create a Server Custom Diskette:
1. Start the LAN Services installation/configuration program in either of
two ways:
o If you are running the LAN Services installation/configuration program
locally from CD-ROM or diskettes, follow steps 1 through 5 under "To
Begin an Easy or Tailored Server Installation" in -- Reference insos21
not found --..
o If you are running the LAN Services installation/configuration program
remotely from the code server, type the remote installation command
described in step 1 in Starting an Attended Remote Installation on the
target workstation's command-line.
2. Select Tailored in the Easy or Tailored Installation/Configuration
window.
3. In the Installation Tasks window, select Create a server custom
diskette. Then select OK.
Keep in mind that all the installation and configuration choices made
after this point are for the user's workstation that you, the network
administrator, are preconfiguring.
Note:
The server custom diskette you create also installs OS/2 LAN
Requester on the user's workstation. For requester-only
installation, see Creating a Requester Custom Diskette.
4. In the Source Drive window, select Do not update an existing copy if the
custom diskette user's workstation does not have any version of the LAN
Server product (2.0, 3.0, or 4.0) already installed.
Otherwise, select Update copy on specified drive (default) and specify
which drive on the custom diskette user's workstation contains the copy
of the LAN Server product from which configuration information will be
retrieved. If you do not want any information retrieved, select Do not
update an existing copy.
Note:
Decisions you make in this window take effect only if the LAN
Services installation/configuration program cannot determine
during custom installation which drive contains the copy of the
LAN Server product from which to retrieve information. If the
program can identify the appropriate drive, information is
retrieved from the LAN Server copy on that drive, regardless of
your selections in the Source Drive window.
Select OK to continue.
5. In the Hard-Disk window, select OK if you want the user to install the
LAN Server product on the hard disk on which the previous version (if
any) is currently installed. In the absence of a previous version, this
selection causes the LAN Server product to be installed on the target
workstation's OS/2 startup drive. Otherwise, specify another drive and
select OK to continue.
Only the IBMLAN subdirectory is installed on the drive you specify. The
MUGLIB and IBM386FS subdirectories are always installed on the OS/2
startup drive.
6. In the Server Type window, do one of the following:
o To configure the workstation as an additional server in an existing
domain, select Additional server.
o To configure the workstation as a domain controller, select Domain
controller.
o To define the workstation as a backup domain controller, select Backup
domain controller.
o To preserve the current server type of the user's workstation (defined
during a previous installation), select Use target setting. When you
have made your choice, select OK.
7. Follow the instructions in Tailored Installation beginning with step 8
through step 14. Remember the following differences from the regular
Tailored installation path:
o In the Install and Remove window (step 9 in Tailored Installation) you
can select an additional push button. Select Install if required if you
want to let the LAN Services installation/configuration program
determine whether existing code (if any) on the user's workstation
should be replaced. The Action column displays the status of each
selected component to Install (if required). During actual custom
installation, the selected components are installed on the user's
workstation, unless the code already installed is at the same or a
later level.
Note:
If you select Install if required and the custom diskette is
used for an initial installation, the component is installed
only if it is one of the default components installed during an
initial diskette-based Easy installation. For a list of default
components, see Easy Installation.
If you select Install, the Action column displays Install. During
actual custom installation, the selected components are installed on
the user's workstation unless the code already installed is at a later
level.
Note:
If the code already installed is at a later level (for example,
for User Profile Management or FFST/2, which might have been
installed by the Communications Manager/2 or DATABASE 2 OS/2
program), the LAN Services installation/configuration program
ends, and no new code is installed.
o Complete the configuration windows as described in step 12 in Tailored
Installation, remembering that you can select Use target setting if you
want to preserve the target workstation's configuration parameters from
a previous installation.
If you select Use target setting in either the Server and Domain Names
window or the Hardware Vital Product Data window, the custom diskette
user will be prompted for input unless the workstation has settings
from a previous installation.
Note:
To force the custom diskette user to provide input for any of
these windows, even if target settings exist, you must modify
the response file with an ASCII editor. (See Missing Values for
Keyword Entries.)
Complete the following windows as described:
- In the Server and Domain Names window, you have the option to
specify one name, both names, or none at all:
o Select Use target setting (default) for each item for which you
want the custom diskette user prompted to provide a name during
an initial custom installation.
If the user's workstation has settings from a previous
installation, the existing setting is used, and the user is not
prompted to provide information.
o Deselect Use target setting for each name you want to provide,
and type the name in the appropriate entry field. The name or
names you provide cannot be changed by the custom diskette user.
- In the Hardware Vital Product Data window, you can specify any or
none of the requested workstation data:
o Select Use target setting (default) for each item for which you
want the custom diskette user prompted to provide the requested
information during an initial custom installation.
If the user's workstation has settings from a previous
installation, the existing setting is used, and the user is not
prompted to provide information.
o Deselect Use target setting for each item for which you want to
provide the data, and type the correct information in the
appropriate entry field. The data you provide cannot be changed
by the custom diskette user.
8. In the Installation and Configuration window, select Apply the changes.
Then select OK.
9. When prompted, label and insert a blank formatted high-density diskette.
(Drive A is the default drive, but you can select a different one.)
Label the diskette as instructed. Be sure to insert the labeled
diskette into the correct drive, and then select OK.
The files that are needed to support installation and configuration by
means of a custom diskette are copied onto a blank diskette. The size
of the custom diskette must match the size of the original installation
diskettes.
When copying is complete, the Server Custom Diskette Creation Complete
window is displayed. Select Yes to create a custom diskette for another
server; otherwise, select No.
Note:
If you create a custom diskette for another server, the selections
you made for the current custom diskette are shown as defaults.
You can change the defaults.
The server custom diskette can now be used instead of Server - Disk 1 to
support installation or reinstallation on the user's workstation. The user
must still insert any other diskettes from the installation package as
prompted. See Using a Server Custom Diskette for instructions for using the
custom diskette.
The LANINST.RSP file on the custom diskette contains the installation and
configuration selections you made when creating the diskette. You can modify
the LANINST.RSP file using an ASCII text editor. For information, see Response
File Keywords Used in Remote Installation.
ΓòÉΓòÉΓòÉ 7.6.4.2. Using a Server Custom Diskette ΓòÉΓòÉΓòÉ
To install LAN Server code with the help of a server custom diskette, use the
custom diskette created with Creating a Server Custom Diskette (instead of
Server - Disk 1) as well as the remaining diskettes of the installation
package. You must be in an active OS/2 full-screen or window session.
To Use a Server Custom Diskette:
1. Insert the server custom diskette into drive A.
2. Type:
A:INSTALL
Press Enter.
3. A message states that the LAN Services installation/configuration
program is being copied. When the IBM logo is displayed, select OK.
Note:
If you are running a non-IBM version of NetBIOS/802.2, you may
receive errors during the adapter installation. You will be given
the choice to Proceed or Exit. The errors indicate an
incompatibility between IBM's NetBIOS/802.2 and the non-IBM
version, but do not imply that the installation will be corrupted
or that the LAN Server product will suffer any loss in
functionality or resources. Select Proceed.
4. If the creator of the custom diskette did not supply the server or
domain name, the custom diskette user is prompted either to accept the
server or domain name set during a previous installation or
configuration (if applicable) or to provide a name. Follow the
instructions in step 12a in Tailored Installation. The same applies to
hardware vital product data (if the custom diskette creator selected to
install FFST/2). In this case, follow the instructions in step 12b in
Tailored Installation.
Users will also be prompted to insert specific diskettes from the
installation package.
5. If there is not enough disk space available on the hard disk on which
LAN Services is to be installed, the Insufficient Disk Space window is
displayed. This window states both the disk space required to install
LAN Services as configured and the currently available disk space. If
the window is displayed, the user should do one of the following:
o Select Retry to recalculate disk-space requirements. If sufficient disk
space is available, proceed with inserting diskettes as requested. If
sufficient disk space is still not available, the Insufficient Disk
Space window is displayed again.
o Switch to another OS/2 session and take the appropriate action to make
enough space available. Then return to the current session and select
Retry to recalculate disk-space requirements. The user may have to
repeat this step if sufficient disk space is still not available.
o Select Exit to end the LAN Services installation/configuration program.
No changes are made to any of the workstation's hard disks or logical
drives.
6. The Insufficient Disk Space window may be displayed more than once,
depending on the number of hard disks or logical drives involved in LAN
Services installation. (Some components, such as User Profile
Management, are always installed on the OS/2 startup drive, which may be
different from the drive the custom diskette creator specified for LAN
Services installation. The creator of the custom diskette might also
have specified a third drive for the location of the \RPL subdirectory.)
7. Depending on the selections of the creator of the custom diskette,
either the Default User ID and Password window or Define Server window
may be displayed. Follow the instructions in steps 19 and 20 in
Tailored Installation. respectively.
8. After an Installation/Configuration Complete message is displayed, the
user should shut down and restart the workstation if instructed to do
so. (See step Tailored Installation.)
ΓòÉΓòÉΓòÉ 7.7. Installing OS/2 LAN Requester ΓòÉΓòÉΓòÉ
Use the following instructions if you are installing or reinstalling only the
OS/2 LAN Requester component of the LAN Server product. You may want to use the
OS/2 LAN Requester Installation Worksheet to prepare for installation and
configuration.
Note:
Before you run the LAN Services installation/configuration program, read
Before You Install. If this is not an initial installation, read also
Upgrading and Reinstalling, Reconfiguring, or Removing.
You can run the LAN Services installation/configuration program locally either
from CD-ROM or diskette (always the case for initial installation) or hard disk
(if you installed the LAN Services installation/configuration program on your
hard disk during a previous installation of OS/2 LAN Requester). For remote
installation, refer to Remote Installation.
To run the LAN Services installation/configuration program from diskette, you
must be in an active OS/2 full-screen or window session.
Hint:
Make backup copies (using the DISKCOPY command) of the diskettes in your
installation package, and run the LAN Services
installation/configuration program from the backup diskettes. Make sure
that the size of the backup diskettes matches the size of the original
diskettes, and that the diskettes you back up are all from the same
installation package.
Note:
When you have FAT-formatted hard drives, the following naming
restrictions apply:
o The user directory in the domain control database (DCDB) is named as
UserID. Therefore, it will be impossible to create the directory if the
value of the UserID parameter exceeds 8 bytes. The LAN Server product
returns an error when attempting to initialize a user ID longer than 8
characters.
o The DCDB replicator will not fully replicate user directory names longer
than 8 characters.
To Begin an Easy or Tailored Requester Installation:
1. Insert the LAN Server CD-ROM or the Requester - Disk 1 into the
appropriate drive.
2. Start the CD-ROM installation program or the diskette installation
program. To start the CD-ROM or diskette installation program, type
d:INSTALL, where d is the drive letter of the CD-ROM or diskette drive,
and press Enter.
Hint:
To run the LAN Services installation/configuration program from
the hard disk, substitute the following procedure for steps 1 and
2.
o Select OS/2 LAN Services Installation/Configuration from the LAN
Services container on the OS/2 desktop.
Notes:
a. If you do not want the LAN Server product to automatically detect
your adapter, invoke the INSTALL /NS command.
b. If you install The LAN Server 4.0 product on an OS/2 2.0
workstation, use the INSTALL /20 command. Several of the LAN
Server 4.0 functions, including the LAN Server Administration GUI,
will not be available on the OS/2 2.0 workstation. However, most
of the LAN Server command line functions will be available.
3. Select OK in the Welcome window (CD-ROM installation only).
4. Select Install OS/2 LAN Server in the Installation window (CD-ROM
installation only).
The IBM logo is displayed.
5. Select OK on the logo panel.
6. To install a requester workstation, you must have a license for each
requester. Select OK in the Important Licensing Information window.
7. The Easy or Tailored Installation/Configuration window is displayed.
Select Easy if you want to follow the Easy path. (See Easy
Installation.)
Select Tailored for any of the following tasks:
o For a local installation. (See Tailored Installation.)
o To remove OS/2 LAN Requester. (See Removing.)
o To create a custom installation diskette. (See Creating a Requester
Custom Diskette.)
Refer to Installation Paths to help you decide which path to select.
Also, select Tailored if you plan to install any of the following
components:
o Fault Tolerance Administration
o First Failure Support Technology/2 (FFST/2)
o LAN Server Applications Development Toolkit
o Peer service
o Virtual DOS LAN API Support
Note:
In the event that the LAN Services installation/configuration program
cannot be run (for example, if the current operating system is not
compatible with the program), a message is displayed.
ΓòÉΓòÉΓòÉ 7.7.1. Easy Installation ΓòÉΓòÉΓòÉ
If you follow the Easy path for an initial installation of OS/2 LAN Requester,
IBM-supplied default installation and configuration values are used. However,
you must supply the names of the requester and domain.
The following default components are installed during the initial Easy
installation of OS/2 LAN Requester with any of the LAN Server installation
packages:
o LAN Requester (including the Messenger service)
o LAN Server Administration GUI
o Requester installation/configuration program
o User Profile Management (UPM)
If you are reinstalling OS/2 LAN Requester, the default values are those
supplied during the previous installation. When using the Easy installation
path for reinstalling, you can reinstall only components that are currently
installed.
Notes:
1. For the meanings of the OK, Cancel, Help, Retry, and Exit push buttons
displayed on the LAN Services installation and configuration windows,
see Window Layout.
2. Additional windows may appear to ensure that the LAN Server product
installs completely. For example, if you are installing from diskettes,
the LAN Services installation/configuration program displays windows
that prompt for specific diskettes. When this occurs, follow the
instructions in the windows.
To Follow the Easy Path for a Requester:
1. Select Easy in the Easy or Tailored Installation/Configuration window.
2. In the Installation Location window, select OK to install OS/2 LAN
Requester on the default startup drive, or specify another drive and
then select OK. The Installation Location window is displayed only
during initial installation and only if your workstation has more than
one hard disk or more than one partition on a single hard disk.
3. If this is a reinstallation, the Reinstallation Type window is
displayed. Specify whether you want to change requester and domain
names, reinstall from diskette, or do both. (If you choose not to do
both, some of the following steps will be skipped.)
4. In the Requester Name window, type the requester name, and select OK.
Notes:
a. The requester and domain cannot have the same name. The requester
name should not match any workstation name on the network. In
addition, if the requester is being remote IPLed from a server,
the requester name should not match any user ID on the network.
In this case, the workstation name is specified by the
computername parameter in the IBMLAN.INI file.
b. The requester and domain names are not case-sensitive and can be 1
to 15 characters (bytes) in length.
c. The following characters are not valid:
" / \ [ ] ; : , | < > + = ? *
Characters below X'21' are also not valid.
d. If you are using the full-screen interface on requesters with
earlier versions of the LAN Server product, the 8-character
restriction for user IDs, group IDs, server names, and domain
names still applies. For example, when a user at a LAN Server 3.0
requester attempts to log on through the full-screen interface,
the interface rejects the user's ID if it is longer than 8
characters and returns an error upon receiving a domain name or
server name longer than 8 characters.
5. In the Domain Name window, either accept the default domain name or type
the domain name and then select OK. The installation program uses DOMAIN
as the default. If you have only one domain, the default value is
sufficient. However, if you have more than one domain, each domain must
have a unique domain name, so you should accept the DOMAIN default only
if it is one of your unique domain names. For information on domain name
constraints, refer to the preceding notes.
Note:
Additional windows may appear to confirm your adapter
configuration. When this occurs, follow the instructions on the
windows.
6. If disk space is not adequate on the hard disk on which LAN Services is
to be installed, the Insufficient Disk Space window displays both the
disk space required to install LAN Services as configured and the
currently available disk space. Do one of the following:
o Select Retry to recalculate disk-space requirements. If sufficient disk
space is available, proceed with step 7. If sufficient disk space is
still not available, the Insufficient Disk Space window is displayed
again.
o Switch to another OS/2 session and take the appropriate action to make
enough space available. Then return to the current session and select
Retry to recalculate disk-space requirements. You may have to repeat
this step if sufficient disk space is still not available.
o Select Exit to end the LAN Services installation/configuration program.
No changes are made to any of the workstation's hard disks or logical
drives.
The Insufficient Disk Space window may be displayed more than once,
depending on the number of hard disks or logical drives involved in LAN
Services installation. (Some components, such as User Profile
Management, are always installed on the OS/2 startup drive, which can be
a different drive from the drive where other LAN Services components are
installed.)
7. If you are installing from CD-ROM, you will not be prompted for
diskettes. If you are installing from diskettes, you will be prompted
to insert a specific diskette from the installation package. (Drive A
is the default drive, but you can select a different one.)
Warning:
If you select Exit in any of the following windows, you will exit
the LAN Services installation/configuration program, leaving the
product installation in an unknown state. The LAN Server software
will have been partially copied to your hard disk, and your
CONFIG.SYS file will not have been changed. Your LAN will not
function. You must restart the installation program to install and
configure LAN Services to have a functioning LAN.
Make sure you insert the specified diskette into the correct drive, and
then select OK.
Note:
Drive A is the default drive, but you can select a different one.
Insert any additional diskettes as prompted, and then select OK. Use
diskettes from the same installation package.
The program code is copied from the CD-ROM or installation diskettes
onto the hard disk.
Note:
You are not prompted to insert any diskettes if you are changing
only configuration parameters during a reinstallation.
8. The LAN Server product installation is complete message is displayed,
stating that the installation and configuration procedure has completed
successfully. Select OK.
In most cases, you are instructed to shut down your workstation from the
OS/2 desktop. If you are installing from diskette, remove the last
diskette before you shut down your workstation. To shut down your
workstation:
a. Stop all running programs.
b. Move the mouse pointer to an open area on the desktop, and click the
mouse button 2 to display the desktop pop-up menu.
c. Select Shut down.
d. Select OK to confirm the shut down command.
Wait until all disk activity has stopped and a message is displayed
informing you that the shutdown has completed. To restart the system
and implement the changes made by the LAN Services
installation/configuration program, press Ctrl+Alt+Del.
Note:
Unless instructed otherwise, you must shut down and restart the
workstation in the manner described to ensure proper installation
and configuration.
OS/2 LAN Requester installation and configuration is complete. You can
customize the OS/2 LAN Requester code installed on this workstation later by
using the Tailored installation path described in the next section.
ΓòÉΓòÉΓòÉ 7.7.2. Tailored Installation ΓòÉΓòÉΓòÉ
Tailored installation requires more user input than Easy installation. The
Tailored path enables you to select the components to be installed and to
modify IBM-supplied default parameters. If you are reinstalling or upgrading,
you can change previously set parameters.
Notes:
1. For the meanings of the OK, Cancel, Help, Retry, and Exit push buttons
displayed in the LAN Services installation and configuration windows,
see Window Layout.
2. Additional windows may appear to ensure that the LAN Server product
installs completely. For example, if you are installing from diskettes,
the LAN Services installation/configuration program displays windows
that prompt for specific diskettes. When this occurs, follow the
instructions on the windows.
To Follow the Tailored Path for a Requester:
1. Select Tailored in the Easy or Tailored Installation/Configuration
window.
2. The Installation Tasks window is displayed. Select OK to accept Install
or configure this workstation (default).
3. If this is an initial installation and your workstation has more than
one hard disk or more than one partition on a single hard disk, the
Installation Location window is displayed. Select OK to install OS/2 LAN
Requester on the default startup drive, or specify another drive and
then select OK.
Only the \IBMLAN and \MPTN subdirectories are installed on the drive you
specify. The MUGLIB and IBM386FS subdirectories are always installed on
the OS/2 startup drive.
4. Additional windows may appear to confirm your adapter configuration.
When this occurs, follow the instructions on the windows.
5. The LAPS Configuration window is displayed, as seen in as seen in the
figure titled LAPS Configuration Window. This window provides two lists
from which to select, one for supported network adapters and one for
supported protocols, as well as a display of the current configuration.
The current configuration parameters can be edited and changed, or the
driver can be removed. The LAPS Configuration window also provides a
means to define unsupported adapters and protocols.
LAPS Configuration Window
From the LAPS Configuration window you can add, change, or delete
network adapters and protocols.
o To change a network adapter:
a. Select an adapter in the Current Configuration list.
b. Select the adapter you want from the Network Adapters list.
c. Select the Change push button under the Network Adapters list to
switch the old adapter with the newly selected adapter.
o To delete a network adapter and its associated protocol(s):
Note:
You must remove all protocols from the adapter you wish to
delete before you delete the adapter.
a. Select a protocol in the Current Configuration list.
b. Select Remove to delete that protocol.
c. Select Yes to the Remove Protocol message.
d. Repeat the preceding steps until all protocols have been removed
from the adapter.
e. Select the adapter in the Current Configuration list.
f. Select Remove.
g. Select Yes to the Remove Network Adapter message.
o To add a network adapter:
a. Select the network adapter from the Network Adapters list.
b. Select Add under the Network Adapters list. The newly added
network adapter will appear in the Current Configuration list.
o To add a protocol:
a. Select the network adapter in the Current Configuration list to
which you will add a protocol.
b. Select the desired protocol in the Protocols list.
c. Select Add under the Protocols list. The newly added protocol
will appear under the network adapter in the Current Configuration
list.
Select OK.
For detailed information on the LAPS Configuration window, refer to "
Attended LAPS Configuration" in the MPTS - AnyNet for OS/2:
Configuration Guide.
Note:
If you are running a non-IBM version of NetBIOS/802.2, you may
receive errors during the adapter installation. You will be given
the choice to Proceed or Exit. The errors indicate an
incompatibility between IBM's NetBIOS/802.2 and the non-IBM
version, but do not imply that the installation will be corrupted
or that the LAN Server product will suffer any loss in
functionality or resources. Select Proceed.
6. If a version of OS/2 LAN Requester has already been installed on your
workstation and the LAN Services installation/configuration program
cannot determine which hard disk contains the copy of OS/2 LAN Requester
that is associated with the currently started base operating system, the
LAN Services to Update window is displayed. Select the appropriate drive
letter if you want to upgrade or reinstall. Select None if you want to
run an initial installation of LAN Services.
7. The Installation and Configuration window, which is now displayed,
enables you to move between the Install and Remove window and the
Configure window. Install or remove a component is the default when the
window is displayed for the first time. Select OK.
8. If this is an initial installation, select one or more components that
you want to install in the Install and Remove window; then select
Install.
Note:
You can select more than one component on this window by using the
Spacebar or mouse.
The Action column displays Install for each selected component.
If you decide not to install a component for which Install is displayed
in the Action column, you can undo your selection by using the Cancel
action push button. Select one or more components, and then select
Cancel action. The Action column displays a blank field for each
selected component.
For components that are required, the Action column displays Install
(required); Cancel action cannot be selected for these components.
If a component has been previously installed, the Status column displays
one of the following:
o Installed
The component is at the same version level as your LAN Services
installation/configuration program.
o Later version
This status is possible only if there is a subsequent release to the
LAN Server 4.0 product.
o Earlier version
The component is at an earlier version level than your LAN Services
installation/configuration program; for example the LAN Server 3.0
product and earlier.
o Damaged
The component is at the same version level as your LAN Services
installation/configuration program, but some of the required files are
missing.
To remove previously installed components, select one or more
components; then select Remove. The Action column displays Remove for
each component selected to be removed. If you select to remove the
Requester component, all components are removed.
Note:
You cannot remove the Requester component when upgrading.
If you select Install for previously installed components, the Action
column displays either Install or Replace (if the previously installed
code is at the same level as your LAN Services
installation/configuration program).
If a Corrective Service Diskette (CSD) has been applied to previously
installed code and you are reinstalling a component or installing a new
component, you must reapply the CSD (or a later version) after running
the LAN Services installation/configuration program.
The figure titled OS/2 LAN Requester Installation Worksheet illustrates
two possible settings (Install (required) and Install) for the Action
column during an initial installation of an OS/2 LAN Requester
workstation.
Install and Remove Window on the Requester Installation Path
When you have finished selecting the components to be installed, select
OK.
Note:
For information about the various components that can be
installed, consult Supported Functions and the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
9. In the Installation and Configuration window, select Configure a
component to configure one or more of the components selected for
installation. Then select OK. If you do not want to do any
configuration, proceed with step 13.
You cannot proceed with step 13 if a component selected for installation
is required to be configured (as displayed on the Configure window in
the next step).
10. The Configure window displays the configuration status of the selected
components. Components for which the Status column displays
Configuration required require input and must be selected. Components
for which the Status column (during an initial installation) displays
IBM defaults pending are installed with the IBM-supplied defaults.
However, you may want to select these components and review the defaults
so that you can change them if desired.
The figure titled Configure Window on the Requester Installation Path is
an example of a Configure window illustrating various settings for the
Status column during an initial installation of an OS/2 LAN Requester
workstation. If LAN Services (or the Communications Manager/2 or
DATABASE 2 OS/2 program) has been previously installed, the Status
column displays Configured for some components.
Configure Window on the Requester Installation Path
Select one by one the components that require configuration or that you
want to configure. After selecting each component, select Configure....
One or more configuration windows from which you can select or change
options are displayed.
Warning:
Change defaults with extreme care, because they can affect
performance. For information about a specific item, select that
item and select Help. For information about parameters and how
they affect performance, refer to the LAN Server Network
Administrator Reference Volume 2: Performance Tuning. Do not
change any default parameter that you do not understand.
11. Following the configuration windows, select the options and fill out the
fields pertinent to your workstation. Use the online help facility for
specific information. Selecting OK on the configuration windows
confirms your selections and brings up the next window in the series or
returns you to the main Configure window. Selecting Cancel returns you
to the previous window. For each configured component, the Status
column on the Configure window displays Configured.
The following paragraphs describe the actions to take in the
configuration windows for each configurable component. Because you are
selecting the configurable components in the main Configure window, the
order in which you see the configuration windows can be different from
the order in which they are described.
o If you select Requester in the main Configure window:
a. In the Requester and Domain Names window, type the requester name,
and press Tab to go to the next entry field. Type the domain
name, and then select OK.
Notes:
1. The requester and domain cannot have the same name. The
requester name should not match any workstation name on the
network. In addition, if the requester is being remote
IPLed from a server, the requester name should not match any
user ID on the network. In this case, the workstation name
is specified by the computername parameter in the IBMLAN.INI
file.
2. The requester and domain names are not case-sensitive and
can be 1 to 15 characters (bytes) in length.
3. The first character must not be numeric and the last one
must not be a dollar sign ($). The following characters are
not valid:
" / \ [ ] ; : , | < > + = ? *
Characters below X'21' are also not valid.
4. If you are using the full-screen interface on requesters
with earlier versions of the LAN Server product, the
8-character restriction for user IDs, group IDs, server
names, and domain names still applies. For example, when a
user at a LAN Server 3.0 requester attempts to log on
through the full-screen interface, the interface rejects the
user's ID if it is longer than 8 characters and returns an
error upon receiving a domain name or server name longer
than 8 characters.
b. In the Start Requester window, select Start the requester
automatically if you want the requester to be started
automatically each time the workstation is started. Otherwise,
select Do not start the requester automatically. Then select OK.
c. Set memory access for the network adapter in the Network Adapter -
Direct Memory Access window. Select All network adapters do not
use 24-bit DMA to allow LAN Server buffers to be located above the
16MB physical memory address boundary. Before selecting this
option, do the following:
- Ensure that you have greater than 16MB of physical memory.
- Ensure that the network adapter device drivers are capable of
performing direct memory access (DMA) operations above the 16MB
boundary.
Warning:
Non-BusMaster network interface cards (NIC) are not subject
to the preceding constraints. However, if you have a
BusMaster NIC, determine whether it is capable of performing
DMA above 16MB. Contact the supplier and ask whether your
card has 24 or 32 address lines. If it has 24, it cannot
perform DMA above 16MB. If it has 32, it can. If you are in
doubt, select Network adapter uses only 24-bit DMA
Select At least one network adapter uses only 24-bit DMA if the
Redirector should lock memory below the 16MB boundary (default on
an initial installation).
If displayed, select Use target setting to use the setting from a
previous installation at the target workstation.
d. In the Requester Services window, select which services you want
started when the requester is started. Then select OK.
o If you select LAN Services Adapters in the main Configure window:
a. In the LAN Adapters window, select one or more configured logical
adapters (numbered 0 through 3) for use by OS/2 LAN Requester.
Then select OK.
Note:
For each selected adapter, a netx statement is generated in
the Networks section of the IBMLAN.INI file. Selecting
adapter 0 adds the net1 statement to the IBMLAN.INI file,
selecting adapter 1 adds the net2 statement, and so on. If
you are creating a response file, the LAN Services
installation/configuration program generates response-file
entries reflecting this correspondence. (See Setting
IBMLAN.INI Parameters in Response Files.)
b. For each selected adapter, a NetBIOS Resources window is
displayed. The NetBIOS Resources window states the NetBIOS
requirements (sessions, commands, and names) for your current OS/2
LAN Requester configuration as well as the NetBIOS resources
currently provided by LAPS. Do one of the following:
- If LAPS provides sufficient NetBIOS resources to satisfy OS/2 LAN
Requester requirements, select OK to continue.
- If LAPS provides fewer NetBIOS resources than required by OS/2
LAN Requester, do one of the following:
o Adjust the value for sessions, commands, or names required by
OS/2 LAN Requester by typing a number (in the appropriate
entry field) that is less than or equal to the sessions,
commands, or names provided by LAPS. Select OK.
Note:
Although reducing required resources will not keep
your system from running, doing so can affect OS/2 LAN
Requester performance.
o Select Cancel to return to the LAPS Configuration window and
reconfigure LAPS to provide sufficient NetBIOS resources. The
program will return to the NetBIOS Resources window. Select
OK.
o If you select First Failure Support Technology/2 in the main Configure
window:
a. In the next three FFST/2 configuration windows, do the following:
1. Specify if First Failure Support Technology/2 is to be
autostarted.
2. Specify where the alerts are to be routed if you selected
Autostart.
3. Specify if messages should be displayed on the FFST/2 message
console.
4. Specify the maximum number of system dumps and the maximum
number of application dumps. Both values must be between 8 and
99; the initial default value is 32.
5. If you want to change the default system dump path and
application dump path, you can do so now.
6. Specify the application message log.
Select OK to continue.
b. In the Hardware Vital Product Data configuration window, specify
the workstation type, workstation serial number, and workstation
ID. The type and serial number are on the workstation. The
workstation ID is the name by which you want the workstation to be
known; the ID can be 1 to 8 characters in length. All specified
characters in this window must be alphanumeric, and all alphabetic
characters must be uppercase. The workstation ID need not be
identical to the requester name you specified in the Requester and
Domain Names window.
Select OK to continue.
o If you select Peer Services in the main Configure window, proceed as
follows:
a. In the Security Mode window, select the security mode to be used
by the Peer Service and then select OK.
b. In the Peer Service window, which is displayed only if a copy of
the NET.ACC file is currently on the workstation, select to either
replace or preserve the NET.ACC file. If you replace the NET.ACC
file, all user, group, and access control information is reset,
and a default NET.ACC file that contains the default user ID and
password is installed.
12. When you finish configuring components, you are ready to complete
installation. In the Configure window, select OK.
13. In the Installation and Configuration window, select Apply the changes.
Then select OK.
14. If disk space is not adequate on the hard disk on which LAN Services is
to be installed, the Insufficient Disk Space window displays both the
disk space required to install LAN Services as configured and the
currently available disk space.
The Insufficient Disk Space window may be displayed more than once,
depending on the number of hard disks or logical drives involved in LAN
Services installation. (Some components, such as User Profile Management
(UPM), are always installed on the OS/2 startup drive, which can be
different from the drive you specified in step 3 for LAN Services
installation.)
Do one of the following:
o Select Retry to recalculate disk-space requirements. If sufficient disk
space is available, proceed with step 15. If sufficient disk space is
still not available, the Insufficient Disk Space window is displayed
again.
o If not enough space is available on the hard disk or drive you
specified in the Installation Location window in step 3, and if your
workstation has more than one hard disk or more than one partition on a
single hard disk, select Cancel. Continue to select Cancel in
subsequent windows until you return to the Hard-Disk window. Specify
another drive in the Hard-Disk window and proceed through the LAN
Services installation/configuration program.
o Switch to another OS/2 session and take the appropriate action to make
enough space available. Then return to the current session and select
Retry to recalculate disk-space requirements. You may have to repeat
this step if sufficient disk space is still not available.
15. If you are installing from CD-ROM, you will not be prompted for
diskettes. If you are installing from diskettes, you will be prompted
to insert a specific diskette from the installation package. (Drive A
is the default drive, but you can select a different one.)
Warning:
If you select Exit in any of the following windows, you exit the
LAN Services installation/configuration program, leaving the
product installation in an unknown state. You must restart the
program to install and configure LAN Services.
Be sure to insert the specified diskette into the correct drive, and
then select OK. Insert any additional diskettes as prompted and select
OK. Use diskettes from the same installation package.
The program code is copied from the diskettes onto the hard disk.
Note:
You are not prompted to insert any diskettes if you are only
changing configuration parameters during a reinstallation.
16. The File Backup window is displayed if any of the following files are
modified as a result of running the LAN Services
installation/configuration program:
o CONFIG.SYS
o IBMLAN.INI
o STARTUP.CMD
o PROTOCOL.INI
The File Name column in the File Backup window displays the names of the
configuration files that are modified. The Backup Name column gives you
the location of the unmodified versions of these files.
Select OK.
17. The Default User ID and Password window is displayed if you selected one
of the following:
o To install the Peer service and your workstation does not have a
NET.ACC file currently installed.
o To replace the current NET.ACC file. Use the user ID and password
provided (USERID and PASSWORD, respectively) for the initial logon.
These values can be customized later for subsequent logons. Select OK.
18. The LAN Server product installation is complete message is displayed,
stating that the installation and configuration procedure has completed
successfully. Select OK.
In most cases, you are instructed to shut down your workstation from the
OS/2 desktop. If you are installing from diskette, remove the last
diskette before you shut down your workstation. To shut down your
workstation:
a. Stop all running programs.
b. Move the mouse pointer to an open area on the desktop, and click the
mouse button 2 to display the desktop pop-up menu.
c. Select Shut down.
d. Select OK to confirm the shut down command.
Wait until all disk activity has stopped and a message is displayed
informing you that the shutdown has completed. To restart the system
and implement the changes made by the LAN Services
installation/configuration program, press Ctrl+Alt+Del.
Note:
Unless instructed otherwise, you must shut down and restart the
workstation in the manner described to ensure proper installation
and configuration.
19. If you were instructed to apply a CSD upon completion of the LAN
Services installation/configuration program, do so now.
The OS/2 LAN Requester installation and configuration is complete. You can
customize the LAN Requester code installed on this workstation later by using
the Tailored installation path.
ΓòÉΓòÉΓòÉ 7.7.3. Custom Installation ΓòÉΓòÉΓòÉ
The network administrator can provide users with a custom installation diskette
to assist installation or reinstallation of specified LAN Requester code at
their workstations. Custom installation requires only limited input from the
workstation user.
The LAN Services installation/configuration program provides a guided path to
create a requester custom diskette. You can create a requester custom diskette
that generates menus prompting the workstation user to provide the following
information:
o Domain name
o Requester name
o Peer service user name
o Hardware vital product data (for First Failure Support Technology/2)
To generate user prompts with the LAN Services installation/configuration
program, select Use target setting for any of the listed options for which you
want the requester custom diskette user to provide information during an
initial installation. If you do not want the user prompted for information for
any of the listed options, do not select Use target setting, and provide the
requested information instead.
Notes:
1. If you select Use target setting and the workstation has settings from a
previous installation, the existing settings are used, and the custom
diskette user is not prompted to provide information.
2. To force a user to provide values even if previous target settings
exist, you must modify the LANINST.RSP file on the custom diskette with
an ASCII text editor. (See Missing Values for Keyword Entries.)
Users doing a custom installation should use the custom installation diskette
in place of the Requester - Disk 1, after which they can use any other diskette
from the installation package as prompted.
Note:
Before you prepare the requester custom installation diskette, read
Before You Install. If the diskette is meant to assist in reinstalling
or reconfiguring OS/2 LAN Requester, read also Upgrading and
Reinstalling, Reconfiguring, or Removing.
ΓòÉΓòÉΓòÉ 7.7.3.1. Creating a Requester Custom Diskette ΓòÉΓòÉΓòÉ
Before you begin this procedure, make sure that you have a blank formatted
high-density diskette that is the same size as the diskettes in your
installation package.
Hint:
Make backup copies (using the DISKCOPY command) of the diskettes in your
installation package, and run the LAN Services
installation/configuration program from the backup diskettes. Make sure
that the size of the backup diskettes matches the size of the original
diskettes, and that the diskettes you back up are all from the same
installation package.
To Create a Requester Custom Diskette:
1. Start the LAN Services installation/configuration program in one of the
following ways:
o If you are running the LAN Services installation/configuration program
locally from CD-ROM, follow steps 1 through 5 in Installing OS/2 LAN
Requester.
o If you are running the LAN Services installation/configuration program
locally from diskettes, follow steps 1 through 5 in Installing OS/2 LAN
Requester. You can use either Server - Disk 1 or Requester - Disk 1.
o If you are running the LAN Services installation/configuration program
remotely from the code server, type the remote installation command
described in step 1 in Starting an Attended Remote Installationat the
workstation's command line.
2. Select Tailored in the Easy or Tailored Installation/Configuration
window.
3. In the Installation Tasks window, select Create a requester custom
diskette.
Remember that all the installation and configuration choices made after
this point are for the user's workstation that the network administrator
is preconfiguring.
4. In the Source Drive window, select Do not update an existing copy if the
custom diskette user's workstation does not have any version of OS/2 LAN
Requester (from LAN Server 2.0, 3.0, or 4.0) already installed.
Otherwise, select Update copy on specified drive (default) and specify
which drive on the custom diskette user's workstation contains the copy
of LAN Requester from which configuration information will be retrieved.
If you do not want any information retrieved, select Do not update an
existing copy.
Note:
Decisions you make in this window take effect only if the LAN
Services installation/configuration program cannot determine
during custom installation which drive contains the copy of OS/2
LAN Requester from which to retrieve information. If the program
can identify the appropriate drive, information is retrieved from
the LAN Requester copy on that drive, regardless of your
selections in the Source Drive window.
Select OK to continue.
5. In the Installation Location window, select OK if you want the user to
install OS/2 LAN Requester on the hard disk on which the previous
version (if any) is currently installed. In the absence of a previous
version, this selection causes OS/2 LAN Requester to be installed on the
target workstation's OS/2 startup drive. Otherwise, specify another
drive and select OK to continue.
Only the IBMLAN subdirectory is installed on the drive you specify. The
MUGLIB and IBM386FS subdirectories are always installed on the OS/2
startup drive.
6. Follow the instructions in Tailored Installation beginning at step 7
through step 12. Keep in mind the following differences from the regular
Tailored installation path:
o In the Install and Remove window (step 8 in Tailored Installation), you
can select an additional push button. Select Install if required to let
the LAN Services installation/configuration program determine whether
existing code (if any) on the user's workstation should be replaced.
The Action column changes the displayed status of each selected
component to Install (if required). During actual custom installation,
the selected components are installed on the user's workstation unless
the code already installed is at the same or later level.
Note:
If you select Install if required and the custom diskette is
used for an initial installation, the component is installed
only if it is one of the default components installed during an
initial CD-ROM or diskette-based Easy installation. For a list
of default components, see Easy Installation.
If you select Install, the Action column displays Install. During
actual remote installation, the selected components are installed on
the target workstation unless the code already installed is a later
level.
Note:
If the code already installed is a later level (for example,
for User Profile Management or FFST/2, which might have been
installed by the Communications Manager/2 or DATABASE 2 OS/2
program), the LAN Services installation/configuration program
ends, and no new code is installed.
o Complete the configuration windows as described in step 11 in Tailored
Installation remembering that you have the option to select Use target
setting if you want to preserve the workstation's configuration
parameters from a previous installation.
If you select Use target setting in either the Requester and Domain
Names window or the Hardware Vital Product Data window, the custom
diskette user is prompted for input unless the workstation has settings
from a previous installation.
Note:
To force the custom diskette user to provide input for any of
these windows, even if target settings exist, you must modify
the response file with an ASCII editor. (See Missing Values
for Keyword Entries.)
Complete the following windows as described:
- In the Requester and Domain Name windows, you have the option to
specify one name, both names, or none at all:
a. Select Use target setting (default) for each item for which you
want the custom diskette user prompted to provide a name during
an initial custom diskette installation.
If the user's workstation has settings from a previous
installation, the existing setting is used, and the user is not
prompted to provide information.
b. Deselect Use target setting for each name you want to provide,
and type the name in the appropriate entry field. The name or
names that you provide cannot be changed by the custom diskette
user.
- In the Hardware Vital Product Data window, you have the option to
specify any or none of the requested workstation data:
a. Select Use target setting (default) for each item for which you
want the custom diskette user prompted to provide a name during
an initial custom installation.
If the user's workstation has settings from a previous
installation, the existing setting is used, and the user is not
prompted to provide information.
b. Deselect Use target setting for each item for which you want to
provide the data, and type the correct information in the
appropriate entry field. The data you provide cannot be changed
by the custom diskette user.
7. In the Installation and Configuration window, select Apply the changes.
Then select OK.
8. When prompted, label and insert a blank formatted high-density diskette.
(Drive A is the default drive, but you can select a different one.)
Label the diskette as instructed. Be sure to insert the labeled diskette
into the correct drive, and then select OK.
The Requester - Disk 1 and any other files needed to support
installation and configuration by means of a custom diskette are copied
onto a blank diskette. The size of the custom diskette must match the
size of the original installation diskettes.
When copying is complete, the Requester Custom Diskette Creation
Complete window is displayed. Select Yes if you want to create a custom
diskette for another requester. Otherwise, select No.
Note:
If you create a custom diskette for another requester, the
selections you made for the current custom diskette are shown as
defaults. You can change the defaults.
The requester custom diskette can now be used instead of Requester - Disk 1 to
support installation or reinstallation on the user's workstation. The user must
still insert any other diskette from the installation package as prompted. See
the following section for instructions for using the custom diskette.
The LANINST.RSP file on the custom diskette contains the installation and
configuration selections you made when creating the diskette. You can modify
the LANINST.RSP file using an ASCII text editor. For detailed information, see
Response File Keywords Used in Remote Installation.
ΓòÉΓòÉΓòÉ 7.7.3.2. Using a Requester Custom Diskette ΓòÉΓòÉΓòÉ
To install LAN Requester code with the help of a requester custom diskette, use
the custom diskette created with Creating a Requester Custom Diskette (instead
of Requester - Disk 1), the remaining requester disks, and the Network Adapter
Drivers diskette of the installation package. You must be in an active OS/2
full-screen or window session.
To Use a Requester Custom Diskette:
1. Insert Requester Custom Disk 1 into drive A.
2. Type:
A:INSTALL
Press Enter.
3. A message states that the LAN Services installation/configuration
program is being copied. When the IBM logo is displayed, select OK.
Note:
If you are running a non-IBM version of NetBIOS/802.2, you may
receive errors during the adapter installation. You will be given
the choice to Proceed or Exit. The errors indicate an
incompatibility between IBM's NetBIOS/802.2 and the non-IBM
version, but do not imply that the installation will be corrupted
or that the LAN Server product will suffer any loss in
functionality or resources. Select Proceed.
4. If the creator of the custom diskette did not supply the requester or
domain name, the custom diskette user is prompted either to accept the
default requester or domain name set during a previous installation and
configuration (if applicable) or to provide a name. Follow the
instructions in step 11a in Tailored Installation. The same applies to
hardware vital product data (if the custom diskette creator selected to
install FFST/2). In this case, follow the instructions in step 11b in
Tailored Installation.
Users are also prompted to insert specific diskettes from the
installation package.
5. If disk space is inadequate on the hard disk on which LAN Services is to
be installed, the Insufficient Disk Space window is displayed. This
window states both the disk space required to install LAN Services as
configured and the currently available disk space. If the window is
displayed, the user should do one of the following:
o Select Retry to recalculate disk-space requirements. If sufficient disk
space is available, proceed with inserting diskettes as requested. If
sufficient disk space is still not available, the Insufficient Disk
Space window is displayed again.
o Switch to another OS/2 session and take the appropriate action to make
enough space available. Then return to the current session and select
Retry to recalculate disk-space requirements. The user might have to
repeat this step if sufficient disk space is still not available.
o Select Exit to end the LAN Services installation/configuration program.
No changes are made to any of the workstation's hard disks or logical
drives.
6. The Insufficient Disk Space window can be seen more than once, depending
on the number of hard disks or logical drives involved in LAN Services
installation. (Some components such as User Profile Management are
always installed on the OS/2 startup drive, which can be different from
the drive the custom diskette creator specified for LAN Services
installation.)
7. Depending on the selections of the creator of the custom diskette, the
Default User ID and Password window might be displayed. Follow the
instructions in step Tailored Installation.
8. After an Installation/Configuration Complete message is displayed, the
user should shut down and restart the workstation if instructed to do
so. (See step Tailored Installation.)
ΓòÉΓòÉΓòÉ 7.8. Reinstalling, Reconfiguring, or Removing ΓòÉΓòÉΓòÉ
The following sections describe procedures for reinstalling, reconfiguring, or
removing OS/2 LAN Server, OS/2 LAN Requester, or some of their functions. All
three actions are possible when running the LAN Services
installation/configuration program locally from CD-ROM, diskettes, custom
diskettes, or a hard disk, or when running the LAN Services
installation/configuration program remotely.
ΓòÉΓòÉΓòÉ 7.8.1. Reinstalling ΓòÉΓòÉΓòÉ
Reinstalling refers to installing the OS/2 LAN Server or OS/2 LAN Requester
component of the LAN Server product on a workstation that already has either of
these LAN Server components installed. You may need to reinstall, for example,
if you decide to install an additional component, such as the DOS Remote IPL
service. Also, you may want to install a higher-level installation package.
For example, you can install the Advanced package over the Entry package to
enhance your server workstation with the 386 HPFS.
Before you begin reinstalling, read Migration of Data.
ΓòÉΓòÉΓòÉ 7.8.1.1. Reinstalling OS/2 LAN Server ΓòÉΓòÉΓòÉ
To reinstall OS/2 LAN Server, follow the instructions in Installing OS/2 LAN
Server, keeping in mind the following:
Follow the Easy installation path if your changes are limited to:
o Changing the domain name.
o Changing the server name.
o Refreshing the code (that is, reinstalling the same components as previously
installed and configured).
o Moving the LAN Server product. For more information, refer to Upgrading or
Reinstalling on a Different Hard Disk.
o Installing the Easy default components of a higher-level package in addition
to currently installed components. For a list of default components for each
package, see Easy Installation.
Remember that when following the Easy path, you cannot change the server type
(additional server, domain controller, or backup domain controller). To change
the server type, follow the Tailored installation path.
Before applying the changes, you must stop the network software on the server
to end all connections that requesters may have with the server. The
installation program will stop the requester or server automatically. A
confirmation window will prompt you to select OK.
Note:
If other users are accessing shared resources on the server, stopping
network software on the server can cause them to receive an error the
next time they try to access a resource. Use the NET SESSIONS command to
determine which users have connections to the server, and warn those
users before stopping the software. For more detailed information, see
the online LAN Server Commands and Utilities.
If a Corrective Service Diskette (CSD) has been applied to previously installed
4.0 code, you must reapply the CSD (or a later version) after running the LAN
Services installation/configuration program.
ΓòÉΓòÉΓòÉ 7.8.1.2. Reinstalling OS/2 LAN Requester ΓòÉΓòÉΓòÉ
To reinstall OS/2 LAN Requester, follow the instructions in Installing OS/2 LAN
Requester, keeping in mind the following:
Follow the Easy installation path if your changes are limited to:
o Changing the domain name
o Changing the requester name
o Refreshing the code (that is, reinstalling the same components as previously
installed and configured)
Otherwise, follow the Tailored installation path.
Before applying the changes, (step 7 in Easy Installation in the Easy path;
step 13 in Tailored Installation in the Tailored path), you must stop the
network software on the requester by typing the following command at the
requester command line:
NET STOP REQUESTER /Y
where the /Y switch suppresses the prompt for confirmation to stop the
requester. If a CSD has been applied to previously installed code, you must
reapply the CSD (or a later version) after running the LAN Services
installation/configuration program.
ΓòÉΓòÉΓòÉ 7.8.2. Reconfiguring ΓòÉΓòÉΓòÉ
You can reconfigure (that is, change the values set during the previous
configuration) OS/2 LAN Server or OS/2 LAN Requester at any time without having
to reinstall. Follow the instructions in Installing OS/2 LAN Server or
Installing OS/2 LAN Requester. Follow the Tailored path, which leads to the
Installation and Configuration window.
To see the main Configure window, select Configure a component, and then select
OK. Proceed with step 11 in Tailored Installation if you are reconfiguring OS/2
LAN Server, or with step 10 in Tailored Installation if you are reconfiguring
OS/2 LAN Requester. Before applying the changes, stop the network software as
described in Reinstalling.
ΓòÉΓòÉΓòÉ 7.8.3. Removing ΓòÉΓòÉΓòÉ
To remove components of OS/2 LAN Server or OS/2 LAN Requester follow the
instructions in Installing OS/2 LAN Server or Installing OS/2 LAN Requester.
Follow the Tailored installation path, and remove components from the Install
and Remove window (step 9 in Tailored Installation or step 8 in Tailored
Installation). Before applying the changes, stop the network software as
described in Reinstalling.
Notes:
1. If you are removing or changing a server on which LAN Server for
Macintosh* is installed, the Macintosh support component should first be
removed or reinstalled. Otherwise, the support component will be
disabled.
2. If you are removing DOS or OS/2 remote IPL and there are remote IPL
clients defined on the server, you must delete the clients before remote
IPL can be removed.
To remove the entire OS/2 LAN Server component from a server, select Remove LAN
Server from this workstation in the Installation Tasks window (step 2 in
Tailored Installation). To remove the entire OS/2 LAN Requester component from
a requester, select Remove LAN Requester from this workstation on the
Installation Tasks window (step 2 in Tailored Installation). Alternatively,
select Server or Requester for removal in the Install and Remove window.
Total removal deletes the IBMLAN, MUGLIB, and IBM386FS subdirectories from the
workstation. However, if either the Communications Manager/2 or DATABASE 2
OS/2 program is also installed on the workstation, the MUGLIB subdirectory is
not deleted.
ΓòÉΓòÉΓòÉ 7.8.3.1. Removing the 386 HPFS ΓòÉΓòÉΓòÉ
Before removing the 386 HPFS from your server, you must use the BACKACC utility
to back up the access control profiles for 386-HPFS drives. Then run the LAN
Services installation/configuration program and select to remove 386 HPFS in
the Install and Remove window. When LAN Services installation has completed,
run the RESTACC utility to restore the previously deleted and backed-up access
control profiles.
To remove the 386-HPFS option, you should always use the Install and Remove
window. During the removal process, all access control profiles in the 386-HPFS
file system are removed, allowing the file system to be used by the OS/2 HPFS.
If you do not use the Install and Remove window, access control profiles can be
left in the file system. This situation prevents access by the OS/2 HPFS file
system. For more information about the BACKACC and RESTACC utilities, see the
LAN Server Network Administrator Reference Volume 3: Network Administrator
Tasks.
ΓòÉΓòÉΓòÉ 8. Remote Installation ΓòÉΓòÉΓòÉ
This chapter assists you in setting up and starting a remote installation of
OS/2 LAN Server and OS/2 LAN Requester.
During a remote installation, the product code, instead of being copied from
diskettes, is downloaded from a central workstation, the code server, to one or
more target workstations. The CD-ROM can be used like a code server, as well.
To start the process, an installation command statement must be issued at the
target workstation. The files are downloaded from a subdirectory structure
that you create, called a remote installation subdirectory. This subdirectory
structure is located on the code server and contains a copy of the LAN Server
product diskettes.
The target workstation is an OS/2 workstation that must be able to access the
shared information on the code server. The code server is either a LAN Server
2.0 or higher workstation or an OS/2 workstation that has another means of
sharing installed.
Sharing refers to the concept of making resources available to other
workstations. To access a shared resource on the remote machine, a local
device name must be assigned to the remote shared resource. Typically, a drive
letter, called a redirected drive, is used to access a remote drive,
subdirectory, or file. For more information on sharing, see Resource Sharing
and the LAN Server Network Administrator Reference Volume 3: Network
Administrator Tasks.
This chapter includes information about the means of sharing resources on the
code server and about the software required to enable the target workstation to
access the shared resources.
ΓòÉΓòÉΓòÉ 8.1. Types of Remote Installation ΓòÉΓòÉΓòÉ
LAN Server supports three types of remote installation:
o Unattended
Unattended remote installation is started by a software distribution manager
(SDM), which initiates and manages the installation of LAN Server on the
target workstation.
One example of an SDM is the LAN Configuration Installation Distribution
Utility (LAN CID Utility), which is shipped with LAN Server. An SDM may or
may not require user input to begin its process. But once the SDM
installation process begins, installation of OS/2 LAN Server or OS/2 LAN
Requester proceeds without requiring any user input at the target
workstation. Installation information is obtained from a response file,
which the network administrator makes available, usually on the code server.
A response file contains information that is normally provided by the user
through menu selections.
One advantage of using an SDM such as the LAN CID Utility is that it enables
you to install multiple products on a machine during a single installation
process.
o Lightly attended
Lightly attended remote installation requires a user at the target
workstation to issue an installation command. When started, the LAN Services
installation/configuration program can require the user to provide minimal
installation details (such as the workstation ID and domain name). As with
an unattended installation, other installation information is obtained from a
response file, usually on the code server.
o Attended
Attended remote installation requires a user at the target workstation to
issue an installation command and answer installation questions before the
code is downloaded from the code server. No response file is required.
Note:
Though you might prefer to locate the response files for unattended and
lightly attended remote installation on the code server, they can be
located on any drive accessible to the target workstation. For the sake
of simplicity, assume that your response files are located on the code
server.
ΓòÉΓòÉΓòÉ 8.2. Hardware and Software Requirements ΓòÉΓòÉΓòÉ
The hardware and software requirements that apply to standard local
installation (using CD-ROM or diskettes) also apply to remote installation.
(Refer to Planning Your Network.) In addition, make sure that the code server
and target workstation meet the following requirements:
o OS/2 1.3, 2.0, or 2.1 must be installed on the code server.
Note:
Refer to the documentation provided with the base operating system
for installation information.
o LAN Adapter and Protocol Support (LAPS) must be installed on the code server
and the target workstation.
Note:
For configuration information, see the MPTS - AnyNet for OS/2:
Configuration Guide.
ΓòÉΓòÉΓòÉ 8.3. Software for Sharing and Redirection ΓòÉΓòÉΓòÉ
If you want to install multiple products at the same time (using an SDM such as
the LAN CID Utility), or if you are initially installing OS/2 LAN Server and
OS/2 LAN Requester on your network, you typically use the Service Installable
File System (SRVIFS) or NetView DM/2 as a means of sharing on the code server.
Notes:
1. SRVIFS provides limited-function sharing and file redirection. One of
its functions is to enable unattended remote installation with the LAN
CID Utility. SRVIFS is provided by the Multi-Protocol Transport
Services (MPTS) product, which is shipped with LAN Server.
2. NetView DM/2 provides much the same functionality as SRVIFS except for
DOS LAN Services. Attended, lightly attended, and unattended remote
installation with the LAN CID Utility are all possible. NetView DM/2 is
not part of LAN Server and must be purchased separately.
If you are upgrading OS/2 LAN Server or OS/2 LAN Requester workstations, you
can also consider using LAN Server 2.0 or higher on the code server for
sharing.
To have access to shared information on a code server that uses LAN Server 2.0
or higher as a means of sharing, the target workstation must have OS/2 LAN
Requester (from LAN Server 2.0, 3.0, or 4.0) installed. If the code server
uses SRVIFS as a means of sharing, the target workstation must also have SRVIFS
installed.
This chapter provides abbreviated instructions for installing SRVIFS and refers
you to the appropriate documentation for more detailed information.
ΓòÉΓòÉΓòÉ 8.4. Installation Requirements and Restrictions ΓòÉΓòÉΓòÉ
The following requirements and restrictions apply to remote installation in
addition to those listed for local installation (using CD-ROM or diskettes) in
Installation Requirements and Restrictions.
o Unattended remote installation is not supported on workstations installed
with Local Security.
To install remotely on a workstation with Local Security, you can run a
lightly attended remote installation. Alternatively, you can run the LAN
Services installation/configuration program locally first to remove Local
Security (see Removing), and then run a normal unattended remote
installation.
o Universal naming convention (UNC) names are not supported.
o After copying product diskettes to a code server, the directory structure and
files associated with the product diskettes must not be modified. Product
diskettes are defined as files directly copied under the remote installation
subdirectory, subdirectories beginning with IBM, and the files within these
subdirectories. The remote installation may not proceed properly if these
files are altered.
For a schematic of a code server's directory structure and files, see File
Structure for the Remote Installation Subdirectory.
o It is recommended that you store newly created product diskette files in a
new subdirectory to prevent other files in an existing subdirectory from
being deleted when product diskette files are updated. When you update
product diskette files, all files under the specified remote installation
subdirectory, all subdirectories beginning with IBM under the specified
subdirectory, and the files within these subdirectories are removed and
replaced.
o Administration for the Remote IPL service is not supported by the remote
installation feature. The RIPLINST and GETRPL utilities are not run by the
LAN Services installation/configuration program. You must run these
utilities on each remote IPL server after remote installation is complete.
For more information about these utilities, see the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
ΓòÉΓòÉΓòÉ 8.5. Remote Installation Procedure ΓòÉΓòÉΓòÉ
To Set Up and Start a LAN Server Remote Installation:
1. Install LAN Server on the code server.
2. Use the LAN Services installation/configuration program to copy the LAN
Server product diskettes to a code server.
Notes:
a. It is not necessary to have LAN Server installed to run the LAN
Services installation/configuration program.
b. If you need to copy the product diskettes to a remote code server,
use sharing provided by either LAN Server 2.0 (or higher) or
SRVIFS.
For step-by-step instructions, see Copying LAN Server Product Diskettes
to the Code Server or Copying LAN Server CD-ROM to the Code Server.
3. Create response files for those target workstations where you plan to
use lightly attended or unattended remote installation. A response file
is not needed for attended remote installation.
A response file provides some or all of the installation details for a
workstation, such as:
o Workstation ID and domain name
o Drive on which to install
o Various components and network services to install
o Network services to autostart
Use the guided path provided by the LAN Services
installation/configuration program to create response files. For
step-by-step instructions, see Creating a Response File for an OS/2
Client.
Note:
It is not necessary to have LAN Server installed to run the LAN
Services installation/configuration program.
After you have created a response file, you can use an ASCII text editor
to modify certain keywords and values. For detailed information about
the response file format, processing the files, and the directory
structure for response files, see Response Files.
4. Enable the target workstation to share the copied files from the product
diskettes and from the response file. Refer to Enabling the OS/2 Target
Workstation.
5. Start the remote installation at the target workstation in either of two
ways:
o For a user-initiated installation, issue the appropriate installation
command at the target workstation. For step-by-step instructions, see
Starting a Lightly Attended Remote Installation or Starting an Attended
Remote Installation.
o For an SDM-initiated installation, use startup diskettes or command
files created with the LAN CID Utility. Refer to Starting an Unattended
Remote Installation.
ΓòÉΓòÉΓòÉ 8.5.1. Copying LAN Server CD-ROM to the Code Server ΓòÉΓòÉΓòÉ
To copy the LAN Server CD-ROM to the code server, use the XCOPY command to copy
the IBMLSA or IBMLSE directory to the code server.
Alternatively, the CD-ROM can be used as a code server. The CD-ROM directory
structure is the same as that on a code server to which LAN Server has been
copied. The only prerequisite is that the CD-ROM drive needs to be accessed by
means of redirection.
ΓòÉΓòÉΓòÉ 8.5.2. Copying LAN Server Product Diskettes to the Code Server ΓòÉΓòÉΓòÉ
Remote installation requires either:
o That you share a CD-ROM and use it as a code server. For information on
sharing a CD-ROM, refer to the LAN Server Network Administrator Reference
Volume 3: Network Administrator Tasks.
o That you copy LAN Server product diskettes to the code server before
initiating the installation.
To copy LAN Server product diskettes to a remote installation subdirectory on
the code server, switch to an OS/2 full-screen or window session.
Hint:
Make backup copies (using the DISKCOPY command) of the diskettes in your
installation package and run the LAN Services installation/configuration
program from the backup diskettes. Make sure that the size of the
backup diskettes matches the size of the original diskettes and that the
diskettes you back up are all from the same installation package.
To Copy LAN Server Diskettes to the Code Server:
1. Insert Server - Disk 1 into a diskette drive.
2. Type the installation command:
d:INSTALL
where d is the diskette drive letter.
Press Enter.
3. When the IBM logo is displayed, select OK.
4. In the Easy or Tailored Installation/Configuration window, select
Tailored.
5. In the Installation Tasks window, select Copy product diskettes for
remote installation. Then select OK.
6. In the Copy Product Diskettes window, select LAN Services. To copy one
or more versions of DOS to the remote installation subdirectory, also
select DOS. Then select OK.
Note:
A version of DOS is required for any remotely installed server
that supports the DOS Remote IPL service.
Warning:
If you specify an existing path in the following window, all
subdirectories in the specified path beginning with the prefix IBM
and their contents are removed and replaced.
7. In the Remote Installation Subdirectory window, either accept the
default path or type a path in which to save the LAN Server product
diskettes. Then select OK. If you specify a path that does not
currently exist, it is created if the path name is valid.
If you plan to use the LAN CID Utility, specify a directory that
corresponds to the directory structure used by that utility. See the LAN
CID Utility Guide for more information.
You can place the subdirectory on any local or remote hard disk. If the
code server is running on OS/2 Standard Edition 1.3, you must specify a
remote drive.
8. If you selected to copy DOS product diskettes, the DOS Version Required
window is displayed. Select each version of DOS needed for servers
installing the DOS Remote IPL service, and then select OK.
If you select to copy MS-DOS diskettes (SBCS systems only), you are
prompted to indicate the number of MS-DOS diskettes you have. Specify
the correct number and select OK.
If you select to install DOS 5.0, you must create the DOS 5.0 diskettes
before they can be copied by the LAN Services installation/configuration
program. Make sure you have available blank, formatted diskettes and
proceed as follows:
a. Minimize the current LAN Services installation/configuration program
window.
b. Insert the DOS 5.0 Installation diskette into drive A.
c. From the Command Prompts folder, select DOS from Drive A. The
workstation begins to start from the DOS Installation diskette.
d. Follow the instructions on the screen until the default settings are
displayed.
e. If the default is to install to the hard disk, use the arrow keys to
select Install to.... Press Enter.
f. Select Floppy Disks and press Enter.
g. When Install to: Floppy Disks is displayed, press Enter.
h. Follow the instructions on the screen to complete the installation of
DOS 5.0 to diskettes.
i. When prompted, press Enter. Press Ctrl+Esc to return to the OS/2
desktop.
j. Select and close DOS from Drive A in the Window List.
k. Maximize the current LAN Services installation/configuration program
window and continue with the program.
9. You are prompted to insert a specific diskette from the installation
package. Insert the specified diskette into the correct drive and
select OK. Insert any additional diskettes as prompted and select OK.
Use diskettes from the same installation package.
The program code is copied from the diskettes into the remote
installation subdirectory.
10. In the Installation Tasks window, select to exit the LAN Services
installation/configuration program, or select to create a server or
requester response file.
ΓòÉΓòÉΓòÉ 8.6. Response Files ΓòÉΓòÉΓòÉ
A response file is an ASCII file that consists of keywords and their values
that describe the installation details for a target workstation. Response
files are used in lightly attended and unattended remote installation. You can
create response files using the guided path provided by the LAN Services
installation/configuration program (see Creating a Response File for an OS/2
Client) or by using an ASCII text editor. In addition, you can:
o Edit response files created by the LAN Services installation/configuration
program later.
o Create two types of response files, group and client, to simplify remote
installation.
A client response file specifies options that are unique to a given workstation
or set of workstations on the network. A group response file specifies options
that are common to a group of workstations. During the actual remote
installation, the LAN Services installation/configuration program includes
information from specified group response files in the client response file.
For detailed information about the format of client response files and how
client and group response files are processed, see How Response Files Are
Processed.
It is important to understand the response file format, how response files are
processed, and what directory structure is required.
ΓòÉΓòÉΓòÉ 8.6.1. Response File Format ΓòÉΓòÉΓòÉ
If you are creating or changing a response file with a text editor, keep the
following guidelines in mind:
o Keywords and values follow the format:
keyword=value
Embedded blanks are accepted:
keyword = value
o Keywords and values are not case sensitive; you can use any combination of
uppercase or lowercase alphanumeric characters as long as they are valid for
the keyword.
o Comment lines are preceded by a semicolon. A comment line can be added
anywhere in a file, as in:
;This is comment text
o Use the UpdateIBMLAN, DeleteIBMLAN, and AddIBMLAN keywords in a response file
to modify parameters in the target workstation's IBMLAN.INI file. For more
information, see Keywords and Keyword Values That Affect the IBMLAN.INI File.
o If there are duplicate keywords in a response file, only the last occurrence
of the keyword and its value is recognized.
Note:
A response file can have multiple instances of the UpdateIBMLAN,
DeleteIBMLAN, AddIBMLAN, and Include keywords.
o During remote installation, the cleanup parameter is always set to Y if the
autodisconnect parameter value is set to -1, regardless of the cleanup value
specified by the user.
For descriptions of response file keywords and their values, and examples of
requester and server response files, see Response File Keywords Used in Remote
Installation.
ΓòÉΓòÉΓòÉ 8.6.2. Planning a Response File Subdirectory Structure ΓòÉΓòÉΓòÉ
If you are installing a number of workstations that share similar traits, you
can save time by creating two types of response files (client and group) and
storing them in a directory structure where they can be accessed by the target
workstation.
Create and use group and client response files as follows:
o Group
A group response file is one you create within the group level or
subdirectory for target workstations in the network that share a common
trait. For example, you may want to create one response file for all
workstations defined as domain controllers, one response file for all
workstations defined as backup domain controllers, one response file for
workstations defined as additional servers, and another response file for
workstations defined as requesters.
You can use an ASCII text editor or the guided path provided by the LAN
Services installation/configuration program to create a group response file.
(See Creating a Response File for an OS/2 Client.)
A group response file is accessed by specifying the /G switch in the
installation command statement. (See step 1 in Starting a Lightly Attended
Remote Installation.) In addition, the Include keyword (specifying the file
name of the included group response file) must be present in the client
response file.
For example, if you want to include the GROUP1.RSP response file in the
CLIENT1.RSP file, add the following line to the CLIENT1.RSP file:
INCLUDE = GROUP1.RSP
For more information, see How Response Files Are Processed and Customizing
Response Files.
o Client
A client response file is one you create within the client level or
subdirectory to specify options that are unique to a given workstation or set
of workstations in the network. Examples of response file input on the client
level are the computername and domain parameters for a workstation within a
domain.
You can use an ASCII text editor to create a client response file. If you
use the guided path provided by the LAN Services installation/configuration
program (see Creating a Response File for an OS/2 Client), be sure to modify
the response file with an ASCII text editor to add one or more Include
keywords that specify the group response files to be processed.
A client response file is accessed by specifying the /R switch in the
installation command statement. (See step 1 in Starting a Lightly Attended
Remote Installation.)
When you create response files using the LAN Services
installation/configuration program, they are stored in the default \IBMLSRSP
subdirectory unless you specify a different subdirectory.
A recommended path for storing group response files is:
d:\IBMLSRSP\GROUPx\filename
A recommended path for storing client response files is:
d:\IBMLSRSP\GROUPx\CLIENTx\filename
In both cases, d is a drive letter, x is a number, and filename is the name of
a response file.
ΓòÉΓòÉΓòÉ 8.6.3. How Response Files Are Processed ΓòÉΓòÉΓòÉ
When using response files for remote installation, keep the following
guidelines in mind:
o The full path to the client response file must be specified by the /R switch
of the installation command statement.
o All client response files that specify an Include keyword require the /G
switch in the installation command statement.
o All group response files called by Include keywords in a client response file
must be in the path defined by the /G switch in the installation command
statement.
o The maximum number of response files that can be combined using the Include
keyword is 10. The length of the final composite response file cannot exceed
64KB.
Response files are processed in the following way during lightly attended and
unattended remote installation:
o When the /R switch is specified in the installation command statement, the
client response file is processed first.
o Any group response files are processed as they are encountered in one or more
Include keywords in the client response file.
o Response files are processed from top to bottom; duplicate keywords are
overridden as they are encountered; that is, only the last instance is
recognized.
Note:
Because more than one group response file can be called, there can be
multiple occurrences of the Include keyword. Also, the UpdateIBMLAN,
DeleteIBMLAN, and AddIBMLAN keywords can have multiple entries to
modify several IBMLAN.INI parameters. For more information, see
Keywords and Keyword Values That Affect the IBMLAN.INI File.
o The final response file that is used for remote installation comprises the
combined client and group keywords.
ΓòÉΓòÉΓòÉ 8.6.3.1. Example ΓòÉΓòÉΓòÉ
To illustrate this process, assume that you have a client response file named
CLIENT1.RSP and group response files named GROUP1.RSP and GROUP2.RSP that are
included in CLIENT1.RSP.
The GROUP1.RSP and GROUP2.RSP files contain the following keywords:
GROUP1.RSP
InstallServer = INSTALL
ConfigServerType = MIGRATE
GROUP2.RSP
InstallMSGPopup = INSTALL
InstallGUI = INSTALL
InstallClipBoard = INSTALL
Your CLIENT1.RSP file contains the following keywords:
CLIENT1.RSP
INCLUDE = GROUP1.RSP
.
.
.
UPDATEIBMLAN = REQUESTER
<COMPUTERNAME = PROSPERO
DOMAIN = TEMPEST>
.
.
.
Install386HPFS = INSTALLIFREQUIRED
Config386Cache = WSDETERMINESIZE
ConfigLazyWrite = IMMEDIATE
ConfigHeap = WSDETERMINESIZE
.
.
.
INCLUDE = GROUP2.RSP
After processing the included group files, the resulting composite response
file used for remote installation contains the following keywords in the order
shown:
InstallServer = INSTALL
ConfigServerType = MIGRATE
.
.
.
UPDATEIBMLAN = REQUESTER
<COMPUTERNAME = PROSPERO
DOMAIN = TEMPEST>
.
.
.
Install386HPFS = INSTALLIFREQUIRED
Config386Cache = WSDETERMINESIZE
ConfigLazyWrite = IMMEDIATE
ConfigHeap = WSDETERMINESIZE
.
.
.
InstallMSGPopup = INSTALL
InstallGUI = INSTALL
InstallClipBoard = INSTALL
For the meaning of the various keywords and their values, refer to Response
File Keywords Used in Remote Installation.
ΓòÉΓòÉΓòÉ 8.6.4. Customizing Response Files ΓòÉΓòÉΓòÉ
You must create response files to install remotely using lightly attended or
unattended installation. To save time, you can model and customize response
files using either of the following methods:
o Copy the IBM-supplied default response file and modify its keywords.
o Create group and client response files, and include one or more group
response files in a client response file for workstations that share similar
traits.
To illustrate the second method, assume that you plan to install three
additional servers, named NANCY, ZOE, and BOSKY. You can create one response
file called ADDSERVR.RSP, which contains all the keywords common for all
additional servers:
ADDSERVR.RSP
InstallServer = INSTALL
ConfigServerType = ADDITIONALSERVER
ConfigSourceDrive = C
ConfigTargetDrive = C
.
.
.
.
.
.
.
.
.
To customize response files for the three additional servers, create three
client response files containing workstation-unique keywords. In the following
examples, the keyword UpdateIBMLAN is used to specify the workstation ID and
domain name for each additional server:
NANCY.RSP
INCLUDE = ADDSERVR.RSP
UPDATEIBMLAN = REQUESTER
<COMPUTERNAME = NANCY>
UPDATEIBMLAN = REQUESTER
<DOMAIN = SCOOBY>
ZOE.RSP
INCLUDE = ADDSERVR.RSP
UPDATEIBMLAN = REQUESTER
<COMPUTERNAME = ZOE>
UPDATEIBMLAN = REQUESTER
<DOMAIN = SCOOBY>
BOSKY.RSP
INCLUDE = ADDSERVR.RSP
UPDATEIBMLAN = REQUESTER
<COMPUTERNAME = BOSKY>
UPDATEIBMLAN=REQUESTER
<DOMAIN = SCOOBY>
Notice that the generic group file (ADDSERVR.RSP) has been included at the top
of each file. Now assume that you are starting the remote installation of
NANCY (the installation command statement specifies to process
/R:d:\path\NANCY.RSP). When the client response file NANCY.RSP is processed,
the group keywords in ADDSERVR.RSP are combined with the NANCY
workstation-unique keywords.
The resulting response file looks like this:
InstallServer = INSTALL
ConfigServerType = ADDITIONALSERVER
ConfigSourceDrive = C
ConfigTargetDrive = C
.
.
.
UPDATEIBMLAN = REQUESTER
<COMPUTERNAME = NANCY>
UPDATEIBMLAN = REQUESTER
<DOMAIN = SCOOBY>
The response files ZOE.RSP and BOSKY.RSP for the two other additional servers
ZOE and BOSKY are processed in the same way, if correctly specified in the
installation command statement.
Using the Include keyword in client response files eliminates the need to copy
identical keywords into multiple response files.
For the meaning of the various keywords and their values, refer to Response
File Keywords Used in Remote Installation.
ΓòÉΓòÉΓòÉ 8.6.5. Planning a Response File for an OS/2 Client ΓòÉΓòÉΓòÉ
Unattended and lightly attended remote installations require that you specify
installation details for the target workstation in a response file.
The installation program will prompt for any of the following information if it
is missing from the response file:
o Domain name
o Server name
o Requester name
o Hardware vital product data (for First Failure Support Technology/2)
Notes:
1. If you select Use target setting and the target workstation has settings
from a previous installation, the existing settings are used, and the
user is not prompted to provide information.
2. To force a user to provide values even if previous target settings
exist, you must modify the response file with an ASCII text editor.
(See Missing Values for Keyword Entries.)
3. Generate user prompts with the LAN Services installation/configuration
program by selecting Use target setting for any of the listed options
for which you want the user at the target workstation to provide
information during an initial installation.
4. If you do not want the user prompted for information for any of the
listed options, do not select Use target setting, and provide the
requested information in the response file instead.
If you plan to install multiple workstations with identical configurations, you
can create one response file with user prompts to provide workstation-specific
information. This installation would be a lightly attended remote installation.
Unattended installations require that all information be provided either from
the response file or from settings at the target workstation from a previous
installation.
ΓòÉΓòÉΓòÉ 8.6.6. Creating a Response File for an OS/2 Client ΓòÉΓòÉΓòÉ
This section provides step-by-step instructions for creating a response file,
using the guided path provided by the LAN Services installation/configuration
program. Note that this path is similar to creating a custom installation
diskette.
Note:
To customize a response file using an ASCII editor, refer to Response
Files, which also describes the response file format, processing
response files, and the directory structure that is required.
To Create a Response File:
1. Switch to an OS/2 full-screen or window session.
2. Start the LAN Services installation/configuration program in one of
three ways:
o To run the LAN Services installation/configuration program locally from
CD-ROM, insert the CD-ROM into the CD-ROM drive drive, and then go to
step 3.
o To run the LAN Services installation/configuration program locally from
diskettes, insert Server - Disk 1 into a diskette drive, and then go to
step 3.
o To run the LAN Services installation/configuration program remotely,
type the remote installation command described in step 1 in Starting an
Attended Remote Installation, and then go to step 5.
Note:
You can run the LAN Services installation/configuration program
remotely only if your system has been previously set up for
remote installation as described in Enabling the OS/2 Target
Workstation.
3. Type the installation command:
d:INSTALL
where d is the drive letter.
Press Enter.
4. A message states that the LAN Services installation/configuration
program is being copied. When the IBM logo is displayed, select OK.
5. In the Easy or Tailored Installation/Configuration window, select
Tailored.
6. In the Installation Tasks window, select Create a server response file
for remote installation or Create a requester response file for remote
installation. Then select OK.
Remember that all the installation and configuration choices made after
this point are for the user's workstation that the network administrator
is preconfiguring for remote installation.
Note:
If you are preparing for a default initial installation of the
target workstation, be sure to select Install if required for all
items in the Install and Remove window (see step 11) and Use
target setting in all configuration windows. The user at the
target workstation then essentially performs an initial Easy
installation. For a list of default components installed during
an initial Easy installation, see Easy Installation (server) or
Easy Installation (requester).
7. In the Response File Name window, either accept the default path and
file name, or type the path and file name in which to save the response
file. Then select OK.
The default path and file name for OS/2 LAN Server is:
C:\IBMLSRSP\LANSRV.RSP
The default path and file name for OS/2 LAN Requester is:
C:\IBMLSRSP\LANREQ.RSP
If you plan to create multiple response files, change the default file
name to a unique name. It is a good idea to name each new response file
using the workstation ID as part of the file name. For example, the
response file intended for a workstation named NANCY could be called
NANCY.RSP.
Note:
If you are using the LAN CID Utility as your SDM for an unattended
remote installation, refer to the LAN CID Utility Guide for
directory structure requirements.
Though you might prefer to locate response files on the code server,
they can be located on any drive that can be accessed by the target
workstation.
8. In the Source Drive window, select Do not update an existing copy if the
workstation you are installing remotely does not have any version of
OS/2 LAN Server (4.0 or earlier) or any version of OS/2 LAN Requester
(from LAN Server 2.0, 3.0, or 4.0) already installed.
Otherwise, select Update copy on specified drive (default) and specify
which drive on the workstation contains the copy of OS/2 LAN Server or
OS/2 LAN Requester from which configuration information will be
retrieved. Select Do not update an existing copy if you do not want any
information retrieved.
Note:
Decisions you make in this window take effect only if, during
remote installation, the LAN Services installation/configuration
program cannot determine which drive contains the copy of OS/2 LAN
Server or OS/2 LAN Requester from which to retrieve information.
If the LAN Services installation/configuration program can
identify the appropriate drive, information will be retrieved from
the OS/2 LAN Server or OS/2 LAN Requester copy on that drive,
regardless of your selections in the Source Drive window.
Select OK to continue.
9. In the Hard Disk window, select OK if you want to install OS/2 LAN
Server or OS/2 LAN Requester on the target workstation's hard disk on
which the previous version (if any) is currently installed. Without a
previous version, this selection causes OS/2 LAN Server or OS/2 LAN
Requester to be installed on the target workstation's OS/2 startup
drive. Otherwise, specify another drive and select OK to continue.
Only the IBMLAN subdirectory is installed on the drive you specify. The
MUGLIB and IBM386FS subdirectories always are installed on the OS/2
startup drive.
10. In the Server Type window (server installation only), select one of the
following:
o Additional server, if you want to configure the workstation as an
additional server in an existing domain
o Domain controller, if you want to configure the workstation as a domain
controller
o Backup domain controller, if you want to define the workstation as a
backup domain controller
o Use target setting, if you want to preserve the current server type of
the target workstation (defined during a previous installation)
Note:
If you select Use target setting and the response file is used for
an initial installation, an additional server is installed on the
target workstation.
Then select OK.
11. Follow the instructions for Tailored installation described in the
appropriate sections of LAN Services Installation and Configuration:
Note:
Read the rest of the information in this step first to understand
the differences from the regular Tailored path.
o For a server installation, follow step 8 through 13 in Tailored
Installation.
o For a requester installation, follow step 7 through 12 in Tailored
Installation.
Differences from the Tailored Path
o In the Install and Remove window, (step 9 in Tailored Installation or
step 8 in Tailored Installation), you can select an additional push
button. Select Install if required if you want to let the LAN Services
installation/configuration program determine whether existing code (if
any) on the target workstation should be replaced. The Action column
changes the displayed status of each selected component to Install (if
required). During remote installation, the selected components are
installed on the user's workstation, unless the code already installed
is at the same or later level.
Note:
If you select Install if required and the response file is used
for an initial installation on the target workstation, the
component is installed only if it is one of the default
components installed during an initial, diskette-based Easy
installation. For a list of server and requester default
components, see Easy Installation and Easy Installation,
respectively.
If you select Install, the Action column displays Install. During
actual remote installation, the selected components are installed on
the target workstation, unless the code already installed is a later
level.
Note:
If the code already installed is a later level (for example,
for User Profile Management or FFST/2, which might have been
installed by the Extended Services program), the LAN Services
installation/configuration program ends. No new code is
installed on the target workstation.
o Complete the configuration windows as described in step 12 in Tailored
Installation (server installation) or step 11 in Tailored Installation
(requester installation), remembering that you have the option to
select Use target setting if you want to preserve the target
workstation's configuration parameters from a previous installation.
If you select Use target setting in the Server and Domain Names window,
the Requester and Domain Names window, or the Hardware Vital Product
Data window, the user at the target workstation will be prompted for
input during a lightly attended remote installation unless the target
workstation has settings from a previous installation.
Note:
To force the user at the target workstation to provide input
for any of these windows, even if target settings exist, you
must modify the response file with an ASCII editor. (See
Missing Values for Keyword Entries.)
During an unattended remote initial installation, an error will be
logged and the LAN Services installation/configuration program will end
if you do not provide the requested information and no settings are
available from a previous installation.
Complete these windows as described:
- In the Server and Domain Name windows or Requester and Domain Name
windows, you have the option to specify one name, both names, or
none at all:
o Select Use target setting (default) for each name for which you
want the user at the target workstation prompted to provide a
name during an initial, lightly attended remote installation.
If a target workstation has settings from a previous
installation, the existing setting is used, and the user is not
prompted to provide information.
o Deselect Use target setting for each name you want to provide,
and type the name in the appropriate entry field. The names you
provide cannot be changed by the user at the target workstation.
- In the Hardware Vital Product Data window, you have the option to
specify any or none of the requested workstation data:
o Select Use target setting (default) for each item for which you
want the user at the target workstation prompted during an
initial, lightly attended remote installation.
If a target workstation has settings from a previous
installation, the existing setting is used, and the user is not
prompted to provide information.
o Deselect Use target setting for each item for which you want to
provide the data, and type the correct information in the
appropriate entry field. The data you provide cannot be changed
at the target workstation.
12. In the Installation and Configuration window, select Apply the changes.
Then select OK.
13. The response file is completed and you are returned to the Installation
Tasks window. Select to exit the LAN Services installation/configuration
program or select to create another server or requester response file.
ΓòÉΓòÉΓòÉ 8.6.7. Enabling the OS/2 Target Workstation ΓòÉΓòÉΓòÉ
To enable the target workstation for remote installation, you must make
resources on the code server available to the target workstation and make it
possible for the target workstation to access those resources. More
specifically, the code server must be enabled to share the drive or the
subdirectories containing the copy of the product diskettes and the response
file; the target workstation must be enabled to access this drive or these
subdirectories.
Note:
For simplicity, this chapter assumes that you save the response file or
files on the code server. You can, however, locate response files on
any drive that can be accessed by the target workstation. If the
response file or files are located on a hard disk on a remote
workstation, that workstation must be enabled for sharing in the same
way as described for the code server in the following two sections.
As explained in Software for Sharing and Redirection, you can use either LAN
Server (2.0 or higher), NetView DM/2, or the Service Installable File System
(SRVIFS) as a means of sharing, depending on your particular situation.
ΓòÉΓòÉΓòÉ 8.6.7.1. Using SRVIFS ΓòÉΓòÉΓòÉ
Note:
Refer to the LAN CID Utility Guide for detailed information on
installing and using SRVIFS and the THINSRV, THINIFS, and SRVATTCH
utilities mentioned in the following instructions. SRVIFS and the
utilities are provided by the MPTS product and are shipped with LAN
Server.
To Enable the Target Workstation, Using SRVIFS:
1. Use the THINSRV utility to install SRVIFS on the code server.
2. Install OS/2 and LAPS on the target workstation if you have not already
done so.
3. Use the THINIFS utility to install SRVIFS on the target workstation.
4. Shut down and restart the target workstation to run the SRVATTCH
statement in the CONFIG.SYS file.
5. Start the code server using the SERVICE.EXE command.
6. If you completed the preceding steps correctly following the guidelines
in the LAN CID Utility Guide, connections to either the drive or the
subdirectories containing the copy of the product diskettes and the
response file have now been created.
Issue further SRVATTCH commands at a command-line prompt as needed to
use aliases provided at the code server.
Note:
After completing the remote installation, consider deleting SRVIFS from
the target workstation. Refer to the LAN CID Utility Guide for
instructions.
ΓòÉΓòÉΓòÉ 8.6.7.2. Using LAN Server ΓòÉΓòÉΓòÉ
If you plan to use LAN Server 2.0 or higher as the means of sharing on the code
server, refer to the LAN Server Network Administrator Reference Volume 3:
Network Administrator Tasks for information about sharing network resources and
to the OS/2 LAN Requester User's Guide for information about assigning shared
resources. Remember that the target workstation must have OS/2 LAN Requester
(from LAN Server 2.0, 3.0, or 4.0) installed.
ΓòÉΓòÉΓòÉ 8.6.8. Enabling the DOS LAN Services Target Workstation ΓòÉΓòÉΓòÉ
To enable the target workstation for remote installation, you must make
resources on the code server available to the target workstation and make it
possible for the target workstation to access those resources. More
specifically, the code server must be enabled to share the drive or the
subdirectories containing the copy of the product diskettes and the response
file; the target workstation must be enabled to access this drive or these
subdirectories.
ΓòÉΓòÉΓòÉ 8.6.8.1. Using NetView DM/2 ΓòÉΓòÉΓòÉ
If you plan to use NetView DM/2 as the means of sharing on a DOS LAN Services
code server, the following tasks must be performed:
1. Transfer diskette images to the NetView DM/2 server in preparation for a
CID install of PC DOS, LAN Support Program, NetView DM/2, and DOS LAN
Services.
2. Create a seed diskette for the transfer of minimal PC DOS, LAN Support
Program, NetView DM/2, and DOS LAN Services code to a workstation without
an installed operating system (a pristine system).
3. Install PC DOS, LAN Support Program NetView DM/2, and DOS LAN Services on
the requester.
For the steps associated with each of these tasks and for detailed conceptual
information on NetView DM/2, refer to CID Enablement of DOS Local Area
Networks.
ΓòÉΓòÉΓòÉ 8.6.9. Starting a Lightly Attended Remote Installation ΓòÉΓòÉΓòÉ
Note:
MPTS must be installed on the target workstation before LAN Server when
using a response file.
To Start a Lightly Attended Remote Installation:
1. To start the LAN Services installation/configuration program, enter the
following at a command-line prompt on the target workstation:
o For a server installation:
d:\path\LANINSTR /SRV /R:d:\path\filename [/G:d:\path] [/L1:d:\filename]
[/L2:d:\filename]
o For a requester installation:
d:\path\LANINSTR /REQ /R:d:\path\filename [/G:d:\path] [/L1:d:\filename]
[/L2:d:\filename]
where: .
[ ] Indicate optional parameters.
d Specifies an accessible hard-disk drive. The
drive name must be followed by a fully qualified
path name (or file name, where indicated). The
specified drives need not be identical.
d:\path\LANINSTR Runs the LAN Services installation/configuration
program.
d:\path is the path to the remote installation
subdirectory structure on the code server.
/SRV Specifies that you are installing server code.
/REQ Specifies that you are installing requester code.
/R Specifies the fully qualified file name of the
response file or the client response file to use
for installation on the target workstation.
If you are not using any group response files,
specify your response file here. If you created
client and group response files following the
guidelines in Response Files, specify your client
response file here.
/G Specifies the fully qualified path name of all
group response files included in the client
response file.
Do not use this parameter if you did not create
any group response files.
If you created client and group response files
following the guidelines in Response Files,
specify the path name to your group response file
or files here. Do not specify a file name.
/L1 Specifies the fully qualified path name of the
error log on the code server (or any accessible
drive). The error log is always available in the
OS2\INSTALL\IBMLANER.LOG file on the target
workstation, regardless of whether this parameter
is set.
/L2 Specifies the fully qualified path name of the
history log on the code server (or any accessible
drive). The history log is always available on
the target workstation in the
OS2\INSTALL\IBMLSHST.LOG file, regardless of
whether this parameter is set.
2. A message states that the LAN Services installation/configuration
program is being copied. When the IBM logo is displayed, select OK.
3. The user at the target workstation follows essentially the same path as
the custom diskette user except that no diskettes have to be inserted to
load the LAN Server product code. Refer to Using a Server Custom
Diskette or Using a Requester Custom Diskette.
Error messages and messages that require input are displayed at the
target workstation. If a critical error occurs, the LAN Services
installation/configuration program ends.
Note:
If the network administrator, when planning for an initial remote
installation, created a response file by selecting Install if
required for all items in the Install and Remove window, and Use
target setting in all configuration windows, the user at the
target workstation essentially performs an initial Easy
installation.
4. After the remote installation is completed, the target workstation user
may be instructed to shut down the workstation from the OS/2 desktop and
restart it by pressing Ctrl+Alt+Del.
5. Check the error log and the history log at either the target workstation
or the drive you specified in the /L1 and /L2 switches in the
installation command statement to ensure that the installation completed
normally.
ΓòÉΓòÉΓòÉ 8.6.10. Starting an Unattended Remote Installation ΓòÉΓòÉΓòÉ
Initiate an unattended remote installation by using a software distribution
manager (SDM), such as the LAN Configuration Installation Distribution Utility
(LAN CID Utility). The LAN CID Utility enables you to install several products
remotely (such as OS/2, Communications Manager/2, DATABASE 2 OS/2, or LAN
Server), using only one REXX command file and sharing provided by SRVIFS. To
install on workstations without any existing software, you can create startup
diskettes to start the installation program.
Notes:
1. The LAN CID Utility is part of the MPTS product, which is shipped with
LAN Server.
2. If you plan to use the LAN CID Utility to upgrade LAN Server 2.0 or 3.0
remotely, read also Upgrading LAN Server 2.0 or 3.0 Using the LAN CID
Utility.
To install LAN Server, the LAN CID Utility uses the LANINSTR installation
command and parameters described in Starting a Lightly Attended Remote
Installation.
Note:
When you use the installation command statement as part of a LAN CID
Utility command file, you have the option of specifying your response
file using the RSPDR and DEFAULT parameters instead of the /R switch.
You must specify either the /R switch or the RSPDIR and DEFAULT
parameters. If you specify values for all three values, the LAN CID
Utility concatenates all three values causing undesirable results. If
you specify only the /R parameter (full path and file name), the LAN CID
Utility uses that response file. If instead, you specify values for
RSPDIR and DEFAULT, the LAN CID Utility first searches the directory
name assigned to RSPDIR for a response file called computername.RSP
where computername is the name of the target workstation. If the utility
cannot find that name, it searches the same directory for the name you
specified in the DEFAULT parameter.
Remember not to specify the /G switch in the LANINSTR command if you are
not using a group response file.
The LAN Services installation/configuration program detects that the
installation command is being run under an SDM and automatically goes into
unattended (as opposed to lightly attended) mode. Where error messages or
messages that require input would be displayed during a lightly attended
installation, errors are logged. The LAN Services installation/configuration
program ends if a critical error occurs.
For detailed information about using the LAN CID Utility for unattended remote
installation, see the LAN CID Utility Guide.
ΓòÉΓòÉΓòÉ 8.6.11. Starting an Attended Remote Installation ΓòÉΓòÉΓòÉ
To Start an Attended Remote Installation:
1. To start the LAN Services installation/configuration program, enter one
of the following installation command statements at a target
workstation's command line:
o For a server installation:
d:\path\LANINSTR /SRV [/L1:d:\filename] [/L2:d:\filename]
o For a requester installation:
d:\path\LANINSTR /REQ [/L1:d:\filename] [/L2:d:\filename]
where: .
[ ] Indicate optional parameters.
d Specifies an accessible hard-disk drive. The
drive name must be followed by a fully qualified
path name (or file name, where indicated). The
specified drives need not be identical.
d:\path\LANINSTR Runs the LAN Services installation/configuration
program.
d:\path is the path to the remote installation
subdirectory structure on the code server.
/SRV Specifies that you are installing server code.
/REQ Specifies that you are installing requester code.
/L1 Specifies the fully qualified file name of the
error log on the code server (or any accessible
drive). The error log is always available on the
target workstation in the
OS2\INSTALL\IBMLANER.LOG file, regardless of
whether this parameter is set.
/L2 Specifies the fully qualified file name of the
history log on the code server (or any accessible
drive). The history log is always available on
the target workstation in the
OS2\INSTALL\IBMLSHST.LOG file, regardless of
whether this parameter is set.
2. A message states that the LAN Services installation/configuration
program is being copied. When the IBM logo is displayed, select OK.
3. The user at the target workstation essentially follows the same path as
for a fully attended, local installation except that no diskettes have
to be inserted to load the LAN Server product code.
For step-by-step instructions to install OS/2 LAN Server, refer to Easy
Installation or Tailored Installation.
For step-by-step instructions to install OS/2 LAN Requester, refer to
Easy Installation or Tailored Installation.
Error messages are displayed at the target workstation. If a critical
error occurs, the LAN Services installation/configuration program ends.
4. After the remote installation is completed, the target workstation user
may be instructed to shut down the workstation from the OS/2 desktop and
restart the target workstation by pressing Ctrl+Alt+Del.
5. Check the error log and the history log at either the target workstation
or the drive specified by the /L1 and /L2 switches in the installation
command statement to ensure that the installation completed normally.
ΓòÉΓòÉΓòÉ 8.7. File Structure for the Remote Installation Subdirectory ΓòÉΓòÉΓòÉ
The figure titled Remote Installation Subdirectory Structure is an example of a
remote installation subdirectory used to store product diskettes on the code
server. Do not modify the files directly under the base subdirectory, the
subdirectories, or the files within these subdirectories; otherwise, your
installation may not proceed properly.
The default remote installation subdirectory names provided by LAN Server are:
o C:\IBMLSE (LAN Server-Entry)
o C:\IBMLSA (LAN Server-Advanced)
When copying the LAN Server CD-ROM or diskettes to the code server (see Copying
LAN Server CD-ROM to the Code Server or Copying LAN Server Product Diskettes to
the Code Server), you can specify a different name for the remote installation
subdirectory, but you cannot change the name of any of the other
subdirectories. The following subdirectory is for LAN Server-Advanced:
Remote Installation Subdirectory Structure
ΓòÉΓòÉΓòÉ 9. Installing and Optimizing DOS LAN Services ΓòÉΓòÉΓòÉ
This chapter helps you to install DOS LAN Services, upgrade a PC LAN Program
Version 1.3 (or later) requester to DOS LAN Services, and enable DOS LAN
Requester users to upgrade their workstations. Note that the latter option is
available only for DOS LAN Services from OS/2 LAN Server 1.3 or later. This
chapter also explains how to make more conventional memory on a DOS LAN
Services workstation available for applications.
If you plan to use DOS LAN Services Windows functions, you must install (1) DOS
LAN Services using the instructions in this chapter, and (2) Windows using the
Windows documentation. The order in which you install these components is not
important. After installation, refer to Changing the DOS LAN Services
Configuration, for additional information.
Note:
This chapter describes how to install DOS LAN Services on DOS. If you
want to run DOS LAN Services on OS/2, refer to Installing and Running
DOS LAN Services on OS/2, for more information.
ΓòÉΓòÉΓòÉ 9.1. Installing DOS LAN Services ΓòÉΓòÉΓòÉ
DOS LAN Services is provided by the LAN Server product and can be installed on
a requester in one of the following ways:
o Installing DOS LAN Services from CD-ROM.
o Installing DOS LAN Services from diskettes. Users at PC LAN Program Version
1.3 (or later) Base Services requesters must use this method. Users at PC
LAN Program Version 1.3 (or later) Communications Manager/2 or DATABASE 2
OS/2 requesters can also install DOS LAN Services from diskettes. See
Installing DOS LAN Services from CD-ROM or Diskettes for instructions.
Note:
DOS requesters without hard disks can receive DOS LAN Services IPL
images by diskette or by remote IPL from a server. For more information,
see DOS LAN Services and the LAN Server Network Administrator Reference
Volume 3: Network Administrator Tasks.
ΓòÉΓòÉΓòÉ 9.1.1. Installing DOS LAN Services from CD-ROM or Diskettes ΓòÉΓòÉΓòÉ
This section describes how to install DOS LAN Services on DOS workstations. If
you need additional DOS sessions to run other DOS applications, you can use
OS/2 2.0 to create emulated versions of DOS. DOS LAN Services is not supported
on emulated DOS sessions. For more information about using DOS LAN Services on
OS/2 workstations, refer to Installing and Running DOS LAN Services on OS/2.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: DOS LAN Services Windows is Γöé
Γöé not available in the Asian version of DOS 5.0. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Hints:
o If you reinstall Windows after installing DOS LAN Services, run the DOS
LAN Services installation program (INSTALL.EXE).
o If you change the DOS LAN Services configuration file (NETWORK.INI), run
the DOS LAN Services installation program (INSTALL.EXE) to make your
changes take effect.
o You cannot start DOS LAN Services while the DOS shell is running.
Therefore, either move the DOSSHELL statement after the DOS LAN Services
information in your AUTOEXEC.BAT file, or comment out the DOSSHELL
statement in the AUTOEXEC.BAT file after installing the DOS program.
DOS LAN Services is provided by the LAN Server product. To install DOS LAN
Services from diskettes, your workstation must have a hard disk. To prepare
for installation, use the DOS LAN Services Installation Worksheet. The
worksheet outlines the information you need before installing DOS LAN Services.
To Install DOS LAN Services:
1. Ensure that you have installed a network adapter in the DOS workstation.
Refer to the documentation that came with the adapter for more
information.
2. If you have not already done so, install DOS using the DOS installation
documentation. For the supported versions of DOS, refer to Software
Requirements and Compatibility.
3. To use DOS LAN Services with the Windows interface, install Windows or
Windows for Workgroups (using the Windows documentation).
4. If the DOS shell is running, press F3 to exit from the DOS shell.
5. If you are installing from a CD-ROM, start the DOS LAN Services
installation program by typing:
d:\DLS\INSTALL
where d represents the drive letter for the CD-ROM.
6. If you are installing from diskettes, insert DOS LAN Services - Disk 1
in diskette drive A or B and start the installation program by typing:
d:INSTALL
where d represents the drive into which you placed the DOS LAN Services
- Disk 1.
7. Follow the instructions displayed on the screen until you see the
installation window shown in the figure titled DOS LAN Services
Installation Options Window 1.
Note:
If you need more information about any of the Install windows,
press F1 for help.
DOS LAN Services Installation Options Window 1
8. The Installation Options Window 1 lists DOS LAN Services configuration
information for the workstation. Ensure that each option is set
correctly. To change an option:
a. Use the Up Arrow () or Down Arrow () key to highlight the field you
want to change.
b. Press the Enter key to change the highlighted field.
The fields in the Installation Options Window 1 are defined as follows:
Graphical User Interface Specifies whether the graphical user interface
is installed with DOS LAN Services.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: Asian versions of DOS 5.0 Γöé
Γöé do not support the DOS LAN Services graphical user interface. DOS Γöé
Γöé 5.0/V does support the graphical user interface. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Peer Services Specifies whether Peer Services is installed with DOS LAN
Services. Peer services allows you to share disks and printers
with other network stations.
Windows Support Specifies whether Windows support is installed with DOS
LAN Services. You need to install Windows support if you will
use DOS LAN Services in Windows.
Protocol Driver Specifies the protocol driver for the network adapter
card installed in your workstation.
After you have verified your selections, select The listed options are
correct and press Enter. The installation window depicted in the figure
titled DOS LAN Services Installation Options Window 2 displays.
DOS LAN Services Installation Options Window 2
9. The Installation Options Window 2 also lists DOS LAN Services
configuration information for the workstation. Ensure that each option
is set correctly.
The fields in the Installation Options Window 2 are defined as follows:
Machine ID Specifies the machine ID for the DOS workstation. DOS LAN
Services automatically gives your computer the same name as
your user name, but you can select a different name if you
want. If you select a machine ID that is different from your
user name, the machine ID should not match any user ID or
computername on the network.
User name Identifies you as a member of the network. Select a name that
no one else in the network is using. For example, you could
combine your first and last names, such as NANCYC or JAMESP.
Domain name Specifies the default domain name for your DOS workstation to
access. DOS LAN Services allows you to log on to domains other
than your default domain. If you are not logged on to a
specific domain, the resources in that domain do not appear
when you browse for resources; however, you can connect to
resources in other domains if you know the names of those
resources.
Redirector Specifies the type of redirector that DOS LAN Services uses.
The redirector transfers requests from the DOS requester to a
server on the network. DOS LAN Services has three redirectors:
basic redirector The basic redirector helps conserve workstation
memory. Use the basic redirector if you:
o Do not have much memory on your workstation
o Do not want to use aliases (nicknames assigned by an
administrator) to identify resources
o Do not plan to use Windows
o Are using a workstation with an 8086 processor
When using the basic redirector, the logon processing is
performed locally (on your workstation) without password
validation at a remote server. You cannot use the basic
redirector if you are using DOS LAN Services with the
Windows interface.
full redirector The full redirector provides support for using aliases
to identify resources and support for using Windows. The
full redirector also provides support for server validation
of the user name and password at logon. Although the full
redirector uses more memory than the basic redirector,
consider using the full redirector because it provides
greater function, improved performance, and full API
support. The full redirector is the default redirector when
not installing Windows support.
virtual redirector The virtual redirector optimizes memory usage when
in the Windows interface. The virtual redirector frees low
memory to be used by other Windows applications. This is
the default redirector when you are running DOS LAN Services
in the Windows interface.
Startup option Specifies the options to run at startup. Select one of
the following:
Do not run DOS LAN Services Specifies not to start DOS LAN Services at
system startup. As a result, you will have to type NET
LOGON at the DOS command prompt to start DOS LAN Services,
after which you will be prompted to log on.
Run DOS LAN Services only Starts DOS LAN Services with each system
startup. You must type NET LOGON at the DOS command prompt
to gain access to shared resources.
Run DOS LAN Services and log on (default) Starts DOS LAN Services and
prompts you to log on to your requester with each system
startup.
Path Specifies the path to the subdirectory in which to install DOS
LAN Services. The path must specify drive C, D, E, or F. The
following characters for the directory name are valid:
a through z
A through Z
0 through 9
! @ # $ ┬░ - _ & () {} ^ ~
Network card Specifies the type of network adapter card installed in your
workstation.
After you have verified your selections, select The listed options are
correct and press Enter.
10. The next window displays the settings for the network card. The DOS LAN
Services installation program automatically detects the network card you
are using and configures DOS LAN Services for that adapter card. Press
Enter to accept the settings.
11. When instructed, restart the workstation (press Enter) to complete the
installation program.
Note:
If you are running on an Ethernet adapter and using the
DXME0MOD.SYS and DXMT0MOD.SYS device drivers for IEEE 802.2
support, you must add CF=Y to the DXMT0MOD.SYS line in your
CONFIG.SYS file. For more information on the CF parameter, refer
to Summary of the Keyword Values for the NetBIOS New Parameters.
Restart your DOS workstation to make the CONFIG.SYS change active.
If you have any problems setting up DOS LAN Services, see the CONNECT.TXT file,
which is in the directory that contains the DOS LAN Services files. This ASCII
file contains problem determination information for DOS LAN Services
installation. You can view CONNECT.TXT by using any ASCII text editor.
For the steps to change your configuration, refer to Changing the DOS LAN
Services Configuration.
ΓòÉΓòÉΓòÉ 9.2. Changing the DOS LAN Services Configuration ΓòÉΓòÉΓòÉ
When you run the DOS LAN Services installation program (INSTALL.EXE), you
provide or confirm information about the hardware and software you use. This
information is stored in the NETWORK.INI configuration file. The NETWORK.INI
file is located in the directory where you installed DOS LAN Services.
If you change any configuration information, you must run the DOS LAN Services
installation program (INSTALL.EXE) again.
Some common situations in which you need to update your configuration include
the following:
o You want to change your domain name.
o You have changed your network adapter.
o You want to change your startup options.
You can use the installation program to change one or more settings without
reinstalling the DOS LAN Services files.
To Change Your Configuration from Windows:
1. Select File Manager.
2. Open the directory in File Manager where you installed DOS LAN Services.
The default is the NET directory.
3. Start the DOS LAN Services installation program (INSTALL.EXE) by
double-clicking on the program name. The installation program examines
your hardware and software configuration and displays a list of what it
detected.
4. Select the setting that needs to be updated by using the Up Arrow () or
Down Arrow () key, and then press Enter.
5. To change the setting, follow the instructions on the window.
To Change Your Configuration from the DOS Prompt:
1. Change to the directory that contains the DOS LAN Services files. For
example, if the DOS LAN Services files are in the NET directory on drive
C, type the following command at the DOS command prompt and press Enter:
CD C:\NET
2. From the command line, type:
INSTALL
and press Enter. The DOS LAN Services installation program starts. This
program examines your hardware and software configuration and displays a
list of what it detected.
3. Select the setting that needs to be updated by using the Up Arrow () or
Down Arrow () key, and then press Enter.
4. To change the setting, follow the instructions on the screen. If you
need help, press F1.
ΓòÉΓòÉΓòÉ 9.3. Upgrading DOS LAN Requester by Installing DOS LAN Services Remotely ΓòÉΓòÉΓòÉ
DOS LAN Requester users at workstations with a hard disk can upgrade their
version of DOS LAN Requester to DOS LAN Services by running the INSTALL command
from a server that has DOS LAN Services installed. This upgrade option is
available only for DOS LAN Requester from OS/2 LAN Server 2.0 or later. To
upgrade to DOS LAN Services, you can either connect to the directory containing
the installation program or define the installation program as a public DOS
application. These two options are described in the following steps.
To Upgrade by Connecting to the Install Directory:
o Connect to the directory on the server that contains the installation
program and run it from the remote drive. The following procedure
explains the prerequisites for running the installation program from the
remote drive:
1. Create a directory on the server for the installation files. For
example, at an OS/2 prompt, type the following command and press
Enter:
MD C:\DLSINST
2. Copy the DOS LAN Services diskettes into the newly created directory.
3. Share the directory by creating an alias and an access control
profile. For example, create the alias DLS for the C:\DLSINST
directory and assign read (R) access to the USERS group in the access
control profile. Refer to the LAN Server Network Administrator
Reference Volume 3: Network Administrator Tasks for more information.
4. Connect to the shared directory from the requester by assigning a
local drive letter and running the NET USE command at a DOS command
prompt, as follows:
NET USE X: DLS
where X is local drive letter that you assign to the directory on the
server. Press Enter.
5. To invoke the installation program, type the local drive letter
followed by the INSTALL command, as follows:
X:INSTALL
where X specifies the local drive letter assigned to the shared
directory.
For example, if you entered NET USE E: DLS, then you would type the
following:
E:INSTALL
To Upgrade by Defining the Installation Program as a Public DOS
Application:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: Because the full screen Γöé
Γöé interface is not supported on DOS LAN Requester 2.0/3.0 on DBCS Γöé
Γöé systems, this procedure is not supported in DBCS countries. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
o Define the installation program as a public DOS application on the server
and grant appropriate access permission to the DOS LAN Requester users.
To define the installation program (INSTALL.EXE) as a public DOS
application and add it to the user's Served Applications window, proceed
as follows on your server workstation:
Note:
For more detailed information about each step, see the LAN Server
Network Administrator Reference Volume 3: Network Administrator
Tasks.
1. Log on to the domain as an administrator.
2. Create a directory and define it as a directory alias.
3. Modify the access control profile of this directory alias to ensure
that the group USERS has read (R) access.
4. Using the Create DOS Application window, define a public DOS
application specifying the following field values:
Field Value
Application ID DLSSETUP
Description DLS Version x.x (where x.x is the
version number)
DOS command line INSTALL.EXE
Alias Name of alias created in step 2
Remaining path to program \
Assigned drive *
Prompt user for parameters? No
5. Make a working directory for the upgrade option as follows:
a. In the Manage DOS Applications window, select DLSSETUP.
b. Select Actions from the action bar.
c. Select Working directory from the Actions pull-down menu.
d. Complete the Working Directory window by specifying the following
field values:
Field Value
Working directory Name of alias created in step 2
Remaining path \
Assigned drive *
6. Add the upgrade option to the user's Served Applications window as
follows:
a. In the Manage DOS Applications window, select DLSSETUP.
b. Select Selector from the action bar.
c. Select Add from the Selector pull-down menu.
d. Using the Spacebar, select the user IDs that will have access to
the upgrade option.
Note:
If you want all users to access the upgrade option, select
F6=All.
7. To activate the upgrade option on a DOS LAN Requester workstation:
a. Start the DOS LAN Requester workstation.
b. At the DOS command prompt, type:
NET START
Press Enter.
c. To start the DOS LAN Requester graphical user interface, type:
INITFSI
Press Enter, and then type:
NET
Again press Enter.
d. Log on to the domain as a user.
e. Select DLS Version x.x from the Served Applications window.
f. After all disk activity has stopped, restart the workstation to
implement the changes.
When the workstation has been successfully upgraded, the user should delete the
upgrade option (DLS Version x.x) from the Served Applications window.
ΓòÉΓòÉΓòÉ 9.4. Configuring DOS LAN Services Windows ΓòÉΓòÉΓòÉ
If you have Windows already installed when you install DLS (with Windows
support), the DLSSETUP program runs automatically the next time you start
Windows. However, if you install Windows again after installing DLS, you will
need to run the INSTALL command and select Windows support.
If you are running on an Ethernet adapter and using the DXME0MOD.SYS and
DXMT0MOD.SYS device drivers for IEEE 802.2 support, you must add CF=Y to the
DXMT0MOD.SYS line in your CONFIG.SYS file. For more information about the CF
parameter, refer to Summary of the Keyword Values for the NetBIOS New
Parameters. Restart your DOS workstation to make the CONFIG.SYS change active.
ΓòÉΓòÉΓòÉ 9.5. Modifying the DOS LAN Services Windows Configuration ΓòÉΓòÉΓòÉ
If you receive a message from the DLSSETUP program that the Windows system
settings cannot be modified, it may be necessary to modify these settings using
an ASCII editor such as Windows Notepad.
Note:
The WINSETUP program (from DOS LAN Requester 3.0) has been changed to
the DLSSETUP program for DOS LAN Services.
To modify the Windows system settings, use an ASCII editor to edit the
SYSTEM.INI file in the Windows directory and insert or modify the selections as
follows:
[Network]
COMPUTERNAME=Name
LANROOT=C:\NET
DOMAIN=DefaultDomain
[Boot]
NETWORK.DRV=DLSNET.DRV
[Boot.Description]
NETWORK.DRV=IBM DOS LAN Services
If you are running in 386-enhanced mode, the following section must be
modified:
[386Enh]
NETWORK=VNETBIOS.386,VNETSUP.386,VREDIR.386
In addition to the changes to the SYSTEM.INI file, the following changes should
be made to the WIN.INI file:
[Windows]
Load=wdls
[Network]
Restore=0
The Boot section contains a list of drives and modules that DOS LAN Services
Windows uses each time it starts.
The Boot.Description section contains a list of devices you can change when you
run the INSTALL command.
The 386Enh section contains information specific to running DOS LAN Services
Windows in 386-enhanced mode, including information used for virtual-memory
page swapping.
ΓòÉΓòÉΓòÉ 9.6. Example Configuration Files ΓòÉΓòÉΓòÉ
The following are examples (based on CPU type) of modifications made to
configuration files on IBM workstations enabling DOS LAN Services to be used
under Windows.
These examples assume that you are using the DXMJ0MOD.SYS driver over a
Token-Ring.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: The following examples are Γöé
Γöé for SBCS systems only. The examples apply to specific CPU types used Γöé
Γöé in the U.S. version. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
If you are using Windows as a shared application from a DOS LAN Services
workstation having 1MB or more of memory, do the following:
1. Have the device driver files HIMEM&per.SYS and SMARTDRV&per.EXE on the
requester.
2. Modify the requester CONFIG&per.SYS file to call these device drivers.
ΓòÉΓòÉΓòÉ 9.6.1. CPU 8086/8088 without Expanded Memory ΓòÉΓòÉΓòÉ
In the following example, the 8086/8088 has 640KB of memory. DOS LAN Services
is already installed.
ΓòÉΓòÉΓòÉ 9.6.1.1. AUTOEXEC&per.BAT File ΓòÉΓòÉΓòÉ
The AUTOEXEC&per.BAT file looks like this before you install Windows:
@ECHO OFF
SET COMSPEC=C:\COMMAND&per.COM
VERIFY OFF
PATH=C:\NET;C:\DOS60;C:\;C:\DOSTOOLS
PROMPT $P$G
VER
@ECHO OFF
C:\NET\NET START
After you install Windows, the AUTOEXEC&per.BAT file looks like this:
@ECHO OFF
SET COMSPEC=C:\COMMAND&per.COM
VERIFY OFF
PATH=C:\WINDOWS;C:\NET;C:\DOS60;C:\;C:\ DOSTOOLS;
PROMPT $P$G
VER
@ECHO OFF
C:\NET\NET START
SET TEMP=C:\WINDOWS\TEMP
ΓòÉΓòÉΓòÉ 9.6.1.2. CONFIG&per.SYS File ΓòÉΓòÉΓòÉ
The following CONFIG&per.SYS file does not change after you install Windows:
BUFFERS=20
BREAK=ON
FILES=30
LASTDRIVE=Z
SHELL=C:\COMMAND&per.COM /E:2000 /P
DEVICE=C:\NET\PROTMAN.DOS /I:C:\NET
DEVICE=C:\NET\IBMTOK.DOS
DEVICE=C:\NET\DLSHELP&per.SYS
FCBS=16,8
ΓòÉΓòÉΓòÉ 9.6.2. CPU 8086/8088 with Expanded Memory ΓòÉΓòÉΓòÉ
In the following example, the 8086/8088 has 2MB of expanded memory installed.
DOS LAN Services is already installed.
ΓòÉΓòÉΓòÉ 9.6.2.1. AUTOEXEC&per.BAT File ΓòÉΓòÉΓòÉ
The AUTOEXEC&per.BAT file looks like this before you install Windows:
@ECHO OFF
SET COMSPEC=C:\DOS\COMMAND&per.COM
VERIFY OFF
PATH=C:\NET;C:\DOS;C:\;
APPEND /E
APPEND C:\DOS
PROMPT $P$G
VER
C:\NET\NET START
After you install Windows, the AUTOEXEC&per.BAT file looks like this:
@ECHO OFF
SET COMSPEC=C:\DOS\COMMAND&per.COM
VERIFY OFF
PATH=C:\WINDOWS;C:\NET;C:\DOS;C:\;
APPEND /E
APPEND C:\DOS
PROMPT $P$G
VER
C:\NET\NET START
SET TEMP=C:\WINDOWS\TEMP
ΓòÉΓòÉΓòÉ 9.6.2.2. CONFIG&per.SYS File ΓòÉΓòÉΓòÉ
The CONFIG&per.SYS file looks like this before you install Windows:
BUFFERS=20
BREAK=ON
FILES=30
LASTDRIVE=Z
SHELL=C:\COMMAND&per.COM /E:2000 /P
DEVICE=C:\DOS\ANSI&per.SYS
DEVICE=HIMEM.SYS
DEVICE=C:\DOS\EMM386&per.EXE P255=D000
DEVICE=C:\NET\PROTMAN.DOS /I:\NET
DEVICE=C:\NET\IBMTOK.DOS
DEVICE=C:\NET\DLSHELP.SYS
FCBS=16,8
After you install Windows, the CONFIG&per.SYS file looks like this:
BUFFERS=20
BREAK=ON
FILES=30
LASTDRIVE=Z
SHELL=C:\COMMAND&per.COM /E:2000 /P
DEVICE=HIMEM&per.SYS
DEVICE=C:\DOS\ANSI&per.SYS
DEVICE=C:\NET\PROTMAN.DOS /I:\NET
DEVICE=C:\NET\IBMTOK.DOS
DEVICE=C:\NET\DLSHELP.SYS
FCBS=16,8
ΓòÉΓòÉΓòÉ 9.6.3. CPU 80286 without Expanded Memory ΓòÉΓòÉΓòÉ
In the following example, the 80286 has 640KB of memory. DOS LAN Services is
already installed.
ΓòÉΓòÉΓòÉ 9.6.3.1. AUTOEXEC&per.BAT File ΓòÉΓòÉΓòÉ
The AUTOEXEC&per.BAT file looks like this before you install Windows:
@ECHO OFF
SET COMSPEC=C:\COMMAND&per.COM
VERIFY OFF
PATH=C:\NET;C:\DOS33;C:\;C:\PE2;
PROMPT $P$G
VER
C:\NET\NET START
After you install Windows, the AUTOEXEC&per.BAT file looks like this:
@ECHO OFF
SET COMSPEC=C:\COMMAND&per.COM
VERIFY OFF
PATH=C:\WINDOWS;C:\NET;C:\DOS33;C:\;C:\PE2;
PROMPT $P$G
VER
C:\NET\NET START
SET TEMP=C:\WINDOWS\TEMP
ΓòÉΓòÉΓòÉ 9.6.3.2. CONFIG&per.SYS File ΓòÉΓòÉΓòÉ
The CONFIG&per.SYS file looks like this before you install Windows:
BUFFERS=20
BREAK=ON
FILES=30
LASTDRIVE=Z
SHELL=C:\COMMAND&per.COM /E:2000 /P
DEVICE=C:\NET\PROTMAN.DOS /I:\NET
DEVICE=C:\NET\IBMTOK.DOS
DEVICE=C:\NET\DLSHELP.SYS
FCBS=16,8
After you install Windows, the CONFIG&per.SYS file looks like this:
BUFFERS=20
BREAK=ON
FILES=30
LASTDRIVE=Z
SHELL=C:\COMMAND&per.COM /E:2000 /P
DEVICE=C:\HIMEM&per.SYS
DEVICE=C:\NET\PROTMAN.DOS /I:\NET
DEVICE=C:\NET\IBMTOK.DOS
DEVICE=C:\NET\DLSHELP.SYS
FCBS=16,8
Note:
The extended memory driver (HIMEM&per.SYS) is installed even if no
extended memory is available.
ΓòÉΓòÉΓòÉ 9.6.4. CPU 80286 with Expanded Memory ΓòÉΓòÉΓòÉ
In the following example, the 80286 has 2MB of expanded memory. DOS LAN
Services is already installed.
ΓòÉΓòÉΓòÉ 9.6.4.1. AUTOEXEC&per.BAT File ΓòÉΓòÉΓòÉ
The AUTOEXEC&per.BAT file looks like this before you install Windows:
@ECHO OFF
SET COMSPEC=C:\DOS\COMMAND&per.COM
VERIFY OFF
PATH=C:\NET;C:\DOS;C:\DOSTOOLS;
APPEND C:\DOS
PROMPT $P$G
VER
C:\NET\NET START
After you install Windows, the AUTOEXEC&per.BAT file looks like this:
@ECHO OFF
SET COMSPEC=C:\DOS\COMMAND&per.COM
VERIFY OFF
PATH=C:\WINDOWS;C:\NET;C:\DOS;C:\DOSTOOLS;
APPEND C:\DOS
PROMPT $P$G
VER
C:\NET\NET START
SET TEMP=C:\WINDOWS\TEMP
ΓòÉΓòÉΓòÉ 9.6.4.2. CONFIG&per.SYS File ΓòÉΓòÉΓòÉ
The CONFIG&per.SYS file looks like this before you install Windows:
BREAK=ON
BUFFERS=20
FILES=30
LASTDRIVE=Z
SHELL=C:\COMMAND&per.COM /E:2000 /P
DEVICE=C:\HIMEM.SYS
DEVICE=C:\DOS\EMM386S&per.EXE P255=D400
DEVICE=C:\NET\PROTMAN.DOS /I:\NET
DEVICE=C:\NET\IBMTOK.DOS
DEVICE=C:\NET\DLSHELP.SYS
FCBS=16,8
After you install Windows, the CONFIG&per.SYS file looks like this:
BREAK=ON
BUFFERS=20
FILES=30
LASTDRIVE=Z
SHELL=C:\COMMAND&per.COM /E:2000 /P
DEVICE=C:\HIMEM&per.SYS
DEVICE=C:\NET\PROTMAN.DOS /I:\NET
DEVICE=C:\NET\IBMTOK.DOS
DEVICE=C:\NET\DLSHELP.SYS
FCBS=16,8
ΓòÉΓòÉΓòÉ 9.6.5. CPU 80386 or 80486 (1.5MB Extended Memory) ΓòÉΓòÉΓòÉ
In the following example, the 80386 or 80486 has 1&per.5MB of extended memory.
DOS LAN Services is already installed.
ΓòÉΓòÉΓòÉ 9.6.5.1. AUTOEXEC&per.BAT File ΓòÉΓòÉΓòÉ
The AUTOEXEC&per.BAT file looks like this before you install Windows:
@ECHO ON
PATH=C:\NET;C:\DOS33;C:\DOSTOOLS;
APPEND=C:\DOSTOOLS;C:\DOS33
PROMPT $P$G
CLS
:EXIT
C:\NET\NET START
After you install Windows, the AUTOEXEC&per.BAT file looks like this:
@ECHO ON
PATH=C:\WINDOWS;C:\NET;C:\DOS33;C:\DOSTOOLS;
APPEND=C:\DOSTOOLS;C:\DOS33
PROMPT $P$G
CLS
:EXIT
C:\NET\NET START
SET TEMP=C:\WINDOWS\TEMP
ΓòÉΓòÉΓòÉ 9.6.5.2. CONFIG&per.SYS File ΓòÉΓòÉΓòÉ
The CONFIG&per.SYS file looks like this before you install Windows:
DEVICE=C:\NET\PROTMAN.DOS /I:\NET
DEVICE=C:\NET\IBMTOK.DOS
DEVICE=C:\NET\DLSHELP.SYS
SHELL=C:\COMMAND&per.COM /E:2000 /P
LASTDRIVE=Z
FILES=30
BUFFERS=20
FCBS=16,8
After you install Windows, the CONFIG&per.SYS file looks like this:
DEVICE=C:\HIMEM&per.SYS
DEVICE=C:\NET\PROTMAN.DOS /I:\NET
DEVICE=C:\NET\IBMTOK.DOS
DEVICE=C:\NET\DLSHELP.SYS
SHELL=C:\COMMAND&per.COM /E:2000 /P
LASTDRIVE=Z
FILES=30
BUFFERS=20
FCBS=16,8
ΓòÉΓòÉΓòÉ 9.6.6. CPU 80386 or 80486 (3MB Extended Memory) ΓòÉΓòÉΓòÉ
In the following example, the 80386 or 80486 has 3MB of extended memory.
ΓòÉΓòÉΓòÉ 9.6.6.1. AUTOEXEC&per.BAT File ΓòÉΓòÉΓòÉ
The AUTOEXEC&per.BAT file looks like this before you install DOS LAN Services
and Windows:
@ECHO OFF
SET COMSPEC=C:\COMMAND&per.COM
PATH=C:\DOS40X;C:\;C:\DOSTOOLS;
APPEND C:\DOSTOOLS
PROMPT $P$G
After you install DOS LAN Services and Windows, the AUTOEXEC&per.BAT file looks
like this:
@ECHO OFF
SET COMSPEC=C:\COMMAND.COM
PATH=C:\NET;C:\WINDOWS;C:\DOS40X;C:\;C:\DOSTOOLS;
APPEND C:\DOSTOOLS
PROMPT $P$G
SET TEMP=C:\WINDOWS\TEMP
C:\NET\NET START
ΓòÉΓòÉΓòÉ 9.6.6.2. CONFIG&per.SYS File ΓòÉΓòÉΓòÉ
The CONFIG&per.SYS file looks like this before you install DOS LAN Services and
Windows:
BREAK=ON
BUFFERS=30
FILES=30
SHELL=C:\COMMAND&per.COM /E:2000 /P
DEVICE=C:\NET\PROTMAN.DOS /I:\NET
DEVICE=C:\NET\IBMTOK.DOS
DEVICE=C:\NET\DLSHELP.SYS
FCBS=16,8
After you install DOS LAN Services and Windows, the CONFIG&per.SYS file looks
like this:
BREAK=ON
BUFFERS=30
FILES=30
LASTDRIVE=Z
SHELL=C:\COMMAND&per.COM /E:2000 /P
DEVICE=C:\HIMEM&per.SYS
DEVICE=C:\NET\PROTMAN.DOS /I:\NET
DEVICE=C:\NET\IBMTOK.DOS
DEVICE=C:\NET\DLSHELP.SYS
FCBS=16,8
ΓòÉΓòÉΓòÉ 9.7. DOS LAN Services Memory Management ΓòÉΓòÉΓòÉ
You can use DOS memory managers, such as HIMEM and EMM386, to enable DOS LAN
Services to use memory more efficiently. If your workstation is configured
with expanded or extended memory above 1MB, parts of the DOS LAN Services code
can be loaded into that memory. This procedure reduces the amount of low memory
required for DOS LAN Services while more memory becomes available to run DOS
applications. The use of high memory also allows the workstation to run
applications that require extended or expanded memory.
Refer to your DOS documentation for more information about DOS memory
management. This section briefly describes the use of the HIMEM and EMM386
device drivers.
ΓòÉΓòÉΓòÉ 9.7.1. Using the HIMEM Utility ΓòÉΓòÉΓòÉ
HIMEM is a utility that manages the use of workstation extended memory. It
manages up to 64KB for the high memory area (HMA). HIMEM prevents two
applications from using the same memory at the same time. Installing HIMEM is
a prerequisite for installing EMM386. Refer to the DOS documentation for
installation and usage information.
ΓòÉΓòÉΓòÉ 9.7.2. Using the EMM386 Emulator ΓòÉΓòÉΓòÉ
EMM386 is an expanded memory emulator that uses extended memory to simulate
expanded memory in a DOS LAN Services workstation. When installing EMM386,
specify the noems option unless other applications running on the requester use
EMS. Installing HIMEM is a prerequisite for installing EMM386. Refer to the
DOS documentation for installation and usage information.
ΓòÉΓòÉΓòÉ 9.7.3. Maximizing Memory Utilization with DOS 5.0 or Later ΓòÉΓòÉΓòÉ
If you run DOS LAN Services with DOS 5.0 or later, you can further maximize
memory utilization on the workstation. DOS 5.0 or later can make more memory
available to applications than earlier DOS versions. For example, DOS 5.0 or
later can be loaded into the first 64KB of extended memory, called the high
memory area (HMA).
The HMA is available on workstations with a 286 (or greater) processor with at
least 1MB of memory. Most systems also have 384KB of space called the upper
memory area. DOS 5.0 or later can store information in this upper memory area
on workstations with 386 (or greater) processors and extended memory. DOS 5.0
or later can take advantage of available memory by installing various memory
managers, such as HIMEM and EMM386. Refer to your DOS documentation for more
information about memory and memory managers.
ΓòÉΓòÉΓòÉ 10. Installing and Running DOS LAN Services on OS/2 ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: This chapter is for Single- Γöé
Γöé Byte Character Set (SBCS) users only. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
OS/2 provides the ability to start a DOS session with a specific version of DOS
(for example, DOS 5.0). A specific DOS session enables you to keep your
existing DOS environment (if migrating) and to run DOS LAN Services (DLS) or PC
LAN Program at your OS/2 workstation. Neither DOS LAN Services nor PC LAN
Program is supported in an emulated version of DOS under the OS/2 program. For
information about specific and emulated DOS sessions, refer to the OS/2
documentation.
Notes:
1. PC LAN Program 1.34 (or later) requesters (Base Services and
Communications Manager/2 or DATABASE 2 OS/2) are supported in OS/2
specific DOS sessions. PC LAN Program servers are not supported on OS/2.
2. Do not start DOS LAN Services from a specific DOS session on which the
VNETAPI.SYS device driver has been installed. If you do, the NET START
command generates the following error message:
Incorrect NETWORK version
Using DOS LAN Services on OS/2 involves using both the DOS functions of the
base operating system and the LAN Server product.
When you run OS/2 LAN Requester on an OS/2 workstation, all network assignments
(redirected drives or ports), are available in each OS/2 session and (except
for serial device assignments) each emulated DOS session and any specific DOS
session. Network API access, from the DOS machine, to support LAN-aware DOS
applications is also available using the DOS LAN Requester virtual device
drivers. However, you can override redirected devices by using DOS LAN Services
or PC LAN Program in the specific DOS session. Network assignments made in a
specific DOS session with DOS LAN Services or PC LAN Program are not available
in any other OS/2 or DOS session on the workstation.
This chapter describes the following two methods of installing DOS LAN Services
in a specific DOS session:
o Using DOS LAN Services installed in a partition
o Using DOS LAN Services installed in an image file
To start a specific DOS session from a primary partition, DOS must be installed
in a primary partition on drive C, and OS/2 must be installed on drive D (or
higher). If OS/2 is already installed on drive C or there is no drive D or
higher, you can install DOS LAN Services in a specific DOS session started from
an image file. This method is not as straightforward as starting the session
from a primary partition.
When running DOS LAN Services or PC LAN Program in a specific DOS session, you
do not need to install LAN Support Program. LAN Adapter and Protocol Support
(LAPS) provides the OS/2 virtual device drivers (normally provided by LAN
Support Program) needed for communication with NetBIOS or 802.2.
This support for programs also allows you to have multiple DLS sessions on a
workstation. Each specific DOS session can support one DLS session. You can
have a maximum of four DLS sessions on one OS/2 workstation. For information
about setting up multiple DOS LAN Services on one OS/2 workstation, refer to
Tips for Setting Up Multiple DOS LAN Services. No other NetBIOS application
from another DOS or OS/2 session is able to run on adapter 0 at the same time.
ΓòÉΓòÉΓòÉ 10.1. Installing DOS LAN Services (DLS) in a Specific DOS Session Started from a Primary Partition ΓòÉΓòÉΓòÉ
To start a specific DOS session from a primary partition, DOS must be installed
in a primary partition on drive C, and OS/2 must be installed on drive D (or
higher).
To Install DLS on a Specific DOS Session Started from a Primary
Partition:
1. Install DOS and OS/2 if you have not already done so. For an initial
installation, use the OS/2 Boot Manager feature to install DOS in a
primary partition on drive C. OS/2 must be installed in an extended
partition on a logical drive (D or higher). Then the DOS primary
partition can be started as a specific DOS session running under OS/2.
For more information about installing OS/2 and DOS, refer to the chapter
on installing multiple operating systems in the OS/2 documentation.
Notes:
a. Make the size of your DOS partition at least 8MB before you
install DOS LAN Services.
b. If you have both DOS and OS/2 on your Boot Manager menu, whenever
your system starts up (for example, after a restart), ensure that
you always select the OS/2 session to run DOS LAN Services in a
specific DOS session after you have completed the following
procedure.
2. Install and configure LAPS. LAPS installs the OS/2 virtual device
drivers needed to run DOS LAN Services or PC LAN Program on an OS/2
workstation and provides the NetBIOS resources to run all your OS/2,
DOS, and OEM applications. Use NetBIOS Resources Required for an OS/2
Workstation to calculate how many NetBIOS resources (sessions, commands,
and names) to configure for adapter 0.
Calculate the totals for sessions, commands, and names required by all
your applications, and use these totals when configuring the NetBIOS
protocol with LAPS. If you have multiple occurrences of a certain
application, you must add resources for each occurrence. For example,
if you have two DOS LAN Services sessions on your workstation, you must
double the sessions, commands, and names values. Remember that you must
also add any OEM requirements to your totals.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 6. NetBIOS Resources Required for an OS/2 Workstation Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé APPLICATION Γöé SESSIONS Γöé COMMANDS Γöé NAMES Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS LAN Services Γöé 20 Γöé 20 Γöé 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PC LAN Program(1,2) Γöé 6 Γöé 8 Γöé 1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OS/2 LAN Requester Γöé 40 Γöé 85 Γöé 21 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Other applications Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TOTAL NETBIOS RESOURCES Γöé Γöé Γöé Γöé
Γöé REQUIRED Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTES: Γöé
Γöé Γöé
Γöé 1. Values for PC LAN Program vary for workstations defined as receivers or Γöé
Γöé redirectors. For information about how to determine the values needed Γöé
Γöé for sessions, commands, and names, refer to the PC LAN Program documen- Γöé
Γöé tation. Γöé
Γöé Γöé
Γöé 2. PC LAN Program is available on SBCS systems only. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Using an ASCII editor, verify that the following two statements are in
your OS/2 CONFIG.SYS file:
DEVICE=D:\IBMCOM\PROTOCOL\LANVDD.0S2
DEVICE=D:\IBMCOM\PROTOCOL\LANPDD.OS2
If these statements are present, continue with step 3. If these
statements are not in the OS/2 CONFIG.SYS file, use an ASCII editor to
insert them, and then shut down and restart your system. Note that D:
may not be the proper drive if OS/2 is installed on the C drive; adjust
these two lines to point to the correct drive.
For instructions on configuring LAPS, see the MPTS - AnyNet for OS/2:
Configuration Guide.
3. Configure NetBIOS resources (sessions, commands, and names) for the
specific DOS session that is running PC LAN Program or DOS LAN Services.
This configuration is different from the LAPS configuration performed in
step 2. At this point, you are configuring only the NetBIOS sessions,
names, and commands for the specific DOS session. LAPS, on the other
hand, configures NetBIOS sessions, names, and commands for all OS/2 and
DOS applications running on the OS/2 workstation.
The LTSVCFG utility called by the AUTOEXEC.BAT file is used to specify
the NetBIOS resources required for the specific DOS session. In most
cases, the default NetBIOS resources used in the following step support
DOS LAN Services. Refer to your PC LAN Program documentation for
information about determining the correct values for a redirector or
receiver workstation. To specify NetBIOS resources for a specific DOS
session for DOS LAN Services:
a. Go to a DOS command prompt and use an ASCII text editor to edit the
AUTOEXEC.BAT file on drive C.
b. Add the following line to the AUTOEXEC.BAT file:
d:\IBMCOM\LTSVCFG S=20 C=20 N=8
where d is the OS/2 startup drive, S is the number of sessions, C is
the number of commands, and N is the number of names.
Note:
If you have a DOS application that requires more NetBIOS
resources than the specified defaults, you receive an error
from the DOS application. If you receive an error, increase
the values in the AUTOEXEC.BAT file and close the specific DOS
session. Use LAPS to increase the sessions, commands, and
names values by the same amounts for the NetBIOS protocol.
Shut down your workstation from the OS/2 desktop, and then
restart it to activate the LAPS changes you made. Restart the
specific DOS session and start the DOS application again.
4. Modify the files on the DOS partition to be able to run a specific DOS
session. For the procedure to start a DOS session from a partition,
refer to the DOS information in the online Master Help Index. Look for
the information on modifying the AUTOEXEC.BAT and CONFIG.SYS files.
Note:
While editing the CONFIG.SYS file on the DOS partition, ensure
that the value of the files parameter is set to a minimum of 20.
In addition, if you will be running PCLP in the specific DOS session,
add the following line to the CONFIG.SYS file for the specific DOS
session:
DEVICE=d:\IBMCOM\PROTOCOL\LANVMEM.SYS
where d is the startup drive.
5. Create a DOS session object (icon) for the specific version of DOS in
which you want to install DOS LAN Services:
a. On the OS/2 desktop, display the folders for the OS/2 System object.
b. Open the Command Prompts folder and place your cursor on either the
full-screen or windowed DOS session object.
c. Hold down the Ctrl key while using the right mouse button to drag the
object to a part of the desktop not occupied by another object. When
ready, release the Ctrl key and the right mouse button to place the
new DOS session object on the desktop.
d. If you already have another DOS session object on the desktop with
the same name, you are prompted to rename the new object at this
time. Rename the DOS session object as instructed.
e. Select OK to create the new DOS session object.
6. To set the startup drive for the specific DOS session:
a. Click the right mouse button with the cursor on the DOS session
object.
b. Select the arrow next to Open on the pop-up menu, and then select
Settings.
c. In the Settings window, select the Session tab on the right, and then
select DOS Settings.
d. Select DOS_STARTUP_DRIVE from the list of settings, and then type C:
in the Value field. Be sure to include the colon (:).
e. Select Save, and then close the DOS Settings window.
7. Install DOS LAN Services or PC LAN Program. The following steps are for
installing DOS LAN Services. Refer to your PC LAN Program documentation
for information about installing PC LAN Program.
a. Start the specific DOS session on the workstation.
You cannot start DOS LAN Services while the DOS shell is running.
For this reason, consider (1) moving the DOSSHELL statement after the
DOS LAN Services information in your AUTOEXEC.BAT file, or (2)
commenting out the DOSSHELL statement in the AUTOEXEC.BAT file after
installing the DOS program.
You may also want to back up your AUTOEXEC.BAT and CONFIG.SYS files.
b. If the DOS shell is running, press F3 to exit from the DOS shell.
c. If you are installing from a CD-ROM, start the DOS LAN Services
installation program by typing:
d:\DLS\INSTALL
where d represents the drive letter for the CD-ROM. Press Enter.
d. If you are installing from diskettes, insert DOS LAN Services - Disk
1 into diskette drive A or B and start the installation program by
typing:
d:INSTALL
where d represents the drive in which you placed the DOS LAN Services
- Disk 1. Press Enter.
e. Follow the instructions displayed on the screen until the
installation window shown in the figure titled DOS LAN Services
Installation Options Window 1 is displayed.
Note:
If you need more information about any of the installation
windows, press F1 for help.
DOS LAN Services Installation Options Window 1
f. The Installation Options Window 1 lists DOS LAN Services
configuration information for the workstation. Ensure that each
option is set correctly. To change an option, follow the
instructions in the window.
The fields in the Installation Options Window 1 are defined as
follows:
Graphical User Interface Specifies whether the graphical user
interface is installed with DOS LAN Services.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: Asian versions of DOS 5.0 Γöé
Γöé do not support the DOS LAN Services graphical user interface. DOS Γöé
Γöé 5.0/V does support the graphical user interface. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Peer Services Specifies whether Peer Services is installed with DOS
LAN Services. Peer Services allows you to share disks and
printers with other network stations.
Windows Support Specifies whether Windows support is installed with
DOS LAN Services. You need to install Windows support if
you will use DOS LAN Services in Windows.
Protocol Driver Specifies the protocol driver for the network adapter
card installed in your workstation.
After you have verified your selections, select The listed options
are correct and press Enter. The installation window depicted by the
figure titled DOS LAN Services Installation Options Window 2 is
displayed.
DOS LAN Services Installation Options Window 2
g. The Installation Options Window 2 also lists DOS LAN Services
configuration information for the workstation. Ensure that each
option is set correctly. To change an option, follow the
instructions in the window.
The fields in the Installation Options Window 2 are defined as
follows:
Machine ID Specifies the machine ID for the DOS workstation. DOS LAN
Services automatically gives your computer the same name as
your user name, but you can select a different name. If you
select a machine ID that is different from your user name,
the machine ID should not match any user ID or computername
on the network.
User name Identifies you as a member of the network. Select a name
that no one else in the network is using. For example, you
could combine your first and last names, such as NANCYC or
JAMESP.
Domain name Specifies the default domain name for your DOS workstation
to access. DOS LAN Services allows you to log on to domains
other than your default domain. If you are not logged on to
a specific domain, the resources in that domain do not
appear when you browse for resources; however, you can
connect to resources in other domains if you know the names
of those resources.
Redirector Specifies the type of redirector that DOS LAN Services
uses. The redirector transfers requests from the DOS
requester to a server on the network. DOS LAN Services has
three redirectors:
basic redirector The basic redirector helps conserve workstation
memory. Use the basic redirector if you:
o Do not have much memory on your workstation
o Do not want to use aliases (nicknames assigned by an
administrator) to identify resources
o Do not plan to use Windows
o Are using a workstation with an 8086 processor
When using the basic redirector, the logon processing is
performed locally (on your workstation) without password
validation at a remote server. You cannot use the basic
redirector if you are using DOS LAN Services with the
Windows interface.
full redirector The full redirector provides support for using
aliases to identify resources and support for using
Windows. The full redirector also provides support for
server validation of the user name and password at logon.
Although the full redirector uses more memory than the
basic redirector, it also provides greater function,
improved performance, and full API support. The full
redirector is the default redirector when not installing
Windows support.
virtual redirector The virtual redirector optimizes memory usage in
the Windows interface. The virtual redirector frees low
memory to be used by other Windows applications. This is
the default redirector when you are running DOS LAN
Services in the Windows interface.
Startup option Specifies the options to run at startup. Select one of
the following:
Do not run DOS LAN Services Specifies not to start DOS LAN Services
at system startup. As a result, you will have to run the
NET LOGON command at the DOS command prompt to start DOS
LAN Services, after which you will be prompted to log on.
Run DOS LAN Services only Starts DOS LAN Services with each system
startup. You must run the NET LOGON command at the DOS
command prompt to gain access to shared resources.
Run DOS LAN Services and log on (default) Starts DOS LAN Services
and prompts you to log on to your requester with each
system startup.
Path Specifies the path to the subdirectory in which to install
DOS LAN Services. The path must specify drive C, D, E, or
F. The following characters for the directory name are
valid:
a through z
A through Z
0 through 9
! @ # $ ┬░ - _ & () {} ^ ~
Network card Specifies the type of network adapter card installed in
your workstation.
After you have verified your selections, select The listed options
are correct and press Enter.
h. The next window displays the settings for the network card. If the
OS/2 virtual device drivers (LANVDD.OS2 and LANPDD.OS2) are not
installed, the DOS LAN Services installation program automatically
detects the network card you are using and configures DOS LAN
Services for that adapter card. If the virtual device drivers are
installed, DOS LAN Services installation program inserts device
driver statements in the CONFIG.SYS file that you must remove. Step
8e explains which statements to remove from the CONFIG.SYS file.
Press Enter to accept the settings.
i. When instructed, press F3 to complete and exit the installation
program.
j. Run the following command:
COPY C:\CONFIG.XXX CONFIG.SYS
where XXX is a number from 000 to 999. Copy the highest number.
k. Edit the newly copied C:\CONFIG.SYS file and add the following line:
DEVICE=C:\NET\DLSHELP.SYS
where NET is the subdirectory into which DOS LAN Services was
installed.
l. Edit the C:\NET\NETWORK.INI file and add the following line at the
bottom:
LANAS=0
Note:
If you are running on an Ethernet adapter and using the
DXME0MOD.SYS and DXMT0MOD.SYS device drivers for IEEE 802.2
support, you must add CF=Y to the DXMT0MOD.SYS line in your
CONFIG.SYS file. For more information about the CF parameter,
refer to Summary of the Keyword Values for the NetBIOS New
Parameters. Restart your DOS workstation to make the
CONFIG.SYS change active.
If you have any problems setting up DOS LAN Services, see the
CONNECT.TXT file, which is in the directory that contains the DOS LAN
Services files. This ASCII file contains problem determination
information for DOS LAN Services installation. You can view CONNECT.TXT
by using any ASCII text editor.
For the steps to change your configuration, refer to Changing the DOS
LAN Services Configuration.
8. Exit the DOS session as follows:
a. Press Ctrl+Esc to go to the Window List.
b. With the cursor on the DOS entry, click the right mouse button once.
c. Select Close.
d. Select Yes to confirm.
e. Edit your CONFIG.SYS file and remove all DOS LAN Services device
driver statements except for the following:
DEVICE=C:\NET\DLSHELP.SYS
Note:
The Path field (see the figure titled DOS LAN Services
Installation Options Window 2) specifies C:\NET as the default
installation directory. If you accept the default directory,
the only DOS LAN Services device driver in the C:\NET
subdirectory that you should not delete is DLSHELP.SYS.
9. Shut down the workstation from the OS/2 desktop, and then restart it by
pressing Ctrl+Alt+Delete. The restart initializes the OS/2 transport
with the new values in the PROTOCOL.INI file.
10. Start DOS LAN Services in the specific DOS session.
11. Modify the AUTOEXEC.BAT file on the C drive to include the following
statements:
PATH=C:\DOSXX;
SET COMSPEC=C:\DOSXX\COMMAND.COM
PROMPT $P$G
C:\IBMCOM\LTSVCFG S=20 C=20 N=8
C:
REM DOSXX.BAT should always be the last line in the file.
DOSXX.BAT
The S, C, and N parameters in C:\IBMCOM\LTSVCFG S=20 C=20 N=8 set the
values for the number of NetBIOS sessions, commands, and names,
respectively.
Note:
Refer to step 3 for detailed information about configuring these
NetBIOS resources for the specific DOS session.
12. Create the C:\DOSXX: directory by running the following command:
MD DOSXX
where XX corresponds to the workstation's DOS version. Press Enter.
13. In the newly created directory, create a DOSXX.BAT file, where XX
corresponds to the workstation's DOS version. Edit the file and add the
following statement:
C:\OS2\MDOS\FSACCESS A:
Note:
The DOSXX directory must be created prior to running the VMDISK
command. You can also add lines to this batch file to further
tailor it; for example,
DOSKEY.COM
C: CD \DIR1\DIR2
14. With the startup diskette in drive A, create a DOS image file by typing
the following at an OS/2 prompt:
VMDISK A: C:\DOSXX\DOSXX.IMG
where XX corresponds to the workstation's DOS version. Press Enter.
Note:
The DOSXX.IMG file must have the IMG extension and must reside on
the C drive.
ΓòÉΓòÉΓòÉ 10.2. Installing DOS LAN Services (DLS) in a Specific DOS Session Started from an Image File ΓòÉΓòÉΓòÉ
Use the following procedure if you are not able to install a specific DOS
session from a primary partition on drive C, because you have already installed
OS/2 on drive C or you have no drive D or higher available.
Note:
For more information about starting a specific version of DOS from an
image file, refer to the online Master Help Index for OS/2.
To Install DLS on a Specific DOS Session Started from an Image
File:
1. Install and configure LAPS.
2. Install a specific DOS version from an image file as follows:
Note:
If you start a specific DOS version from an image file, only
certain components of DOS, such as COMMAND.COM, are available to
the DOS session after starting. DOS LAN Services and PC LAN
Program require the availability of more DOS components than
COMMAND.COM; therefore, you must load the specific version of DOS
on the hard disk.
a. Install DOS to diskette. This step also provides a DOS startup
(boot) diskette. Follow the instructions provided in the DOS
documentation.
b. On the OS/2 workstation, use the MD command to create the C:\DOSXX
directory, where XX represents DOS version 5.0 or later. Copy the
contents of the newly installed DOS diskettes into the newly created
C:\DOSXX directory.
c. Copy C:\OS2\MDOS\FSFILTER.SYS to the DOS startup diskette.
d. Modify the CONFIG.SYS file on the DOS startup diskette to include the
following statements:
BREAK=ON
BUFFERS=20
FILES=30
DEVICE=A:\FSFILTER.SYS
DEVICE=C:\OS2\MDOS\HIMEM.SYS
SHELL=C:\DOSXX\COMMAND.COM /E:2000 /P
STACKS=0,0
FCBS=16,8
Note:
If you need to use the expanded memory simulator (EMS), you can
also include the line:
DEVICE=C:\OS2\MDOS\EMM386.SYS
If you plan to install PC LAN Program, make sure to add the following
line to the CONFIG.SYS file for the specific DOS session:
DEVICE=d:\IBMCOM\PROTOCOL\LANVMEM.SYS
where d is the startup drive. Note that this line is not needed for
DOS LAN Services.
e. Modify the AUTOEXEC.BAT file on the DOS startup diskette to include
the following statements:
PATH=C:\DOSXX;C:\OS2\MDOS;C:\IBMCOM
SET COMSPEC=C:\DOSXX\COMMAND.COM
PROMPT $P$G
C:\IBMCOM\LTSVCFG S=20 C=20 N=8
C:
C:\OS2\MDOS\MOUSE
REM DOSXX.BAT should always be the last line in the file.
DOSXX.BAT
The S, C, and N parameters in C:\IBMCOM\LTSVCFG S=20 C=20 N=8 set the
values for the number of NetBIOS sessions, commands, and names,
respectively.
Note:
Refer to step 3 in Installing DOS LAN Services (DLS) in a
Specific DOS Session Started from a Primary Partition for
detailed information about configuring these NetBIOS resources
for the specific DOS session.
f. Create a DOSXX.BAT file in the C:\DOSXX: directory containing the
following statement
C:\OS2\MDOS\FSACCESS A:
You can also add lines to this batch file to further tailor it, for
example,
DOSKEY.COM
C: CD \DIR1\DIR2
g. With the startup diskette in drive A, create a DOS image file by
typing the following at an OS/2 prompt:
VMDISK A: C:\DOSXX\DOSXX.IMG
Note:
The DOSXX.IMG file must have the IMG extension and must reside
on the C drive.
3. To create a DOS session object for the specific version of DOS on which
you want to install DOS LAN Services, refer to steps 5 and 6 in
Installing DOS LAN Services (DLS) in a Specific DOS Session Started from
a Primary Partition. Note that in step 6d of that same procedure, you
must type C:\DOSXX\DOSXX.IMG in the Value field (rather than just C:).
4. Install DOS LAN Services in the specific DOS session:
a. Start the DOS session.
b. Copy C:\AUTOEXEC.BAT to C:\*.OS2.
c. Copy C:\CONFIG.SYS to C:\*.OS2.
Note:
Steps 4b and 4c save the OS/2 CONFIG.SYS and AUTOEXEC.BAT files
with an "OS/2" extension.
d. Copy the CONFIG.SYS and AUTOEXEC.BAT files from the DOS startup
diskette to drive C.
e. Insert the DOS LAN Services - Disk 1 into drive A or B and start the
installation program by typing:
d:INSTALL
where d represents the drive into which you placed the DOS LAN
Services - Disk 1. Press Enter.
f. Follow the instructions displayed on the screen until you see the
installation window shown in the figure titled DOS LAN Services
Installation Options Window 1.
Notes:
1. When prompted to insert the Boot Diskette into drive X, insert
the DOS Startup diskette.
2. If you need more information about any of the installation
windows, press F1 for help.
DOS LAN Services Installation Options Window 1
g. The Installation Options Window 1 lists DOS LAN Services
configuration information for the workstation. Ensure that each
option is set correctly. To change an option, follow the
instructions in the window.
The fields in the Installation Options Window 1 are defined as
follows:
Graphical User Interface Specifies whether the graphical user
interface is installed with DOS LAN Services.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: Asian versions of DOS 5.0 Γöé
Γöé do not support the DOS LAN Services graphical user interface. DOS Γöé
Γöé 5.0/V does support the graphical user interface. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Peer Services Specifies whether Peer Services is installed with DOS
LAN Services. Peer Services allows you to share disks and
printers with other network stations.
Windows Support Specifies whether Windows support is installed with
DOS LAN Services. You need to install Windows support if
you will use DOS LAN Services in Windows.
Protocol Driver Specifies the protocol driver for the network adapter
card installed in your workstation.
After you have verified your selections, select The listed options
are correct and press Enter. The installation window depicted in the
figure DOS LAN Services Installation Options Window 2 is displayed.
DOS LAN Services Installation Options Window 2
h. The Installation Options Window 2 also lists DOS LAN Services
configuration information for the workstation. Ensure that each
option is set correctly. To change an option, follow the
instructions in the window.
The fields in the Installation Options Window 2 are defined as
follows:
Machine ID Specifies the machine ID for the DOS workstation. DOS LAN
Services automatically gives your computer the same name as
your user name, but you can select a different name. If you
select a machine ID that is different from your user name,
the machine ID should not match any user ID or computername
on the network.
User name Identifies you as a member of the network. Select a name
that no one else in the network is using. For example, you
could combine your first and last names, such as NANCYC or
JAMESP.
Domain name Specifies the default domain name for your DOS workstation
to access. DOS LAN Services allows you to log on to domains
other than your default domain. If you are not logged on to
a specific domain, the resources in that domain do not
appear when you browse for resources; however, you can
connect to resources in other domains if you know the names
of those resources.
Redirector Specifies the type of redirector that DOS LAN Services
uses. The redirector transfers requests from the DOS
requester to a server on the network. DOS LAN Services has
three redirectors:
basic redirector The basic redirector helps conserve workstation
memory. Use the basic redirector if you:
o Do not have much memory on your workstation
o Do not want to use aliases (nicknames assigned by an
administrator) to identify resources
o Do not plan to use Windows
o Are using a workstation with an 8086 processor
When using the basic redirector, the logon processing is
performed locally (on your workstation) without password
validation at a remote server. You cannot use the basic
redirector if you are using DOS LAN Services with the
Windows interface.
full redirector The full redirector provides support for using
aliases to identify resources and support for using
Windows. The full redirector also provides support for
server validation of the user name and password at logon.
Although the full redirector uses more memory than the
basic redirector, it also provides greater function,
improved performance, and full API support. The full
redirector is the default redirector when not installing
Windows support.
virtual redirector The virtual redirector optimizes memory usage in
the Windows interface. The virtual redirector frees low
memory to be used by other Windows applications. This is
the default redirector when you are running DOS LAN
Services in the Windows interface.
Startup option Specifies the options to run at startup. Select one of
the following:
Do not run DOS LAN Services Specifies not to start DOS LAN Services
at system startup. As a result, you will have to run the
NET LOGON command at the DOS command prompt to start DOS
LAN Services, after which you will be prompted to log on.
Run DOS LAN Services only Starts DOS LAN Services with each system
startup. You must run the NET LOGON command at the DOS
command prompt to gain access to shared resources.
Run DOS LAN Services and log on (default) Starts DOS LAN Services
and prompts you to log on to your requester with each
system startup.
Path Specifies the path to the subdirectory in which to install
DOS LAN Services. The path must specify drive C, D, E, or
F. The following characters for the directory name are
valid:
a through z
A through Z
0 through 9
! @ # $ ┬░ - _ & () {} ^ ~
Network card Specifies the type network adapter card installed in your
workstation.
After you have verified your selections, select The listed options
are correct and press Enter.
i. The next window displays the settings for the network card. If the
OS/2 virtual device drivers (LANVDD.OS2 and LANPDD.OS2) are not
installed, the DOS LAN Services installation program automatically
detects the network card you are using and configures DOS LAN
Services for that adapter card. If the virtual device drivers are
installed, DOS LAN Services installation program inserts device
driver statements in the CONFIG.SYS file that you must remove. Step 8
explains which statements to remove from the CONFIG.SYS file.
j. When instructed, press F3 to complete and exit the installation
program.
Note:
If you are running on an Ethernet adapter and using the
DXME0MOD.SYS and DXMT0MOD.SYS device drivers for IEEE 802.2
support, you must add CF=Y to the DXMT0MOD.SYS line in your
CONFIG.SYS file. For more information about the CF parameter,
refer to Summary of the Keyword Values for the NetBIOS New
Parameters. Restart your DOS workstation to make the
CONFIG.SYS change active.
If you have any problems setting up DOS LAN Services, see the
CONNECT.TXT file, which is in the directory that contains your DOS LAN
Services files. This ASCII file contains problem determination
information for DOS LAN Services installation. You can view CONNECT.TXT
by using any ASCII text editor.
For the steps to change your configuration, refer to Changing the DOS
LAN Services Configuration.
5. Copy C:\AUTOEXEC.OS2 to C:\*.BAT.
6. Copy C:\CONFIG.OS2 to C:\*.SYS.
Note:
Steps 5 and 6 "restore" the OS/2 CONFIG.SYS and AUTOEXEC.BAT
files.
7. Edit the AUTOEXEC.BAT file on the DOS startup diskette and ensure that
the call to DOSXX.BAT is the last line in the file.
8. Edit the CONFIG.SYS file on the DOS startup disk and remove all DOS LAN
Services device driver statements except for the following:
DEVICE=C:\NET\DLSHELP.SYS
Note:
The Path field (see the figure titled DOS LAN Services
Installation Options Window 2) specifies C:\NET as the default
installation directory. If you accept the default directory, the
only DOS LAN Services device driver in the C:\NET subdirectory
that you should not delete is DLSHELP.SYS.
9. Close the specific DOS session. You now need to either remake the DOS
image file or or perform steps 9a through 9e. To remake the DOS image
file, open an OS/2 full screen or window and re-create the DOS image.
The image must be re-created because DOS LAN Services installation made
updates to the CONFIG.SYS and AUTOEXEC.BAT files. With the DOS startup
diskette in drive A, re-create the DOS image file by typing:
VMDISK A: C:\DOSXX\DOSXX.IMG
Press Enter. Then proceed to step 10.
a. Edit the following line in the DOSXX.BAT file:
REM C:\OS2\MDOS\FSACCESS A:
b. Restart the specific DOS session and change to the A drive. (The A
drive is not really a drive, but is the image of a DOS startable
drive. Commenting out the line in the DOSXX.BAT file prevents you
from seeing your A drive, but allows you to see the image file that
was previously created from your DOS startup diskette.)
c. Add the following line to the CONFIG.SYS file that is in the image
file:
DEVICE=C:\NET\DLSHELP.SYS
d. Again, close the specific DOS session, and remove the REM from the
DOSXX.BAT file. Now when you restart your specific DOS session, you
will be able to run DOS LAN Services and also see your A drive.
e. Exit the DOS session as follows:
1. Press Ctrl+Esc to go to the Window List.
2. With the cursor on the DOS entry, click the right mouse button
once.
3. Select Close.
4. Select Yes to confirm.
10. Edit the C:\NET\NETWORK.INI file and add the following line at the
bottom:
LANAS=0
11. To start DOS LAN Services, restart the DOS session.
ΓòÉΓòÉΓòÉ 10.3. Tips for Setting Up Multiple DOS LAN Services ΓòÉΓòÉΓòÉ
You can set up multiple DOS LAN Services on OS/2 in many ways. The following
are helpful tips:
o If you plan to run multiple PC LAN Program requesters from one workstation,
you must specify a different machine ID for each DOS session.
o If you plan to start a specific version of DOS from an image file, you must
create a separate image for each DOS session. For information about creating
image files, see the online Master Help Index for OS/2.
o If you plan to start a specific version of DOS from an image, you should
release drive A after starting each DOS session. See the online Master Help
Index for OS/2 for information about releasing drive A by using the FSACCESS
command.
o The LANVMEM.SYS DOS device driver allocates memory while starting a specific
DOS session. The DOS memory allocated by the LANVMEM.SYS device driver is
NetBIOS extended status information. The LANVMEM device driver is required
for PC LAN Program. Add the following line to the CONFIG.SYS file for the
specific DOS session:
d:\IBMCOM\PROTOCOL\LANVMEM.SYS
where d is the startup drive. This device driver is not needed for DOS LAN
Services but is needed for some LAN applications and for PC LAN Program.
Hint:
If you plan to run multiple DOS LAN Services from one workstation, you
must specify a different machine ID for each DOS session.
To Specify Different Machine IDs:
1. At the OS/2 prompt, type:
COPY C:\NET\NETWORK.INI C:\machid\NETWORK.INI
where machid is a unique directory on drive C for each DOS session.
Press Enter.
Note:
The Path field (see the figure titled DOS LAN Services
Installation Options Window 2) specifies C:\NET as the default
installation directory. If you specified a different name,
substitute that name for NET in the command example.
2. After you have made copies of the C:\NET\NETWORK.INI file for each DOS
session, delete the NETWORK.INI file in the C:\NET subdirectory, by
typing:
DEL C:\NET\NETWORK.INI
Press Enter.
3. Add C:\machid and C:\NET to the path statement of each AUTOEXEC.BAT
file; for example, if you are running three sessions, edit all three
AUTOEXEC.BAT files. Add a machine ID for each DOS LAN Services session.
4. Edit each NETWORK.INI file associated with a machine ID to:
a. Specify a unique machine ID and user name to match the names to be
used for each session.
b. Change the following statement from:
LANROOT=C:\NET
(where NET specifies the default directory in which DOS LAN Services
was installed) to:
LANROOT=C:\machid
This must be done for each DOS LAN Services session you are creating.
5. Copy the NET.EXE, *.MSG, *.DAT, MESSENGR.EXE, DLRPEER.EXE, NETPOPUP.EXE,
and DZG4.EXE files from the NET subdirectory (again, this assumes you
installed DOS LAN Services in the default directory) into each C:\machid
subdirectory you create, using the following commands:
COPY C:\NET\NET.EXE C:\machid
COPY C:\NET\*.MSG C:\machid
COPY C:\NET\*.DAT C:\machid
COPY C:\NET\MESSENGER.EXE C:\machid
COPY C:\NET\DLRPEER.EXE C:\machid
COPY C:\NET\NETPOPUP.EXE C:\machid
COPY C:\NET\DZG4.EXE C:\machid
Having copied these files, delete them from the NET subdirectory as
follows:
DEL C:\NET\NET.EXE
DEL C:\NET\*.MSG
DEL C:\NET\*.DAT
DEL C:\NET\MESSENGER.EXE
DEL C:\NET\DLRPEER.EXE
DEL C:\NET\NETPOPUP.EXE
DEL C:\NET\DZG4.EXE
6. Assign the remaining files in the NET subdirectory read-only permission
as a precaution against multiple sessions accessing executables in the
NET directory. To set the permissions, type the following command:
ATTRIB C:\NET\*.* +R
Press Enter.
ΓòÉΓòÉΓòÉ 10.4. Configuring WIN-OS/2 for Network Operation ΓòÉΓòÉΓòÉ
The procedure for configuring WIN-OS/2 for network operation requires two
parts. The first part ensures that the DOS LAN Services virtual device driver
is installed.
To Install the DOS LAN Services Virtual Device Driver:
1. In the LAN Services folder, select LAN Services
Installation/Configuration Program.
2. Select OK on the logo panel.
3. Select Tailored in the Easy or Tailored Installation/Configuration
window.
4. The Installation Tasks window is displayed. Select OK to accept Install
or configure this workstation (default).
5. The Installation and Configuration window, which is now displayed,
allows you to move between the Install and Remove window and the
Configure window. Install or remove a component is the default when the
window is displayed for the first time. Select OK.
6. Select Virtual DOS LAN API Support. The Action column displays Install
for the selected component.
7. Select Install. This installs the virtual device drivers necessary to
run WIN-OS/2.
8. Exit the LAN Services installation/configuration program.
The second part configures WIN-OS/2.
To Configure WIN-OS/2:
1. From the OS/2 desktop, select the OS/2 System object.
2. Select the Command Prompts folder.
3. Select the WIN-OS/2 Full Screen object.
4. From the Program Manager, select the WIN-OS/2 Main object.
5. Select WIN-OS/2 Setup object.
6. From the Options menu, select Change system settings.
7. Click on the right drop-down list to see a list of choices.
8. From the list, select IBM OS/2 LAN Server (Version 1.3 CSD 5015/5050),
and then select OK.
9. Select OK on the downlevel software panel. Insert OS/2 diskettes as
requested. The Setup program installs the following three files in the
OS2/MDOS/WINOS2/SYSTEM directory:
o NETAPI20.DLL
o PMSPL20.DLL
o LANMAN.DRV
10. Run the following commands to make the DLL files useable:
COPY NETAPI20.DLL NETAPI.DLL
COPY PMSPL20.DLL PMSPL.DLL
If you have DOS or Windows applications that require NetBIOS or 802.2, install
the appropriate virtual device driver, using LAPS. For more information, refer
to the MPTS - AnyNet for OS/2: Configuration Guide.
ΓòÉΓòÉΓòÉ 11. Planning for the LAN Support Program ΓòÉΓòÉΓòÉ
This chapter describes some planning considerations for the LAN Support
Program. See Recommendations and Problem Solving for tips about configuring and
operating the program.
Check the following table for planning advice for adapters or configurations
that apply to you. Contact your network administrator for additional help.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé ADAPTER OR CONFIGURA- Γöé PLANNING TASK Γöé SEE: Γöé
Γöé TION Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Using IBM Token-Ring Γöé o Be sure the data Γöé Data Rate for the Γöé
Γöé Network Adapter (see Γöé rate of the token Γöé IBM Token-Ring Γöé
Γöé note) Γöé ring matches the Γöé Network Adapter Γöé
Γöé Γöé data rate of the Γöé Γöé
Γöé Γöé adapter Γöé Γöé
Γöé Γöé Γöé Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé o Be sure shared RAM Γöé Planning Shared RAM Γöé
Γöé Γöé is set to the Γöé for 16/4-Mbps IBM Γöé
Γöé Γöé desired value Γöé Token-Ring Γöé
Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Using Original PC Γöé o Be sure you meet the Γöé Planning for the Γöé
Γöé Network Adapter Γöé requirements unique Γöé Original PC Network Γöé
Γöé Γöé to this adapter Γöé Adapter Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Using two LAN adapters Γöé o Be sure you meet the Γöé Using Two LAN Γöé
Γöé in one computer Γöé requirements unique Γöé Adapters Γöé
Γöé Γöé to this configura- Γöé Γöé
Γöé Γöé tion Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Having a computer with Γöé o Check the BIOS date; Γöé Checking the BIOS Γöé
Γöé a Basic Input/Output Γöé install the driver Γöé Date on a PC (Not Γöé
Γöé System (BIOS) date Γöé TIMERINT.SYS if nec- Γöé Applicable to PS/2 Γöé
Γöé before June 1985 (not Γöé essary Γöé Computers) Γöé
Γöé applicable to PS/2 com- Γöé Γöé Γöé
Γöé puters) Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Using IEEE 802.2 Γöé o Decide whether to Γöé Whether to Use the Γöé
Γöé support Γöé configure the LAN Γöé IEEE 802.2 Γöé
Γöé Γöé Support Program with Γöé Interface Γöé
Γöé Γöé IEEE 802.2 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Using the IBM Token- Γöé o Configure one or two Γöé Using the IBM Γöé
Γöé Ring Network 16/4 Γöé adapters Γöé Token-Ring Network Γöé
Γöé Adapter II Γöé Γöé 16/4 Adapter II Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTE: The IBM Token-Ring Network 16/4 Adapter II does not require you to Γöé
Γöé set a value for shared RAM. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 11.1. NDIS and Non-NDIS Adapter Support ΓòÉΓòÉΓòÉ
The LAN Support Program consists of device drivers and supporting files. Device
drivers for an adapter provide a software interface to enable application
programs to communicate with the adapter. An adapter can be supported entirely
by device drivers in the LAN Support Program. For example, an IBM PC Network
Adapter can interface with the DXMG0MOD.SYS device driver. An adapter of this
type is called a non-NDIS adapter.
On the other hand, an adapter supported by the LAN Support Program can require
a device driver unique to the adapter as well as drivers in the LAN Support
Program. In this design, the unique device driver conforms to the Network
Driver Interface Specification (NDIS), a standard for writing adapter device
drivers that was jointly developed by Microsoft and 3Com. The device driver
functions at the medium access control (MAC) layer. Therefore, it is called an
NDIS MAC driver. It interfaces with a protocol driver from the LAN Support
Program (DXME0MOD.SYS or DXMJ0MOD.SYS). For example, an IBM FDDI Adapter
requires the NDIS MAC driver IBMFDDI.DOS. Such an adapter is called an NDIS
adapter.
Some IBM Token-Ring Network Adapters can be configured as non-NDIS or NDIS
adapters. These adapters can be supported by a device driver provided in the
LAN Support Program, such as DXMC0MOD.SYS, or they can be supported by an NDIS
MAC driver, such as IBMTOK.DOS. However, the IBM Token-Ring 16/4 Adapter II
must always be configured as an NDIS adapter.
ΓòÉΓòÉΓòÉ 11.1.1. NDIS Adapters ΓòÉΓòÉΓòÉ
If you are using an NDIS adapter, you must obtain the NDIS MAC driver before
you proceed. The NDIS MAC driver is usually found on a diskette provided by the
supplier of the adapter. In the U.S.A., if you need an NDIS MAC driver for a
supported IBM adapter, you may be able to download it from the IBM National
Support Center (NSC) Bulletin Board. See Obtaining a NIF or an IBM NDIS MAC
Driver for more information.
When the NDIS MAC driver is found on a diskette shipped with the adapter, this
diskette is referred to by various names in the adapter documentation. In this
user's guide, it is referred to as the adapter option diskette.
Other files in addition to the NDIS MAC driver are required when configuring
NDIS adapters. One of these files is the network information file (NIF) in IBM
format.
ΓòÉΓòÉΓòÉ 11.2. Files Required for NDIS Adapters ΓòÉΓòÉΓòÉ
In the case of NDIS adapters, the IEEE 802.2 protocol driver for NDIS MAC
drivers (DXME0MOD.SYS) is part of an NDIS protocol stack that provides an IEEE
802.2 interface for IEEE 802.3, IEEE 802.5, and Ethernet DIX Version 2.0 frame
formats. (If you also need NetBIOS support when using the DXME0MOD.SYS protocol
driver, install the DXMT0MOD.SYS protocol driver.) The NetBIOS protocol driver
for NDIS MAC drivers (DXMJ0MOD.SYS) is part of an NDIS protocol stack that
provides a NetBIOS interface for IEEE 802.3, IEEE 802.5, and Ethernet DIX
Version 2.0 frame formats.
NDIS is the LAN Manager Network Driver Interface Specification, which was
jointly developed by Microsoft and 3Com. It is the LAN Manager driver
architecture that lets a DOS or an Operating System/2:* (OS/2*) system support
one or more network adapters and protocol stacks. It gives a standardized way
for writing drivers for network adapters and communications protocols. It also
defines the rules for configuring and binding multiple drivers into the desired
set of layered protocol stacks.
Following is a description of NDIS drivers and files that are part of the NDIS
protocol stack. For more information, refer to Recommendations and Problem
Solving.
o NDIS protocol manager (PROTMAN.DOS)
The protocol manager (PROTMAN.DOS) is a DOS device driver that provides a
standardized way for multiple MAC and protocol drivers to get configuration
information and bind together into the desired protocol hierarchy. The
PROTMAN.DOS device driver statement must be included in the CONFIG.SYS file
before any of the other device drivers associated with the DXME0MOD.SYS
protocol driver.
The protocol manager reads the NDIS configuration information out of the
PROTOCOL.INI file and makes it available to the DXME0MOD.SYS protocol driver
and to the NDIS MAC drivers. The protocol manager looks for the PROTOCOL.INI
file in the default directory LANMAN on the same disk from which DOS was
loaded. You can use the /I: parameter in the DEVICE= statement in the
CONFIG.SYS file to specify the directory where the PROTOCOL.INI file is found
if the PROTOCOL.INI file is not in the default directory. For example,
DEVICE=C:\LSP\PROTMAN.DOS /I:C:\NDIS
specifies that the PROTMAN.DOS device driver is located in the \LSP directory
on the C: drive and that it can find PROTOCOL.INI in the NDIS directory on
the C: drive.
Note: When entering this /I: parameter, be sure to leave a blank space in
front of the parameter, as shown in the preceding example.
If you are configuring the LAN Support Program manually, you must copy the
PROTMAN.DOS device driver and the PROTOCOL.INI file to the working disk.
o NDIS configuration file (PROTOCOL.INI)
The PROTOCOL.INI file contains configuration information that is used by the
protocol manager and the NETBIND program to establish communication between
the DXME0MOD.SYS protocol driver and the NDIS MAC drivers. IBM recommends
that you use the sample of this file shipped on the installation diskette of
the LAN Support Program. The PROTOCOL.INI file must be in the LANMAN
directory on the drive from which DOS is loaded, or in the directory
specified by the /I: parameter for the PROTMAN.DOS command line in the
CONFIG.SYS file.
The PROTOCOL.INI file is divided into named sections for each module in the
NDIS system. Each named section is followed by configuration parameters for
that module. In addition to the parameters stated in the PROTOCOL.INI file,
other parameters for the DXME0MOD.SYS or DXMJ0MOD.SYS protocol driver are
specified in the CONFIG.SYS file's DEVICE= statements. For information about
these parameters, see Parameters for the IEEE 802.2 Protocol Driver for or
Parameters for the NETBIOS Protocol Driver for NDIS Adapters. Refer to the
documentation for the adapter for more specific information about the
parameters for each NDIS MAC driver.
In the version of the PROTOCOL.INI file shipped on the installation diskette,
[DXME0_MOD] is the module name for the DXME0MOD.SYS protocol driver, and the
driver name for DXME0MOD.SYS is DXME0$. [DXMJ0MOD_MOD] is the module name for
the DXMJ0MOD.SYS protocol driver, and its driver name is NETBEUI$. In the
process of configuring the LAN Support Program, the module names of the
adapters that will be bound to the DXME0MOD.SYS protocol driver must be
entered after the Bindings = statement under [DXME0_MOD]. The process of
binding is the same for the DXMJ0MOD.SYS protocol driver, except that the
Bindings = statement is found in the named section [DXMJ0MOD_MOD].
The NDIS MAC drivers for NDIS adapters must be listed in the CONFIG.SYS file.
The order in which the adapters are defined in the Bindings = statement
determines whether an adapter is primary or alternate.
o NDIS MAC driver (for example, MACETH.DOS, MACETH2.DOS ELNKII.DOS, ELNKMC.DOS,
or SMCMAC.DOS)
NDIS MAC drivers are DOS device drivers that provide low-level access to
network adapters. The main function of a MAC driver is to support
transmitting and receiving packets. The NDIS MAC driver communicates with the
DXME0MOD.SYS protocol driver using NDIS Version 2.01 or earlier. An NDIS MAC
driver must be loaded for each Ethernet or other adapter supported by an NDIS
MAC driver in the computer.
NDIS MAC drivers are usually supplied with their associated adapters. NDIS
MAC drivers are not supplied with the LAN Support Program. The appropriate
NDIS MAC driver must be loaded in the CONFIG.SYS file after the PROTMAN.DOS
device driver and before the DXMA0MOD.SYS protocol driver. For example, if
you are using the IBM PS/2 Ethernet Adapter/A and the directory is \LSP, the
following line must be added to the CONFIG.SYS file:
DEVICE=\LSP\MACETH.DOS
o NDIS protocol drivers (DXME0MOD.SYS and DXMJ0MOD.SYS)
NDIS protocol drivers provide higher level communication services from data
link to session. DXME0MOD.SYS is a protocol driver that provides an IEEE
802.2 interface at the top and interfaces with an NDIS MAC driver at the
bottom. DXMJ0MOD.SYS is a protocol driver that provides a NetBIOS interface
at the top and interfaces with an NDIS MAC driver at the bottom.
o NETBIND.COM
NETBIND is a program that initiates the bind process between the NDIS
protocol driver and the NDIS MAC driver. Adapter activity cannot begin until
the bind process is completed. NETBIND should be coded at the beginning of
AUTOEXEC.BAT.
Other LAN Support Program device drivers are also used with NDIS adapters; see
Device Driver Summary for more information.
ΓòÉΓòÉΓòÉ 11.3. Obtaining a NIF or an IBM NDIS MAC Driver ΓòÉΓòÉΓòÉ
U.S. customers may obtain the NDIS MAC drivers for some IBM NDIS adapters
through the IBM National Support Center (NSC) Bulletin Board. Network
Information Files (NIFs) for many NDIS adapters supported by the LAN Support
Program, both IBM and non-IBM, are also available. All files are offered in a
format suitable for downloading, and each downloaded device driver comes with
its own terms and conditions.
The NSC Bulletin Board is available 24 hours a day on a toll-call basis, with
no access charge to the bulletin board. To access the NSC system, call
1-404-835-6600. The files required by the LAN Support Program are found in
Directory 32.
The files are available from IBM without charge. However, the customer is
responsible for all telephone toll charges incurred when electronically
downloading the files.
Requirements for the asynchronous electronic connection to the NSC bulletin
board are as follows:
o A modem that supports 1200 baud or more
o Communication software capable of supporting XMODEM file transfer protocols
o A switched telephone line
The modem should be set to:
o 8 data bits
o 1 stop bit
o No parity
o Standard transmission speed from 1200 to 9600 baud
ΓòÉΓòÉΓòÉ 11.4. Configuring for NDIS Adapters ΓòÉΓòÉΓòÉ
The diskette on which the NDIS MAC driver and NIF are located is considered the
adapter option diskette, whether the diskette was shipped with the adapter or
obtained in some other way. The adapter option diskette should contain the NDIS
MAC driver, any other required files, such as an NDIS message file, and the
NIF.
SMC adapters require you to choose among Micro Channel, jumpered, and
software-configured adapters.
ΓòÉΓòÉΓòÉ 11.5. Data Rate for the IBM Token-Ring Network Adapter ΓòÉΓòÉΓòÉ
When using an IBM Token-Ring Network Adapter, you must check the adapter data
rate to make sure that it matches the data rate on the network. If these data
rates do not match, the ring will beacon when the adapter is opened (prepared
for use on the network). All data on the network stops temporarily. During the
time the data is not transmitted on the ring, application failures may occur.
Then, the adapter is disconnected from the ring, and data transmission is
resumed. Error messages from the LAN Support Program and the application
program may be displayed.
To avoid this problem, you must be sure that the adapter data rate matches the
data rate on the token ring. If you know that the two rates match, go to
Planning Shared RAM for 16/4-Mbps IBM Token-Ring or proceed with the
configuration.
If you are not sure that the rates match, compare the data rate on the adapter
with the data rate on the ring.
To Compare the Adapter Data Rate with Network Data Rate:
1. Run the diagnostics included on the diskette that is packaged with the
adapter to find out the data rate of the adapter. (See the documentation
included with your adapter for more information.)
If you do not have the diagnostics and you are using a non-NDIS
Token-Ring Network Adapter, you can load the DXMA0MOD.SYS and
DXMC0MOD.SYS device drivers. (Do not load the DXMT0MOD.SYS device
driver.) When you try to activate the LAN Support Program, the data
rate of the adapter is displayed. This technique does not cause the
ring to beacon.
2. Determine the data rate of the network. If you do not know the data
rate, ask your LAN administrator or the person who installed your LAN
adapter what the data rate of the network is. If you cannot find out the
data rate, check the adapter data rate of another station on the network
that is known to be operating correctly. The data rate is either 4 or
16 Mbps.
3. Compare the data rate on your adapter with the data rate on the network.
If the data rate on the adapter does not match the network data rate,
change the data rate of the adapter, if possible, or replace the
adapter. Refer to the installation instructions that came with the
adapter.
ΓòÉΓòÉΓòÉ 11.6. Planning Shared RAM for 16/4-Mbps IBM Token-Ring ΓòÉΓòÉΓòÉ
Network Adapters
Most 16/4 Token-Ring network adapters contain 64KB of shared RAM. [ You cannot
set the shared RAM address for the IBM Token-Ring Network 16/4 Adapter II,
which is not a shared RAM adapter. ] When installing the adapters, you can set
the shared RAM size to 8, 16, 32, or 64KB. When set to 16KB, the adapters allow
access to the entire 64KB shared RAM by using a technique called RAM paging.
This technique saves memory in the computer by paging the shared RAM on the
adapter into the memory map of the computer one page at a time.
For most uses, you should install these adapters with a shared RAM size of
16KB. This configuration makes the entire 64KB of shared RAM available and
minimizes the possibility that the memory addresses of the adapters may
conflict with addresses used by other adapters in the computer. Setting shared
RAM to 16KB is especially recommended when two LAN adapters are installed in
one computer.
If 16KB of RAM are not available in the computer, install the adapter with an
8KB page size; in this case, paging is not available and shared RAM is limited
to 8KB.
See the instructions in the documentation for your adapter to set the size of
shared RAM.
Note: If you are using the NDIS MAC driver IBMTOK.DOS, the shared RAM address
is set in the PROTOCOL.INI file. For more information, see the documentation
for your adapter.
ΓòÉΓòÉΓòÉ 11.7. Planning for the Original PC Network Adapter ΓòÉΓòÉΓòÉ
When the original PC Network Adapter is used with the LAN Support Program, the
following rules apply:
o Only one original PC Network Adapter is supported in each workstation. No
other communications adapters (for example, LAN adapters or modems) should be
used in the workstation.
o The device driver for the original PC Network Adapter (DXMG2MOD.SYS) cannot
be used in LAN bridges or gateways.
o The performance of the device driver for the original PC Network Adapter
(DXMG2MOD.SYS) may not meet your needs if used on a workstation configured by
the PC LAN Program as a file or print server.
o The messages originated by the DXMG2MOD.SYS device driver are only displayed
in U.S. English or German. The default is U.S. English.
You may need to replace the original PC Network Adapter with one of the other
PC Network Adapters if the original PC Network Adapter does not meet your
requirements.
ΓòÉΓòÉΓòÉ 11.8. Using Two LAN Adapters ΓòÉΓòÉΓòÉ
The LAN Support Program can support two LAN adapters, except when you are using
the original PC Network Adapter. The following section lists some planning
considerations for this configuration.
ΓòÉΓòÉΓòÉ 11.8.1. Adapter Interrupt Level for ISA Bus Computers ΓòÉΓòÉΓòÉ
If you use an Industry Standard Architecture (ISA) bus computer, check to be
sure that each of the two adapters has a different interrupt level, except when
you are using two IBM Token-Ring Network 16/4 Adapter IIs. See Using Two IBM
Token-Ring Network 16/4 Adapter IIs for a description of this configuration.
ΓòÉΓòÉΓòÉ 11.8.2. Using an IBM PC Network Adapter ΓòÉΓòÉΓòÉ
If only one of two adapters is a PC Network Adapter, the PC Network Adapter
must be set up in the hardware as primary. For example, if a PC Network Adapter
and an IBM Token-Ring Network Adapter are installed in the same computer, the
PC Network Adapter must be set up as a primary adapter. The Token-Ring Network
Adapter may be set up as either primary or alternate.
Note:
If a PC Network Adapter and a non-NDIS IBM Token-Ring Network Adapter
are both set up as primary adapters in the same computer, the LAN
Support Program can support this configuration. Although both are
primary adapters as determined by the setup of the hardware, the LAN
Support Program configures the PC Network Adapter as the primary adapter
and the Token-Ring Network Adapter as the alternate adapter.
If you do manual configuration with this arrangement, be sure to list
the DXMGnMOD.SYS device driver entry before DXMCnMOD.SYS in the
CONFIG.SYS file so that the LAN Support Program can handle the PC
Network Adapter as the primary adapter.
Another alternative when both adapters are set up in the hardware as
primary adapters is to configure the PC Network Adapter as a non-NDIS
primary adapter and the Token-Ring Network Adapter as an alternate NDIS
adapter.
ΓòÉΓòÉΓòÉ 11.8.3. Using IBM Token-Ring Network Adapters ΓòÉΓòÉΓòÉ
If you are using an IBM Token-Ring Network Adapter (**) with any other
supported adapter, the shared RAM and the ROM addresses of the Token-Ring
Network Adapter must be set to avoid memory conflicts with the other adapter.
On a Micro Channel computer, memory conflicts are noted by the reference
diskette during the setup of the adapters. You must enter a value for the
shared RAM address in the CONFIG.SYS file as a parameter for the DXMC0MOD.SYS
or DXMC1MOD.SYS driver only if you are using an ISA bus computer and
configuring the LAN Support Program manually. See Shared RAM and Editing
Parameters for the IBM Token-Ring Network Device Drivers for information about
entering this parameter.
If you are using the NDIS MAC driver IBMTOK.DOS, the shared RAM address is set
in the PROTOCOL.INI file. For more information, see the adapter documentation.
The suggested Token-Ring Network Adapter shared RAM addresses are D8000 for the
primary adapter and D4000 for the alternate adapter. When you use these
addresses, the shared RAM size must be 32KB or less.
If your Token-Ring Network Adapter allows you to set the shared RAM size, it is
recommended that you set the shared RAM size to 16KB. See Planning Shared RAM
for 16/4-Mbps IBM Token-Ring and the documentation for your adapter.
If your Token-Ring Network Adapter has ROM, you must check the ROM address.
The suggested Token-Ring Network Adapter ROM physical addresses are CC000 for
the primary adapter and DC000 for the alternate adapter.
ΓòÉΓòÉΓòÉ 11.8.4. Setting Up the Primary and Alternate Adapters ΓòÉΓòÉΓòÉ
IBM Token-Ring Network Adapters [ Other than the IBM Token-Ring Network 16/4
Adapter II. ] and IBM PC Network Adapters are set up as primary or alternate
adapters in the hardware of the computer. For computers with Micro Channel
architecture, you can change the setup of these adapters using the reference
diskette. For computers with ISA bus architecture, you can make this selection
using the jumper pins or switches located on the adapter.
If these adapters are configured as non-NDIS adapters, the LAN Support Program
determines which of the adapters is primary and which is alternate, depending
on the hardware setup of the adapters. One exception to this rule is the
combination of a PC Network Adapter and a non-NDIS Token-Ring Network Adapter,
both set up as primary adapters. In this case, the LAN Support Program
configures the PC Network Adapter as primary and the Token-Ring Network Adapter
as alternate.
If Token-Ring Network Adapters are used as NDIS adapters, the LAN Support
Program ignores the hardware setup. For these, as for all NDIS adapters, you
specify the primary and alternate adapters during manual configuration.
ΓòÉΓòÉΓòÉ 11.8.5. Two NDIS Adapters Supported by the Same NDIS MAC Driver ΓòÉΓòÉΓòÉ
If you have this configuration on a Micro Channel computer, you may have to
specify the correct slot locations of the adapters by changing some NDIS MAC
driver parameters in the PROTOCOL.INI file. Consult your adapter documentation
for more information.
ΓòÉΓòÉΓòÉ 11.9. Checking the BIOS Date on a PC (Not Applicable to PS/2 Computers) ΓòÉΓòÉΓòÉ
If you have an IBM PC, Personal Computer XT, or Personal Computer AT computer
with a BIOS date earlier than June 1985, you need to use TIMERINT.SYS. To check
the BIOS date, access the BIOSDATE.EXE file on the "Program" diskette in the A:
drive. Then, type:
BIOSDATE
This program displays the BIOS date for your computer. If the BIOS is dated
before June 1985, copy the TIMERINT.SYS file from the "Program" diskette to
your working disk and include the following statement in the CONFIG.SYS file:
DEVICE=\LSP\TIMERINT.SYS
\LSP stands for the name of the directory where the LAN Support Program files
are located. Substitute the name of the directory you used if necessary.
TIMERINT.SYS is a device driver that replaces the timer interrupt code on the
IBM workstation BIOS. It reduces the likelihood of the DOS internal stack
error. The STACKS= statement in the CONFIG.SYS file is no longer required.
ΓòÉΓòÉΓòÉ 11.10. Whether to Use the IEEE 802.2 Interface ΓòÉΓòÉΓòÉ
You need the IEEE 802.2 interface in any of the following cases:
o You plan to use application programs that use the IEEE 802.2 interface, such
as IBM Personal Communications/3270 or IBM Application System/400* PC
Support.
o You plan to use an IBM PC Network Adapter.
o You plan to use an IBM Token-Ring Network Adapter as a non-NDIS adapter.
Non-NDIS adapters always use the IEEE 802.2 interface, which is provided by LAN
Support Program device drivers. NDIS adapters use the protocol driver
DXME0MOD.SYS when the IEEE 802.2 interface is required. With this driver, the
NetBIOS interface is provided by the device driver DXMT0MOD.SYS.
You need the IEEE 802.2 interface unless you are using NDIS adapters with
application programs that require only the NetBIOS interface. If you have this
configuration, you can use the protocol driver DXMJ0MOD.SYS, and you do not
need DXMT0MOD.SYS.
IBM recommends that you use DXMJ0MOD.SYS when possible, because you can get
better NetBIOS performance with it.
ΓòÉΓòÉΓòÉ 11.11. Using the IBM Token-Ring Network 16/4 Adapter II ΓòÉΓòÉΓòÉ
The LAN Support Program supports the IBM Token-Ring Network 16/4 Adapter II as
an NDIS adapter only. The required NDIS MAC driver is IBM16TR.DOS, which is
supplied on the adapter option diskette.
Edit the CONFIG.SYS file . Enter this statement at the top of the file:
STACKS=9,512
ΓòÉΓòÉΓòÉ 11.11.1. Using Two IBM Token-Ring Network 16/4 Adapter IIs ΓòÉΓòÉΓòÉ
The adapter I/O base address, the DMA channel, and the adapter interrupt level
are set by switches on the adapters. To use two of these adapters in the same
host computer, make sure that they do not use the same I/O base or DMA channel,
but that they do share the same interrupt level.
In this configuration, you must also change some parameters. Specify the
correct adapter I/O base address for each adapter so that it reflects the
address set by the switches on that adapter. Other parameters that have to be
changed are the Maximum Number of Queued Transmits (MAXTRANSMITS) and the
Minimum Number of Adapter Driver Receive Buffers (MINRCVBUFFS).
MAXTRANSMITS should be changed to 10, and the MINRCVBUFFS should be changed to
7, on both the primary and the alternate adapter.
Please note that these parameters should be changed only in the case of
configuration for two adapters. For one adapter, use the default values of 15
for MAXTRANSMITS and 8 for MINRCVBUFFS.
If you do a manual configuration, these same parameters must be changed in the
PROTOCOL.INI file.
Edit the CONFIG.SYS file. Enter this statement at the top of the file:
STACKS=9,512
ΓòÉΓòÉΓòÉ 12. Customizing the LAN Support Program Device Driver Parameters ΓòÉΓòÉΓòÉ
This chapter describes the LAN Support Program device driver parameter values
and tells you how to edit the parameter values in CONFIG.SYS. See the
documentation that came with your adapter for more information about changing
the NDIS MAC driver parameters.
For Remote IPL, the LAN Support Program device drivers are specified in the CNF
files instead of CONFIG.SYS. The DRV statements in the CNF files can be
updated to specify the parameters described in this chapter.
Notes:
1. The highlighted letters distinguish each device driver from the other
LAN Support Program device drivers.
2. The sample directory provided in the examples showing you how to edit
CONFIG.SYS is \LSP. Substitute the name of your directory if it is
different.
ΓòÉΓòÉΓòÉ 12.1. Device Driver Summary ΓòÉΓòÉΓòÉ
The LAN Support Program contains the following device drivers:
o Interrupt arbitrator
DXMA0MOD.SYS Is required by all installations.
o Device drivers which provide support for non-NDIS Token-Ring Network Adapters
DXMC0MOD.SYS Supports IBM Token-Ring Network Adapters.
DXMC1MOD.SYS Is used instead of DXMC0MOD.SYS when running the IBM
3270 Workstation Program.
o Device drivers which provide support for PC Network Adapters
DXMG0MOD.SYS Supports PC Network Adapters.
DXMG1MOD.SYS Is used instead of DXMG0MOD when running the 3270
Workstation Program. This device driver does not
support the original PC Network Adapter.
DXMG2MOD.SYS Supports the original PC Network Adapter. See
restrictions on the use of the original PC Network
Adapter in Planning for the Original PC Network
Adapter.
o Protocol drivers for NDIS adapters
DXME0MOD.SYS Enables communication between an NDIS MAC driver and an
application program that uses the IEEE 802.2 interface.
This driver works with DXMT0MOD.SYS to provide the
NetBIOS interface to application programs when it is
required. DXME0MOD.SYS supports MAC drivers that use
the IEEE 802.3, 802.5, or Ethernet DIX Version 2.0
interface and are compliant with NDIS Version 2.01 or
earlier.
The following files are associated with DXME0MOD.SYS:
PROTMAN.DOS NDIS protocol manager
PROTOCOL.INI Data file that contains the configuration parameters for
NDIS modules
NETBIND.COM NDIS binding utility
DXMJ0MOD.SYS Enables communication between an NDIS MAC driver and an
application program that uses the NetBIOS interface.
DXMJ0MOD.SYS supports MAC drivers that use the IEEE
802.3 or 802.5 interface or the Ethernet DIX Version
2.0 interface and are compliant with NDIS Version 2.01
or earlier.
The following files are associated with DXMJ0MOD.SYS:
PROTMAN.DOS NDIS protocol manager
PROTOCOL.INI Data file that contains the configuration parameters for
NDIS modules
NETBIND.COM NDIS binding utility
o NetBIOS interface device driver (not used with DXMJ0MOD.SYS)
DXMT0MOD.SYS Is required to provide NetBIOS application programs
with a program interface to the adapter support device
drivers. It cannot be used unless at least one of the
drivers DXMCnMOD.SYS, DXMGnMOD.SYS, or DXME0MOD.SYS has
been configured.
ΓòÉΓòÉΓòÉ 12.2. Parameters with Special Functions (W, N, CF, MINSAP, MINLINK, X, and R/T) ΓòÉΓòÉΓòÉ
Some parameters are new or offer special functions. In certain configurations,
you must change the default values of these parameters to enable the LAN
Support Program to run. These parameters are listed in Parameters with Special
Functions. The purpose of the table is to identify the parameters and to refer
you to fuller descriptions of them.
Note:
When using the MINLINK or MINSAP parameters with NDIS adapters or PC
Network Adapters, you may need to increase the work space for the
adapter. See Work Space, Heavy Network Load Using PC Network Adapters,
and Increasing Work Space for NDIS Adapters for more information about
the work space parameter.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 7. Parameters with Special Functions Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé FUNCTION Γöé SEE: Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé W Γöé Parameter for DXMCnMOD.SYS. When two Γöé The W Γöé
Γöé Γöé non-NDIS Token-Ring network adapters Γöé Parameter.. Γöé
Γöé Γöé are used, this parameter ensures that Γöé Γöé
Γöé Γöé DXMCnMOD.SYS runs only on the primary Γöé Γöé
Γöé Γöé adapter, leaving the alternate adapter Γöé Γöé
Γöé Γöé available. Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CF Γöé Parameter for DXMT0MOD.SYS. It is Γöé Summary of the Γöé
Γöé (CALL.FAR) Γöé required when using Windows or the DOS Γöé Keyword Values Γöé
Γöé Γöé memory management programs with a con- Γöé for the NetBIOS Γöé
Γöé Γöé figuration of the LAN Support Program Γöé New Parameters.. Γöé
Γöé Γöé that includes DXMT0MOD.SYS. Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé N Γöé Parameter for DXMCnMOD.SYS, Γöé The N Γöé
Γöé Γöé DXMGnMOD.SYS, and DXME0MOD.SYS. This Γöé Parameter.. Γöé
Γöé Γöé parameter does not apply to Γöé Γöé
Γöé Γöé DXMG2MOD.SYS, because MINSAP and Γöé Γöé
Γöé Γöé MINLINK are not parameters of Γöé Γöé
Γöé Γöé DXMG2MOD.SYS. You must use this Γöé Γöé
Γöé Γöé parameter when you use MINSAP or Γöé Γöé
Γöé Γöé MINLINK. The N parameter enables the Γöé Γöé
Γöé Γöé device driver to interpret the MINSAP Γöé Γöé
Γöé Γöé and MINLINK parameters correctly. Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MINSAP Γöé Parameter for DXMCnMOD.SYS, Γöé MINSAP.. Γöé
Γöé Γöé DXMGnMOD.SYS, and DXME0MOD.SYS. (Does Γöé Γöé
Γöé Γöé not apply to DXMG2MOD.SYS.) You can Γöé Γöé
Γöé Γöé use this parameter to set the minimum Γöé Γöé
Γöé Γöé number of service access points Γöé Γöé
Γöé Γöé (SAPs). The N parameter must be Γöé Γöé
Γöé Γöé present when this parameter is used. Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MINLINK Γöé Parameter for DXMCnMOD.SYS, Γöé MINLINK.. Γöé
Γöé Γöé DXMGnMOD.SYS, and DXME0MOD.SYS. (Does Γöé Γöé
Γöé Γöé not apply to DXMG2MOD.SYS.) You can Γöé Γöé
Γöé Γöé use this parameter to set the minimum Γöé Γöé
Γöé Γöé number of link stations. The N param- Γöé Γöé
Γöé Γöé eter must be present when this param- Γöé Γöé
Γöé Γöé eter is used. Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé X Γöé Parameter for DXME0MOD.SYS. LAN Γöé The X Γöé
Γöé Γöé Support Program Versions 1.3 and 1.2 Γöé Parameter Γöé
Γöé Γöé use different values to identify Γöé Γöé
Γöé Γöé Ethernet adapters to application pro- Γöé Γöé
Γöé Γöé grams. The X parameter causes the LAN Γöé Γöé
Γöé Γöé Support Program to provide the value Γöé Γöé
Γöé Γöé from Version 1.2. Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé R/T Γöé Parameter for DXMCnMOD.SYS. Each of Γöé IBM Token-Ring Γöé
Γöé Γöé these parameters reduces the work area Γöé Work Area Γöé
Γöé Γöé for the device driver. Γöé Reduction Γöé
Γöé Γöé Γöé Parameters.. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 12.3. Parameter for the Interrupt Arbitrator Device Driver (DXMA0MOD.SYS) ΓòÉΓòÉΓòÉ
DXMA0MOD.SYS has one parameter that defines the language in which load-time
messages are displayed. This parameter corresponds to one of the values defined
as DOS country codes in the IBM Personal Computer Disk Operating System user's
guide for your version of DOS. The country codes that are supported are as
follows:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé COUNTRY Γöé Γöé COUNTRY Γöé Γöé
Γöé CODE Γöé LANGUAGE Γöé CODE Γöé LANGUAGE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 002 Γöé Canadian French Γöé 351 Γöé Portuguese Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 033 Γöé French Γöé 034 Γöé Spanish Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 049 Γöé German Γöé 088 Γöé Taiwanese Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 081 Γöé Japanese Γöé 001 Γöé U.S. English Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 12.4. Non-NDIS IBM Token-Ring Network Device Driver (DXMC0MOD.SYS and DXMC1MOD.SYS) Parameters ΓòÉΓòÉΓòÉ
The Token-Ring Network device drivers for a non-NDIS Token-Ring Network Adapter
are DXMC0MOD.SYS and DXMC1MOD.SYS. Several parameters can be edited with these
device drivers: the N parameter, work area reduction parameters, adapter
addresses, shared RAM locations, the Early Token Release option, MINSAP, and
MINLINK. If your computer has two Token-Ring Network Adapters, these parameters
can be set individually for each adapter.
ΓòÉΓòÉΓòÉ 12.4.1. IBM Token-Ring Work Area Reduction Parameters ΓòÉΓòÉΓòÉ
This parameter has two values: R and T. The value R reduces the work area for
DXMC0MOD.SYS or DXMC1MOD.SYS by one half; the value T reduces the work area for
one of these device drivers to 598 bytes. If no value is entered for this
parameter, the default worksize values of 4864 bytes for DXMC0MOD.SYS and 8976
bytes for DXMC1MOD.SYS are retained. Using the R or T parameter allows you to
reduce the memory requirements for loading the LAN Support Program. However,
reducing the work area also limits the resources available for IEEE 802.2
applications.
For example, if you have entered the T parameter for the DXMCnMOD.SYS driver,
installed the DOS LAN Requester with the default NetBIOS parameters (parameters
for DXMT0MOD.SYS), and added the NetBIOS parameters ES=1 and EST=1 to support a
program such as Personal Communications/3270, you may get the message:
DXMT031E Requested resources exceed capabilities on adapter `n'.
If you get this message, the work space for the adapter is too small. Try
using the R parameter to provide enough work space.
Note:
If there are two IBM Token-Ring Network Adapters, this parameter affects
both of them.
ΓòÉΓòÉΓòÉ 12.4.2. The W Parameter ΓòÉΓòÉΓòÉ
The W parameter prevents the device driver from using the alternate token-ring
network adapter when two Token-Ring network adapters are installed. You may
need this parameter if the application program using the alternate adapter
cannot share the adapter with the LAN Support Program. For example, if the LAN
Support Program is using the primary adapter, you may need this parameter to
dedicate the alternate adapter to a Transmission Control Protocol/Internet
Protocol (TCP/IP) application program or to an NDIS protocol stack.
ΓòÉΓòÉΓòÉ 12.4.3. The N Parameter ΓòÉΓòÉΓòÉ
The N parameter alerts the software to read values for MINSAP and MINLINK. If
you enter values for MINSAP and MINLINK, but do not enter the N parameter, the
MINSAP and MINLINK parameters are ignored if there is one adapter or
misinterpreted if there are two.
ΓòÉΓòÉΓòÉ 12.4.4. IBM Token-Ring Network Adapter Addresses ΓòÉΓòÉΓòÉ
The address of the adapter is in the range that is administered universally by
the standards committees for LANs. This universally administered address is
the default address for the adapter if no other address is assigned, and is
often referred to as the burned-in address.
Your network administrator may assign a locally administered address that
overrides the universally administered address. This address must consist of
12 hexadecimal digits that range from X'4000 0000 0000' to X'7FFF FFFF FFFF'.
Values outside this range may be incompatible with other products on the
network.
IBM recommends that the address be restricted to decimal values. The locally
administered address would range from X'4000 0000 0000' to X'4000 7999 9999'
decimal.
Notes:
1. Make sure that the address is recorded on the physical and logical
address locator charts. These charts and an explanation of them can be
found in the IBM Token-Ring Network Introduction and Planning Guide.
2. Each address must be unique on the LAN segment. An error results when
two or more adapters with the same address attempt to use the same LAN
segment. Each address should be unique on the network and unique on the
LAN segment.
To enter the adapter address, see Editing Parameters for the IBM Token-Ring
Network Device Drivers.
ΓòÉΓòÉΓòÉ 12.4.5. Shared RAM ΓòÉΓòÉΓòÉ
Many Token-Ring Network Adapters contain RAM that is shared with the computer.
[The IBM Token-Ring 16/4 Credit Card Adapter is one of the adapters with shared
RAM, but the IBM Token-Ring Network 16/4 Adapter II is not a shared RAM
adapter] The default segment location for the primary adapter, where the
computer locates the RAM, is D800. (Note that segment D800 is memory address
D8000.) For the alternate adapter, it is D400. If other features installed on
your system unit use these locations, you must assign other locations. Valid
locations must consist of 4 hexadecimal digits that represent the upper 4
digits of a 5-digit hexadecimal address.
The Token-Ring Network PC Adapter shared RAM address should be on an 8KB
boundary. The adapter needs 8KB of memory above this address.
The Token-Ring Network PC Adapter II and the Token-Ring Network Adapter/A
shared RAM address should be on a 16KB boundary. These adapters need 16KB of
memory above this address.
The 16/4 Token-Ring Network Adapter and the 16/4 Token-Ring Network Adapter/A
allow you to set the shared RAM size to 8, 16, 32, or 64KB. The shared RAM
address should be on the same boundary as the shared RAM size. For most
application programs, you should select the shared RAM size to be 16KB. For
this size, the adapter uses a technique called RAM paging to give you access to
the entire 64KB shared RAM. When you set a larger shared RAM size, you must be
sure that the address range does not conflict with the address ranges of other
adapters that may be in the computer.
To find shared RAM locations, refer to the technical reference manual for your
computer for a list of workstation memory locations. On a computer with Micro
Channel architecture, the configuration utility on the reference diskette will
indicate when shared RAM locations are in conflict. Refer to Editing Parameters
for the IBM Token-Ring Network Device Drivers for instructions on entering the
shared RAM address.
Notes:
1. If you have two adapters, the shared RAM address for the alternate
adapter must be different from that of the primary adapter.
2. If the Token-Ring Network Adapter/A or 16/4 Token-Ring Network Adapter/A
is used, the LAN Support Program ignores the shared RAM address
parameter. Instead, it uses the shared RAM address that was set when the
adapter was installed.
ΓòÉΓòÉΓòÉ 12.4.6. Early Token Release ΓòÉΓòÉΓòÉ
The Early Token Release option is supported if the Token-Ring Network 16/4
Adapter or Token-Ring Network 16/4 Adapter/A is operating at the data rate of
16Mbps. Early Token Release increases the use of the network by reducing the
time between the release of tokens on the token-ring, and is the default. You
can disable Early Token Release by changing a command line parameter for
DXMC0MOD.SYS (see Editing Parameters for the IBM Token-Ring Network Device
Drivers).
ΓòÉΓòÉΓòÉ 12.4.7. MINSAP ΓòÉΓòÉΓòÉ
This parameter is used to define the minimum number of SAPs that the adapter
will support when opened. It enables multiple 802.2 applications to coexist.
For example, IBM Personal Communications/3270 and IBM Application System/400
PC Support can run on the same workstation if MINSAP is set to a high enough
value to include the total number of SAPs required by both application
programs.
The N parameter must be present when this parameter is used. If MINSAP is
omitted, 0 is used as its value. The range is 0-127.
ΓòÉΓòÉΓòÉ 12.4.8. MINLINK ΓòÉΓòÉΓòÉ
This parameter sets the minimum number of link stations that the adapter will
support when opened. It enables multiple 802.2 applications to coexist. For
example, IBM Personal Communications/3270 and IBM Application System/400 can
run on the same workstation if MINLINK is set to a high enough value to include
the total number of link stations required by both application programs. (The
MINSAP parameter must also be set to a high enough value to include the total
number of SAPs required by both application programs.)
The N parameter must be present when this parameter is used. If MINLINK is
omitted, 0 is used as its value. The range is 0-254.
ΓòÉΓòÉΓòÉ 12.4.9. Editing Parameters for the IBM Token-Ring Network Device Drivers ΓòÉΓòÉΓòÉ
The following parameters are valid for DXMC0MOD.SYS and DXMC1MOD.SYS: [In
CONFIG.SYS, the list of parameters must be continued on one line]
DEVICE=\LSP\DXMCnMOD.SYS. R/T W N addr0,mem0,etr0,minsap0,minlink0,
&3672.addr1,mem1,etr1,minsap1,minlink1
ΓòÉΓòÉΓòÉ 12.4.9.1. Global and Positional Parameters ΓòÉΓòÉΓòÉ
The parameters R/T, W, and N are global parameters. They must be separated from
the words around them by spaces only. If one of them is omitted, its absence
is not marked. They can be entered in any order, but must precede the
positional parameters.
The parameters separated by commas are positional parameters. They must be
entered in the sequence shown in the preceding example. If one of these
parameters is omitted and another parameter follows it, a comma must be
included to mark its place. No comma is required if the omitted parameter is at
the end of the list. The first parameter, whether global or positional (or a
comma marking the location of the first positional parameter), must be
separated from the device driver name by a space. For more information about
entering these parameters, see Examples of Editing the Parameter List.
ΓòÉΓòÉΓòÉ 12.4.9.2. Parameter Definitions ΓòÉΓòÉΓòÉ
DXMCnMOD.SYS can be configured with the following parameters:
R/T Reduces the work area for DXMCnMOD.SYS.
W Prevents the device driver from using the alternate Token-Ring
Network Adapter when two Token-Ring Network Adapters are installed.
N Is required when MINSAP or MINLINK is present to alert the program
to read these positional parameters correctly.
addr0 Is replaced with the locally administered address for the primary or
only Token-Ring Network Adapter.
mem0 Is replaced with the RAM location for the primary or only Token-Ring
Network Adapter.
etr0 0=Use Early Token Release, 1=Do not use Early Token Release. This
parameter is ignored if the adapter data rate is 4Mbps, and becomes
effective only if the data rate is 16Mbps. The default is 0.
minsap0 Sets the minimum number of SAPs that the adapter will support when
opened. The N parameter must be present when this parameter is given
a value.
minlink0 Sets the minimum number of link stations that the adapter will
support when opened. The N parameter must be present when this
parameter is given a value.
addr1 Is replaced with the locally administered address for the alternate
adapter.
mem1 Is replaced with the RAM location for the alternate adapter.
etr1 0=Use Early Token Release, 1=Do not use Early Token Release. This
parameter is ignored if the adapter data is 4Mbps, and becomes
effective only if the data rate is 16 Mbps. The default is 0.
minsap1 Sets the minimum number of SAPs for the alternate adapter. The N
parameter must be present when this parameter is given a value.
minlink1 Sets the minimum number of link stations for the alternate adapter.
The N parameter must be present when this parameter is given a
value.
If two Token-Ring Network Adapters are installed in the same computer, you must
edit the parameters for the primary adapter first and the alternate adapter
second.
ΓòÉΓòÉΓòÉ 12.4.9.3. Examples of Editing the Parameter List ΓòÉΓòÉΓòÉ
To add parameters, edit the CONFIG.SYS file, as in the following examples:
o To specify a locally administered address for the primary adapter, use the
following line:
DEVICE=\LSP\DXMCnMOD.SYS 400000000001
In this example, 400000000001 is the new address for the primary adapter,
which overrides the default address encoded on the adapter. All other
defaults are retained.
o To specify the parameter to reduce the work area of the device driver by half
and to specify a locally administered address for the primary adapter, use
the following line:
DEVICE=\LSP\DXMCnMOD.SYS R 400000000001
Note that R is not followed by a comma, but only by a space. If you do
not use this parameter, leave only a space, no comma, between DXMCnMOD.SYS
and the next parameter or comma.
o To specify a new shared RAM address for the primary adapter use the following
line:
DEVICE=\LSP\DXMCnMOD.SYS ,C400
In this example, C400 is the new shared RAM segment (the physical address is
C4000) for the primary adapter. The default location for the RAM address on
the primary adapter is overridden. All other defaults are retained. Note the
comma before the RAM location. This comma indicates that a parameter (the
primary adapter address) has been omitted.
o To disable the Early Token Release option for the primary or only adapter,
use the following line:
DEVICE=\LSP\DXMCnMOD.SYS ,,1
In this example, the value 1 disables the Early Token Release option. This
parameter can be either 0 or 1, and is used only for adapters with a data
rate of 16Mbps. If the adapter data rate is 16Mbps, the option is enabled by
default. You must change the parameter value to 1 to disable it. Early Token
Release is not used for adapters with a data rate of 4Mbps.
o To specify MINSAP of 2 and MINLINK of 4 for the primary adapter:
DEVICE=\LSP\DXMCnMOD.SYS R N 400000000001,,,2,4
In this example, the first comma separates the locally administered address,
which is present. The two following commas mark places for the RAM location
and the Early Token Release parameter. Note that the N parameter must be
used.
o Following are four more examples:
- To specify addresses for the primary and alternate adapter:
DEVICE=\LSP\DXMCnMOD.SYS 400000000001,,,400000000002
In this example, 400000000001 is the address for the primary adapter and
400000000002 is the address for the alternate adapter. The second comma
indicates that the default value for the primary shared RAM location is
being retained. The third comma indicates that the default value for
Early Token Release is to be used for the primary adapter. The shared RAM
location for the alternate adapter is also retained because nothing is
entered after the alternate adapter address in the list.
- To specify a MINSAP and a MINLINK for each of two adapters:
DEVICE=\LSP\DXMCnMOD.SYS N 400000000001,,,3,2,400000000002,,,4,4
In this example, the primary adapter has a MINSAP of 3 and a MINLINK of 2,
and the alternate adapter has a MINSAP of 4 and a MINLINK of 4. Commas
mark the places of the omitted parameters; the N parameter is present.
- To specify shared RAM locations for two adapters:
DEVICE=\LSP\DXMCnMOD.SYS ,C400,,,D800
In this example, C400 is the shared RAM location for the primary adapter
and D800 is the shared RAM location for the alternate adapter. The default
adapter addresses for both adapters are retained.
- To specify adapter addresses and shared RAM locations for two adapters:
DEVICE=\LSP\DXMCnMOD.SYS 400000000001,C400,,400000000002,D800
In this example, the defaults for both adapter addresses and both shared
RAM locations have been changed.
ΓòÉΓòÉΓòÉ 12.5. IBM PC Network Device Driver (DXMG0MOD.SYS, DXMG1MOD.SYS, and DXMG2MOD.SYS) Parameters ΓòÉΓòÉΓòÉ
In addition to adapter address and work space parameters, PC Network device
drivers have the N, MINSAP, and MINLINK parameters.
Note:
The N, MINSAP, and MINLINK parameters cannot be used with DXMG2MOD.SYS,
the device driver for the original PC Network Adapter.
ΓòÉΓòÉΓòÉ 12.5.1. The N Parameter ΓòÉΓòÉΓòÉ
This parameter enables the device driver to interpret the MINSAP and MINLINK
parameters correctly. See The N Parameter for a description.
ΓòÉΓòÉΓòÉ 12.5.2. IBM PC Network Adapter Addresses ΓòÉΓòÉΓòÉ
For adapter address information, see IBM Token-Ring Network Adapter Addresses.
ΓòÉΓòÉΓòÉ 12.5.3. Work Space ΓòÉΓòÉΓòÉ
The PC Network device drivers allow a maximum internal work space of 64KB per
adapter, all of which may or may not be needed. The amount of work space
depends on the requirements of the application program. The default work space
is 8KB for each adapter in your computer.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 8. PC Network Adapter Work Space Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé REQUIREMENTS FOR ONE ADAPTER Γöé WORK SPACE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Default Γöé 8KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Fewer than 16 sessions Γöé 8KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 16 to 32 sessions Γöé 12KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 24 to 32 sessions Γöé 16KB Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Notes:
1. Use this table as a guideline. As the number of SAPs, link stations, or
sessions increases, you may have to increase the work space. For more
information about situations that require changing the work space
parameter, see Heavy Network Load Using PC Network Adapters.
2. To define the work space parameter, see Editing Parameters for the PC
Network Device Drivers.
ΓòÉΓòÉΓòÉ 12.5.4. MINSAP ΓòÉΓòÉΓòÉ
This parameter defines the minimum number of SAPs. See MINSAP for a
description.
ΓòÉΓòÉΓòÉ 12.5.5. MINLINK ΓòÉΓòÉΓòÉ
This parameter defines the minimum number of link stations. See MINLINK for a
description.
ΓòÉΓòÉΓòÉ 12.5.6. Editing Parameters for the PC Network Device Drivers ΓòÉΓòÉΓòÉ
The following parameters are valid for DXMG0MOD.SYS and DXMG1MOD.SYS. Only the
address and workspace parameters, not the N, MINSAP, or MINLINK parameters, are
valid for DXMG2MOD.SYS: [In CONFIG.SYS, the list of parameters must be
continued on one line]
DEVICE=\LSP\DXMGnMOD.SYS N addr0,wrk0,minsap0,minlink0,
addr1,wrk1,minsap1,minlink1
Note:
See Global and Positional Parameters. This section describes global and
positional parameters and explains how to enter them. N is a global
parameter.
N Is required when MINSAP or MINLINK is present.
addr0 Is replaced with the locally administered address for the primary or
only PC Network Adapter.
wrk0 Is replaced with the work space for the primary or only PC Network
Adapter.
minsap0 Sets the minimum number of SAPs that the adapter will support when
opened. The N parameter must be present when this parameter is given
a value.
minlink0 Sets the minimum number of link stations that the adapter will
support when opened. The N parameter must be present when this
parameter is given a value.
addr1 Is replaced with the locally administered address for the alternate
adapter.
wrk1 Is replaced with the work space for the alternate adapter.
minsap1 Sets the minimum number of SAPs that the alternate adapter will
support when opened. The N parameter must be present when this
parameter is given a value.
minlink1 Sets the minimum number of link stations that the alternate adapter
will support when opened. The N parameter must be present when this
parameter is given a value.
If two PC Network Adapters are installed in the same computer, enter the
parameters for the primary adapter first and the parameters for the alternate
adapter second.
To enter the adapter address, see the address examples in Editing Parameters
for the IBM Token-Ring Network Device Drivers.
You must enter the workspace parameters as one or two decimal digits. This
value is interpreted as the number of kilobytes of work space to reserve. If
no value is specified, or if the value is less than the default, the default
value will be used. A value greater than 64 will be reduced to 64. To specify
a work space different from the default, add the parameter as in the following
example:
DEVICE=\LSP\DXMGnMOD.SYS ,20
In this example, 20 is the new size of the work space for the primary or only
PC Network Adapter (20KB). All other defaults are retained. Note the comma
before the work space size. This comma indicates that a parameter (the primary
adapter address) has been omitted.
In this example, work space has been increased and MINSAP and MINLINK are
specified for the primary adapter:
DEVICE=\LSP\DXMGnMOD.SYS N ,20,2,4
Note:
The N, MINSAP, and MINLINK parameters cannot be used with DXMG2MOD.SYS.
ΓòÉΓòÉΓòÉ 12.6. Parameters for the IEEE 802.2 Protocol Driver for ΓòÉΓòÉΓòÉ
NDIS Adapters (DXME0MOD.SYS)
You can enter seven parameters for this driver (DXME0MOD.SYS): the N parameter,
the X parameter, adapter address, work space size, transmit/swap, MINSAP, and
MINLINK.
ΓòÉΓòÉΓòÉ 12.6.1. The N Parameter ΓòÉΓòÉΓòÉ
This parameter enables the device driver to interpret the MINSAP and MINLINK
parameters correctly. See The N Parameter for a description.
ΓòÉΓòÉΓòÉ 12.6.2. The X Parameter ΓòÉΓòÉΓòÉ
LAN Support Program Version 1.3 uses one value to identify Ethernet adapters to
application programs. Version 1.2 used a different value. Some application
programs, such as IBM Application System/400 PC Support, use the value from
Version 1.2. For these programs, enter the X parameter when you use an Ethernet
adapter.
ΓòÉΓòÉΓòÉ 12.6.3. Adapter Address ΓòÉΓòÉΓòÉ
For adapter address information, see IBM Token-Ring Network Adapter Addresses.
ΓòÉΓòÉΓòÉ 12.6.4. Work Space ΓòÉΓòÉΓòÉ
For work space information, see Work Space. Refer to Increasing Work Space for
NDIS Adapters for a description of situations that may require you to change
this parameter.
ΓòÉΓòÉΓòÉ 12.6.5. Transmit/Swap ΓòÉΓòÉΓòÉ
The transmit function of this parameter determines the frame format. Frames can
be transmitted on the Ethernet network in one of two formats: Ethernet DIX
Version 2.0 or IEEE 802.3. The default is to transmit IEEE 802.3 frames.
The swap function determines whether addresses are transmitted with or without
their bits swapped. Addresses may be transmitted with their bits swapped on a
byte basis. For example, if the value X'10007BC00402' is an address and
address bit swapping is on, the address will be transmitted as X'0800DE032040'.
The default is to transmit with the address bits swapped. Changing the
parameter so that the address bits are not swapped is not recommended.
The XMIT_SWAP parameter must be entered as a single decimal digit; each digit
defines one of the following user options:
0 Transmit IEEE 802.3 frame and swap address bits (default)
1 Transmit Ethernet DIX Version 2.0 frame and swap address bits
2 Transmit IEEE 802.3 frame and do not swap address bits
3 Transmit Ethernet DIX Version 2.0 frame and do not swap address bits.
If you are using IEEE 802.5 frames on an IBM FDDI Network or an IBM Token-Ring
Network, the value of this parameter does not affect the network. However, it
must be a valid number (0, 1, 2, or 3).
ΓòÉΓòÉΓòÉ 12.6.6. MINSAP ΓòÉΓòÉΓòÉ
This parameter defines the minimum number of SAPs. See MINSAP for a
description.
ΓòÉΓòÉΓòÉ 12.6.7. MINLINK ΓòÉΓòÉΓòÉ
This parameter defines the minimum number of link stations. See MINLINK for a
description.
ΓòÉΓòÉΓòÉ 12.6.8. Editing Parameters for the IEEE 802.2 Protocol Driver for NDIS Adapters (DXME0MOD.SYS) ΓòÉΓòÉΓòÉ
The following parameters are valid for DXME0MOD.SYS: [ In CONFIG.SYS, the list
of parameters must be continued on one line. ]
DEVICE=\LSP\DXME0MOD.SYS N X addr0,wrk0,xmit_swap0,minsap0,minlink0,
addr1,wrk1,xmit_swap1,minsap1,minlink1
Note:
See Global and Positional Parameters. This section describes global and
positional parameters and explains how to enter them. N and X are global
parameters.
N Is required when MINSAP or MINLINK is present.
X Enables application programs that use the value for Ethernet
adapters used in LAN Support Program Version 1.2 to communicate
with LAN Support Program Version 1.3. See The X Parameter for
more information.
addr0 Is replaced with the locally administered address for the primary
or only NDIS adapter.
wrk0 Is replaced with the work space for the primary or only NDIS
adapter.
xmit_swap0 Is replaced with the transmit/swap parameter for the primary or
only NDIS adapter.
minsap0 Sets the minimum number of SAPs that the adapter will support when
opened. The N parameter must be present when this parameter is
given a value.
minlink0 Sets the minimum number of link stations that the adapter will
support when opened. The N parameter must be present when this
parameter is given a value.
addr1 Is replaced with the locally administered address for the
alternate adapter.
wrk1 Is replaced with the work space for the alternate adapter.
xmit_swap1 Is replaced with the transmit/swap parameter for the alternate
adapter.
minsap1 Sets the minimum number of SAPs that the alternate adapter will
support when opened. The N parameter must be present when this
parameter is given a value.
minlink1 Sets the minimum number of link stations that the alternate
adapter will support when opened. The N parameter must be present
when this parameter is given a value.
If two NDIS adapters are installed in the same computer, the parameters for the
primary adapter are entered first, followed by the parameters for the alternate
adapter. When editing a parameter list, observe these rules:
o Use a blank to separate the parameter list from DEVICE=\LSP\DXME0MOD.SYS.
o Use a comma to separate one parameter from another.
o Indicate an omitted parameter with a comma.
o If one or more parameters are omitted from the end of the list, the commas
are unnecessary.
To specify the adapter address, see the address examples in Editing Parameters
for the IBM Token-Ring Network Device Drivers.
To specify the work space, see the work space example in Editing Parameters for
the PC Network Device Drivers.
To specify a value for the transmit/swap parameter, use the values described in
Transmit/Swap. For example:
DEVICE=\LSP\DXME0MOD.SYS 400000000001,20,1
specifies an adapter address of 400000000001, 20KB of work space, and Ethernet
DIX Version 2.0 frame format with address-bit swapping for the primary or only
NDIS adapter.
DEVICE=\LSP\DXME0MOD.SYS ,20,,,,1
The parameter 20 specifies 20KB of work space for the primary NDIS adapter, and
the parameter 1 specifies Ethernet DIX Version 2.0 format with address-bit
swapping for the alternate adapter.
To specify the LAN Support Program Version 1.2 Ethernet adapter type, you would
use a statement similar to this one:
DEVICE=\LSP\DXME0MOD.SYS X 400000000001,20
To increase the work space for the primary NDIS adapter to 20KB, the workspace
for the alternate NDIS adapter to 10KB, and to specify MINSAP of 2 and MINLINK
of 2 for each adapter, you would use this statement:
DEVICE=\LSP\DXME0MOD.SYS N ,20,,2,2,,10,,2,2
ΓòÉΓòÉΓòÉ 12.6.9. Editing the Parameter for PROTMAN.DOS ΓòÉΓòÉΓòÉ
PROTMAN.DOS is a file required when NDIS adapters are used. It has one
parameter (the /I: parameter) that must be included when PROTOCOL.INI is
located in any directory other than \LANMAN.
ΓòÉΓòÉΓòÉ 12.7. NetBIOS Device Driver Parameters (Parameters for DXMT0MOD.SYS) ΓòÉΓòÉΓòÉ
If you require both NetBIOS and IEEE 802.2 interface support, use DXMT0MOD.SYS.
However, if you do not require IEEE 802.2 interface support and you are using
an NDIS adapter, performance may be enhanced if you use DXMJ0MOD.SYS. Neither
DXME0MOD.SYS nor DXMT0MOD.SYS is used with DXMJ0MOD.SYS. For information about
DXMJ0MOD.SYS parameters, see Parameters for the NETBIOS Protocol Driver for
NDIS Adapters.
The NetBIOS interface has many optional parameters available to customize the
driver for certain network application programs. Only one of the parameters,
the Enable parameter, is position dependent. If used, it must be entered as the
first parameter. For example:
DEVICE=\LSP\DXMT0MOD.SYS ENABLE
Note:
ENABLE may be abbreviated as E.
The processing of a NetBIOS command occurs when the X'5C' interrupt is issued.
Because interrupts are disabled for a short time, some loss of data may occur
in an asynchronous adapter if it is used simultaneously with a LAN adapter.
If the computer contains an asynchronous adapter that is used simultaneously
with a LAN adapter, use the Enable parameter. In this case, the NetBIOS command
will be processed at a later time, during a LAN adapter appendage interrupt.
Because interrupts are enabled, data is not lost. But because of the short
delay, there may be some loss in performance.
ΓòÉΓòÉΓòÉ 12.7.1. Summary of the Keyword Values for the NetBIOS Old Parameters ΓòÉΓòÉΓòÉ
The keyword parameter, unlike the positional parameter, does not rely on its
position in a list. Instead, the name of the parameter, called the keyword, is
set equal to its value. The keyword and its value can be placed at any
position in the list of parameters.
The new releases of the NetBIOS program use keyword parameters. However, the
old releases used positional parameters. If you are using a previous NetBIOS
program release, a migration selection allows you to select the positional
parameters that were used in the past. To do this, see the following example:
DEVICE=\LSP\DXMT0MOD.SYS OLD.PARMS.0=x y z OLD.PARMS.1=a b c
OLD.PARMS.0 is the keyword indicating that the old form of positional
parameters will be used for the primary or only adapter. The x y z indicates
the old parameters:
x PC RAM used as internal work space. The default is 9 (9KB). For large
systems, this value may have to be increased (the maximum value is 64
[64KB]).
y Extra SAPs. This indicates the number of extra (non-NetBIOS) SAPs that
will be defined when NetBIOS opens the adapter. The default value is 0
and the maximum value is 99.
z Extra link stations. This indicates the number of extra (non-NetBIOS)
link stations that will be defined when NetBIOS opens the adapter. The
default value is 0 and the maximum value is 99.
OLD.PARMS.1 is the keyword for positional parameters for the alternate adapter.
The a b c indicates the positional parameters.
Note:
If one of two adapters uses the old parameters, the other adapter must
also use the old parameters.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 9. NetBIOS (Default = OLD.PARMS) Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LOAD PARAMETERS Γöé VALID VALUES Γöé DEFAULTS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Work area Γöé 0 to 64 Γöé 9 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé EXTRA.SAPs Γöé 0 to 99(1) Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé EXTRA.STATIONS Γöé 0 to 99(1) Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé (1) If this value is too large, the adapter will fail to open. The maximum Γöé
Γöé value allowed here typically exceeds current adapter maximum values. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Notes:
1. If y is specified, x must be specified. If z is specified, both x and y
must be specified. The same is true for a, b, and c. Only these
parameters can be changed by an entry on the CONFIG.SYS command line.
2. Listed in the following table are the old parameters whose default
values differ from those listed NetBIOS Device Driver New Keyword
Values. Use the NetBIOS RESET command to change the values for STATIONS,
SESSIONS, and COMMANDS.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 10. NetBIOS Old Parameters Defaults Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETERS Γöé DEFAULTS Γöé VALID VALUES Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé STATIONS Γöé 6 Γöé 1 to 32 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SESSIONS Γöé 6 Γöé 1 to 32 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé COMMANDS Γöé 12 Γöé 1 to 32 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OPEN.ON.LOAD Γöé NO Γöé Cannot be changed Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 12.7.2. Summary of the Keyword Values for the NetBIOS New Parameters ΓòÉΓòÉΓòÉ
NetBIOS Device Driver New Keyword Values shows all the new NetBIOS keywords and
their default values. They are not position dependent. They need to be
separated by a blank as shown in the examples that follow. They must also be on
the same line.
Keywords may be defined for either one or two adapters; if there are two
adapters, the keywords are separated by a slash (/). Furthermore, any undefined
keywords take the default value. If the / is used, any undefined keywords
before it apply to the primary adapter and any undefined keywords to the right
of it apply to the alternate adapter.
One or more keywords can be specified for each adapter:
o For the primary or only adapter, or to specify keywords for the primary
adapter and use all keyword defaults for the alternate adapter, see the
following example:
DEVICE=\LSP\DXMT0MOD.SYS E ST=64 S=64 N=32 C=32
Some of the keyword values (for example, O) are defaults for the primary
adapter as well.
In this instance, 64 sessions are defined, and the Enable parameter is
activated. Remember that Enable is the parameter that activates the Enable
function, and that it is the only position-dependent NetBIOS new parameter.
If used, it must precede any other NetBIOS parameters listed. (You can
represent ENABLE with the abbreviation E.)
o To specify keywords for the alternate adapter and use all keyword defaults
for the primary adapter, if it exists (note the /), see the following
example:
DEVICE=\LSP\DXMT0MOD.SYS / ST=16 S=32 C=32
o To specify keywords for both the primary and alternate adapters (note the /),
see the following example:
DEVICE=\LSP\DXMT0MOD.SYS ST=16 S=32 C=16 / ST=8 S=8
o To specify keywords for the primary adapter and define the alternate adapter
the same way (note the / =), see the following example:
DEVICE=\LSP\DXMT0MOD.SYS ST=16 S=32 C=16 / =
Notes:
1. These parameters are used to customize the system, if required.
2. These parameters cannot be used if OLD.PARMS.0, OLD.PARMS.1, or both are
used.
3. The keywords STATIONS, SESSIONS, and COMMANDS provide maximum values
that can be used; if a program issues a RESET command, and the RESET
indicates a value larger than indicated by these keywords, the keyword
value will be used.
4. If any of these keywords are used, all other keywords will assume the
default values indicated in NetBIOS Device Driver New Keyword Values.
5. If an NDIS adapter is being used and any new parameter is specified, O=N
must also be specified. Without O=N, NetBIOS will try to open the
adapter at load time, and will fail because NETBIND, the COM file that
enables the adapter to open, is not executed until AUTOEXEC.BAT is
executed.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 11. NetBIOS Device Driver New Keyword Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé KEYWORD Γöé ABV. Γöé VALID VALUES Γöé MINIMUM Γöé DEFAULΓöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé STATIONS Γöé ST Γöé 0 to 254 (1) Γöé 1 Γöé 16 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SESSIONS Γöé S Γöé 0 to 254 Γöé 1 Γöé 16 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé COMMANDS Γöé C Γöé 0 to 255 Γöé 1 Γöé 12 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NAMES Γöé N Γöé 0 to 254 Γöé 2 Γöé 17 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OPEN.ON.LOAD Γöé O Γöé Y (Yes) / N (No) Γöé - Γöé Yes Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DATAGRAM.MAX Γöé DG Γöé Y (Yes) / N (No) Γöé - Γöé No Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CLOSE.ON.RESET Γöé CR Γöé Y (Yes) / N (No) Γöé - Γöé No Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CALL.FAR Γöé CF Γöé Y (Yes) / N (No) Γöé - Γöé No Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DHB.SIZE Γöé DS Γöé 0, 200 to 17960 Γöé 200 Γöé (2) Γöé
Γöé Γöé Γöé (1) Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DHB.NUMBER Γöé DN Γöé 0 to 9 (1) Γöé - Γöé (2) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RECEIVE.BUFFER.SIZE Γöé R Γöé 0 to 9999 (1) Γöé (3) Γöé (2) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TRANSMIT.TIMEOUT Γöé TT Γöé 0 to 20 Γöé 0 Γöé 1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TRANSMIT.COUNT Γöé TC Γöé 0 to 10 Γöé 0 Γöé 6 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DLC.MAXOUT Γöé MO Γöé 0 to 9 Γöé 0 Γöé 2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DLC.MAXIN Γöé MI Γöé 0 to 9 Γöé 0 Γöé 1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RING.ACCESS Γöé RA Γöé 0 to 3 Γöé 0 Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé EXTRA.SAPS Γöé ES Γöé 0 to 99 (1) Γöé 0 Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé EXTRA.STATIONS Γöé EST Γöé 0 to 254 (1) Γöé 0 Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé REMOTE.NAME.DIRECTORY Γöé RND Γöé 0 to 255 Γöé 0 Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé REMOTE.DATAGRAM.CONTROL Γöé RDC Γöé Y (Yes) / N (No) Γöé - Γöé No Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RESET.VALUES Γöé RV Γöé Y (Yes) / N (No) Γöé - Γöé No Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ADAP.ADD.NOT.REVERSED Γöé ANR Γöé Y (Yes) / N (No) Γöé - Γöé No Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DLC.RETRY.COUNT Γöé RC Γöé 0 to 255 Γöé 0 Γöé 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DLC.T1 Γöé T1 Γöé 0 to 10 Γöé 0 Γöé 5 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DLC.T2 Γöé T2 Γöé 0 to 11 Γöé 0 Γöé 2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DLC.TI Γöé TI Γöé 0 to 10 Γöé 0 Γöé 10 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PIGGYBACKED ACKNOWLEDGMENTS Γöé PBA Γöé 0 to 5 Γöé 0 Γöé 3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTE: On this table, (1) means see note 1, (2) means see note 2, and (3) Γöé
Γöé means see note 3. The notes follow. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Notes:
1. If this value is too large, the adapter fails to open. The maximum value
allowed here typically exceeds current adapter maximum values.
2. The default value set by the NetBIOS interface device driver is based on
the number of stations. See NetBIOS Adapter Transmit and Receive Buffer
Default Sizes.
3. If a value is specified for RECEIVE.BUFFER.SIZE, the value is not
checked by the NetBIOS interface device driver. The value is checked by
the adapter upon opening. Current adapters require a minimum value of
96.
ΓòÉΓòÉΓòÉ 12.7.3. NetBIOS Device Driver Keyword Parameter Descriptions ΓòÉΓòÉΓòÉ
Each keyword has an abbreviated version, which is indicated in parentheses
following the keyword:
STATIONS= (ST=)
o Indicates the maximum number of NetBIOS interface link stations that can
be defined.
o Must be a decimal number from 0 to 254.
- The realistic maximum is affected by the size of the shared RAM on the
adapter.
- The EXTRA.STATIONS value reduces the maximum for the NetBIOS interface.
o If other than the default is used, CLOSE.ON.RESET must be set to Y (Yes).
o If omitted or 0, the default value is 16.
SESSIONS= (S=)
o Indicates the maximum number of NetBIOS interface device driver sessions
that can be defined.
o Must be a decimal number from 0 to 254.
o If omitted or 0, the default value is 16.
If the value is less than STATIONS, it will be set to the value of
STATIONS.
COMMANDS= (C=)
o Indicates the maximum number of NetBIOS interface command network control
blocks (NCB) that can be outstanding at one time.
o Must be a decimal number from 0 to 255.
o If omitted or 0, the default value is 12.
NAMES= (N=)
o Indicates the maximum number of NetBIOS interface device driver names that
can be defined, including the NAME_NUMBER_1.
o Must be a decimal number from 0 to 254.
o If omitted or 0, the default value is 17.
o If 1, the value will be set to 2.
OPEN.ON.LOAD= (O=)
o If Y (YES), the NetBIOS interface will open the adapter at load time.
Having NetBIOS open the adapter eliminates the delay caused by opening the
adapter later when an application program is loaded and the first NCB is
issued.
o Must be specified as either Y (Yes) or N (No).
o If omitted, the default is Y (Yes).
o Must be N (No) for NDIS adapters.
DATAGRAM.MAX= (DG=)
o Indicates that the maximum length datagram transmitted by the NetBIOS
interface device driver will be based on the size of the transmit buffer
or data hold buffer (DHB) of the adapter. Usually, a datagram is limited
to 512 bytes.
o Must be specified as either Y (Yes) or N (No).
o If the maximum length of a datagram is:
DHB length - 86 (the size of the transmit buffer less 86 bytes).
o If omitted or N, this function is not performed.
CLOSE.ON.RESET= (CR=)
o Indicates that the NetBIOS interface will close the adapter and reopen it
when a RESET is issued.
o Must be specified as either Y. (Yes) or N (No).
o Must be specified as Y if you want to change the number of link stations.
o If omitted or N, this function will not be performed.
CALL.FAR= (CF=)
o Prevents an application program from intercepting the X'5C' interrupt
issued by the NetBIOS device driver DXMT0MOD.SYS. If an application
program intercepts this interrupt incorrectly, LAN Support Program
processing is terminated.
o Must be specified as either Y (Yes) or N (No). The default value is N.
o Must be specified as Y. when Windows or DOS memory managers are used with
the LAN Support Program. This keyword must also be set to Y for any other
application programs that may intercept X'5C' interrupts.
For two adapters, enter this parameter on the command line once.
o If omitted or N, this function will not be performed. The default value is
N.
DHB.SIZE= (DS=)
o Indicates the size of the DHB (the transmit buffers of the adapter).
o Must be a decimal number within the range acceptable to the adapter. Note
that the minimum size allowed by the NetBIOS interface is 200. Therefore,
the value entered must be either 0 or a number from 200 to 17960.
o If omitted or 0, the value is determined by the NetBIOS interface. See
NetBIOS Adapter Transmit and Receive Buffer Default Sizes for information
about the NetBIOS default values.
DHB.NUMBER= (DN=)
o Indicates the number of DHBs allocated by the adapter.
o Must be a decimal number within the range acceptable to the adapter.
o If omitted or 0, the value is determined by the NetBIOS interface device
driver. See NetBIOS Adapter Transmit and Receive Buffer Default Sizes for
information about the NetBIOS default values.
RECEIVE.BUFFER.SIZE= (R=)
o Indicates the size of the receive buffers of the adapter. A minimum of
eight adapter buffers of the specified size will be allocated.
o Must be a decimal number within the range acceptable to the adapter.
o If omitted or 0, the value is determined by the NetBIOS interface. See
NetBIOS Adapter Transmit and Receive Buffer Default Sizes for information
about the NetBIOS default values.
TRANSMIT.TIMEOUT= (TT=)
o Indicates the time between transmission of queries (for example, CALL).
o Is indicated in 1/2-second periods.
o Must be a decimal number from 0 to 20.
o If omitted or 0, the default is 1 (1/2 second).
TRANSMIT.COUNT= (TC=)
o Indicates the number of times queries (for example, CALL) are transmitted.
o Must have a decimal value from 1 to 10. If a number from 1 to 10 is
specified, that number is the value.
o If omitted or 0, the default is 6.
DLC.MAXOUT= (MO=)
o Sets the MAXOUT value for all NetBIOS interface link stations. The MAXOUT
value indicates the number of I-frames sent before waiting for an
acknowledgment.
o The sender's MAXOUT value must always be greater than the receiver's MAXIN
value.
o Must have a decimal value from 1 to 9. If a number from 1 to 9 is
specified, that number is the value.
o If omitted or 0, the default is 2.
DLC.MAXIN= (MI=)
o Sets the MAXIN value for all NetBIOS interface link stations. The MAXIN
value indicates the number of I-frames received before sending an
acknowledgment.
o The receiver's MAXIN value must always be less than the sender's MAXOUT
value.
o Must have a decimal value from 1 to 9. If a number from 1 to 9 is
specified, that number is the value.
o If omitted or 0, the default is 1.
RING.ACCESS= (RA=)
o Indicates the ring access priority for this adapter for NetBIOS device
driver interface messages. This parameter is valid for Token-Ring adapters
only.
o Must be a decimal number from 0 to 3.
o If omitted or 0, the default is 0.
o The higher the number, the higher the priority.
EXTRA.SAPS= (ES=)
o Indicates additional SAPs requested by the NetBIOS interface when it
implicitly opens the adapter by activating the parameters specified on the
NetBIOS command line. These SAPs are not used by the NetBIOS interface.
o Must be a decimal number from 0 to 99.
o If omitted or 0, no additional SAPs are requested.
Notes:
1. If this value exceeds the adapter maximum value, the error will be
detected when the adapter fails to open.
2. If this value is less than the value of MINSAP, the value of MINSAP
will be used.
EXTRA.STATIONS= (EST=)
o Indicates additional link stations requested by the NetBIOS interface when
it implicitly opens the adapter by activating the parameters specified on
the NetBIOS command line. These link stations are not used by the NetBIOS
interface.
o Requesting extra stations reduces link stations available for the use on
the NetBIOS interface.
o Must be a decimal number from 0 to 254.
o If omitted or 0, no additional stations are requested.
Notes:
1. If this value exceeds the adapter maximum value, the error will be
detected when the adapter fails to open.
2. If this value is less than the value of MINLINK, the value of MINLINK
will be used.
REMOTE.NAME.DIRECTORY= (RND=)
o Can be coded as a number from 0 to 255.
o If omitted or 0, the REMOTE.NAME.DIRECTORY (RND) function is not
implemented. All CALLS, STATUS QUERIES, and SEND DATAGRAMS will operate
as in previous levels of NetBIOS and broadcast messages to all NetBIOS
nodes.
o If a nonzero value is coded, the RND function is implemented with the
value indicating the number of remote names that can be saved by the local
node. Note that 4 is the minimum number of name entries; if coded as 1,
2, or 3, the value of 4 is used. When RND is implemented (after the local
station has located a remote name), the remote node address is saved and
subsequent messages to that name will be to a specific node rather than a
broadcast to all nodes. This is true for CALLS, STATUS QUERIES, and SEND
DATAGRAMS (see next keyword REMOTE.DATAGRAM.CONTROL).
Important: Using the RND function can significantly improve performance in
situations where large numbers of DATAGRAMS, CALLS, and
REMOTE_ADAPTER_STATUS commands are used.
Warning:
When the RND function is being used, a duplicate network name will
not be detected by a CALL function unless it is the first time
that the remote (CALL) name has been used.
REMOTE.DATAGRAM.CONTROL= (RDC=)
o Is meaningless if REMOTE.NAME.DIRECTORY is omitted or coded as 0.
o If omitted or coded as N (No), SEND DATAGRAMS will not use the RND
function.
o If coded as Y (Yes), SEND DATAGRAMS will also use the RND function for
sending to remote nodes. Note that if a bridge in the transmission path
drops out, datagrams give no indication that the path is no longer valid.
Therefore, if this function is used, you may want to update the RND if you
become aware that the remote node is not receiving datagrams. You can
update the RND by having the application program issue a FIND_NAME command
with a receive buffer length of 0. This function allows an application to
update the RND without having to execute either a CALL or REMOTE ADAPTER
STATUS.
RESET.VALUES= (RV=)
o If omitted or coded as N (No), RESET works as it does in earlier releases
of NetBIOS.
o If coded as Y (Yes), when a RESET is issued:
- If the number of sessions is coded as 0 in the RESET, the default will
be the value defined by the keyword SESSIONS= rather than the normal
default value of 6.
- If the number of commands is coded as 0 in the RESET, the default will
be the value defined by the keyword COMMANDS= rather than the normal
default value of 12.
ADAP.ADDR.NOT.REVERSED= (ANR=)
o If omitted or coded as N (No), the universally administered address of the
adapter as used in the ADAPTER_STATUS command and in NAME_NUMBER_1 will be
byte-reversed (that is, if the value is X'010203040506', it will be saved
as X'060504030201').
o If coded as Y (Yes), the universally administered address of the adapter
as used in the ADAPTER_STATUS command and in NAME_NUMBER_1 will not be
byte-reversed (that is, if the value is X'010203040506', it will be saved
as X'010203040506').
DLC.RETRY.COUNT= (RC=)
o Determines the number of retry attempts to be made by the logical link
control (LLC) code.
o Must be a decimal value from 1 to 255. If a number from 1 to 255 is
specified, that number is the value.
o If omitted or 0, the default value of 8 is used. The default value is
equal to 9 seconds.
DLC.T1= (T1=)
o Determines the value of the T1 response timer in the LLC code. The T1
timer sets the maximum time to wait for an acknowledgment before
retransmitting a link-level frame.
o Must be a decimal value from 0 to 10. See DLC Timer Values for
correlations between parameters and seconds.
o If omitted or 0, the default value of 5 is used.
DLC.T2= (T2=)
o Determines the value of the T2 acknowledgment timer in the LLC code. The
T2 timer sets the maximum delay before sending an acknowledgment.
o Must be a decimal value from 0 to 11. See DLC Timer Values for
correlations between parameters and seconds.
o If 11, the T2 timer function is not implemented.
o If omitted or 0, the default value of 2 is used.
DLC.TI= (TI=)
o Determines the value of the TI inactivity timer in the LLC code. The TI
timer sets how long to wait before generating a data link control (DLC)
status if there is no link station traffic.
o Must be a decimal value from 0 to 10. If a number is specified, that
number is the value. See DLC Timer Values for correlations between
parameters and seconds.
o If omitted or 0, the default value of 10 is used.
PIGGYBACKED.ACKNOWLEDGMENTS= (PBA=)
o Specifies whether the NetBIOS protocol sends and receives acknowledgments
piggybacked with incoming data. If PBA is enabled, the acknowledgment of
the frame received is sent as a piggyback on the next frame transmitted.
If PBA is disabled, a separate acknowledgment frame is sent. Network
performance may be improved when PBA is enabled.
o Must be a decimal value from 0 to 5.
o If changed to 0, the workstation neither sends nor requests piggybacked
acknowledgments. If the workstation is used in a low traffic environment,
setting PBA=0 is recommended.
o If omitted, the default value of 3 is used.
o If the default parameter is not changed, the workstation sends and
requests piggybacked acknowledgments.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 12. DLC Timer Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DLC.T1 Γöé DLC.T2 Γöé DLC.TI Γöé
Γöé (RESPONSE) Γöé (ACKNOWLEDGMENT) Γöé (INACTIVITY) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Parm Γöé Seconds Γöé Parm Γöé Seconds Γöé Parm Γöé Seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T1=1 Γöé 0.2-0.4 Γöé T2=1 Γöé 0.04-0.08 Γöé TI=1 Γöé 1-2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T1=2 Γöé 0.4-0.6 Γöé T2=2(1) Γöé 0.08-0.12(1) Γöé TI=2 Γöé 2-3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T1=3 Γöé 0.6-0.8 Γöé T2=3 Γöé 0.12-0.16 Γöé TI=3 Γöé 3-4 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T1=4 Γöé 0.8-1.0 Γöé T2=4 Γöé 0.16-0.20 Γöé TI=4 Γöé 4-5 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T1=5(1) Γöé 1.0-1.2(1) Γöé T2=5 Γöé 0.20-0.24 Γöé TI=5 Γöé 5-6 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T1=6 Γöé 1-2 Γöé T2=6 Γöé 0.4-0.8 Γöé TI=6 Γöé 5-10 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T1=7 Γöé 2-3 Γöé T2=7 Γöé 0.8-1.2 Γöé TI=7 Γöé 10-15 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T1=8 Γöé 3-4 Γöé T2=8 Γöé 1.2-1.6 Γöé TI=8 Γöé 15-20 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T1=9 Γöé 4-5 Γöé T2=9 Γöé 1.6-2.0 Γöé TI=9 Γöé 20-25 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T1=10 Γöé 5-6 Γöé T2=10 Γöé 2.0-2.4 Γöé TI=10(1)Γöé 25-30(1) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé Γöé T2=11 Γöé Disabled Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé (1) Default value Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 12.8. NetBIOS Adapter Transmit and Receive Buffer Default Sizes ΓòÉΓòÉΓòÉ
When the adapter is opened by NetBIOS, transmit and receive buffer sizes of the
adapter are determined by NetBIOS, unless specifically overridden. The adapter
type and the number of link stations are used to determine these values, as
shown in the following tables.
Note:
The Data Holding Buffer (DHB) = the adapter transmit buffer size. The
Number of DHBs (DHB.NUMBER) = the number of transmit buffers.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 13. Token-Ring Network Adapter with 8KB of Shared RAM Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMBER OF LINK Γöé NUMBER OF Γöé TRANSMIT BUFFERS Γöé RECEIVE BUFFERS Γöé
Γöé STATIONS Γöé TRANSMIT BUFFERS Γöé IN BYTES Γöé IN BYTES Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1 to 6 Γöé 2 Γöé 1048 Γöé 280 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 7 to 12 Γöé 1 Γöé 1048 Γöé 192 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 13 to 18 Γöé 1 Γöé 600 Γöé 144 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 19 to 24 Γöé 1 Γöé 600 Γöé 112 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé More than 24 Γöé 1 Γöé 600 Γöé 96 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 14. Token-Ring Network Adapter with More Than 16KB and Less Than 64KB Γöé
Γöé of Shared RAM. These values also apply to the IBM Token-Ring Γöé
Γöé Network Adapter II. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMBER OF LINK Γöé NUMBER OF Γöé TRANSMIT BUFFERS Γöé RECEIVE BUFFERS Γöé
Γöé STATIONS Γöé TRANSMIT BUFFERS Γöé IN BYTES Γöé IN BYTES Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1 to 32 Γöé 2 Γöé 4192 Γöé 280 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 33 to 48 Γöé 2 Γöé 4192 Γöé 280 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 49 to 64 Γöé 1 Γöé 4192 Γöé 280 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé More than 64 Γöé 2 Γöé 2040 Γöé 280 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 15. Token-Ring Network Adapter with 64KB of Shared RAM Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMBER OF LINK Γöé NUMBER OF Γöé TRANSMIT BUFFERS Γöé RECEIVE BUFFERS Γöé
Γöé STATIONS Γöé TRANSMIT BUFFERS Γöé IN BYTES Γöé IN BYTES Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1 to 32 Γöé 2 Γöé 4192 Γöé 280 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 33 to 48 Γöé 2 Γöé 4192 Γöé 280 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 49 to 64 Γöé 2 Γöé 4192 Γöé 280 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé More than 64 Γöé 2 Γöé 2040 Γöé 280 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 16. PC Network Adapter Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMBER OF LINK Γöé TRANSMIT BUFFERS Γöé RECEIVE BUFFERS Γöé
Γöé STATIONS Γöé IN BYTES Γöé IN BYTES Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1 to 64 Γöé 2048 Γöé 280 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé More than 64 Γöé 2048 Γöé 144 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 17. Ethernet Adapter Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMBER OF LINK Γöé TRANSMIT BUFFERS Γöé RECEIVE BUFFERS Γöé
Γöé STATIONS Γöé IN BYTES Γöé IN BYTES Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1 to 64 Γöé 1496 Γöé 280 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé More than 64 Γöé 1496 Γöé 208 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 18. IBM FDDI Adapter Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMBER OF LINK Γöé TRANSMIT BUFFERS Γöé RECEIVE BUFFERS Γöé
Γöé STATIONS Γöé IN BYTES Γöé IN BYTES Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé any number Γöé 4464 Γöé 584 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 12.9. NetBIOS Determination of Session Data Transmit Frame ΓòÉΓòÉΓòÉ
Size
When a session is established between two NetBIOS nodes, the length of the
largest data frame sent between the two sessions is determined by three
factors:
o The size of the sender's transmit buffer
o The amount of receive-buffer space in the receiver
o The maximum frame that can pass any bridge in the path
On each side (node) the receive-buffer space calculation is made in the
following way:
o The number of receive buffers is calculated.
o One-half of the number of receive buffers is multiplied by the data size of
one buffer. This determines the maximum size frame that can be transmitted
to the session. The purpose of this is to ensure that one adapter can hold
two maximum-size received frames.
Notes:
1. Ethernet frames cannot exceed 1514 bytes.
2. FDDI frames cannot exceed 4491 bytes.
ΓòÉΓòÉΓòÉ 12.10. Parameters for the NETBIOS Protocol Driver for NDIS Adapters ΓòÉΓòÉΓòÉ
(DXMJ0MOD.SYS)
There are many parameters available to customize the NetBIOS protocol driver
for NDIS MAC drivers to run network application programs.
ΓòÉΓòÉΓòÉ 12.10.1. Network Adapter Address Configuration ΓòÉΓòÉΓòÉ
To specify a locally administered address for an NDIS MAC driver that is bound
to DXMJ0MOD.SYS, the address must be configured in the MAC section of the
PROTOCOL.INI file. This address must consist of 12 hexadecimal digits.
Following are the NDIS MAC driver names and the keywords you should add to the
MAC section of the PROTOCOL.INI file to configure the locally administered
address.
NDIS MAC DriverName Keyword
IBMTOK.DOS NETADDRESS
IBM16TR.DOS NETADDRESS
IBMXLN.DOS NETADDRESS
ELNKII.DOS NETADDRESS
ELNKMC.DOS NETADDRESS
To enter the NETADDRESS parameter in PROTOCOL.INI, use a statement in
PROTOCOL.INI that resembles the following example. (This example is for
IBMTOK.DOS with a NETADDRESS value of 400000000001.)
[IBMTOK_MOD]
DriverName = IBMTOK$
NETADDRESS = 400000000001
The IBM Ethernet NDIS MAC drivers and the SMC NDIS MAC drivers do not support
configuration of the locally administered address. These NDIS MAC drivers are
MACETH.DOS, MACETH2.DOS, SMCMAC.DOS, and SMCMAC2.DOS. If you are using one of
these drivers and require the locally administered address, configure the
workstation to use DXME0MOD.SYS and DXMT0MOD.SYS instead of DXMJ0MOD.SYS.
ΓòÉΓòÉΓòÉ 12.10.2. Editing Parameters for the NETBIOS Protocol Driver for NDIS Adapters (DXMJ0MOD.SYS) ΓòÉΓòÉΓòÉ
If you need to change the values, edit PROTOCOL.INI. Parameter values placed
in PROTOCOL.INI override the default values.
The parameters in PROTOCOL.INI are in the form Keyword = Value. Each parameter
must be on a separate line in the [DXMJ0MOD_MOD] section. The parameters can
be in any order.
The following example shows the [DXMJ0MOD_MOD] section of the PROTOCOL.INI
found on the installation diskette:
[DXMJ0MOD_MOD]
DriverName = NETBEUI$
Bindings =
CHAINX5C = 1
To edit this file, add the keyword and its value on a separate line. Each line
should come after Bindings = . If PROTOCOL.INI is set up to bind an adapter
using MACETH.DOS, and if a value of 18 is added for SESSIONS, the
[DXMJ0MOD_MOD] section of PROTOCOL.INI looks like this:
[DXMJ0MOD_MOD]
DriverName = NETBEUI$
Bindings = MACETH_MOD
SESSIONS = 18
CHAINX5C = 1
ΓòÉΓòÉΓòÉ 12.10.3. Summary of the Keyword Values for the NETBIOS Protocol Driver for NDIS MAC Drivers ΓòÉΓòÉΓòÉ
NetBIOS Protocol Driver for NDIS MAC Drivers Keyword Values shows the keywords
and their default values for the NetBIOS protocol driver for NDIS MAC drivers.
For information about editing the parameters in PROTOCOL.INI, see Editing
Parameters for the NETBIOS Protocol Driver for NDIS Adapters (DXMJ0MOD.SYS).
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 19. NetBIOS Protocol Driver for NDIS MAC Drivers Keyword Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé KEYWORD Γöé VALID Γöé MINIMUM Γöé DEFAULT Γöé
Γöé Γöé VALUES Γöé VALUE Γöé VALUE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ETHERAND_TYPE Γöé I (IEEE Γöé - Γöé I (IEEE Γöé
Γöé Γöé 802.3) / Γöé Γöé 802.3) Γöé
Γöé Γöé D (DIX Γöé Γöé Γöé
Γöé Γöé 2.0) Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé USEADDRREV Γöé Y (Yes) / Γöé - Γöé Yes Γöé
Γöé Γöé N (No) Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SESSIONS Γöé 1 to 254 Γöé 1 Γöé 16 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NCBS Γöé 1 to 255 Γöé 1 Γöé 15 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NAMES Γöé 2 to 254 Γöé 2 Γöé 21 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé USEMAXDATAGRAM Γöé Y (Yes) / Γöé - Γöé No Γöé
Γöé Γöé N (No) Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ADAPTRATE Γöé 0 to Γöé 0 Γöé 1000 Γöé
Γöé Γöé 65535 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé WINDOWERRORS Γöé 0 to 10 Γöé 0 Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé STACKSIZE Γöé 512 to Γöé 512 Γöé 2048 Γöé
Γöé Γöé 4096 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TI Γöé 1000 to Γöé 1000 Γöé 30000 Γöé
Γöé Γöé 65535 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T1 Γöé 50 to Γöé 50 Γöé 1000 Γöé
Γöé Γöé 65535 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé T2 Γöé 50 to Γöé 50 Γöé 200 Γöé
Γöé Γöé 65535 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXIN Γöé 1 to 127 Γöé 1 Γöé 1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXOUT Γöé 1 to 127 Γöé 1 Γöé 1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NETBIOSTIMEOUT Γöé 500 to Γöé 500 Γöé 500 Γöé
Γöé Γöé 10000 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NETBIOSRETRIES Γöé 1 to 50 Γöé 1 Γöé 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NAMECACHE Γöé 0 to 255 Γöé 0 Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PIGGYBACKACKS Γöé 0/1 Γöé - Γöé 1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LOOPPACKETS Γöé 1 to 1000 Γöé 1 Γöé 1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DATAGRAMPACKETS Γöé 2 to 1000 Γöé 2 Γöé 2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PACKETS Γöé 1 to 1000 Γöé 1 Γöé 50 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PIPELINE Γöé 1 to 200 Γöé 1 Γöé 20 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXDATARCV Γöé 512 to Γöé 512 Γöé 4168 Γöé
Γöé Γöé 16384 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXTRANSMITS Γöé 1 to Γöé 1 Γöé 6 Γöé
Γöé Γöé 10000 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MINTRANSMITS Γöé 0 to 9999 Γöé 0 Γöé 2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DLCRETRIES Γöé 1 to Γöé 1 Γöé 8 Γöé
Γöé Γöé 65535 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LANABASE Γöé 0 to 254 Γöé 0 Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CHAINX5C Γöé 0/1 Γöé - Γöé 0 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 12.10.4. Keyword Parameter Descriptions for the NETBIOS Protocol Driver for NDIS Adapters ΓòÉΓòÉΓòÉ
ETHERAND_TYPE
o Specifies the default protocol conventions to use when the NetBIOS
protocol is bound to an Ethernet network adapter driver that supports both
IEEE 802.3 and DIX 2.0 conventions.
o Must be specified as either I (IEEE 802.3) or D (DIX 2.0).
o If omitted, the default is I (IEEE 802.3).
USEADDRREV
o Specifies whether the addresses used for the universally administered
address and NAME_NUMBER_1 are reversed.
o Must be specified as either Y (Yes) or N (No).
o If set to Y, the universally administered address used in the
ADAPTER_STATUS command and in NAME_NUMBER_1 will be byte-reversed (that
is, if the address is X'010203040506', it will be saved as
X'060504030201').
o If omitted, the default is Y.
SESSIONS
o Specifies the maximum number of NetBIOS sessions that can be open
simultaneously. The NetBIOS protocol uses a session each time it adds or
finds a NetBIOS name.
o Increase the value of this parameter if ADD.NAME or FIND.NAME requests
occur simultaneously.
o If a request fails because of a lack of sessions, the protocol returns an
interface-busy error.
o Must be a decimal number from 1 to 254.
o If omitted, the default is 16.
NCBS
o Specifies the number of network control block (NCB) descriptors to
allocate for managing NCBs submitted to the NetBIOS protocol.
o Must be a decimal number from 1 to 255.
o If omitted, the default is 15.
NAMES
o Specifies the maximum number of NetBIOS names that can be defined. One
name is reserved for defining the station address of the network adapter.
If the NetBIOS protocol is bound to multiple network adapter drivers, this
parameter specifies the maximum number of NetBIOS names in the name table
of each network adapter driver.
o Must be a decimal number from 2 to 254.
o If omitted, the default is 21.
USEMAXDATAGRAM
o Specifies whether to request the full transmit buffer size for datagrams.
o Must be specified as either Y (Yes) or N (No).
o If set to N, the length of a datagram has a maximum of 512 bytes. If this
parameter is set to Y, the full transmit buffer size is used for
datagrams.
o If omitted, the default is N.
ADAPTRATE
o Specifies the time, in milliseconds, between runs of the adaptive window
algorithm. For each link, the NetBIOS protocol uses the adaptive window
algorithm to change the Maximum Receives Outstanding and Maximum Transmits
Outstanding parameter values to match the values set on the remote
workstation.
o Must be a decimal number from 0 to 65535.
o If 0, the algorithm is turned off.
o If omitted, the default is 1000.
WINDOWERRORS
o Specifies the number of dropped packets that the adaptive window allows
before decreasing the Maximum Transmits Outstanding parameter value.
Increase the value of this parameter on a network with a heavy workload.
Decrease the value of this parameter on a network with a light workload.
o Must be a decimal number from 0 to 10.
o If omitted, the default is 0.
STACKSIZE
o Specifies the internal stack space used when called by the timer
interrupt, receive interrupt, or NCB interrupt.
o Must be a decimal number from 512 to 4096.
o If omitted, the default is 2048.
TI
o Specifies the inactivity timer value in milliseconds. The inactivity
timer determines how often the NetBIOS protocol checks an inactive link to
verify that the link is still operational. To minimize unnecessary link
checks, it is recommended that this parameter be set to the default of
30000 milliseconds.
o Must be a decimal number from 1000 to 65535.
o If omitted, the default is 30000.
o For more information, refer to the Response Timer (T1) parameter.
T1
o Specifies the transmission timer value for NetBIOS links and determines,
in milliseconds, the delay before transmitting a link-level frame again if
no acknowledgment is received. The three timer parameters must have the
following relationship: T2 < T1 <TI. The T1 parameter value should be
approximately two to five times the T2 parameter value.
o Must be a decimal number from 50 to 65535.
o If omitted, the default is 1000.
T2
o Specifies the delayed acknowledgment timer value and determines, in
milliseconds, the length of the delay before acknowledging a received
frame, when the number of frames received is less than the Maximum
Receives Outstanding parameter value.
o Must be a decimal number from 50 to 65535.
o If omitted, the default is 200.
MAXIN
o Specifies the number of NetBIOS message packets to receive before sending
an acknowledgment.
o The Maximum Receives Outstanding parameter value should be less than or
equal to the Maximum Transmits Outstanding parameter value.
o Must be a decimal number from 1 to 127.
o If omitted, the default is 1.
MAXOUT
o Specifies the number of NetBIOS message packets to send before expecting
an acknowledgment.
o The Maximum Transmits Outstanding parameter value should be greater than
the Maximum Receives Outstanding parameter value.
o Must be a decimal number from 1 to 127.
o If omitted, the default is 1.
NETBIOSTIMEOUT
o Specifies the time, in milliseconds, that the NetBIOS protocol waits
between transmission attempts.
o Must be a decimal number from 500 to 10000.
o If omitted, the default is 500.
o For more information, refer to the NetBIOSRETRIES parameter.
NETBIOSRETRIES
o Specifies the number of times the NetBIOS protocol attempts transmissions
at the NetBIOS level before assuming that the receiver is not present.
The transmission activities include name claims, session setups, and other
similar actions.
o Must be a decimal number from 1 to 50.
o If omitted, the default is 8.
o For more information, refer to the NETBIOSTIMEOUT parameter.
NAMECACHE
o Specifies the number of remote names that the workstation contacts.
o If set to 0, the remote name directory is not used. The remote name
directory reduces the number of frames broadcast to the NetBIOS functional
address on the network. The remote name directory sends a frame to a
specific node whenever possible.
o Must be a decimal number from 0 to 255.
o If omitted, the default is 0.
PIGGYBACKACKS
o Specifies whether the NetBIOS protocol sends and receives acknowledgments
piggybacked with incoming data.
o Must be either 0 or 1.
o If set to 1, the workstation sends and requests piggybacked
acknowledgments. If this parameter is set to 0, the workstation neither
sends nor requests piggybacked acknowledgments.
o If omitted, the default is 1.
LOOPPACKETS
o Specifies the number of internal loop-back packet descriptors. Loop-back
packets are used when sending I-frames or UI-frames, if the sending node
and the receiving node are the same.
o Must be a decimal number from 1 to 1000.
o If omitted, the default is 1.
DATAGRAMPACKETS
o Specifies the number of data descriptors to allocate for packeting NetBIOS
datagrams into UI-frames. Increase this parameter value when the NetBIOS
protocol sends a large number of datagrams.
o Must be a decimal number from 2 to 1000.
o If omitted, the default is 2.
PACKETS
o Specifies the number of I-frame packet descriptors that the NetBIOS
protocol can use to build DLC frames from NetBIOS messages. Increase the
value of this parameter if large frames are being sent through the
network.
o Must be a decimal number from 1 to 1000.
o If omitted, the default is 50.
PIPELINE
o Specifies the number of NetBIOS message packets that are prebuilt and
waiting in a pipeline for each session. Increase the value of this
parameter if long streams of packets are usually sent. Decrease the value
of this parameter if short, occasional groups of packets are sent.
o Must be a decimal number from 1 to 200.
o If omitted, the default is 20.
MAXDATARCV
o Specifies, in bytes, the maximum receive data size. This is the maximum
size of the user data in any frame that this node will receive on a
session. The session partner will limit the size of the user data in
frames transmitted over the session to this size or to the size available
in its transmit buffer, whichever is smaller. NetBIOS takes into account
the maximum size that bridges in the path will forward. It will never
send a frame larger than what the bridge will forward.
o Must be a decimal number from 512 to 16384.
o If omitted, the default is 4168.
MAXTRANSMITS
o Specifies the number of packets that the NetBIOS protocol can send at once
to an NDIS MAC driver. The NetBIOS protocol queues the packets internally
when this parameter value is low. The NDIS MAC driver must queue the
packets when this parameter value is high.
o Must be a decimal number from 1 to 10000.
o If omitted, the default is 6.
MINTRANSMITS
o When a network adapter driver returns an out-of-resource condition, the
NetBIOS protocol stops sending packets. This parameter specifies the
number of transmission confirmations the NetBIOS protocol must receive
from the network adapter driver before sending additional packets. This
value should be less than the Maximum Transmits parameter value.
o Must be a decimal number from 0 to 9999.
o If omitted, the default is 2.
DLCRETRIES
o Specifies the number of additional transmission attempts that the NetBIOS
protocol makes before assuming that the DLC layer of the receiving
workstation is not responding. The value of this parameter can be low on
a reliable network that does not drop many packets. Increase this
parameter value on a network that drops a large number of packets.
o Must be a decimal number from 1 to 65535.
o If omitted, the default is 8.
LANABASE
o Specifies the base number for the primary adapter. For example, if this
parameter is set to 3, the primary adapter is identified as adapter 3 and
the alternate adapter as adapter 4. If the default of 0 is used, the
primary adapter is adapter 0 and the alternate adapter is adapter 1.
o Must be a decimal number from 0 to 254.
o If omitted, the default is 0.
CHAINX5C
o If the NCB specifies an adapter for which DXMJ0MOD.SYS is not configured,
or if the control block is a CCB, DXMJ0MOD.SYS cannot complete the
command. If this parameter is set to 1, the command is passed to the
INT5C handler that was installed before DXMJ0MOD.SYS. If no handler is
found or the parameter is 0, error codes are returned.
o Must be 0 or 1.
o If omitted, the default is 0.
ΓòÉΓòÉΓòÉ 13. Worksheets ΓòÉΓòÉΓòÉ
This appendix provides:
o Installation worksheets that can help you install OS/2 LAN Server, OS/2 LAN
Requester, and DOS LAN Services
o Network setup worksheets that can help plan for network servers, requesters,
resources, applications, users, and groups
o Memory and hard-disk estimating worksheets that can help plan for sufficient
memory and hard-disk resources on each workstation on your network
ΓòÉΓòÉΓòÉ 13.1. Installation Worksheets ΓòÉΓòÉΓòÉ
The following worksheets are provided:
o The OS/2 LAN Server Installation Worksheet in topic OS/2 LAN Server
Installation Worksheet helps plan the installation and configuration of
servers. Complete one worksheet for each server.
o The OS/2 LAN Requester Installation Worksheet in topic OS/2 LAN Requester
Installation Worksheet helps plan the installation and configuration of OS/2
LAN Requester workstations. Complete one worksheet for each OS/2 requester.
o The DOS LAN Services Installation Worksheet in topic DOS LAN Services
Installation Worksheet helps you (or the workstation user) plan the
installation of DOS requesters from diskettes. Complete one worksheet for
each DOS requester.
ΓòÉΓòÉΓòÉ 13.1.1. OS/2 LAN Server Installation Worksheet ΓòÉΓòÉΓòÉ
This worksheet helps you prepare your installation options. Use it in
conjunction with the procedure described in Tailored Installation. For more
information about the fields, see also Overview of the LAN Server Product, the
LAN Server Network Administrator Reference Volume 2: Performance Tuning, and
the LAN Server Network Administrator Reference Volume 3: Network Administrator
Tasks.
Topic 1 of 4
LAN Server
Worksheet
Server Installation
Check or fill in the blanks:
Location of LAN Server to update, if applicable (C, D ...): __
Hard disk on which to install/configure (C, D ...): __
Server role:
o Domain controller: __
Reinitialize domain control database: __
o Additional server: __
o Backup domain controller: __
Components to install/configure:
Note: Required components are defaulted to install.
o Server: __ Server name (1 to 15 characters): ____________
Domain name (1 to 15 characters): ____________
Workstation is running DOS LAN Services on OS/2 virtual DOS machine
(VDM)?
Yes: __ No: __
Start server automatically when workstation is IPLed: __
Lock buffers for LAN adapters above the 16MB boundary: __
Services to start automatically when server starts:
- Server services:
Alerter: __
Replicator: __
DCDB Replicator: __
Netlogon: __
Netrun: __
Generic Alerter: __
Remote IPL: __
Uninterruptible Power Supply: __
Timesource (domain controller only): __
- Requester services:
Messenger: __
Topic 2 of 4
LAN Server
Worksheet
Server Installation
o Graphical User Interface: __
o 386 HPFS (Advanced package only): __
Cache size:
- To be determined by workstation: __
- To be specified by you: ____ KB Lazy write:
- Write during disk-idle time: __
Maximum cache age: _________ msec (default = 5000)
Minimum buffer idle-time: _________ msec (default = 500)
- Write immediately to disk: __
Maximum heap size:
- To be determined by workstation: __
- To be specified by you: ____ KB
Cache location:
- Above 16MB physical address boundary, if available: __
o Fault Tolerance for Hard Disk (Advanced package only): __
o Local Security for 386 HPFS (Advanced package only): __
o DOS Remote IPL service: __
DOS programs to be copied to hard disk:
- DOS LAN Services: __
- LAN Support Program: __
- DOS (IBM ___ or MS ___):
3.3: __ 3.3: __
5.0: __ 5.0: __
6.1: __ 6.0: __
6.3: __ 6.2: __
Remote IPL subdirectory (\RPL) location (must be same as for OS/2 Remote
IPL):
- Do not move the \RPL subdirectory: __
- Move the \RPL subdirectory: __ (new drive: _____)
Remote IPL User subdirectory (\RPLUSER) location:
- Do not move the \RPLUSER subdirectory: __
- Move the \RPLUSER subdirectory: __ (new drive: _____)
Topic 3 of 4
LAN Server
Worksheet
Server Installation
o OS/2 Remote IPL service: __
Program to be copied to hard disk:
- OS/2 LAN Requester: __
- LAN Support Program: __
Remote IPL subdirectory (\RPL) location (must be same as for DOS Remote
IPL):
- Do not move the \RPL subdirectory: __
- Move the \RPL subdirectory: __ (new drive: _______)
Remote IPL User subdirectory (\RPLUSER) location:
- Do not move the \RPLUSER subdirectory: __
- Move the \RPLUSER subdirectory: __ (new drive: _____)
o Loop Back Driver: __
o User Profile Management: __
o LAN Services Adapters: __
Adapter(s) to be used with OS/2 LAN Server; fill in logical adapter
number(s):
- __
- __
- __
- __
Adapter(s) to be used with the OS/2 or DOS Remote IPL service;
fill inlogical adapter number(s):
- __
- __
- __
- __
o Uninterruptible Power Supply Support: __ Communication port to which UPS
hardware is attached:
- COM1: __
- COM2: __
Topic 4 of 4
LAN Server
Worksheet
Server Installation
o First Failure Support Technology/2: __
- Autostart: __
Route alerts to:
NetView: __
IBM LAN Network Manager: __
- Display messages: __
- System information:
Maximum dumps (8-99): __
Dump path: _____________ Application information:
Maximum dumps (8-99): __
Dump path: _____________
Message log: _____________
- Hardware vital product data:
Workstation type: _____________
Workstation serial number: _____________
Workstation ID: _____________
o Migration Import Utility (SBCS users only): __
o Generic Alerter service: __
o LAN Services Installation/Configuration Program: __
o LAN Server Applications Development Toolkit: __
o Virtual DOS LAN API Support: __
ΓòÉΓòÉΓòÉ 13.1.2. OS/2 LAN Requester Installation Worksheet ΓòÉΓòÉΓòÉ
This worksheet helps you prepare your installation options. Use this worksheet
in conjunction with the procedure described in Tailored Installation. For more
information about the fields, see also Overview of the LAN Server Product, the
LAN Server Network Administrator Reference Volume 2: Performance Tuning, and
the LAN Server Network Administrator Reference Volume 3: Network Administrator
Tasks.
Topic 1 of 2
LAN Server Worksheet
OS/2 LAN Requester Installation
Check or fill in the blanks:
Location of OS/2 LAN Requester to update, if applicable (C, D ...): __
Hard disk on which to install/configure (C, D ...): __
Components to install/configure:
Note: Required components are defaulted to install.
o Requester: __ Requester name (1 to 15 characters): ____________
Domain name (1 to 15 characters): ____________
Start requester automatically when workstation is IPLed: __
Lock buffers for LAN adapters above the 16MB boundary: __
Requester services to start automatically when requester starts:
Messenger: __
Peer service: __
o Graphical User Interface: __
o Peer service: __
Security:
- User-level: __
User ID of peer workstation owner: ____________
OR
- Share-level: __
o User Profile Management: __
Topic 2 of 2
LAN Server Worksheet
OS/2 LAN Requester Installation
o LAN Services Adapters: __
Adapter(s) to be used with OS/2 LAN Requester; fill in logical adapter
number(s):
- __
- __
- __
- __
o Fault Tolerance Administration: __
o First Failure Support Technology/2: __
- Autostart: __
Route alerts to:
NetView: __
IBM LAN Network Manager: __
- Display messages: __
- System information:
Maximum dumps (1-99): __
Dump path: _____________ Application information:
Maximum dumps (1-99): __
Dump path: _____________
Message log: _____________
- Hardware vital product data:
Workstation type: _____________
Workstation serial number: _____________
Workstation ID: _____________
o LAN Services Installation/Configuration Program: __
o LAN Server Applications Development Toolkit: __
o Virtual DOS LAN API Support: __
ΓòÉΓòÉΓòÉ 13.1.3. DOS LAN Services Installation Worksheet ΓòÉΓòÉΓòÉ
This worksheet helps you prepare for installing DOS LAN Services on a hard disk
in your workstation. Use it in conjunction with Installing DOS LAN Services
from CD-ROM or Diskettes.
LAN Server Worksheet
DOS LAN Services Installation from Diskettes
Check, circle, or fill in the blanks:
DOS programs to install (if not yet installed):
DOS (IBM ___ or MS ___):
3.3: __ 3.3: __
5.0: __ 5.0: __
6.1: __ 6.0: __
6.3: __ 6.2: __
Diskette Drive Letter: A or B
Graphical User Interface Needed?: Yes or No
Windows Support Needed?: Yes or No
Peer Services Needed?: Yes or No
Protocol Driver: ________________________
Machine ID: ________________________ (1-15 characters)
User Name: ________________________ (1-20 characters)
Domain Name: ________________________ (1-15 characters)
Redirector: Basic or Full or Virtual
Start-up Option:
Do not run DOS LAN Services __
Run DOS LAN Services only __
Run DOS LAN Services and log on (this is the default) __
Path in which to install DOS LAN Services: ________________________ (default is
C:\NET)
Network adapter card type: ________________________
If you are running on an Ethernet adapter and using the DXME0MOD.SYS and
DXMT0MOD.SYS device drivers for IEEE 802.2 support, you must add CF=Y to the
DXMT0MOD.SYS line in your CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 13.2. Network Setup Worksheets ΓòÉΓòÉΓòÉ
The network setup worksheets are intended to help plan for network servers,
requesters, resources, applications, users, and groups.
The following worksheets are provided:
o The Server Summary Worksheet in topic Server Summary Worksheet summarizes the
resources you plan to install on a server. Complete one worksheet for each
server.
o The Remote IPL Server Worksheet in topic Remote IPL Server Worksheet helps
you configure a server to remote-IPL DOS or OS/2 LAN requesters. Complete
one worksheet for each remote IPL server.
o The Resource Worksheets for files, printers, and serial devices in topics
Directory Resource Worksheet, Printer Resource Worksheetand Serial Device
Resource Worksheet help you plan resource paths on each server, port
connections for printers and serial devices, access permissions for each
resource, and how to share each resource.
o The Application Worksheet in topic Application Worksheet helps you plan for
application file paths, the working directory, and resource assignments for
an application. Complete one worksheet for each application.
o The User Worksheet in topic User Worksheet helps you plan the logon
assignments, program starter applications, and operator privileges for each
user. Complete one worksheet for each user ID.
o The Group Worksheet in topic Group Worksheet helps you plan the user ID
membership for each group. Complete one worksheet for each group.
ΓòÉΓòÉΓòÉ 13.2.1. Server Summary Worksheet ΓòÉΓòÉΓòÉ
The Server Summary Worksheet summarizes the resources you plan to install on a
server.
LAN Server
Server Summary Worksheet
Fill in the blanks:
o Server name ________________________________
o Domain name ________________________________
o Available hard-disk space __________________
o Resources:
Directory aliases Description Hard-disk space
_______________________ _________________________ _______________
_______________________ _________________________ _______________
_______________________ _________________________ _______________
_______________________ _________________________ _______________
_______________________ _________________________ _______________
_______________________ _________________________ _______________
_______________________ _________________________ _______________
_______________________ _________________________ _______________
_______________________ _________________________ _______________
_______________________ _________________________ _______________
Print queue aliases Description
_______________________ ___________________________________________
_______________________ ___________________________________________
_______________________ ___________________________________________
Serial device queue aliases Description
_______________________ ___________________________________________
_______________________ ___________________________________________
_______________________ ___________________________________________
ΓòÉΓòÉΓòÉ 13.2.2. Remote IPL Server Worksheet ΓòÉΓòÉΓòÉ
The Remote IPL Server Worksheet helps configure a server to support remote IPL
of DOS or OS/2 workstations. Use this worksheet in conjunction with the
information on the Remote IPL service in the LAN Server Network Administrator
Reference Volume 3: Network Administrator Tasks.
LAN Server
Remote IPL Server Summary Worksheet
Fill in the blanks:
o Server name ________________________________
o Domain name ________________________________
If DOS remote IPL is supported on this server:
Remote workstation name Adapter address* Image file
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
If OS/2 remote IPL is supported on this server:
Remote workstation name Adapter address* FIT file
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
____________________ ______________ _______________
* 12-digit universally administered address (See adapter documentation).
ΓòÉΓòÉΓòÉ 13.2.3. Directory Resource Worksheet ΓòÉΓòÉΓòÉ
The Directory Resource Worksheet helps define and set up a directory resource,
and plan access control to it.
LAN Server
Resource Worksheet: Directory
Fill in the blanks:
o Alias ____________________ Server ________________________________
o Path _________________________________
o Description _________________________
o Maximum number of concurrent users (optional) ______
o How is the resource shared? (circle one)
At startup At user request By administrator action
o Resource permissions:
User ID Permissions
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
Group ID Permissions
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
Universal access permissions __________________________
Audit trail? (circle one)
None All accesses Failed accesses Successful accesses
ΓòÉΓòÉΓòÉ 13.2.4. Printer Resource Worksheet ΓòÉΓòÉΓòÉ
The Printer Resource Worksheet helps define and set up a printer resource, and
plan access control to it.
LAN Server
Resource Worksheet: Printers
Fill in the blanks:
o Resource Type _____________________________
o Alias ___________ Server ____________________
o Description _______________________________
o Spooler queue name ___________________________
o Maximum number of concurrent users (optional) _____
o How is the resource shared? (circle one)
At startup By administrator action
o Servicing the queue:
Device Port
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
o Permissions:
User ID Permissions
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
Group ID Permissions
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
Universal access permissions ______________________
Audit trail? (circle one)
None All accesses Failed accesses Successful accesses
ΓòÉΓòÉΓòÉ 13.2.5. Serial Device Resource Worksheet ΓòÉΓòÉΓòÉ
The Serial Device Resource Worksheet helps define and set up a serial device
resource, and plan access control to it.
LAN Server
Resource Worksheet: Serial Devices
Fill in the blanks:
o Resource Type _____________________________
o Alias ___________ Server ____________________
o Description _______________________________
o Device Pool Priority ___________________________
o Maximum number of concurrent users (optional) _____
o How is the resource shared? (circle one)
At startup By administrator action
o Servicing the queue:
Device Port
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
o Permissions:
User ID Permissions
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
Group ID Permissions
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
Universal access permissions ______________________
Audit trail? (circle one)
None All accesses Failed accesses Successful accesses
ΓòÉΓòÉΓòÉ 13.2.6. Application Worksheet ΓòÉΓòÉΓòÉ
The Application Worksheet helps plan for application file paths, the working
directory, and resource assignments for an application.
LAN Server
Application Worksheet (Page 1 of 2)
Fill in the blanks:
o Application ID ______________________________
o Application operating system (circle one): DOS OS/2
o Application type (circle one):
Public (Network) Private
o Description _____________________________
o Command line ____________________________
o Parameters ______________________________
o Prompt user for parameters? (Y/N) _____
o Program location (circle one): Local (OS/2 only) Remote
o Drive (if local) or alias (if remote): __________
o Remaining path to program ___________________________
o Assigned Drive (circle one)
None Next available Specified
o Working directory (circle one)
None Local (OS/2 only) Remote
Drive (if local) or alias (if remote) ______
Remaining path ____________ _____________
Assigned drive (circle one)
Next Available Specified
o Program mode (OS/2 only) (circle one)
OS/2 PM Protected mode (Protmode) Video I/O (VIO)
LAN Server
Application Worksheet (Page 2 of 2)
o Network assignments:
Directory aliases Drive
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
Print queue aliases Port
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
Serial device aliases Port
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
ΓòÉΓòÉΓòÉ 13.2.7. User Worksheet ΓòÉΓòÉΓòÉ
The User Worksheet helps plan the logon assignments, program starter
applications, and operator privileges for a user ID.
LAN Server
User Worksheet (Page 1 of 2)
Fill in the blanks:
o User name ___________________________
o User ID _____________________________
o Description _________________________
o Password ____________________________
Required (Y/N) ____
Changeable by administrator only (Y/N) ____
o Privilege levels (circle one)
User Administrator
- User privileges (circle one or more)
None Print Accounts Comm Server
- Operator privileges (circle one or more)
Print Accounts Comm Server
o Home directory (circle one)
None Assigned
o Local requester drive (circle one)
Letter ____ Next Available
o Server name __________________________
o Local path at server ____________________
o CHKSTOR threshold ______ KB
LAN Server
User Worksheet (Page 2 of 2)
o Account options (circle one)
Disabled Can be deleted
o Expiration (circle one)
Never Specified (Date _________ Time _________)
o Logon workstations (circle one)
Any Allowable names
Allowable names list:
______________________ ______________________
______________________ ______________________
______________________ ______________________
______________________ ______________________
o Logon assignments:
Resources
Device Type
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
Applications on program starter:
Application ID Description
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
____________________ __________________
Group memberships: __________________________________________
ΓòÉΓòÉΓòÉ 13.2.8. Group Worksheet ΓòÉΓòÉΓòÉ
The Group Worksheet helps plan the user ID membership of a group.
LAN Server
Group Worksheet
Fill in the blanks:
o Group ID _________________
o Description _________________
o Users:
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
__________________ _______________ _________________
ΓòÉΓòÉΓòÉ 13.3. Memory and Hard-Disk Estimating Worksheets ΓòÉΓòÉΓòÉ
Use the following worksheets as guidelines in determining the memory and
hard-disk requirements for each server or requester workstation on your
network. Add the size required for the server or requester product to the size
required for the operating system (OS/2 for OS/2 LAN Server and OS/2 LAN
Requester; DOS for DOS LAN Services) and the size required for each
application. Include an allowance for user application data. For considerations
regarding memory and hard-disk size, refer to Hardware, Memory, and Hard-Disk
Requirements.
Hard-disk requirements for workstations on your network can be changed if you
do one of the following:
o Follow the Tailored installation path during installation
o Provide users of workstations with custom installation diskettes
o Create response files for remote installation
In each case, more efficient use can be made of the available hard-disk space,
because only the code relevant to the components or functions you specified is
installed. However, the Tailored path also allows you to install functions not
available on the Easy path. Adding more information might cause your
workstation to require more hard-disk space.
The following worksheets break down the requirements for OS/2 LAN Server and
OS/2 LAN Requester, making it easy to determine how much memory or hard-disk
space your particular workstation requires.
System memory requirements are based only on applications and functions that
run concurrently. The memory requirement is less if the user does not run all
installed functions and applications concurrently. Memory requirements vary
from application to application, and depend on the conditions under which each
application is used.
Using less than the recommended memory could increase the time required to
switch from one function or application to another, reduce keystroke
responsiveness, or reduce throughput. For the impact of caching, buffers, and
tuning, refer to the LAN Server Network Administrator Reference Volume 2:
Performance Tuning.
If the workstation has more than one hard disk, the LAN Services
installation/configuration program allows you to select the hard disk on which
to install OS/2 LAN Server or OS/2 LAN Requester. However, User Profile
Management and the First Failure Support Technology/2 product are always
installed on the startup drive.
Note:
You must determine and install the proper memory and disk capacities in
your machines, and select the programs to achieve intended results. You
are also responsible for the installation of, use of, and results
obtained from the machines and programs.
IBM does not warrant or otherwise guarantee any performance or usability
results implied by this data. You should ensure that your hardware
configuration is flexible enough to accommodate possible changes, such
as future enhancements, new customer applications, and increased user
data requirements.
ΓòÉΓòÉΓòÉ 13.3.1. Memory Estimating Worksheet for OS/2 LAN Server Workstations ΓòÉΓòÉΓòÉ
The following table lists the minimum memory requirements for the OS/2 LAN
Server component of the LAN Server product.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé MEMORY ESTIMATING WORKSHEET - OS/2 LAN SERVER WORKSTATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé RECOMMENDED Γöé Γöé
Γöé Γöé MEMORY Γöé Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ YOUR Γöé
Γöé Γöé SBCS Γöé DBCS Γöé WORK- Γöé
Γöé FUNCTIONS Γöé (MB) Γöé (MB) Γöé STATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Operating system: Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Base (OS/2 2.1)(1,2) Γöé 2.8 Γöé 3.3 Γöé Γöé
Γöé HPFS(2) Γöé 0.2 Γöé 0.2 Γöé Γöé
Γöé Active spooling (while printing) Γöé 0.7 Γöé 0.7 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LAN Adapter and Protocol Support Γöé 0.6 Γöé 0.6 Γöé Γöé
Γöé (shipped with LAN Server) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Server (select one): Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Domain controller Γöé 2.2 Γöé 3.7 Γöé Γöé
Γöé (LAN Server-Entry) Γöé Γöé Γöé Γöé
Γöé Domain controller Γöé 3.5 Γöé 4.8 Γöé Γöé
Γöé (LAN Server-Advanced)(3) Γöé Γöé Γöé Γöé
Γöé Backup domain controller Γöé 2.2 Γöé 3.7 Γöé Γöé
Γöé (LAN Server-Entry) Γöé Γöé Γöé Γöé
Γöé Backup domain controller Γöé 3.5 Γöé 4.8 Γöé Γöé
Γöé (LAN Server-Advanced)(3) Γöé Γöé Γöé Γöé
Γöé Additional server Γöé 1.9 Γöé 3.4 Γöé Γöé
Γöé (LAN Server-Entry) Γöé Γöé Γöé Γöé
Γöé Additional server Γöé 2.3 Γöé 3.9 Γöé Γöé
Γöé (LAN Server-Advanced)(3) Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé NOTE: The figures include the memory require- Γöé Γöé Γöé Γöé
Γöé ments for the Messenger, Netlogon, and Γöé Γöé Γöé Γöé
Γöé LSserver services, which are autostarted Γöé Γöé Γöé Γöé
Γöé when the server is started. Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LAN Server Administration GUI(4) Γöé 4.5 Γöé 6.0 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS Remote IPL service(5) Γöé 0.7 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OS/2 Remote IPL service(5) Γöé 0.8 Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications(6) Γöé N/A Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications data(7) Γöé N/A Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TOTAL Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTES: Γöé
Γöé Γöé
Γöé 1. Includes default FAT cache disk size of 512KB, which allows good per- Γöé
Γöé formance with less RAM cost. Γöé
Γöé 2. Add memory for disk cache. Γöé
Γöé 3. Includes the 386 HPFS. Add memory for disk cache. Γöé
Γöé 4. When the LAN Server Administration GUI is not running, this memory can Γöé
Γöé be used by other applications. Γöé
Γöé 5. DBCS DOS and OS/2 remote IPL were not available for testing. Γöé
Γöé 6. Use figures provided by the supplier of the application. Γöé
Γöé 7. Figures are dependent on the application and the user. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 13.3.2. Memory Estimating Worksheet for OS/2 LAN Requester Workstations ΓòÉΓòÉΓòÉ
The following table lists the minimum memory requirements for the OS/2 LAN
Requester component of the LAN Server product.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé MEMORY ESTIMATING WORKSHEET - OS/2 LAN REQUESTER WORKSTATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé RECOMMENDED Γöé Γöé
Γöé Γöé MEMORY (MB) Γöé Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ YOUR Γöé
Γöé Γöé SBCS Γöé DBCS Γöé WORK- Γöé
Γöé FUNCTIONS Γöé (MB) Γöé (MB) Γöé STATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Operating system: Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Base (OS/2 2.1)(1,2) Γöé 2.8 Γöé 3.3 Γöé Γöé
Γöé HPFS(2) Γöé 0.2 Γöé 0.2 Γöé Γöé
Γöé Active spooling (while printing) Γöé 0.7 Γöé 0.7 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LAN Adapter and Protocol Support Γöé 0.6 Γöé 0.6 Γöé Γöé
Γöé (shipped with LAN Server) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Requester Γöé 1.5 Γöé 2.7 Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Includes the memory required for User Profile Γöé Γöé Γöé Γöé
Γöé Management, which is autostarted when the Γöé Γöé Γöé Γöé
Γöé requester is started. Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Peer service Γöé 1.4 Γöé 2.4 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LAN Server Administration GUI(3) Γöé 4.5 Γöé 6.0 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications(4) Γöé N/A Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications data(5) Γöé N/A Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TOTAL Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTES: Γöé
Γöé Γöé
Γöé 1. Includes default FAT cache disk size of 512KB, which allows good per- Γöé
Γöé formance with less RAM cost. Γöé
Γöé 2. Add memory for disk cache. Γöé
Γöé 3. When the LAN Server Administration GUI is not running, this memory can Γöé
Γöé be used by other applications. Γöé
Γöé 4. Use figures provided by the supplier of the application. Γöé
Γöé 5. Figures are dependent on the application and the user. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 13.3.3. Memory Estimating Worksheet for DOS LAN Services Workstations ΓòÉΓòÉΓòÉ
The following table lists the memory availability information for the DOS LAN
Services component of the LAN Server product. The required low memory depends
on whether memory managers are used and, if so, which ones. Memory managers
make it possible to load segments of the code into the 384KB upper memory or
the memory above 1MB, thus making more memory available for DOS applications.
DOS LAN Services automatically uses upper memory blocks (UMB) and extended
memory specification (XMS) space, if available.
Note:
The corresponding memory managers must be installed and activated in the
CONFIG.SYS file.
The available memory values are based on 110KB of UMB space. These values
indicate the amount of conventional memory that is available after loading the
DOS LAN Services redirector and transport. If you are using a supported
version of DOS that is not listed in this table, your available memory may
differ.
The amount of low memory needed is dependent on your hardware configuration and
the resulting memory segments available in the UMB memory space. In the best
case, as little as 30KB of low memory is required.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé WORK- Γöé TRANSPORT Γöé REDI- Γöé DOS Γöé AVAIL- Γöé AVAIL- Γöé
Γöé STATION Γöé Γöé RECTOR Γöé VERSION Γöé ABLE Γöé ABLE Γöé
Γöé TYPE Γöé Γöé Γöé Γöé MEMORY Γöé UMB Γöé
Γöé Γöé Γöé Γöé Γöé Γöé MEMORY Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 8086/8088 Γöé LAN Support Program Γöé Basic Γöé 3.3 Γöé 496KB Γöé N/A Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 8086/8088 Γöé JETBEUI Γöé Basic Γöé 3.3 Γöé 475KB Γöé N/A Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 8086/8088 Γöé JETBEUI and IEEE 802.2 Γöé Basic Γöé 3.3 Γöé 467KB Γöé N/A Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 80386 Γöé LAN Support Program Γöé Basic Γöé 6.3 Γöé 604KB Γöé 28KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 80386 Γöé LAN Support Program Γöé Full Γöé 6.3 Γöé 555KB Γöé 37KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 80386 Γöé JETBEUI Γöé Basic Γöé 6.3 Γöé 604KB Γöé 15KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 80386 Γöé JETBEUI and IEEE 802.2 Γöé Basic Γöé 6.3 Γöé 604KB Γöé 7KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 80386 Γöé JETBEUI and IEEE 802.2 Γöé Full Γöé 6.3 Γöé 555KB Γöé 16KB Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
In the following table, select one DOS 5.0, or 6.X option with the memory
setting you want to use on the workstation. To calculate the memory remaining
for use by your applications and data, subtract the low memory required by the
selected option from 640KB (total low memory).
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé MEMORY ESTIMATING WORKSHEET DOS LAN REQUESTER WORKSTATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé RECOMMENDED Γöé Γöé
Γöé Γöé MEMORY (KB) Γöé Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé
Γöé Γöé REQUIREΓöé REQUIREΓöé Γöé
Γöé Γöé LOW Γöé LOW Γöé YOUR Γöé
Γöé Γöé MEMORY Γöé MEMORY Γöé WORK- Γöé
Γöé DOS LAN SERVICES CONFIGURATION Γöé (SBCS) Γöé (DBCS) Γöé STATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS LAN Services 4.0 (with DOS, DOS Netbeui, Γöé Γöé Γöé Γöé
Γöé and full redirector installed)(3,4): Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with low memory(1) Γöé 259.4 Γöé 334.7 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with high memory Γöé 215.2 Γöé 283.1 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with UMB(2) Γöé 137.8 Γöé 205.8 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with low memory(1) Γöé 259 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with high memory Γöé 216.1 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with UMB(2) Γöé 133.5 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with low memory(1) Γöé N/A Γöé 345.7 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with high memory Γöé N/A Γöé 296.1 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with UMB(2) Γöé N/A Γöé 207.8 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with low memory(1) Γöé N/A Γöé 354 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with high memory Γöé N/A Γöé 307 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with UMB(2) Γöé N/A Γöé 224.5 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS LAN Services 4.0 (with DOS, LAN Support Γöé Γöé Γöé Γöé
Γöé Program 1.35, and full redirector Γöé Γöé Γöé Γöé
Γöé installed)(3,4): Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with low memory(1) Γöé 248.4 Γöé 323.7 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with high memory Γöé 204.2 Γöé 272.1 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with UMB(2) Γöé 126.8 Γöé 194.8 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with low memory(1) Γöé 248 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with high memory Γöé 205 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with UMB(2) Γöé 122.5 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with low memory(1) Γöé N/A Γöé 334.7 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with high memory Γöé N/A Γöé 285.1 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with UMB(2) Γöé N/A Γöé 196.8 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with low memory(1) Γöé N/A Γöé 343 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with high memory Γöé N/A Γöé 296 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with UMB(2) Γöé N/A Γöé 213.5 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS LAN Services 4.0 (with DOS, DOS Netbeui, Γöé Γöé Γöé Γöé
Γöé and basic redirector installed)(3,4): Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with low memory(1) Γöé 219.3 Γöé 341.7 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with high memory Γöé 275.1 Γöé 190 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with UMB(2) Γöé 88.3 Γöé 173.3 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with low memory(1) Γöé 219 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with high memory Γöé 176 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with UMB(2) Γöé 84 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with low memory(1) Γöé N/A Γöé 252.6 Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé MEMORY ESTIMATING WORKSHEET DOS LAN REQUESTER WORKSTATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé RECOMMENDED Γöé Γöé
Γöé Γöé MEMORY (KB) Γöé Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé
Γöé Γöé REQUIREΓöé REQUIREΓöé Γöé
Γöé Γöé LOW Γöé LOW Γöé YOUR Γöé
Γöé Γöé MEMORY Γöé MEMORY Γöé WORK- Γöé
Γöé DOS LAN SERVICES CONFIGURATION Γöé (SBCS) Γöé (DBCS) Γöé STATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with high memory Γöé N/A Γöé 203 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with UMB(2) Γöé N/A Γöé 175.3 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with low memory(1) Γöé N/A Γöé 261 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with high memory Γöé N/A Γöé 214 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with UMB(2) Γöé N/A Γöé 192 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS LAN Services 4.0 (with DOS, LAN Support Γöé Γöé Γöé Γöé
Γöé Program 1.35, and basic redirector Γöé Γöé Γöé Γöé
Γöé installed)(3,4): Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with low memory(1) Γöé 208.3 Γöé 230.7 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with high memory Γöé 164.1 Γöé 179 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 with UMB(2) Γöé 111.3 Γöé 162.3 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with low memory(1) Γöé 208 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with high memory Γöé 165 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3 with UMB(2) Γöé 107 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with low memory(1) Γöé N/A Γöé 241.6 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with high memory Γöé N/A Γöé 192 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V with UMB(2) Γöé N/A Γöé 164.3 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with low memory(1) Γöé N/A Γöé 250 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with high memory Γöé N/A Γöé 203 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IBM DOS 6.3/V with UMB(2) Γöé N/A Γöé 180 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications(5) Γöé N/A Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications data(6) Γöé N/A Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TOTAL LOW MEMORY Γöé Γöé Γöé 640KB Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTES: Γöé
Γöé Γöé
Γöé 1. Approximately 15KB of additional memory can be gained by minimizing Γöé
Γöé certain NETWORK.INI parameters; some loss of performance results. Γöé
Γöé 2. The amount of low memory needed is dependent on your hardware configura- Γöé
Γöé tion and the resulting memory segments available in the UMB memory Γöé
Γöé space. In the best case, as little as 30KB of low memory is required. Γöé
Γöé 3. DOS Netbeui is installed by default. The LAN Support Program is Γöé
Γöé installed when you select the 802.2 protocol. Γöé
Γöé 4. Figures in this table were generated with autocache set to NO. Γöé
Γöé 5. Use figures provided by the supplier of the application. Γöé
Γöé 6. Figures are dependent on the application and the user. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 13.3.4. Hard-Disk Estimating Worksheet for OS/2 LAN Server Workstations ΓòÉΓòÉΓòÉ
The following table lists the hard-disk requirements for the OS/2 LAN Server
component of the LAN Server product. When planning the servers on the domain,
make sure to allow for growth in hard-disk space, especially for the domain
controller. Other areas in which to plan for growth include applications, home
directories, and spooler usage. If you plan to install the Fault Tolerance
function on a server, you should also observe the disk requirements discussed
in Disk Requirements for Fault Tolerance.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé HARD-DISK ESTIMATING WORKSHEET - OS/2 LAN SERVER WORKSTATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé RECOMMENDED Γöé Γöé
Γöé Γöé HARD-DISK SPACE Γöé Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ YOUR Γöé
Γöé Γöé SBCS Γöé DBCS Γöé WORK- Γöé
Γöé FUNCTIONS Γöé (MB) Γöé (MB) Γöé STATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Operating system (OS/2 2.1): Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Base (preselected options) Γöé 31.7 Γöé 38.6 Γöé Γöé
Γöé Segment swap data set(1) Γöé 10.0 Γöé 10.0 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MPTS Γöé 4.1 Γöé 4.1 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Requester Γöé 2.6 Γöé 3.0 Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Requester Γöé Γöé Γöé Γöé
Γöé User Profile Management Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Temporary hard-disk space required during Γöé 1.1 Γöé 1.4 Γöé Γöé
Γöé installation(2) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Server (required components for domain con- Γöé 1.0 Γöé 1.5 Γöé Γöé
Γöé troller, LAN Server-Advanced) Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Server Γöé Γöé Γöé Γöé
Γöé DOS LAN Services Online Reference Γöé Γöé Γöé Γöé
Γöé User Profile Management Γöé Γöé Γöé Γöé
Γöé Timesource Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Server (additional components installed during Γöé 10.6 Γöé 15.5 Γöé Γöé
Γöé an initial Easy installation): Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé 386 HPFS (Advanced server only) Γöé Γöé Γöé Γöé
Γöé LAN Services installation/ Γöé Γöé Γöé Γöé
Γöé configuration program (for server) Γöé Γöé Γöé Γöé
Γöé LAN Server Applications Development Toolkit Γöé Γöé Γöé Γöé
Γöé LAN Server Administration GUI Γöé Γöé Γöé Γöé
Γöé Network Messaging Γöé Γöé Γöé Γöé
Γöé Network DDE and Clipboard Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS Remote IPL service(9) Γöé 5.7 Γöé Γöé Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LAN Support Program Γöé 10.3 Γöé Γöé Γöé
Γöé Remote IPL copy of DOS LAN Services Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS Version 6.3: Γöé 0.7 Γöé Γöé Γöé
Γöé Per DOS image Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OS/2 Remote IPL service(9) Γöé 16.8 Γöé Γöé Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LAN Support Program(3) Γöé 0.2 Γöé Γöé Γöé
Γöé Remote IPL copy of Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé User Profile Management Γöé 52.6 Γöé Γöé Γöé
Γöé Remote IPL copy of LAPS Γöé Γöé Γöé Γöé
Γöé Remote IPL copy of OS/2 LAN Requester Γöé Γöé Γöé Γöé
Γöé Per remote IPL workstation(4) Γöé Γöé Γöé Γöé
Γöé Remote IPL copy of OS/2 2.1 Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Server (components that can be selected when Γöé 1.4 Γöé 1.8 Γöé Γöé
Γöé following the Tailored installation path) Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé First Failure Support Technology/2 Γöé Γöé Γöé Γöé
Γöé Loop Back Driver(5,6) Γöé Γöé Γöé Γöé
Γöé Uninterruptible Power Supply service Γöé Γöé Γöé Γöé
Γöé Generic Alerter service Γöé Γöé Γöé Γöé
Γöé Virtual DOS LAN API Support Γöé Γöé Γöé Γöé
Γöé Fault Tolerance for Hard Disk Γöé Γöé Γöé Γöé
Γöé Local Security for the 386 HPFS Γöé Γöé Γöé Γöé
Γöé Migration Import Utility Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications(7) Γöé N/A Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications data(8) Γöé N/A Γöé N/A Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé HARD-DISK ESTIMATING WORKSHEET - OS/2 LAN SERVER WORKSTATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé RECOMMENDED Γöé Γöé
Γöé Γöé HARD-DISK SPACE Γöé Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ YOUR Γöé
Γöé Γöé SBCS Γöé DBCS Γöé WORK- Γöé
Γöé FUNCTIONS Γöé (MB) Γöé (MB) Γöé STATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TOTAL Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTES: Γöé
Γöé Γöé
Γöé 1. A 10MB to 15MB swap area is adequate for many environments. However, Γöé
Γöé swap area is dynamically allocated as applications require more memory Γöé
Γöé than is available. A swap area larger or smaller than shown may be Γöé
Γöé needed. Γöé
Γöé 2. Temporary space is required on the startup drive. Γöé
Γöé 3. 0.5MB is already present if DOS Remote IPL service is already installed. Γöé
Γöé 4. This figure represents hard-disk space required for storing files (such Γöé
Γöé as the CONFIG.SYS file) that are loaded onto a remote IPL requester. Γöé
Γöé This figure assumes that the requester's SWAPPER.DAT file is redirected Γöé
Γöé to the local hard disk on the requester. Otherwise, a requester's Γöé
Γöé SWAPPER.DAT file is located in the Γöé
Γöé \ IBMLAN\RPLUSER\requestername\OS2\SYSTEM subdirectory on the server. Γöé
Γöé The figure increases dynamically depending on the number of applications Γöé
Γöé running on the remote IPL requester and the amount of memory available Γöé
Γöé on the requester. The size of each requester's SWAPPER.DAT file should Γöé
Γöé be less than 2MB to avoid performance degradation. Γöé
Γöé 5. This component is required if LAN Adapter and Protocol Support is not Γöé
Γöé installed. Γöé
Γöé 6. Up to 0.5MB additional hard-disk space may be required for any addi- Γöé
Γöé tional adapter drivers. Γöé
Γöé 7. Use figures provided by the supplier of the application. Γöé
Γöé 8. Figures are dependent on the application and the user. Γöé
Γöé 9. DBCS DOS and OS/2 remote IPL were not available for testing. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 13.3.5. Hard-Disk Estimating Worksheet for OS/2 LAN Requester Workstations ΓòÉΓòÉΓòÉ
The following table lists the minimum hard-disk requirements for the OS/2 LAN
Requester component of the LAN Server product.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé HARD-DISK ESTIMATING WORKSHEET - OS/2 LAN REQUESTER WORKSTATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé RECOMMENDED Γöé Γöé
Γöé Γöé HARD-DISK SPACE Γöé Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ YOUR Γöé
Γöé Γöé SBCS Γöé DBCS Γöé WORK- Γöé
Γöé FUNCTIONS Γöé (MB) Γöé (MB) Γöé STATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Operating system (OS/2 2.1): Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Base (preselected options) Γöé 31.7 Γöé 38.6 Γöé Γöé
Γöé Segment swap data set(1) Γöé 10.0 Γöé 10.0 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MPTS Γöé 4.1 Γöé 4.1 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Temporary hard-disk space required during Γöé 1.1 Γöé 1.4 Γöé Γöé
Γöé installation(2) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Requester (required) Γöé 2.6 Γöé 3.0 Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Requester Γöé Γöé Γöé Γöé
Γöé User Profile Management Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Requester (additional components installed Γöé 8.7 Γöé 12.8 Γöé Γöé
Γöé during an initial Easy installation) Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Network Messaging Γöé Γöé Γöé Γöé
Γöé Network DDE and Clipboard Γöé Γöé Γöé Γöé
Γöé LAN Services installation Γöé Γöé Γöé Γöé
Γöé configuration program (for requester) Γöé Γöé Γöé Γöé
Γöé LAN Server Administration GUI Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Requester (components that can be selected when Γöé 2.3 Γöé 2.8 Γöé Γöé
Γöé following the Tailored installation path) Γöé Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé LAN Server Applications Development Toolkit Γöé Γöé Γöé Γöé
Γöé First Failure Support Technology/2 Γöé Γöé Γöé Γöé
Γöé Fault Tolerance Administration Γöé Γöé Γöé Γöé
Γöé Virtual DOS LAN API Support Γöé Γöé Γöé Γöé
Γöé Peer service(3) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications(4) Γöé N/A Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications data(5) Γöé N/A Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TOTAL Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTES: Γöé
Γöé Γöé
Γöé 1. A 10MB to 15MB swap area is adequate for many environments. However, Γöé
Γöé swap area is dynamically allocated as applications require more memory Γöé
Γöé than is available. A swap area larger or smaller than shown may be Γöé
Γöé needed. Γöé
Γöé 2. Temporary space is required on the startup drive. Γöé
Γöé 3. The Peer service cannot be installed concurrently with the server. Γöé
Γöé 4. Use figures provided by the supplier of the application. Γöé
Γöé 5. Figures are dependent on the application and the user. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 13.3.6. Hard-Disk Estimating Worksheet for DOS LAN Services Workstations ΓòÉΓòÉΓòÉ
The following table lists the minimum hard-disk requirements for the DOS LAN
Services component of the LAN Server product.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé HARD-DISK ESTIMATING WORKSHEET - DOS LAN SERVICES WORKSTATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé REQUIRED Γöé Γöé
Γöé Γöé HARD-DISK SPACE Γöé Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ YOUR Γöé
Γöé Γöé SBCS Γöé DBCS Γöé WORK- Γöé
Γöé FUNCTIONS Γöé (MB) Γöé (MB) Γöé STATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0 Γöé 2.3 Γöé 2.3 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 5.0/V Γöé N/A Γöé 4.8 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 6.3 Γöé 2.6 Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS 6.3/V Γöé N/A Γöé 7.2 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS LAN Services 4.0 - DOS Netbeui (provided Γöé 3.9 Γöé 4.8 Γöé Γöé
Γöé with LAN Server) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOS LAN Services 4.0 - LAN Support Program 1.35 Γöé 4.0 Γöé 5.0 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications(1) Γöé N/A Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Applications data(2) Γöé N/A Γöé N/A Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TOTAL Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTES: Γöé
Γöé Γöé
Γöé 1. Use figures provided by the supplier of the application. Γöé
Γöé 2. Figures are dependent on the application and the user. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 14. Migrating PCLP to an IBM OS/2 LAN Server Environment ΓòÉΓòÉΓòÉ
This appendix contains information about migrating your system from a PC LAN
Program 1.3 or later environment to an IBM OS/2 LAN Server environment.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: This appendix is for Γöé
Γöé Single-Byte Character Set users only. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
When migrating a PCLP domain to a LAN Server domain, you use the PCLP Migration
Utility to move the domain definitions from the PCLP environment to the domain
control database (DCDB) in the LAN Server environment while preserving the
integrity and consistency of the data. The PCLP Migration Utility is provided
with the LAN Server product.
Domain definitions (information about a domain) are stored in directories in
the PCLP 1.3 and LAN Server environment. Throughout this chapter, the domain
definitions are referred to as the domain control database, or DCDB.
The DCDB contains domain definitions such as logon assignments, application
selector information, resources to be shared as defined by the network
administrator, and access control profiles.
A domain can be migrated at one time or in stages over a period of time. The
resources in the destination domain can be the same as or different from those
in the source domain.
ΓòÉΓòÉΓòÉ 14.1. Overview of PCLP Migration ΓòÉΓòÉΓòÉ
The following table summarizes the process and tasks required to migrate PCLP
to the LAN Server product. Other topics to consider, such as passwords, domain
names, and security, are also discussed later in this section. You should
become familiar with this entire section before proceeding with the migration.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 20. PCLP Migration Tasks Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TASK: Γöé STARTS ON TOPIC: Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Preparing the network and user community, which Γöé Preparing the Network Γöé
Γöé involves such tasks as upgrading hardware if nec- Γöé and User Community Γöé
Γöé essary and informing network users about the Γöé Γöé
Γöé migration schedule. Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Preparing for the export phase, which involves Γöé Preparing for the Γöé
Γöé such tasks as printing the existing domain defi- Γöé Export Phase Γöé
Γöé nitions for later comparisons and creating a Γöé Γöé
Γöé backup copy of the existing domain definitions on Γöé Γöé
Γöé diskette, as well as reviewing and documenting the Γöé Γöé
Γöé current access permissions for each network Γöé Γöé
Γöé resource. Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Exporting the source domain definitions to a tem- Γöé Exporting the Domain Γöé
Γöé porary DCDB file. Γöé Definitions to a Tempo- Γöé
Γöé Γöé rary DCDB File Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Preparing for the import phase, which involves Γöé Preparing for the Γöé
Γöé preparing the new domain controller (installing Γöé Import Phase Γöé
Γöé the appropriate software) and modifying the tempo- Γöé Γöé
Γöé rary DCDB file for the new environment as Γöé Γöé
Γöé required. Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Importing the domain definitions from the tempo- Γöé Importing the Domain Γöé
Γöé rary DCDB file to the destination DCDB. Γöé Definitions to the Des- Γöé
Γöé Γöé tination Domain Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Completing the migration, which involves such Γöé Completing the Γöé
Γöé tasks as restoring resources that have not been Γöé Migration Γöé
Γöé migrated and upgrading the requesters in the Γöé Γöé
Γöé domain. This also involves migrating users and Γöé Γöé
Γöé all their related information to the LAN Server Γöé Γöé
Γöé domain. Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
All servers in the source domain must be started in order to export the DCDB.
All servers in the destination domain must be started in order to import the
DCDB.
Note:
During the actual migration, no other users or administrators should be
logged on to the domain, because this could interfere with the process.
It is especially important that other network administrators do not
modify any domain definitions in the databases while the migration is
taking place.
The migration process uses the PCLP Migration Utility to process the data
related to the user and resource definitions. The PCLP Migration Utility uses
DCDB Export and DCDB Import functions to move and process the domain
definitions from the current domain to the new one. The Export function is
contained on the PCLP Migration Utility diskette provided with the LAN Server
product. The network administrator runs the Export function on the source
(PCLP 1.3) domain controller. The Import function is installed by selecting
the PCLP Migration Import Utility component during LAN Server installation.
The network administrator runs the Import function on the destination (LAN
Server) domain controller.
The Export function uses a mapping component to map the attributes of the LAN
objects (for example, users and access profiles) from the source DCDB format to
the destination DCDB format. The exported attributes are written to a temporary
DCDB file.
After the LAN Server product is installed, the Import function is used to
import the information from the temporary DCDB file into the LAN Server DCDB
and the UPM Services database. Only the definitions of the LAN objects and
access control profiles are migrated. The resources themselves are not
migrated. The network administrator and network users must manually move
physical resources, such as software applications and user files, from the
source domain to the destination domain.
If a critical error occurs during migration, the process stops. To identify and
correct the error, the network administrator can refer to PCLP Migration Error
Messages and check the history file generated by the utility. A noncritical
error, such as a duplicate resource not being migrated or a resource not being
shared, that occurs during the migration is also logged in the history file.
The network administrator can review and correct noncritical errors at any
time.
Notes:
1. The migration scenarios describe migration to a LAN Server domain
containing only the default LAN definitions. If the LAN Server domain
controller contains any definitions other than those defaults, then
prior to importing, check for duplicate information between the
temporary DCDB file and the existing LAN Server DCDB. If duplicates are
found, make the appropriate changes either to the temporary DCDB file or
to the LAN Server DCDB.
When the Import function is run, existing entries in the LAN Server DCDB
are preserved if conflicts (such as duplicate entries) arise with
imported entries. For example, if the temporary DCDB file contains a
user ID that is identical to a user ID already residing on the
destination domain, the user ID on the destination domain is retained.
The exception to this happens when the temporary DCDB file contains a
duplicate server and resource combination, such as a printer that uses
the same server and same port as the printer that is already assigned to
the destination domain. In this case, the migration stops and the
network administrator must decide which resource to keep.
2. The network administrator must verify that the country information (code
page, country code, and keyboard parameters in the CONFIG.SYS file) is
the same in the source and destination domains.
3. If the DCDB is too large to fit on one diskette, the Export and Import
functions support multiple diskettes. During the export phase, the
network administrator is prompted for additional formatted diskettes and
a new temporary DCDB file name for each additional diskette. The
temporary DCDB file names should be unique and in sequential order (for
example, DCDB1.TMP, DCDB2.TMP and DCDB3.TMP). The Import function does
not prompt for additional diskettes. The network administrator must use
the Import function to process each diskette in the sequential order in
which it was created. The import phase is complete when all diskettes
have been processed.
4. Certain text editors may insert tab characters in the files that you
edit. Verify that the TAB option is set to OFF for the editor you are
using. The OS/2 System Editor does not add tab characters.
ΓòÉΓòÉΓòÉ 14.1.1. Backing Up DCDB Definitions ΓòÉΓòÉΓòÉ
Before starting the migration, the network administrator should manually back
up the source DCDB using a series of XCOPY commands. The PCLP Migration
Utility does not perform this function. It is important to have a copy of the
original DCDB in case of errors or system failure during the migration.
To verify the domain definitions, the network administrator should print the
definitions before and after the migration process, and compare both sets. The
PCLP Migration Utility does not perform this function.
The following domain definitions are migrated:
o Machine definitions (excluding requesters)
o Files alias definitions (including directory structures)
o Printer alias definitions (including queues)
o Serial device alias definitions (including queues and external resources)
o Public application definitions (excluding working directories)
- Application files assignments
- Application printer assignments
- Application serial device assignments
o User definitions
- Logon file assignments
- Logon printer assignments
- Logon serial device assignments
- Application selector list
o Remote IPL requesters
o Group definitions
o Access control profiles
These definitions (their attributes and values) are exported into a temporary
DCDB file in the order shown. This temporary DCDB file can be edited to change
or add values as necessary before importing the domain definitions to the new
LAN Server DCDB. However, the order of the definitions in the temporary DCDB
file should not be changed. See num=none.Contents of the Temporary DCDB File,
for values for the domain definitions.
The remote IPL requester definitions are migrated by this utility, but the
RPL.MAP file and the images are not. Remote IPL support can be installed using
the LAN Server installation program. New DOS LAN Services IPL images can be
built using the graphical user interface. For more information about remote
IPL, see the LAN Server Network Administrator Reference Volume 3: Network
Administrator Tasks.
Only the definition of the user's home directory is migrated. The files in the
home directory should be backed up before starting the migration. After the
migration is completed, the backed-up files can be restored.
ΓòÉΓòÉΓòÉ 14.1.2. Name and Password Considerations ΓòÉΓòÉΓòÉ
User IDs and Group IDs used in the LAN Server product must contain from 1 to 20
characters. The first character cannot be numeric. The last character cannot
be the dollar sign ($) character. An error occurs if the name does not follow
these naming conventions.
Because original user passwords cannot be decrypted, the PCLP Migration Utility
randomly sets a new password for each migrated user in the LAN Server
destination domain. The new passwords are contained in the
\IBMLAN\NETPROG\DCDBPSWD.DAT file located on the destination domain controller.
The network administrator must notify users of their new passwords so they can
log on to the destination domain.
ΓòÉΓòÉΓòÉ 14.1.3. LAN Resource Considerations ΓòÉΓòÉΓòÉ
If the number of servers in the destination domain does not match the number of
servers in the source domain, the network administrator should make the
appropriate adjustments. For example, if the LAN resources (files, printers,
serial devices, or applications) are distributed over a smaller number of
servers than in the original domain, the network administrator must edit the
domain definitions to reflect the correct server name for each of the
resources. If the PCLP Migration Utility is used, this can be done by editing
the temporary DCDB file prior to importing the definitions into the new LAN
Server domain. Any servers that did not exist in the source domain, but that
will exist in the destination domain, can be added to the temporary DCDB file
or can be added through the graphical user interface after the migration is
complete.
If shared resources are added for the new domain, the network administrator can
define additional resources after the migration has been completed. If there
are resources that will be eliminated from the destination domain, the network
administrator should change the definitions of aliases or possible user logon
assignments before running the Export function.
ΓòÉΓòÉΓòÉ 14.1.4. Access Control Profiles ΓòÉΓòÉΓòÉ
In PCLP 1.3, directories without access control profiles were given maximum
access permissions. The LAN Server 4.0 product denies access to directories
without an access control profile.
To prevent access being given to resources having no access control profiles,
the Import function creates an access control profile for each drive with all
permissions (except P) for the group USERS. This allows access to all files
and directories that do not have any access control profiles. To take
advantage of the expanded access control provisions in the LAN Server 4.0
product, the network administrator should create the appropriate access control
profiles throughout the directory structure and then update or delete the
access control profile of the drive. In addition, the network administrator
should ensure that access control profiles exist for resources that are shared
using NET SHARE commands.
ΓòÉΓòÉΓòÉ 14.1.5. Domain Names ΓòÉΓòÉΓòÉ
PCLP 1.3 required that the domain name and the machine name of the server used
as the domain controller be the same. The LAN Server 4.0 product requires that
the domain name and server machine names be unique. For this reason, when you
migrate PCLP 1.3 to the LAN Server product, you have to change either the
domain name or the server name on the domain controller.
1. If the domain name is selected to be changed, it is changed during
installation of the LAN Server product. Changing the domain name requires
changes to any batch (.BAT) or command (.CMD) files containing instructions
using the domain name.
2. If the server (machine) name is selected to be changed, it can either be
changed during the installation of the LAN Server server, or by using the
CHGSRVR utility. See the LAN Server Network Administrator Reference
Volume 3: Network Administrator Tasks for more information. Changing the
server name also requires making global changes in the temporary DCDB file
created during the export phase to reflect the new server name. Other
areas that may require server name changes are batch (.BAT) or command
(.CMD) files containing instructions using the server (machine) name.
ΓòÉΓòÉΓòÉ 14.1.6. Error Handling ΓòÉΓòÉΓòÉ
If an error is encountered during the migration process, an error message is
displayed at the workstation and is logged into a history file. The history
file when exporting from PCLP 1.3 is as follows:
\PCLP13XS\NET1_30\PCLP13MU.HST
The history file contains chronological data about the migration in the form of
activity and error entries. Each activity that is performed by a component
during the migration is contained in a record. Each error entry is also
contained in a record. Both the activity and error entries are logged in the
history file.
If the error message has a prefix of MUIMP or MUEXP, the network administrator
should refer to PCLP Migration Error Messages and check the history file to
identify and correct the error. If the error message prefix is SYS or NET, the
network administrator can type HELP prefixnnnn at the OS/2 command prompt for
an online explanation of the message (prefixnnnn is the message class and
number that is displayed, for example NET2103).
If an error occurs during the export phase, the network administrator should
find and correct the error, and start the migration from the beginning.
If an error occurs during the import phase, the network administrator should
find and correct the error either by editing the temporary DCDB file or by
changing the LAN Server DCDB. The network administrator can decide whether to
start the Import function from the beginning or to continue from the point at
which the error occurred. To continue the import phase from the point at which
the error occurred, the network administrator should perform the following
steps:
1. Copy the temporary DCDB file that is being processed (for example,
DCDB2.TMP) to a new temporary DCDB file (DCDB2.EDT):
COPY DCDB2.TMP DCDB2.EDT
2. Edit DCDB2.EDT and delete all records (records are separated by "EOR") from
the beginning of the file to the last record (including the "EOR") that was
processed successfully.
3. Restart the Import function to process DCDB2.EDT.
ΓòÉΓòÉΓòÉ 14.2. Migrating a PCLP 1.3 Domain to IBM OS/2 LAN Server ΓòÉΓòÉΓòÉ
This section describes the tasks required to migrate from a PCLP 1.3 domain
(servers and requesters) to a LAN Server domain.
ΓòÉΓòÉΓòÉ 14.2.1. Preparing the Network and User Community ΓòÉΓòÉΓòÉ
The migration from a PCLP 1.3 environment to a LAN Server environment can
require a hardware upgrade of the servers. For information about system,
memory, and hard-disk space requirements, refer to Hardware, Memory, and
Hard-Disk Requirements.
It is recommended that you notify system users about the upgrade to the new
product release. Include the following information in this notification:
o Tell users about the schedule (when their workstations will be migrated).
o Tell users to back up their home directories before the migration, and to
restore the home directories after the migration has been completed.
o Explain that private applications (that exist on the user's workstation only)
will not be migrated, and that the user's must add these applications to
their application selectors after the migration has been completed.
o Tell users to get their new passwords from the network administrator after
the migration has been completed.
ΓòÉΓòÉΓòÉ 14.2.2. Preparing for the Export Phase ΓòÉΓòÉΓòÉ
Before you export the domain definitions to a temporary DCDB file, complete the
following steps.
To Prepare for the Export Phase:
1. Print the current LAN domain definitions by doing the following:
dbscal='1.2'.
a. Log on as an administrator to the source domain controller.
b. Verify that no other users or administrators are logged on and
accessing the DCDB.
c. Select PCLP from the Application Selector menu.
d. Select PRINTDDF from the PCLP Functions menu.
2. Create a backup copy of the current LAN domain definitions by using the
following sequence of DOS XCOPY commands:
XCOPY C:\PCLPUSER A:\PCLPUSER /S /E
XCOPY C:\APPS A:\APPS /S /E
XCOPY C:\PCLP13XS\USER A:\PCLP13XS\USER /S /E
XCOPY C:\PCLP13XS\FILESETS A:\PCLP13XS\FILESETS /S /E
XCOPY C:\PCLP13XS\PRINTERS A:\PCLP13XS\PRINTERS /S /E
XCOPY C:\PCLP13XS\LISTS A:\PCLP13XS\LISTS /S /E
XCOPY C:\PCLP13XS\BATCH A:\PCLP13XS\BATCH /S /E
Note:
This process may require more than one formatted diskette. If an
XCOPY command requires more than one diskette, you should use the
BACKUP command. See your DOS documentation for information about
this command.
3. If You Are Migrating in Stages: Connect an additional OS/2 workstation
to serve as the LAN Server domain controller for the new domain, so you
can continue to use the source PCLP domain controller until migration is
completed.
ΓòÉΓòÉΓòÉ 14.2.3. Exporting the Domain Definitions to a Temporary DCDB File ΓòÉΓòÉΓòÉ
To export the domain definitions to a temporary DCDB file, complete the
following steps at the source domain controller.
To Export the Domain Definitions:
1. Insert Requester - Disk 1 into drive A.
2. Copy the following files to the C:\PCLP13XS\NET1_30 directory (this
syntax assumes you are installing from the A:\> prompt at the command
line):
A:\>COPY A:\PCLP13MU.FMT C:\PCLP13XS\NET1_30
A:\>COPY A:\PCLP13MU.MSG C:\PCLP13XS\NET1_30
A:\>COPY A:\PCLPEXPO.EXE C:\PCLP13XS\NET1_30
The PCLP13MU.FMT format file is used to generate the temporary DCDB
file. The PCLP13MU.MSG message file logs the activities (or messages)
in the history file and displays prompts at the workstation. The
PCLPEXPO.EXE file contains the executable Export program for PCLP 1.3.
3. Remove Requester - Disk 1 diskette from drive A.
4. Start all PCLP 1.3 servers (the domain controller and additional
servers) in the domain.
5. Log on as an administrator to the domain controller.
Note:
You may have to change your NET START parameters to make
additional memory available to enable you to log on to the domain
controller.
6. Select DOS.
7. Make C:\PCLP13XS\NET1_30 the current directory.
8. Type the following to start the export function:
PCLPEXPO path
where the path parameter specifies the full path and file name of the
temporary DCDB file that you want to create during the export phase.
The path can include the drive letter. For example, to create the
temporary DCDB export file DCDB.TMP on drive A, type the following:
PCLPEXPO A:DCDB.TMP
The Export function reads each attribute for the LAN objects defined in
the PCLP 1.3 source domain and maps each attribute to the corresponding
attribute in the LAN Server DCDB format. The Export function then
writes the attribute to a temporary DCDB file that can be edited by the
network administrator as necessary.
The following message is displayed when the Export function is
completed:
Program completed successfully.
9. If you have an RPL.MAP file containing remote IPL machine definitions:
a. Type the following to copy the RPL.MAP file to a new diskette:
COPY C:\PCLP13XS\IMAGES\RPL.MAP A:
b. If the remote IPL server name has changed, edit the DCDB.TMP files
and the RPL.MAP file to reflect the new server name. Ensure that no
extra characters or blank lines are added to the files.
Notes:
1. If the DCDB being exported is larger than one diskette, the function
prompts for another formatted diskette and a new file name. The file
names on the multiple diskettes should be in sequential order.
2. If an error occurs, refer to PCLP Migration Error Messages. Check
the history file to identify and correct the error, and to learn what
steps to take to continue.
3. The C:\PCLP13XS\NET1_30\PCLP13MU.HST history file is created each
time the Export function is started.
ΓòÉΓòÉΓòÉ 14.2.4. Preparing for the Import Phase ΓòÉΓòÉΓòÉ
Before you import the domain definitions to the new DCDB, complete the
following steps.
To Prepare to Import Domain Definitions:
1. Install the LAN Server product on the workstation that has been
designated as the new (destination) domain controller and on the
workstations designated as the additional servers. If you are migrating
in stages and need to keep your PCLP domain controller active, make sure
you designate another workstation to serve as the LAN Server domain
controller.
Note:
Select the PCLP Migration Import Utility component for
installation when installing the LAN Server product on the new
domain controller. Do not install the PCLP Migration Import
Utility on any additional servers. For more information, see the
LAN Server Network Administrator Reference Volume 1: Planning,
Installation, and Configuration.
2. Edit the temporary DCDB file to change the following:
o All occurrences of the old domain name to the new domain name (IBMDC to
LS40DC in the typical migration scenario)
o All devices (such as LPT1) to queues (such as LPT1Q) in the PRINTER
ALIASES section
Verify that the server (machine) names in the temporary DCDB file are
the same names that are in the destination domain. If they are not the
same, edit the temporary DCDB file and globally replace the PCLP server
(machine) names with the new LAN Server server (machine) names.
If you print the temporary DCDB file after the export phase has
completed, the DCDB prints in columnar form; however, the DCDB that is
displayed on your workstation (if you are using the OS/2 2.0 System
Editor) is not displayed in columnar form. To display the DCDB on your
workstation exactly as it is printed, you must change the font setting
on the System Editor by doing the following:
a. Select Options from the System Editor menu bar.
b. Select Set font from the Options menu.
c. Select the down arrow to the right of the Name field to display a
list of fonts.
d. Select Helv from the list.
e. Select OK.
3. Define and start all LAN Server servers.
4. Log on as an administrator.
5. Create a Print Manager spooler queue for each printer to be migrated.
See the operating system documentation for information about creating
spooler queues.
Notes:
1. A redirected drive cannot be used to import access control profiles.
For example, if the source domain has resources on Server1 on drive D
and the destination domain Server1 does not have a physical drive D,
the temporary DCDB file must be edited to change the drive
designation for all resources on Server1 from drive D to drive C.
For more information, see the LAN Server Network Administrator
Reference Volume 1: Planning, Installation, and Configuration.
2. Drive X: is reserved to perform the Import function.
ΓòÉΓòÉΓòÉ 14.2.5. Importing the Domain Definitions to the Destination Domain ΓòÉΓòÉΓòÉ
To import the domain definitions to the new DCDB on the destination domain,
complete the following steps at the destination domain controller.`
To Import Domain Definitions:
1. Log on as an administrator.
2. Start the Import function of the PCLP Migration Utility using the
following command:
LS12IMPO path
where the path parameter specifies the full path and file name of the
temporary DCDB file (created during the export phase). The path can
include the drive letter. For example, to start the Import function
with the temporary DCDB export file DCDB.TMP located on drive A, type
the following:
LS12IMPO A:DCDB.TMP
The Import function reads the attributes of each LAN object from the
temporary DCDB file in order and writes these attributes to the new DCDB
in the destination domain. A message is displayed on the workstation
for each object definition that is successfully written to the new DCDB.
If the Import function encounters either a duplicate server and path or
server and spooler queue combination, or cannot process an attribute, a
message indicating the error is displayed, and the function stops. The
error message is also logged in the \IBMLAN\NETPROG\LS12MU.HST file
(which also contains entries for all migration activities performed).
After you correct the error, edit the temporary DCDB file to correct the
attribute in this file as well, and then start the Import function again
using the LS12IMPO command described previously.
Notes:
a. Duplicate user, group, or resource information is ignored by the
Import function (the process does not stop). However, warning
messages that indicate the duplicate information are displayed on
the workstation and logged in the history file.
b. If you are at the C: prompt and want to print the LS12MU.HST file
to locate the error, type the following command:
TYPE LS12MU.HST > PRN
The Import function also generates new passwords for users (contained in
the \IBMLAN\NETPROG\DCDBPSWD.DAT file).
When the Import function is completed, the following message is
displayed:
Program completed successfully.
Note:
If multiple diskettes were used to export the domain definitions,
you must run the Import function on each diskette. (You will not
be prompted to insert multiple diskettes.) Be sure to process the
diskettes in the same order in which they were created. The
Import function is actually complete after the last diskette has
been processed.
If the Import function is not completed successfully, see PCLP Migration
Error Messages, look through the history file LS12MU.HST to find the
error, and correct it. If you correct an error, you must rename the
history file to preserve its entries before starting the Import function
again.
3. Secure the \IBMLAN\NETPROG\DCDBPSWD.DAT password file that was generated
by the Import function.
4. Migrate the resources from the PCLP domain controller to the LAN Server
domain controller. Include printers, serial devices, files, and
applications.
5. Migrate the contents of the users' home directories on the PCLP domain
controller to the LAN Server domain controller.
6. Optionally, use the Home Directory Conversion (HDCON) utility to convert
home directories with aliases to a new home directory format that makes
the task of sharing home directories easier to perform. The HDCON
utility can convert all users in the domain, or it can convert the users
specified at the command line. To convert all users, type the following
at the OS/2 command prompt:
HDCON -N *
For more information, see the LAN Server Network Administrator Reference
Volume 3: Network Administrator Tasks.
7. If you have an RPL.MAP file containing remote IPL machine definitions,
copy the RPL.MAP file to the appropriate subdirectory using the
following command:
COPY A:RPL.MAP C:\IBMLAN\DCDB\IMAGES
Note:
If the C:\IBMLAN\DCDB\IMAGES directory does not exist, it must be
created.
ΓòÉΓòÉΓòÉ 14.2.6. Completing the Migration ΓòÉΓòÉΓòÉ
To Complete the Migration:
1. Print the imported LAN domain definitions and verify the migrated
definitions by doing the following: dbscal='1.2'.
a. Ensure that you are still logged on as an administrator to the domain
controller.
b. Select Definitions from the Main Panel.
c. Select Print the domain definition from the Definitions menu.
d. Select the default printer (or the printer that applies to you) from
the Device Name column on the Print Domain Definition window.
2. Verify that all user logon assignments (NET USE definitions) have been
updated as required.
For example, on an existing PCLP 1.3 domain controller called IBMDC, the
directory C:\PAYROLL\PAY89 is shared with the network name PAY (with the
definition NET SHARE PAY=C:\PAYROLL\PAY89), and has the following NET
USE definition:
NET USE E: \\IBMDC\PAY
To access the PAY resource after it is migrated to the new LAN Server
domain controller (LS40DC), the NET USE definition must be changed to
the following:
NET USE E: \\LS40DC\PAY
If the names of additional servers are maintained when installing the
LAN Server product, no changes to NET USE definitions are required for
the directory resources on the additional server. For example, the
network name PAY has the following NET USE definition on an additional
server called ADSERV01:
NET USE E: \\ADSERV01\PAY
If the additional server name was maintained (ADSERV01), the NET USE
definition is still valid.
Because PCLP shares printer ports (such as LPT1 and LPT2), the network
administrator must create printer queues for the printer resources to be
shared in the LAN Server environment. For example, a printer is defined
on the existing PCLP 1.3 domain controller to be shared with the
following NET SHARE and NET USE definitions:
NET SHARE PRINT1 = LPT2
NET USE LPT3 \\IBMDC\PRINT1.
In the LAN Server environment, the NET SHARE and NET USE definitions are
as follows:
NET SHARE LPT2Q /PRINT
NET USE LPT3 \\LS40DC\LPT2Q
LPT2Q is the queue name created with the Print Manager for the migrated
printer that is attached to the LPT1 port on server LS40DC.
3. If you are migrating in stages: Give the user ID named GUEST access
permissions to those network resources on the LAN Server domain still
required by users on PCLP workstations.
4. Issue new passwords for the user IDs that require a password from the
\IBMLAN\NETPROG\DCDBPSWD.DAT file that was generated by the Import
function.
5. If you have remote IPL images that were migrated, do the following:
o If standard image names were migrated, use the LAN Server graphical
user interface to select and make each standard image used in the
RPL.MAP file.
o If nonstandard images were migrated, the network administrator must
create and make each nonstandard image. For more information, see the
LAN Server Network Administrator Reference Volume 3: Network
Administrator Tasks.
6. For the requesters in the domain:
a. If remote IPL machines will continue to be supported, create DOS LAN
Services IPL images and machine definitions to replace the PCLP 1.3
Requester IPL images and definitions. For information about how to
create these images, see the LAN Server Network Administrator
Reference Volume 3: Network Administrator Tasks.
b. Install the appropriate software on the workstations.
If the workstation will be an OS/2 requester: Verify that the
workstation is appropriately configured (memory and hard-disk space),
and install the LAN Server 4.0 product.
If the workstation will be a DOS requester: Install DOS (LAN Support
Program if installing the DOS Remote IPL service), and DOS LAN
Services. For the supported versions of DOS, refer to Software
Requirements and Compatibility.
Note:
When you install the DOS or OS/2 Remote IPL service, you must run the
RIPLINST and GETRPL utilities upon completion of the LAN Services
installation/configuration program after restarting the server. For
more detailed information about these utilities, refer to the LAN Server
Network Administrator Reference Volume 3: Network Administrator Tasks.
ΓòÉΓòÉΓòÉ 14.3. num=none.Contents of the Temporary DCDB File ΓòÉΓòÉΓòÉ
The temporary DCDB file is the output from the export phase of the LAN Server
migration process. This section describes only the numeric machine-translated
definition fields in the temporary DCDB file, which contains more definitions
than are described in this section. If you edit resource names or machine IDs,
be sure those changes are made for every occurrence in the file.
ΓòÉΓòÉΓòÉ 14.3.1. Machines ΓòÉΓòÉΓòÉ
Machine Type
1 - Additional server
2 - Remote IPL machine
ΓòÉΓòÉΓòÉ 14.3.2. Files ΓòÉΓòÉΓòÉ
Files Type
0 - Internal
1 - External and used on DOS machines
2 - External and used on OS/2 machines
3 - External and used on DOS and OS/2 machines
Share Mode
0 - At server startup
1 - By administrator action
2 - By user request
ΓòÉΓòÉΓòÉ 14.3.3. Printers ΓòÉΓòÉΓòÉ
Print Queue Type
0 - internal
1 - External and used on DOS machines
2 - External and used on OS/2 machines
3 - External and used on DOS and OS/2 machines
Share Mode
0 - At server startup
1 - By administrator action
ΓòÉΓòÉΓòÉ 14.3.4. Public Applications ΓòÉΓòÉΓòÉ
Command Line (command to start program)
Fileset for Program (alias or drive name)
(alias) - OS/2 remote (server) and DOS
(drive) - OS/2 local (requester)
Fileset to Be Made as Working Directory
(alias) - OS/2 remote (server) and DOS
(blank) - OS/2 local (requester)
Drive to Be Current
(drive) - OS/2 remote (server) and DOS
(blank) - OS/2 local (requester)
Prompt for Parameters
0 - No
1 - Yes
DOS Application
0 - No (this is an OS/2 application)
1 - Yes (this is a DOS application)
ΓòÉΓòÉΓòÉ 14.3.5. Users ΓòÉΓòÉΓòÉ
System Administrator (user type)
0 - No (a user)
1 - Yes (a system administrator)
OS/2 or DOS User (user operating system)
0 - DOS
1 - OS/2
Home Fileset Required (home directory)
0 - Not required
1 - Required
Password Required
0 - Not required
1 - Required
Logon Revoked (logon disabled)
0 - Not disabled (logon is enabled)
1 - Disabled
Application Selector (application type)
1 - Public (shared application)
Note:
Only public application is allowed. The user's private application
starter must be individually re-created.
ΓòÉΓòÉΓòÉ 14.3.6. Access Control Profiles ΓòÉΓòÉΓòÉ
Resource Type
0 - Files
1 - Printer
Profile Type
1 - Discrete
2 - Generic
Access List Values, Access Permissions (LAN Server)
0 - No access allowed
1 - Reading allowed
2 - Writing allowed
4 - Creation allowed
8 - Program execution allowed
16 - Deletion allowed
32 - Attribute change allowed
64 - Permission modification allowed
127 - Access all
128 - Permission for a group
Note:
Combinations of accesses result in the addition of the access permission
number. For example, access permission of 3 indicates that 2 (writing)
and 1 (reading) are both allowed.
Access Permission Mapping for PCLP 1.3 to LAN Server compares the access
permissions from PCLP 1.3 to the LAN Server product.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 21. Access Permission Mapping for PCLP 1.3 to LAN Server Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PCLP 1.3 Γöé LAN SERVER Γöé ACCESS Γöé
Γöé Γöé Γöé VALUE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé None Γöé No access Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Read Γöé Read, execute Γöé 9 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Write Γöé Read, execute, write, delete, attribute, permis- Γöé 127 Γöé
Γöé Γöé sions Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 14.4. PCLP Migration Error Messages ΓòÉΓòÉΓòÉ
The following section contains error messages with the prefixes of MUEXP or
MUIMP, which you might receive during the export and import phases of the
migration process. If the error message prefix is SYS or NET, the network
administrator can type HELP prefixnnnn at the OS/2 command prompt for an online
explanation of the message (prefixnnnn is the message class and number that is
displayed, for example NET2103).
MUEXP01 The PC LAN Program is not started.
Cause: You did not start the PC LAN Program.
Action: Start the PC LAN Program and try again.
MUEXP02 There is already a network administrator.
Cause: Only one network administrator can be logged on.
Action: Ensure that there is nobody logged on as network
administrator and start the Export program again.
MUEXP03 The user does not have administrator privilege.
Cause: You did not log on as an administrator.
Action: Log off and then log on as an administrator.
MUEXP04 An error occurred while creating the output file.
Cause: The specified file name may contain characters that are not
valid, or the path may not exist.
Action: Verify that the output file specified contains valid
characters. Run the Migration Utility again.
MUEXP05 The definition format file does not exist.
Cause: The format file PCLP13MU.FMT is missing.
Action: Reinstall the Export program and try again. If the problem
persists, report the problem and the method by which it can be
reproduced to your IBM support representative.
MUEXP06 An error occurred while writing to the print output file.
Cause: The target diskette may be bad.
Action: Replace the target diskette and try again. If the problem
persists, report the problem and the method by which it can be
reproduced to your IBM support representative.
MUEXP07 An internal error occurred.
Cause: The error may be caused by missing or damaged files.
Action: Check the history file and try to correct the problem. If
the problem persists, report the problem and the method by which it
can be reproduced to your IBM support representative.
MUIMP30 No user is logged on to this machine.
Cause: You did not log on before starting the Import program.
Action: Log on to the domain controller and try again.
MUIMP31 You do not have administrator privilege.
Cause: You did not log on as an administrator.
Action: Log off and then log on as an administrator.
MUIMP32 You are not logged on at the domain controller.
Cause: The workstation on which you are running this program is not
the domain controller.
Action: Log off and then log on at the domain controller.
MUIMP33 An error occurred while opening file %1.
Cause: The error usually occurs because the specified file does not
exist.
Action: Verify that the specified file exists and has the correct
name. Run the Migration Utility again.
MUIMP34 The temporary domain control database (DCDB) file contains an
unrecognized field type.
Cause: The error may be caused when a user edits the temporary DCDB
file.
Action: Check the history file and identify the record that caused
the problem. Edit the temporary DCDB file and correct the format.
MUIMP35 The temporary domain control database (DCDB) file contains an
unrecognized domain definition.
Cause: The error may be caused when a user edits the temporary DCDB
file.
Action: Check the temporary DCDB file and correct the domain
definition.
MUIMP36 An incorrect resource type is specified in the temporary DCDB file.
Cause: The error usually occurs when a user edits the temporary
domain control database (DCDB) file.
Action: Check the history file and identify the profile record that
caused the problem. Edit the temporary DCDB file and correct the
resource type in this profile record. The resource type must be one
of three values (0, 1, or 2).
MUIMP37 An incorrect profile type is specified in the temporary DCDB file.
Cause: The error usually occurs when a user edits the temporary
domain control database (DCDB) file.
Action: Check the history file and identify the profile record that
caused the problem. Edit the temporary DCDB file and correct the
profile type in this profile record. The profile type value must be
either 1 or 2.
MUIMP38 There is not enough memory to run the program.
Cause: A lot of memory is used by other programs running on this
domain controller.
Action: Stop any programs running in other OS/2 sessions and restart
the Import program.
MUIMP39 The network name cannot be found.
Cause: The error may be caused by an incorrect network name.
Action: Check the temporary domain control database (DCDB) file to
make sure the network names are correct.
MUIMP40 The network path cannot be found.
Cause: The error may be caused because a remote server does not exist
or has not been started.
Action: Check the temporary domain control database (DCDB) file to
make sure the network path is valid.
MUIMP41 The Server service is not started.
Cause: The Server service must be started before running the Import
program.
Action: Start the Server service and try again.
MUIMP42 The user ID cannot be found.
Cause: The error usually occurs when a user ID that does not exist
appears in the profiles definition record of the temporary domain
control database (DCDB) file.
Action: Check the destination domain to make sure the user ID is
defined and try again.
MUIMP43 The user ID or group ID parameter is not valid.
Cause: A user ID or group ID in the temporary domain control database
(DCDB) file may contain characters that are not valid.
Action: Check the history file and identify the user ID or group ID
that caused the problem. Change this user ID or group ID in the
temporary DCDB file and try again.
MUIMP44 The group ID cannot be found.
Cause: The error usually occurs when a group ID that does not exist
appears in the profiles definition record of the temporary domain
control database (DCDB) file.
Action: Check the destination domain to make sure the group ID is
defined and try again.
MUIMP45 The user already belongs to this group.
Cause: The error usually occurs when more than one occurrence of the
same user ID is encountered in a single record of the temporary
domain control database (DCDB) file.
Action: Check the history file and locate the user ID. Delete this
user ID from the list and restart the Migration Utility.
MUIMP46 The operation is not allowed on a special group.
Cause: An attempt was made to delete one of the special groups such
as USERS, ADMINS, or GUESTS.
Action: Delete the special group from the temporary domain control
database (DCDB) file and try again.
MUIMP47 The specified server cannot be located.
Cause: The error may be caused by an incorrect server name.
Action: Check the temporary domain control database (DCDB) file to
make sure all the server names are correct.
MUIMP48 The netname has already been shared.
Cause: The Import program attempted to share a netname that is
already in use.
Action: Check the history file and identify the netname. Delete this
netname and try again.
MUIMP49 The operation is not allowed on a redirected resource.
Cause: The Import program attempted to perform an operation that is
not permitted on a redirected device.
Action: Specify devices that are not redirected, or delete the
assignments to the redirected devices.
MUIMP50 The print queue or print destination does not exist.
Cause: The specified print queue or print destination was not created
prior to starting the Import program.
Action: Check the printer section of the temporary domain control
database (DCDB) file to identify the spooler queue names. Create the
necessary print destinations. Try again.
MUIMP51 The temporary DCDB file contains too many permission records.
Cause: The number of group and user permission records in a profiles
record exceeds the maximum allowed.
Action: If migrating from a PCLP 1.3 domain:
1. Determine sets of users with matching access permissions to the
resource.
2. Delete these permissions and rerun the export and import phases.
3. Create a new group definition on the LAN Server x.x domain and add those
users whose permissions were removed to the new group.
4. Give the group access permissions to the resources that match those of
the removed users.
If migrating from a LAN Server 1.0 domain:
1. Define new groups of users to the LAN Server 1.0 domain.
2. Delete users with similar access permissions from the profile that
exceeded the limit and add them to the newly defined group.
3. Give the groups access permissions to the resources that match those of
the removed users.
MUIMP52 The device cannot be shared as both a spooled and a nonspooled
resource.
Cause: You cannot route requests from both a printer queue and a
serial device queue to the same device.
Action: Delete the existing shares for the device or select another
device for this share.
MUIMP53 There are no more file handles available.
Cause: There are too many open files on this domain controller.
Action: Close some files and try again.
MUIMP54 The disk is full.
Cause: The disk drive containing the \IBMLAN directory is full.
Action: Delete files to create more disk space and try again.
MUIMP55 An error occurred while reading from or writing to a file.
Cause: The I/O error may be caused by a bad device or media.
Action: Try again. If the problem persists, run the Export program
again to create a new temporary domain control database (DCDB) file
that uses a different media or device.
MUIMP56 An error occurred while creating a home fileset directory.
Cause: A drive is bad, or a redirected drive is already in use.
Action: Check the import history file to identify the home directory
drive. Examine this drive to locate the problem. Correct the
problem and try again.
MUIMP57 The server and path or spooler queue combination is defined by
another alias.
Cause: The Import program attempted to create an alias for a path or
a spooler queue that is already defined by another alias.
Action: Determine why the other alias also uses the same UNC name.
Delete the existing alias, or delete the redundant alias from the
temporary domain control database (DCDB) file and try again.
MUIMP58 There are too many entries in a domain definition.
Cause: The error may be caused by a format error in the temporary
domain control database (DCDB) file.
Action: Check the temporary DCDB file to make sure each definition
has the correct end-of-entry (EOE) and end-of-record (EOR) markers.
MUIMP59 An error occurred while creating the specified path.
Cause: The error may be caused by a path that is not valid.
Action: Verify that the path format is valid for the operating system
being used.
MUIMP60 The accounts database is full.
Cause: There are too many names in the user account system.
Action: If possible, delete the access control records of some
resources and try again. If the problem persists, report the problem
and the method by which it can be reproduced to your IBM support
representative.
MUIMP61 An error occurred while accessing the accounts database.
Cause: The error can be caused by a damaged accounts database file or
a hardware problem with the disk drive.
Action: Print the domain definition and correct any network database
errors. If the problem persists, use your most recent database
backup.
MUIMP62 An error occurred while accessing the workstation record.
Cause: The error may occur when the LAN is not started.
Action: Start the server and try again. If the problem persists,
report the problem and the method by which it can be reproduced to
your IBM support representative.
MUIMP63 An incorrect parameter was specified.
Cause: This problem may be caused by an error in the code or by a
damaged IMPORT.EXE file.
Action: Stop all applications currently running, reinstall the server
code, and restart the Migration Utility. If the problem persists,
report the problem and the method by which it can be reproduced to
your IBM support representative.
MUIMP64 An incorrect system-call level was specified.
Cause: This problem may be caused by an error in the code or by a
damaged IMPORT.EXE file.
Action: Stop all applications currently running, reinstall the server
code, and restart the Migration Utility. If the problem persists,
report the problem and the method by which it can be reproduced to
your IBM support representative.
MUIMP65 The API return buffer is not large enough.
Cause: This problem may be caused by an error in the code or by a
damaged IMPORT.EXE file.
Action: Stop all applications currently running, reinstall the server
code, and restart the Migration Utility. If the problem persists,
report the problem and the method by which it can be reproduced to
your IBM support representative.
MUIMP66 A remote API error has occurred.
Cause: This error may be caused by a problem at a remote server.
Action: Check the history file to identify which record caused the
problem. Identify the server name in the record and ensure that the
server has been started. If the problem persists, report the problem
and the method by which it can be reproduced to your IBM support
representative.
MUIMP67 An internal error occurred when calling the workstation driver.
Cause: An incorrect NETWKSTA.SYS driver may be installed.
Action: Stop all applications currently running, reinstall the
requester and server code, and restart the Migration Utility. If the
problem persists, report the problem and the method by which it can
be reproduced to your IBM support representative.
MUIMP68 An error occurred while accessing the domain control database (DCDB)
files.
Cause: The checksum of information stored in the DCDB files may be
incorrect. Write errors, restarts during writes, or a power failure
occurred.
Action: Restore the DCDB from a backup and restart the Migration
Utility. If the problem persists, report the problem and the method
by which it can be reproduced to your IBM support representative.
MUIMP69 A protection violation has occurred.
Cause: This problem may be caused by an error in the code.
Action: Reinstall the server code. If the problem persists, report
the problem and the method by which it can be reproduced to your IBM
support representative.
MUIMP70 The specified file name or path name was not found.
Cause: The specified file name or path name may not exist or may
contain characters that are not valid.
Action: Check the history file to identify which record caused the
problem. Identify the path name or file name in the record and
ensure that it exists. If the problem persists, report the problem
and the method by which it can be reproduced to your IBM support
representative.
MUIMP71 The network directory or device name is incorrect.
Cause: A network directory or device name in the temporary domain
control database (DCDB) file may contain characters that are not
valid.
Action: Examine the temporary DCDB file and correct the device name.
If the problem persists, report the problem and the method by which
it can be reproduced to your IBM support representative.
MUIMP72 The local device name is already in use.
Cause: The device name specified in the temporary domain control
database (DCDB) file is already in use.
Action: Check the history file and identify the device name. Edit
the record in the temporary DCDB file that contains this device name
and change the name. If the problem persists, report the problem and
the method by which it can be reproduced to your IBM support
representative.
ΓòÉΓòÉΓòÉ 15. Configuration Considerations ΓòÉΓòÉΓòÉ
This appendix helps you determine the values of some configuration parameters
in the IBMLAN.INI and PROTOCOL.INI files for OS/2 LAN Server.
For a more extensive discussion of IBMLAN.INI parameter values and their effect
on system performance, refer to the LAN Server Network Administrator Reference
Volume 2: Performance Tuning.
The LAN Server Tuning Assistant is available to assist you in configuring and
performance tuning your server. It does not give exactly the same results as
this appendix, but it is recommended, because it does a number of checks for
error conditions.
The PROTOCOL.INI file is the LAN Adapter and Protocol Support configuration
file. LAN Adapter and Protocol Support (LAPS) is part of the IBM
Multi-Protocol Transport Services - AnyNet for OS/2 product, which is shipped
with the LAN Server product. Refer to the MPTS - AnyNet for OS/2:
Configuration Guide for an example.
Note:
Do not change any default parameter that you do not understand.
ΓòÉΓòÉΓòÉ 15.1. Calculating IEEE 802.2 and NetBIOS Resources for OS/2 LAN Servers ΓòÉΓòÉΓòÉ
You can use the following tables to calculate capacity-related parameters in
the IBMLAN.INI and PROTOCOL.INI configuration files. Network resources
required for only LAN servers are considered. In addition, you need to
consider any other applications that use these configuration files, such as
DATABASE 2 OS/2 or Communications Manager/2. If you install the LAN Server
program and either the Communications Manager/2 or the DATABASE 2 OS/2 program,
you need additional IEEE 802.2 and OS/2 NetBIOS resources not reflected in
these tables.
After calculating the required values for your IBMLAN.INI and PROTOCOL.INI
configuration files, change the current values as follows:
o Use an ASCII text editor to modify values in the IBMLAN.INI file.
o Reconfigure LAPS to modify values in the PROTOCOL.INI file.
ΓòÉΓòÉΓòÉ 15.1.1. IBMLAN.INI File ΓòÉΓòÉΓòÉ
The following two parameters in the IBMLAN.INI file may need adjustment for
your environment after installation. For detailed information on the IBMLAN.INI
file, refer to the LAN Server Network Administrator Reference Volume 2:
Performance Tuning.
o netx
o maxusers
ΓòÉΓòÉΓòÉ 15.1.1.1. Netx Statement (in Networks Section) ΓòÉΓòÉΓòÉ
For each logical adapter selected on the LAN Adapters window during LAN
Services installation and configuration, a netx statement is generated in the
Networks section of the IBMLAN.INI file.
The netx statement has the following format:
netx=NETBEUI$,a,pdt,x1, x2, x3
where:
x Specifies a number distinguishing each netx statement. The LAN
Services installation/configuration program adds the net1
statement to the IBMLAN.INI file if logical adapter 0 is
selected; it adds the net2 statement if logical adapter 1 is
selected; and so on.
NETBEUI$ Specifies the NetBIOS protocol driver.
a Specifies the logical adapter number as defined on the Configure
Workstation window. This variable must have a value of 0 through
3 and cannot have the same value in two different netx
statements referencing the NetBIOS protocol driver.
pdt Specifies the protocol driver type. Possible values are LM10
for the NetBEUI driver and MB30 for the NetBIOS driver.
x1 Specifies the number of NetBIOS sessions the requester
allocates. The default is 102.
x2 Specifies the number of simultaneous NetBIOS commands (network
control blocks) a requester or server can post. The default is
175.
x3 Specifies the number of NetBIOS names the requester allocates.
For detailed information on the netx statement, refer to the LAN Server Network
Administrator Reference Volume 2: Performance Tuning.
Calculations for the x1, x2, and x3 operands follow.
ΓòÉΓòÉΓòÉ 15.1.1.1.1. Netx Parameter, x1 Operand (NetBIOS sessions) ΓòÉΓòÉΓòÉ
Calculate the value of the x1 operand as follows:
x1 = a + b + c + d + e + f + g
Determine the value of each variable as indicated in the following table.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 22. Netx Parameter, x1 Operand Calculation (NetBIOS sessions) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé VARIABLE Γöé APPLICABLE WORK- Γöé SETTING Γöé YOUR Γöé
Γöé Γöé STATIONS Γöé Γöé VALUE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé a Γöé Domain controller Γöé 1 per additional server (if any) Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé b Γöé Additional server Γöé 1 for domain controller Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé c Γöé Remote IPL server Γöé 1 for each remote IPL requester to Γöé Γöé
Γöé Γöé Γöé be IPLed simultaneously Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé d Γöé Server Γöé 1 for each OS/2 LAN Requester and Γöé Γöé
Γöé Γöé Γöé each DOS LAN Requester Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé e Γöé Server Γöé 1 if the Messenger service is Γöé Γöé
Γöé Γöé Γöé running; 0 otherwise Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé f Γöé Server Γöé 2 if a user is logged on at the Γöé Γöé
Γöé Γöé Γöé server; 0 otherwise Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé g Γöé Server Γöé 1 session per server being Γöé Γöé
Γöé Γöé Γöé accessed outside the domain; Γöé Γöé
Γöé Γöé Γöé 0 otherwise Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇTotal: Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 15.1.1.1.2. Netx Parameter, x2 Operand (NetBIOS commands) ΓòÉΓòÉΓòÉ
Calculate the value of the x2 operand as follows:
x2 = 2 x x1
Your value: ____
Note:
If many requesters are accessing the network simultaneously, you might
need to increase this value.
ΓòÉΓòÉΓòÉ 15.1.1.1.3. Netx Parameter, x3 Operand (NetBIOS names) ΓòÉΓòÉΓòÉ
Calculate the value of the x3 operand as follows:
x3 = 14 (default value)
Your value: 14
ΓòÉΓòÉΓòÉ 15.1.1.2. Maxusers (in Server Section) ΓòÉΓòÉΓòÉ
Calculate the value of the maxusers parameter as follows:
maxusers = a + b + c
Determine the value of each variable as indicated in the following table.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 23. Maxusers Calculation Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé VARIABLE Γöé APPLICABLE WORK- Γöé SETTING Γöé YOUR Γöé
Γöé Γöé STATIONS Γöé Γöé VALUE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé a Γöé Domain controller Γöé 1 per additional server (if any) Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé b Γöé Remote IPL server Γöé 1 for each remote IPL requester to Γöé Γöé
Γöé Γöé Γöé be IPLed simultaneously Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé c Γöé Server Γöé 1 for each OS/2 LAN Requester and Γöé Γöé
Γöé Γöé Γöé each DOS LAN Requester Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇTotal: Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 15.1.2. PROTOCOL.INI File ΓòÉΓòÉΓòÉ
The following parameters in the PROTOCOL.INI file may need adjustment for your
environment after installation. For detailed information on the PROTOCOL.INI
file, refer to the MPTS - AnyNet for OS/2: Configuration Guide.
o For the IBM OS/2 NetBIOS protocol driver:
- NCBS
- NAMES
- SESSIONS
o For the IBM IEEE 802.2 protocol driver:
- MAX_SAPS
- USERS
ΓòÉΓòÉΓòÉ 15.1.2.1. NCBS Parameter (NetBIOS) ΓòÉΓòÉΓòÉ
Calculate the value of the NCBS parameter as follows:
NCBS = 2 x (SESSIONS)
Your value: ____
Note:
If many requesters are accessing the network simultaneously, you may
need to increase this value.
ΓòÉΓòÉΓòÉ 15.1.2.2. NAMES Parameter (NetBIOS) ΓòÉΓòÉΓòÉ
Calculate the value of the NAMES parameter as follows:
NAMES = a + b + 1
Determine the value of each variable as indicated in the following table.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 24. NAMES Calculation Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé VARIABLE Γöé APPLICABLE WORK- Γöé SETTING Γöé YOUR Γöé
Γöé Γöé STATIONS Γöé Γöé VALUE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé a Γöé Server Γöé x3 operand of the NETx parameter Γöé Γöé
Γöé Γöé Γöé in the IBMLAN.INI file Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé b Γöé Server Γöé 2 if a user is logged on at the Γöé Γöé
Γöé Γöé Γöé server; 0 otherwise Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1 Γöé Server Γöé Reserved for NetBIOS software Γöé 1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇTotal: Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 15.1.2.3. SESSIONS Parameter (NetBIOS) ΓòÉΓòÉΓòÉ
Calculate the value of the SESSIONS parameter as follows:
SESSIONS = a
Determine the value of the variable as indicated in the following table.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 25. SESSIONS Calculation Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé VARIABLE Γöé APPLICABLE WORK- Γöé SETTING Γöé YOUR Γöé
Γöé Γöé STATIONS Γöé Γöé VALUE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé a Γöé Server Γöé x1 operand of the NETx parameter Γöé Γöé
Γöé Γöé Γöé in the IBMLAN.INI file Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇTotal: Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 15.1.2.4. MAX_SAPS Parameter (IEEE 802.2) ΓòÉΓòÉΓòÉ
Calculate the value of the MAX_SAPS parameter as follows:
MAX_SAPS = a + b
Determine the value of each variable as indicated in the following table.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 26. MAX_SAPS Calculation Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé VARIABLE Γöé APPLICABLE WORK- Γöé SETTING Γöé YOUR Γöé
Γöé Γöé STATIONS Γöé Γöé VALUE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé a Γöé Remote IPL server Γöé 2 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé b Γöé Server Γöé 1 per IEEE 802.2 application; Γöé Γöé
Γöé Γöé Γöé 0 otherwise Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇTotal: Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 15.1.2.5. USERS Parameter (IEEE 802.2) ΓòÉΓòÉΓòÉ
Calculate the value of the USERS parameter as follows:
USERS = a + b
Determine the value of each variable as indicated in the following table.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 27. USERS Calculation Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé VARIABLE Γöé APPLICABLE WORK- Γöé SETTING Γöé YOUR Γöé
Γöé Γöé STATIONS Γöé Γöé VALUE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé a Γöé Remote IPL server Γöé 1 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé b Γöé Server Γöé 1 per IEEE 802.2 application; Γöé Γöé
Γöé Γöé Γöé 0 otherwise Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇTotal: Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 15.2. Calculating Resources for OS/2 Remote IPL Servers ΓòÉΓòÉΓòÉ
If you are installing the OS/2 Remote IPL service on your server, you need to
adjust some configuration parameters in the IBMLAN.INI and PROTOCOL.INI files.
The value of these parameters depends on the number of remote IPL requesters
supported by the server. Use the following guidelines to make your
calculations. These guidelines take into account only the requirements for
remote IPL. Add the figure for remote IPL to other requirements, such as
communication with nonremote IPL requesters and other servers. Maximum values
are given for reference.
After calculating the required values for your IBMLAN.INI and PROTOCOL.INI
configuration files, change the current values as follows:
o Use an ASCII text editor to modify values in the IBMLAN.INI file.
o Reconfigure LAPS to modify values in the PROTOCOL.INI file. For configuration
information, see step Tailored Installation in the Tailored installation
procedure or the IBM Multi-Protocol Transport Services - AnyNet for OS/2.
If starting the remote IPL requesters causes problems after you adjusted
parameters according to the following guidelines, check the error log at the
remote IPL server. If the log indicates that a network resource was exhausted,
increase the corresponding parameter.
ΓòÉΓòÉΓòÉ 15.2.1. IBMLAN.INI File ΓòÉΓòÉΓòÉ
The following parameters in the Server and Remoteboot sections of the
IBMLAN.INI file may need adjustment for your environment after installation of
the Remote IPL service. For more information about these parameters and their
interdependency on other parameters, refer to the LAN Server Network
Administrator Reference Volume 2: Performance Tuning.
In the following information, n stands for the number of supported OS/2 remote
IPL requesters.
ΓòÉΓòÉΓòÉ 15.2.1.1. Server Section ΓòÉΓòÉΓòÉ
Parameter Value
numreqbuf 4 x n
Maximum value: 408
maxopens n x (65 + maximum number of user files opened per
workstation, including applications and data files)
Maximum value: 8000
Note:
This parameter is not needed for a remote IPL 386-HPFS server.
maxsessopens 100 + maximum number of user files opened per workstation,
including applications and data files
Note:
This parameter is not needed for a remote IPL 386-HPFS server.
ΓòÉΓòÉΓòÉ 15.2.1.2. Remoteboot Section ΓòÉΓòÉΓòÉ
Parameter Value
maxthreads 6
For large environments, increasing this parameter might
decrease performance. Specify a value that is not greater
than 6.
ΓòÉΓòÉΓòÉ 15.2.2. PROTOCOL.INI File ΓòÉΓòÉΓòÉ
The following parameters may need adjustment for your environment if you are
installing the Remote IPL service. For detailed information on the PROTOCOL.INI
file, refer to the MPTS - AnyNet for OS/2: Configuration Guide.
In the following information, n stands for the number of supported OS/2 remote
IPL requesters; m stands for the number of both OS/2 and DOS remote IPL
requesters.
Parameter Value
NCBS 4 x n
SESSIONS m
ΓòÉΓòÉΓòÉ 16. Language Support and Code Page Considerations ΓòÉΓòÉΓòÉ
The following information discusses available languages and code page
considerations. The LAN Server product is available in the following languages:
o Canadian French
o French
o German
o Italian
o Japanese
o Korean
o Norwegian
o Spanish
o Swedish (only DOS LAN Services and the DOS LAN Services and Windows User's
Guide)
o Taiwanese (Traditional Chinese)
o U.K. English
o U.S. English
ΓòÉΓòÉΓòÉ 16.1. General Code Page Considerations ΓòÉΓòÉΓòÉ
The default code page for the U.S. is 437. If code page switching is to be
used, use only the uppercase characters A through Z and digits 0 through 9 when
assigning names to users and resources and when creating files and directories.
This practice prevents problems when switching between code pages and their
associated name-character capitalization rules.
Resources named with characters other than A through Z or digits 0 through 9
should be accessed using the same country code and code pages with which they
were created. If either the country code or code page is set to a different
value, this user may be unable to log on. If you change the code page after
logging on and then encounter problems, change back to your original code page.
ΓòÉΓòÉΓòÉ 16.2. Code Page Considerations for DOS LAN Services Windows ΓòÉΓòÉΓòÉ
All servers and requesters in a domain should use the same code page. However,
Windows supports only the ANSI character set, and OS/2 and DOS support several
code pages. The differences in code pages may cause problems. Characters may
not print or display correctly when sent from a workstation running Windows to
a workstation running OS/2 or DOS. In addition, when logging on using DOS LAN
Services Windows, users might encounter problems with user IDs, passwords, and
domains that use extended characters.
To limit these problems, DOS LAN Services Windows uses OEM-to-ANSI and
ANSI-to-OEM conversion routines to convert data passed between Windows and
non-Windows workstations. These conversion routines use tables that are
supplied by Windows to map the correlation between the ANSI character set and
the code pages supported by non-Windows workstations. These tables allow
characters to be presented accurately whether a user is using Windows, DOS, or
OS/2.
Because DOS LAN Services Windows does these conversions automatically, be
careful when using the extended characters available through Windows. The
conversion routines are sometimes forced to do an approximate conversion when
an ANSI character does not exist in the OS/2 or DOS code page. If the routines
are forced to do an approximate conversion, the routines map to the closest
character possible.
For example, if Windows was installed with code page 437 and you are running
with a domain code page 437, many of the uppercase diacritic characters
available through Windows are not available in code page 437. The uppercase
characters A-dieresis (О), A-acute (╡), and A-grave (╖) do not exist in code
page 437 and are converted to the same uppercase A by the AnsiToOem conversion
routine. If a conversion routine is not used, the previous characters are
represented as nondisplayable characters on a non-Windows display. In code page
437, most of the line-drawing characters available are converted to plus signs
(+), dashes (-), and vertical lines (|) on a Windows display.
If Windows was installed with code page 850, the conversion routines use a
different conversion table and most of the diacritic characters are converted
correctly. Conversions are done when DOS LAN Services Windows sends or receives
data between Windows and non-Windows workstations.
Note:
To minimize problems when using Windows with DOS LAN Services, avoid
using extended ASCII characters when defining user IDs, domain names,
alias names, and so forth. Users who log on at workstations running DOS
LAN Services with Windows may encounter problems resulting from
approximate character conversions performed by the OEM-to-ANSI and
ANSI-to-OEM conversion routines.
For the conversion routines to run correctly, load the same active code page in
Windows that is loaded on the workstation. DOS LAN Services Windows supports
conversion tables for the following OS/2 and DOS code pages:
o 437
o 850
o 860
o 863
o 865
Because of code page differences between DOS LAN Services Windows and the LAN
Server product, Windows documents might not print correctly on network
printers.
ΓòÉΓòÉΓòÉ 17. Upgrading LAN Server 2.0 or 3.0 ΓòÉΓòÉΓòÉ
This appendix assists you in upgrading a LAN Server 2.0 or 3.0 domain to a LAN
Server 4.0 environment.
Upgrading a domain involves installing and configuring an existing LAN Server
2.0 or 3.0 domain controller as a LAN Server 4.0 domain controller.
Note:
Remember that while the domain definitions and existing resources are
being upgraded to the new LAN Server domain and the new environment is
being set up, the server cannot provide logon service to users on the
domain.
The LAN Server product allows you to upgrade any of the following:
o OS/2 1.3 with LAN Server 2.0-Entry (FAT)
o OS/2 1.3 with LAN Server 2.0-Entry (HPFS)
o OS/2 1.3 with LAN Server 2.0-Advanced (386 HPFS)
o OS/2 2.0 with LAN Server 2.0-Entry (FAT)
o OS/2 2.0 with LAN Server 2.0-Entry (HPFS)
o OS/2 2.0 with LAN Server 2.0-Advanced (386 HPFS)
o OS/2 2.0 with LAN Server 3.0-Entry (FAT)
o OS/2 2.0 with LAN Server 3.0-Entry (HPFS)
o OS/2 2.0 with LAN Server 3.0-Advanced (386 HPFS)
o OS/2 2.1 with LAN Server 3.0-Entry (FAT)
o OS/2 2.1 with LAN Server 3.0-Entry (HPFS)
o OS/2 2.1 with LAN Server 3.0-Advanced (386 HPFS)
These systems can be upgraded to:
o OS/2 2.0 with LAN Server 4.0-Entry (FAT)
o OS/2 2.0 with LAN Server 4.0-Entry (HPFS)
o OS/2 2.0 with LAN Server 4.0-Advanced (386 HPFS)
o OS/2 2.1 with LAN Server 4.0-Entry (FAT)
o OS/2 2.1 with LAN Server 4.0-Entry (HPFS)
o OS/2 2.1 with LAN Server 4.0-Advanced (386 HPFS)
Notes:
1. A LAN Server 2.0 server with the capability to remotely IPL OS/2 1.3
requesters on the domain does not maintain this capability when upgraded
to the LAN Server product. (SBCS systems only).
2. For information about the compatibility of server and requester
workstations installed with previous releases of OS/2 LAN Requester and
OS/2 LAN Server, refer to Compatibility among Servers and Requesters.
ΓòÉΓòÉΓòÉ 17.1. Preparing the Network and User Community ΓòÉΓòÉΓòÉ
Upgrading from a LAN Server 2.0 or 3.0 environment to a LAN Server 4.0-Entry or
LAN Server 4.0-Advanced environment may require a hardware upgrade for the
servers. For information about system, memory, and hard-disk space requirements
for the LAN Server product, see Planning Your Network. For information about
performing a simultaneous upgrade of hardware and software on a server, see
Upgrading Server Hardware and Software Simultaneously.
Notify users about the upgrade to the new product release and about the
expected schedule (when users can expect interruptions in service).
To reduce disruption of service to users on the domain, you can upgrade domain
controllers, backup domain controllers, and additional servers remotely during
off-peak hours. For more information, refer to Upgrading LAN Server 2.0 or 3.0
Using the LAN CID Utility.
ΓòÉΓòÉΓòÉ 17.2. Upgrading an Attended Server ΓòÉΓòÉΓòÉ
This procedure describes the steps required for the most complex attended
upgrade scenario (upgrading a server with the 386 HPFS and Fault Tolerance
installed).
If any of the following conditions apply, you must also reinstall or upgrade
OS/2 on the workstation:
o You want Fault Tolerance and there are only two hard disks on the
workstation, or you want Local Security. You must have a primary partition
on the hard disk containing the startup drive.
o You do not have the required level of OS/2 (2.1 or higher).
o You want to change file systems or disk partitions.
If you plan to format the drive or reinstall OS/2, pay special attention to the
steps explaining how to back up files (for example, user applications, the
DCDB, and access control profiles) using the BACKACC, BACKUP, NET COPY, or
XCOPY command.
Some of the following steps require using OS/2 BACKUP and RESTORE commands.
Make sure that these commands are available on the server before you start
upgrading. If you upgrade or reinstall the operating system during your
upgrade, ensure that you install all the OS/2 options required for the LAN
Server product (see Installation Requirements and Restrictions).
To Upgrade an Attended Server:
1. Stop all LAN Server services.
Ensure that all users are logged off and that none of the resources on
the server are being used during the upgrade process. Otherwise, the
backup procedures cannot be completed successfully.
2. If you are upgrading a server with Local Security for the 386 HPFS
installed, log on locally as an administrator.
3. Use the BACKACC utility to back up the user accounts file (NET.ACC), the
audit information file (NET.AUD), and the access control profiles.
Insert Requester - Disk 1 in drive A, and type the following at an OS/2
command prompt:
A:BACKACC d:\ /S /V
where d is the drive containing the file permissions to be backed up.
The optional /V parameter causes the names of the access control files
to be displayed as they are being backed up. The /S parameter backs up
all descendent subdirectories.
Notes:
a. If the server being upgraded supports many aliases or users with
home directories, the BACKACC process may take some time. For
example, it may take over an hour to run the BACKACC utility on
networks with more than 100 aliases or 200 users with home
directories.
b. If you are upgrading the LAN Server 2.0 or 3.0-Advanced product to
the LAN Server 4.0-Advanced product, you are not strictly required
to run the BACKACC and RESTACC utilities. In such a case use the
PREPACL utility referred to in step 9 to back up and restore the
386HPFS access control profiles. However, running the BACKACC
utility as described in the present step can help you recover in
case of accidental loss of information.
For more information about the BACKACC utility, see the LAN Server
Network Administrator Reference Volume 3: Network Administrator Tasks.
The contents of the files are saved as follows:
o NET.ACC is saved to \IBMLAN\ACCOUNTS\NETACC.BKP.
o NET.AUD is saved to \IBMLAN\LOGS\NETAUD.BKP.
o File permissions are saved to \IBMLAN\ACCOUNTS\ACLBAKd.ACL (where d is
a drive letter).
Note:
Run the BACKACC utility for each logical drive that you are
converting to or from the 386 HPFS
4. If you are formatting the hard disk or resetting the DCDB, save the
backup file for NET.ACC (NETACC.BKP), the backup file for NET.AUD
(NETAUD.BKP), and the \IBMLAN\DCDB directory and all its subdirectories.
If you want to format the hard disk or reset the DCDB, use the OS/2
BACKUP command (at an OS/2 command prompt) to save the following
subdirectories and files to a diskette or to a hard disk that will not
be formatted during the upgrade:
o \IBMLAN\DCDB and all subdirectories
o \IBMLAN\ACCOUNTS\NETACC.BKP
o \IBMLAN\LOGS\NETAUD.BKP
o \IBMLAN\ACCOUNTS\ACLBAKd.ACL (where d is a drive letter).
Note:
You can also use the steps documented in the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks to
back up this information to an additional server.
5. Record the printer and queue definitions from Print Manager or from
printer objects.
6. Record the LAN Server tuning parameters.
This information is contained in the IBMLAN.INI file.
Note:
The LAN Services installation/configuration program preserves the
IBMLAN.INI file if you do not format the drive on which the
IBMLAN.INI file resides when installing OS/2 2.1 (step 10).
7. If you are formatting the hard drive or if you have a reason to back up
user applications and associated directories (for example, changing file
systems or partitions), back up all user application programs and
associated directories. Proceed in one of the following ways:
o Back up to tape.
o Use the NET COPY or XCOPY command to back up to another shared drive on
another server.
o From the OS/2 command prompt, use the BACKUP command to back up to
diskettes or to a hard disk that will not be formatted during the
upgrade procedure.
8. If you are upgrading from a LAN Server 2.0-Advanced server with Fault
Tolerance installed, use the FTSETUP utility to unmirror and deactivate
any currently mirrored drives on which you plan to install the LAN
Server product, OS/2 2.0, LAPS, or Corrective Service Diskettes (CSDs).
This step is required to ensure that installed files are not mirrored to
another partition during the upgrade process.
For the procedures on unmirroring and deactivating drives, see the LAN
Server Network Administrator Reference Volume 3: Network Administrator
Tasks.
9. If you are reinstalling, or upgrading from a LAN Server 2.0-Advanced
server with the 386 HPFS installed, do the following:
a. Follow the procedure in Attended Installation. The step-by-step
instructions run the PREPACL utility to temporarily remove and save
the access control profiles from all OS/2 subdirectories and the
\IBM386FS subdirectory. This utility is required because the 386-HPFS
drives are protected by access control profiles, and the OS/2
installation program is unable to access such files.
b. Next, you are instructed to install OS/2 and then run the THIN386 to
create a modified 386 HPFS on which you can install the LAN Server
3.0-Advanced product.
c. After you follow the instructions to install the LAN Server product,
the final step is to run the PREPACL utility again to restore the
access control profiles removed earlier.
10. If any of the conditions on page Upgrading an Attended Server apply,
install OS/2 2.1 or higher on the workstation. See the operating system
documentation for installation information.
If you want to install Fault Tolerance on a server and you have only two
hard disks, you must specify a primary HPFS partition size on the hard
disk containing the startup drive. This specification enables space for
other partitions. To specify a primary HPFS partition during operating
system installation, refer to Disk Requirements for Fault Tolerance and
the OS/2 installation documentation. Make sure you have sufficient
hard-disk storage on your primary partition. Some LAN Server components
such as UPM are always installed on the startup drive. To calculate
hard-disk requirements, see Hard-Disk Estimating Worksheet for OS/2 LAN
Server Workstations.
Note:
When you install OS/2 2.1, you optionally can format the hard disk
where OS/2 2.1 will be located. You can change your partition
size or change your file system from FAT to HPFS.
Make sure to apply the latest CSD program updates. For a list, refer to
Current Corrective Service Diskette (CSD) Levels.
11. Run the LAN Services installation/configuration program to install LAN
Server 4.0-Entry or LAN Server 4.0-Advanced. Follow the Tailored
installation path described in Tailored Installation while keeping the
following in mind:
a. If you did not format the drive on which you are installing the LAN
Server product, on the Reinitialize Domain Control Database window,
select Do not reinitialize the domain control database.
Notes:
1. If you select Reinitialize the domain control database, the
existing DCDB will be erased.
2. This procedure assumes that you are installing the LAN Server
product on the same drive as the LAN Server 2.0 or 3.0 product.
If you plan to install the LAN Server product on a different
drive and want to migrate the DCDB and access control
information, read Upgrading or Reinstalling on a Different Hard
Disk.
Upgrading or Reinstalling on a Different Hard Disk requires you
to run the installation and configuration program twice.
3. If you want to upgrade a LAN Server 2.0 or 3.0 additional
server to a LAN Server 4.0 backup domain controller, change its
role during installation on the Server Type window.
4. Do not install Local Security for the 386 HPFS at this time.
If you do, the NET.ACC file becomes a locked file, and the
remaining steps of the upgrade procedure cannot be completed
properly.
b. Edit the AUTOEXEC.BAT file, and REM out the NET START REQ statement.
This ensures that no network services will be started when you
restart your workstation.
c. Restart the workstation. After restarting, do not log on locally;
doing so blocks the restoration of the NET.ACC file.
12. If you did not format your hard disk in step 10, skip this step.
Restore the printer and queue definitions from Print Manager, as
recorded in step 5. You can create a printer object with the necessary
printer details.
13. If you formatted the hard disk or if you lost data during the upgrade,
restore any user application programs and associated files and
directories that you saved in step 7.
Use the RESTORE command (at an OS/2 command prompt) to perform this step
if the BACKUP command was used to save the files.
14. If necessary (for example, if your drive was formatted in step 10),
restore the \IBMLAN\DCDB directory and the NET.ACC file (saved in steps
3 and 4).
Perform this step if either of the following applies:
o You reformatted the drive where this information was previously
located.
o The DCDB was accidentally overwritten because you selected Reinitialize
the domain control database (in step 11a).
You must use the restoration method that corresponds to the backup
method used:
o If you used the OS/2 BACKUP command in step 4, use the OS/2 RESTORE
command to restore the information.
o If you used the steps in the LAN Server Network Administrator Reference
Volume 3: Network Administrator Tasks to save the \IBMLAN\DCDB
directory, the NET.ACC file, and the NET.AUD file in step 4, use the
steps for restoring information that are also documented in that book.
Restore the information as follows:
a. Make sure that the Server service is not running on the network (step
11b stopped all network services). If necessary, restart the network,
but do not start the Server service.
b. Create a temporary directory, using the MD command.
c. Restore the backed up files to the newly created directory.
d. Copy NETACC.BKP from the temporary directory to NET.ACC in the
\IBMLAN\ACCOUNTS directory.
e. Copy NETAUD.BKP from the temporary directory to NET.AUD in the
\IBMLAN\LOGS directory.
f. Copy ACLBAKd.ACL (where d is the drive letter) from the temporary
directory to the same name in the \IBMLAN\ACCOUNTS directory.
g. Ensure that the files have been copied correctly, and then do the
following:
1. Delete the files in the temporary directory.
2. Change to the parent directory, using the CD command.
3. Remove the temporary directory, using the RD command.
15. If you used the BACKACC utility in step 3, restore the access control
information using the RESTACC utility.
Perform this step if either of the following applies:
o You reformatted the drive where this information was previously
located.
o The DCDB was overwritten because you selected Reinitialize the domain
control database (in step 11a).
The RESTACC utility restores the access control information for the
386 HPFS. Access control information in ACLBAKd.ACL (restored to the
\IBMLAN\ACCOUNTS directory in the previous step) is restructured in the
386HPFS file structure. If the program encounters errors while
restoring the access control profiles, error messages are displayed.
Correct any errors and then run the RESTACC utility again.
Type the following at an OS/2 command prompt:
RESTACC d:\ /S
where d is the drive letter specified in ACLBAKd.ACL.
The file permissions are extracted from ACLBAKd.ACL and assigned
appropriately.
For more information about the RESTACC utility, see the LAN Server
Network Administrator Reference Volume 3: Network Administrator Tasks.
Note:
Run the RESTACC utility for each logical drive that was backed up
by BACKACC.
16. If you are upgrading from a LAN Server 2.0 or 3.0-Advanced server with
Fault Tolerance installed, run the FTSETUP utility to remirror drives
for Fault Tolerance. You can also mirror new drives at this time.
For Fault Tolerance procedures, see the LAN Server Network Administrator
Reference Volume 3: Network Administrator Tasks.
17. Tune the LAN Server server.
If your original server supported many aliases or users on the domain,
you may need to modify the \IBMLAN\IBMLAN.INI file by restoring the
values of your original IBMLAN.INI file. This step helps ensure that
your LAN has adequate resources for startup. Also, the LAN Server
Tuning Assistant is available to assist you in configuring and
performance tuning your server. For information on capacity and
performance tuning, consult the LAN Server Network Administrator
Reference Volume 2: Performance Tuning.
During LAN Server installation, the old IBMLAN.INI file was saved to the
\IBMLAN\BACKUP directory as IBMLAN.nnn, where nnn is a sequence number
(001, 002, and so on) depending on the number of times the previous
version of the LAN Server product was installed.
If you formatted the drive on which the IBMLAN.INI file resides when
installing OS/2 2.1 (step 10), you should have recorded the IBMLAN.INI
tuning parameters as instructed in step 6.
18. Edit the AUTOEXEC.BAT file, and take out the REM in the NET START REQ
statement.
19. Shut down and restart the workstation. The LAN Server server is now
ready for use.
20. If you installed the OS/2 Remote IPL service, you must run the RIPLINST
utility to copy OS/2 2.0 to the remote IPL subdirectory. For more
detailed information about the RIPLINST utility, refer to the LAN Server
Network Administrator Reference Volume 3: Network Administrator Tasks.
21. If you installed the DOS or OS/2 Remote IPL service, you must run the
GETRPL utility to enable successful access from a remote IPL requester
to the directory resources at the server during startup. For more
detailed information about the GETRPL utility, refer to the LAN Server
Network Administrator Reference Volume 3: Network Administrator Tasks.
ΓòÉΓòÉΓòÉ 17.3. Completing Upgrading the Domain ΓòÉΓòÉΓòÉ
To Complete the Upgrade:
o You can upgrade any LAN Server 2.0 or 3.0 OS/2 LAN Requester workstations
to LAN Server 4.0 OS/2 LAN Requester workstations.
o You can upgrade any LAN Server 2.0 or 3.0 additional servers to LAN Server
4.0 additional servers.
o If you are using LAN Server-Advanced and you want to use Local Security
for the 386 HPFS, you can use the LAN Services installation/configuration
program to install Local Security on the servers.
ΓòÉΓòÉΓòÉ 17.4. Upgrading Server Hardware and Software Simultaneously ΓòÉΓòÉΓòÉ
Use the following procedure to upgrade a server's hardware and software
simultaneously while maintaining a built-in backup server. These steps can be
used to upgrade a domain controller, a backup domain controller, or an
additional server. This procedure begins with a down-level server and an
OS/2 2.X workstation without the LAN Server product installed.
To Upgrade Server Hardware and Software Simultaneously:
1. On the new server, install OS/2 2.1 or higher and LAPS, making sure to
install options required for the LAN Server product. For more
information on installation requirements, refer to Installation
Requirements and Restrictions.
The hard-disk space of drives on the new server must be the same or
larger than the hard-disk space of drives on the original server. Also,
make the drive labels on the new server and original server identical.
2. On the new server, run the LAN Services installation/configuration
program to install LAN Server 4.0-Entry or LAN Server 4.0-Advanced.
Follow the Tailored installation path described in Tailored Installation
while keeping the following in mind:
o If you are using the Tailored installation path, do not install Local
Security on the 386 HPFS at this time. Otherwise, you cannot complete
the upgrade process. Local Security can be installed after the upgrade
is complete.
o Configure the server to support the required number of users. The
domain name and server type (domain controller, backup domain
controller, or additional server) should be identical to the original
server. However, specify a different server name on the Server and
Domain Names window.
o On the Start Server window, select Do not start the server
automatically.
3. Use the LAN to copy information from the old server to the new server:
a. On the new server, type NET START REQ. Do not start the Server
service on the new server at this time.
b. From the new server, log on to the original domain as an
administrator.
c. Use the NET COPY or XCOPY command to copy all the directories and
subdirectories of \IBMLAN\DCDB and \IBMLAN\USERS from the original
domain controller to the new one. These subdirectories must be
shared for the NET COPY or XCOPY command to be completed
successfully.
d. Use the NET COPY or XCOPY command to copy to the new server all the
directories and subdirectories of any aliases that are being shared
by the original server.
4. Stop all server and requester services on both the original and new
server.
5. On the new server, edit the IBMLAN.INI file and change the server name
to the name of the original server. In this case, the server name is
specified by the computername parameter in the IBMLAN.INI file. You can
also increase any tuning parameter values (if necessary) to meet the
values of your original server.
6. On the new server, insert a blank formatted diskette into a drive and
execute the following commands:
COPY C:\IBMLAN\NETPROGS\BACKACC d:
COPY C:\IBMLAN\NETPROGS\RESTACC d:
where d specifies the drive in which the diskette resides.
7. On the original server, insert the diskette into drive A, and type the
following at an OS/2 command prompt:
A:BACKACC C:\ /S /V
This command backs up the NET.ACC and NET.AUD file and saves all the
access control profiles for drive C. The optional /V parameter causes
the names of the access control files to be displayed as they are being
backed up. Repeat the process for all the drives of your original
server (D, E, and so on).
8. Back up the following directories and files to the diskette or an unused
location on your hard disk:
o \IBMLAN\DCDB and all subdirectories
o \IBMLAN\ACCOUNTS\NETACC.BKP
o \IBMLAN\LOGS\NETAUD.BKP
o \IBMLAN\ACCOUNTS\ACLBAKd.ACL (where d is a drive letter)
9. Copy the saved files back to the hard disk in their original directories
on the new server:
o Edit the CONFIG.SYS file, and disable (by adding REM at the beginning
of the line) all DEVICE and SET statements that contain the directory
IBMLAN. Save and exit the CONFIG.SYS file.
o Shut down and restart the new server.
o Copy NETACC.BKP to NET.ACC. (Note that NET.ACC would be a locked file
if you had started any LAN Server services such as Local Security.)
o Copy NETAUD.BKP to NET.AUD.
o Copy the ACLBAKd.ACL files to the \IBMLAN\ACCOUNTS directory (where d
is a drive letter).
o Edit the CONFIG.SYS file, and enable (remove the REM on) the DEVICE and
SET statements containing the directory IBMLAN. Save and exit the
file.
o Shut down and restart the new server.
10. On the new server, type RESTACC C:\ /S at an OS/2 command prompt. This
command restores the access control profiles on drive C. Repeat this
command for drive D, and so on. If the program encounters errors while
restoring the access control profiles, error messages are displayed.
Correct any errors and then run the RESTACC utility again.
11. Your DCDB is restored. You can now run the LAN Services
installation/configuration program from the hard disk on the new server
to install Local Security (Advanced Package).
12. On the new server, run the LAN Services installation/configuration
program to change the server startup from manual to automatic. Follow
the Tailored installation path described in Tailored Installation. When
the Start Server window is displayed, select Start server automatically.
13. Start the new server on a local domain to ensure that it works. Change
the server type and name of the original server to that of additional
server or backup domain controller (if one does not already exist). Do
not start the original server unless its name has been changed. The
original server is on the same domain as the new server and having both
active would cause conflicts. Avoid starting servers with the same name
in a single domain.
ΓòÉΓòÉΓòÉ 17.5. Hints for Upgrading ΓòÉΓòÉΓòÉ
The following hints may be useful for certain situations.
Hints:
o If you are formatting your drive, make sure that you do not select Local
Security if you are upgrading to a 386-HPFS server. After running RESTACC
and restoring your DCDB, you can run the LAN Services
installation/configuration program from the hard disk to install Local
Security.
o The FIXACC utility allows you to restore information in a damaged NET.ACC
file. Type the following command at an OS/2 command prompt:
FIXACC
Make sure that UPM is not running and that the Requester service has not
been started.
ΓòÉΓòÉΓòÉ 18. Upgrading or Reinstalling on 386-HPFS Servers ΓòÉΓòÉΓòÉ
This appendix helps you install or reinstall OS/2 and the LAN Server product.
4.0-Advanced on 386-HPFS servers.
Read the information and follow the instructions in this appendix if you plan
to perform any of the following tasks:
o Upgrade a LAN Server 2.0 or 3.0-Advanced workstation to LAN Server
4.0-Advanced workstation
o Reinstall OS/2 on a LAN Server 4.0-Advanced workstation
o Install a new OS/2 release on a LAN Server 4.0-Advanced workstation
Note:
If you are only reinstalling LAN Server 4.0-Advanced and not making any
changes to your current operating system, follow the installation
instructions in Installing OS/2 LAN Server(local installation) or Remote
Installation. Skip this appendix.
Because OS/2 uses its own file system (OS/2 HPFS) to read and write files
during installation, it cannot access files and directories that are protected
by 386-HPFS access control profiles. To bypass this potential problem and make
required files accessible to ensure proper installation, the LAN Server product
provides the following two utilities:
o PREPACL utility
Helps you back up, remove, and restore all 386-HPFS access control profiles
applied to any subdirectories or files that are required during installation.
The PREPACL utility also enables the installation of the THIN386 utility.
You must run the PREPACL utility twice (once to remove access control
profiles and once to restore them) during an attended installation of OS/2
and LAN Server-Advanced on a 386-HPFS server. The PREPACL utility is not
required during an unattended remote installation.
o THIN386 utility
Creates a temporary 386 HPFS that enables OS/2 to access files protected by
386-HPFS access control profiles during LAN Server installation. The THIN386
utility is not required if the PREPACL utility has been run.
You must run the THIN386 utility after an attended installation of OS/2
before installing LAN Server-Advanced on a 386-HPFS server. The THIN386
utility is also required for CSDS.
The THIN386 utility is also used during an unattended remote installation of
OS/2 and LAN Server-Advanced on a 386-HPFS server initiated by the LAN CID
Utility.
Both the PREPACL and THIN386 utilities are provided on the CD-ROM or
installation diskettes.
This appendix helps you understand how the PREPACL and THIN386 utilities work,
provides step-by-step instructions about when and how to run these utilities
during an attended installation, and explains how 386 HPFS access control
profile protection is handled during an unattended remote installation with the
LAN CID Utility.
ΓòÉΓòÉΓòÉ 18.1. Attended Installation ΓòÉΓòÉΓòÉ
Step-by-step instructions to install OS/2 and LAN Server-Advanced on a 386-HPFS
server are provided in Procedure. Read How It Works first to understand what
happens in each installation step.
ΓòÉΓòÉΓòÉ 18.1.1. How It Works ΓòÉΓòÉΓòÉ
Initially, you must run the PREPACL utility to remove and save the access
control profiles from all files and subdirectories that need to be accessed
during installation. The PREPACL utility allows you to use one or both of the
following to specify the files and subdirectories:
o A user-defined list
o An internal list
Notes:
1. For a detailed explanation of the PREPACL parameters and syntax, see
PREPACL Command Syntax.
2. The name and location of the OS/2 internal checklist, if it exists, is:
d:\OS2\INSTALL\CHECKACL.LST
where d is the startup drive.
Each installable product for which access control profiles have to be
removed from certain files to ensure proper installation has an entry in
the CHECKACL.LST file. The entry for the LAN Server product is:
d:\OS2\INSTALL\IBMLSACL.LST
where d is the startup drive. The IBMLSACL.LST file contains a list of
the 386-HPFS files on the startup drive that need to be replaced or
deleted to enable THIN386 installation.
After running the PREPACL utility, you are ready to install OS/2.
Note:
If the internal checklist (CHECKACL.LST) exists, the OS/2 installation
utility checks whether the access control profiles have been removed
from all the files that need to be accessed to ensure proper
installation of OS/2 and various OS/2 applications, such as LAN Server.
This step is done before making any changes on the hard disk.
For the purpose of LAN Server installation, OS/2 checks that the access
control profiles have been removed from the files listed in the
IBMLSACL.LST file, if it exists.
During this verification process, any 386-HPFS files on the startup
drive from which access control profiles have not been removed are
listed in the \OS2\INSTALL\LOCKACL.LST file. If the installation is
successful, this file is later deleted.
After installing OS/2, install the THIN386 utility, which unzips the 386-HPFS
files that work with OS/2 and places them in the d:\IBM386FS directory (where d
is the startup drive). This utility replaces the IFS statement in the
CONFIG.SYS file with a new IFS statement to enable the newly installed THIN386
utility. After you shut down and restart the workstation, the 386-HPFS files
are accessible, and you can successfully run the LAN Services
installation/configuration program to install the LAN Server-Advanced product.
The LAN Services installation/configuration program generates an IBMLSACL.LST
file and replaces a previous version of this file (if any) to reflect the new
386-HPFS files currently installed under OS/2 on the startup drive.
Finally, run the PREPACL utility to restore the access control profiles that
were removed at the beginning of the procedure.
ΓòÉΓòÉΓòÉ 18.1.2. Procedure ΓòÉΓòÉΓòÉ
Follow this procedure only if you are performing a local CD-ROM- or
diskette-based installation of OS/2. You can install the LAN Server
4.0-Advanced product either locally or remotely (lightly or fully attended).
Notes:
1. This procedure does not apply to an installation initiated by the LAN
CID Utility.
2. If you must start your workstation from 386-HPFS startup diskettes (for
example, in case of a hard-disk failure), refer to Using the 386-HPFS
Startup Diskettes to Run the PREPACL Utility before you continue.
Complete the following procedures (installing OS/2 and the LAN Server
4.0-Advanced product) at one time, especially if Local Security for the
386HPFS is running on the workstation and the workstation has critical security
requirements. (Local Security is disabled during this installation procedure.)
Do not leave your workstation unattended.
You can run the PREPACL and THIN386 utilities from CD-ROM or diskette, or you
can run them from the remote installation subdirectory on the code server if
you have copied the LAN Server product diskettes as described in Copying LAN
Server Product Diskettes to the Code Server.
This procedure illustrates simple uses of the PREPACL and THIN386 commands. For
information on the use of other parameters, refer to PREPACL Command Syntax and
THIN386 Command Syntax.
To Run the PREPACL Utility:
Note:
If you are running the PREPACL utility remotely, skip step 1 and
modify step 2 accordingly.
1. Insert Server - Disk 1 into drive A.
2. At the [A:\] prompt, type:
PREPACL /P /DL:filename /B:filename
where:
/P Specifies that the 386-HPFS access control profiles be removed
in preparation for OS/2 installation.
/DL Specifies the ASCII file containing a list of subdirectories
from which to remove access control profiles. For example, if
OS/2 is currently installed on your workstation, list the
following subdirectories in this file:
c:\NOWHERE
c:\OS!2 2.0 DESKTOP
c:\OS2
c:\PSFONTS
c:\SPOOL
c:\IBM386FS
where c is the restart drive.
Note:
If you do not specify the /O parameter, the PREPACL utility
uses the internal checklists generated by the OS/2 and LAN
Server installation programs in addition to your list (see How
It Worksfor more information about internal checklists.)
/B Specifies the file in which to save the access control
profiles.
Press Enter.
Note:
For detailed information about the PREPACL command syntax and
other parameters, see PREPACL Command Syntax.
Warning:
Be aware that your workstation is no longer secure. Complete the
following steps before leaving it unattended.
To Install OS/2:
1. After PREPACL is complete, install OS/2. Follow the instructions in the
OS/2 installation documentation.
2. When the OS/2 installation is complete, shut down the workstation from
the OS/2 desktop, and then press Ctrl+Alt+Del to restart it.
To Run the THIN386 Utility:
Note:
If you are running the THIN386 utility remotely, skip step 1 and
modify step 2 accordingly.
1. Insert Server - Disk 1 into drive A.
2. At the [A:\] prompt, type:
THIN386 /B:d: /T:d:\IBM386FS
where:
/B Specifies the startup drive where the CONFIG.SYS file is
located.
/T Specifies the path in which to install the temporary 386 HPFS.
In this case, the temporary 386 HPFS must be installed in the
\IBM386FS subdirectory on the startup drive.
Press Enter.
Note:
See THIN386 Command Syntax for detailed information about the
THIN386 command syntax and other parameters.
3. Shut down the workstation from the OS/2 desktop, and then press
Ctrl+Alt+Del to restart it.
All files managed by the 386 HPFS are now accessible.
Install LAN Server 4.0-Advanced
Install the LAN Server product following the instructions provided in
Installing OS/2 LAN Server (local installation) or Remote Installation.
To Run the PREPACL Utility:
Note:
If you are running the PREPACL utility remotely, skip step 1 and
modify step 2 accordingly.
1. Insert Server - Disk 1 into drive A.
2. At the [A:\] prompt, type:
PREPACL /R /B:d:\path\filename
where:
/R Specifies that the access control profiles be restored.
/B Specifies the file containing the access control profiles to be
restored.
Press Enter.
Note:
See PREPACL Command Syntax for detailed information about the
PREPACL command syntax and other parameters.
ΓòÉΓòÉΓòÉ 18.2. Unattended Remote Installation ΓòÉΓòÉΓòÉ
The removal of access control profiles by the PREPACL utility as described for
attended installation of OS/2 and the LAN Server product is not required during
a remote installation initiated by an SDM such as the LAN CID Utility. Instead,
the THIN386 is installed twice. This double installation eliminates the need
to remove access control profiles.
The THIN386 utility is installed initially when the maintenance subdirectory is
being created. As a result, when the maintenance subdirectory is started,
access to all files (including files protected by 386-HPFS access control
profiles) is provided. During the installation of all products (entire
installation operation without intermittent restarting of the workstation), the
THIN386 utility is installed again in the d:\IBM386FS subdirectory.
When the workstation is restarted, the LAN Server 4.0-Advanced product can be
installed successfully, because the most recent installation of the THIN386
utility allows the LAN Services installation/configuration program to access
the LAN Server files on the target workstation.
Creating a REXX Command File lists the commands that must be included in a REXX
command file used by the LAN CID Utility to upgrade a remote LAN Server
workstation. REXX Command File Example illustrates the THIN386-specific
information that must be included in a REXX command file used to upgrade a
386-HPFS workstation. Refer to the LAN CID Utility Guide for detailed
information about installations initiated by the LAN CID Utility.
ΓòÉΓòÉΓòÉ 18.3. PREPACL Command Syntax ΓòÉΓòÉΓòÉ
Consult the following for detailed information on the PREPACL syntax.
Note:
The PREPACL command can be run on the following workstations:
o OS/2 1.3 workstation with the LAN Server 2.0 product installed
o OS/2 2.0 workstation with the LAN Server product installed
o OS/2 2.11 workstation with the LAN Server product installed
Syntax
o To remove access control profiles:
PREPACL /P [/FL:filename|/DL:filename|/D:dirname] /B:filename|/N
[/L1:e:\path\filename] [/L2:f:\path\filename]
[/O] [/LR:g:\path]
o To restore access control profiles:
PREPACL /R /B:d:\path\filename [/L1:e:\path\filename]
[/L2:f:\path\filename]
Parameters
/P Specifies that the 386 HPFS access control profiles be removed in
preparation for OS/2 installation.
/R Specifies that previously removed access control profiles be
restored.
/FL Specifies an ASCII file containing a list of files from which to
remove access control profiles. All access control profiles for the
specified files and paths to those files are removed.
For example, if you specify /FL:A:\filename1, and the specified
filename1 contains the entry C:\X\filename2, the access control
profiles associated with the following files, directories, and paths
are removed:
┬╖ C: (drive)
┬╖ C:\ (root directory)
┬╖ C:\X (subdirectory)
┬╖ C:\X\filename2 (file name)
This parameter is optional and cannot be used with the /DL or /D
parameters.
/DL Specifies an ASCII file containing a list of subdirectories from
which to remove access control profiles. If the /DL parameter is
specified, access control profiles associated with the following
files, directories, and paths are removed:
o Specified subdirectories in the list
o All files in the specified subdirectories
o All drives and subdirectories in the path of the specified subdirectories
o All subdirectories and files contained in subdirectories under the
specified subdirectories. For example, if you specify /DL:A:\filename, and
the specified filename contains the entry C:\, the entire C drive is
affected.
The /DL parameter is optional and cannot be used with the /FL or /D
parameters.
/D Specifies a single subdirectory from which to remove access control
profiles.
Note:
The effect of this parameter is identical to the effect of the /DL
parameter followed by a file that contains only one subdirectory.
This parameter is optional and cannot be used with the /FL or /DL
parameters.
/B When removing access control profiles, specifies the name of a file
in which to save the access control profiles. If this parameter is
not used, /N must be specified.
When restoring access control profiles, specifies the file containing
the access control profiles to be restored.
/N Specifies that the access control profiles should be removed but not
backed up. If this parameter is not used, /B must be specified.
/L1 Specifies a remote error log in addition to the
\OS2\INSTALL\IBMLANER.LOG file on the local workstation. This
parameter is optional. It is primarily used when you are running the
PREPACL utility remotely.
/L2 Specifies a remote history log in addition to the
\OS2\INSTALL\IBMLSHST.LOG file on the local workstation. This
parameter is optional. It is primarily used when you are running the
PREPACL utility remotely.
/O Specifies that access control profiles be removed using only the /FL,
/DL, or /D parameters set in this command. If this parameter is not
specified, the PREPACL utility uses the /FL, /DL, or /D parameters in
addition to any internal checklists generated by the OS/2 and the LAN
Server installation programs (see How It Works for more information
about internal checklists).
/LR Specifies the path to the \IBMLAN subdirectory. Specify this
parameter only if you run the PREPACL utility under the operating
system started up from the 386-HPFS diskette, for example, in case of
a hard-disk failure (see Using the 386-HPFS Startup Diskettes to Run
the PREPACL Utility).
ΓòÉΓòÉΓòÉ 18.4. THIN386 Command Syntax ΓòÉΓòÉΓòÉ
Consult the following for detailed information on the THIN386 syntax.
Note:
The THIN386 command can be run only on an OS/2 workstation.
Syntax
THIN386 /B:d: /T:e:\path [/L1:f:\path\filename] [/L2:g:\path\filename]
Parameters
/B Specifies the startup drive where the CONFIG.SYS file is located.
/T Specifies the path in which to install the temporary 386 HPFS. If the
subdirectory does not exist, it is created.
Note:
Specify a subdirectory on the OS/2 startup drive.
/L1 Specifies a remote error log other than the \OS2\INSTALL\IBMLANER.LOG
file on the local workstation. This parameter is optional. It is
primarily used when you are running the THIN386 utility remotely.
/L2 Specifies a remote history log other than the
\OS2\INSTALL\IBMLSHST.LOG file on the local workstation. This
parameter is optional. It is primarily used when you are running the
THIN386 utility remotely.
ΓòÉΓòÉΓòÉ 19. Upgrading LAN Server 2.0 or 3.0 Using the LAN CID Utility ΓòÉΓòÉΓòÉ
If you have a large network, you may want to use a software distribution
manager (SDM), such as the LAN Configuration Installation Distribution Utility
(LAN CID Utility), to upgrade multiple workstations remotely. The LAN CID
Utility allows you to install and upgrade several products remotely using only
one command file. When the installation is initiated with the LAN CID Utility,
upgrading of product code proceeds without requiring anyone's presence at the
target workstation. This unattended upgrading is convenient if you have many
servers to upgrade or if you have several products in addition to the LAN
Server product to install or upgrade.
Note:
The LAN CID Utility is part of the MPTS product, which is shipped with
the LAN Server product. For detailed information on the LAN CID
Utility, refer to the LAN CID Utility Guide.
ΓòÉΓòÉΓòÉ 19.1. Preparing for Unattended Remote Upgrading ΓòÉΓòÉΓòÉ
Before proceeding, read Installation Requirements and Restrictions and make
sure the following conditions are met:
o If you plan to upgrade a LAN Server 2.0 or 3.0 server with Fault Tolerance
currently installed, you must use FTREMOTE or FTSETUP to unmirror and
deactivate any mirrored drives on which you plan to install OS/2 2.0, LAPS,
or the LAN Server product.
Notes:
1. After the upgrade is complete, use FTREMOTE or FTSETUP to remirror
your original drives and, if desired, create new mirrored drives.
2. For information on the FTSETUP and FTREMOTE utilities, refer to the
LAN Server Network Administrator Reference Volume 3: Network
Administrator Tasks.
o If you are upgrading servers that currently have Local Security installed,
you must run the LAN Services installation/configuration program to remove
Local Security (see Removing) before starting an unattended remote
installation.
o Prepare for remote installation by completing the tasks described in Remote
Installation Procedure, steps 2 through 4.
ΓòÉΓòÉΓòÉ 19.2. Creating a REXX Command File ΓòÉΓòÉΓòÉ
To install or upgrade remotely, create a REXX command file that can be
interpreted by the LAN CID Utility. The command file should contain commands
that execute the installation steps required for each product.
The following overview describes the commands necessary to upgrade the LAN
Server 2.0 or 3.0 product remotely with the LAN CID Utility.
Note:
For more information on creating REXX files and on the utilities
referred to in the following steps, refer to the LAN CID Utility Guide
and the MPTS - AnyNet for OS/2: Configuration Guide.
A REXX command file for a remote upgrade can contain commands that perform the
following steps.
1. Run BACKACC to back up access control information on FAT and HPFS drives.
This precautionary step helps prevent accidental loss of this information.
Place the backup files on the code server.
2. Run NET COPY or XCOPY to back up the DCDB. This precautionary step helps
prevent accidental loss of this information. Place the backup files on the
code server.
3. Create a minimal OS/2 system (maintenance system) using the OS/2 SEMAINT
utility.
4. Run the THIN386, THINLAPS, THINIFS, and CASINSTL utilities to create a
temporary file system that enables the installation of OS/2 2.0 over
OS/2 1.3.
The target workstation is automatically restarted when these utilities are
complete.
Note:
The THIN386 utility is required only if the 386 HPFS is currently
installed on the target workstation.
5. Install OS/2 2.0 (using the SEINST utility) and the THIN386, LAPS, THINIFS,
and CASINSTL utilities.
The target workstation is automatically restarted when these utilities are
complete.
Note:
The THIN386 utility is required only if the 386 HPFS is currently
installed on the target workstation.
6. Install the LAN Server product using the LANINSTR command described in
Starting a Lightly Attended Remote Installation. The LAN Services
installation/configuration program detects that the installation command is
being run under an SDM and automatically goes into unattended mode.
Note:
If you plan to restore your printer queues or DCDB, or use RESTACC,
do not install Local Security at this time. Install Local Security
after the upgrade is complete.
7. If you need them, restore the printer queues and DCDB.
8. If you need to access control information, run RESTACC to restore it.
9. If you need them (for example, if you formatted your drive), copy
NETACC.BKP to NET.ACC and NETAUD.BKP to NET.AUD, and restore \IBMLAN\DCDB.
10. If you need Local Security, run the LAN Services installation/configuration
program to install it.
ΓòÉΓòÉΓòÉ 19.3. REXX Command File Example ΓòÉΓòÉΓòÉ
The following examples illustrate portions of a LAN CID Utility REXX command
file that upgrades an OS/2 1.3 workstation with the LAN Server 2.0-Advanced
product to OS/2 2.1 and the LAN Server 4.0-Advanced product.
Note:
The example file does not contain product-specific information or run
installation steps for BACKACC, NETCOPY, or XCOPY. Refer to the
README.DOC file for example files using these utilities and for example
files for upgrading requester workstations.
To upgrade a 386-HPFS workstation, the REXX command file must specify to
install a temporary mini-386 HPFS (THIN386) twice. The following portion of
your REXX command file defines the product-specific information to install the
THIN386 remotely:
x.thin386 = 14 /* structure index */
x.14.name='THIN386' /* product name */
x.14.statevar = '' /* state variable name */
x.14.instprog = 'x:\img\ls30\thin386 ',
/* fully qualified install program name */
' /b:' || bootdrive , /* - config.sys location */
' /t:' || bootdrive ||'\service\temp386 ', /* path to temporary HPFS */
'/l1:x:\log\386hpfs.log' /* log file */
x.14.rspdir = '' /* no auto selection */
x.14.default = ''
x.sec386 = 15 /* structure index */
x.15.name='SEC386' /* product name */
x.15.statevar = '' /* state variable name */
x.15.instprog = 'x:\img\ls30\thin386 ',
/* fully qualified install program name */
' /b:' || bootdrive , /* - config.sys location */
' /t:' ||bootdrive || '\ibm386fs ', /* - path for final HPFS */
'/l1:x:\log\386hpfs2.log' /* log file */
x.15.rspdir = '' /* no auto selection */
x.15.default = ''
The x.thin386 section is included for the first installation of the THIN386
used with the maintenance version of OS/2 2.1.
Note:
The maintenance version of OS/2 2.1 is a skeleton operating system used
before installing the full version of OS/2 2.1. The THIN386 utility
must be installed after each installation of the operating system.
Place the first installation of the THIN386 utility in a subdirectory of the
temporary directory used by the maintenance version of OS/2 2.1. The temporary
OS/2 directory and all its subdirectories are removed after the installation of
the full version of OS/2 2.1.
The x.sec386 section is included for installing the THIN386 utility. in the
standard location (the IBM386FS directory).
The following portion of the REXX command file shows the installation of
products used to upgrade an OS/2 1.3 workstation with the LAN Server
2.0-Advanced product to OS/2 2.1 and the LAN Server 4.0.-Advanced product.
Each product in the command file has a section of product-specific information
similar to the sections illustrated for the THIN386 utility. Note the two
different installations of the THIN386 utility (x.thin386 and x.sec386)
following the installation of two different versions of the operating system
(x.semaint and x.seinst).
OVERALL_STATE = GetEnvironmentVars()
Do Forever
Select
when OVERALL_STATE = 0 then do
if BootDriveIsDiskette() == YES then iterate
/* Check if started from diskette; if it was, then goto state 1 */
if RunInstall(x.semaint) == BAD_RC then exit /* Install maintenance sys */
if RunInstall(x.thin386) == BAD_RC then exit /* run THIN386 utility */
if RunInstall(x.laps_prep) == BAD_RC then exit /* Install LAPS prep system */
if RunInstall(x.thinifs) == BAD_RC then exit /* Install SRVIFS requester */
if RunInstall(x.casinstl) == BAD_RC then exit /* Install LCU */
Call CheckBoot /* Restart if it was requested */
end
when OVERALL_STATE = 1 then do
if RunInstall(x.seinst) == BAD_RC then exit /* Install operating system */
if RunInstall(x.sec386) == BAD_RC then exit /* run THIN386 utility */
if RunInstall(x.laps) == BAD_RC then exit /* Install LAPS */
if RunInstall(x.thinifs) == BAD_RC then exit /* Install SRVIFS requester */
if RunInstall(x.casinstl) == BAD_RC then exit /* Install LCU */
Call CheckBoot /* Restart if it was requested */
end
when OVERALL_STATE = 2 then do
if RunInstall(x.laninstr) == BAD_RC then exit /* Install LS */
Call CheckBoot /* Restart if it was requested */
end
when OVERALL_STATE = 3 then do
if RunInstall(x.ifsdel) == BAD_RC then exit /* Delete SRVIFS requester */
if RunInstall(x.casdelet) == BAD_RC then exit /* Delete LCU */
Call Reboot /* Restart */
end
end
end
exit
ΓòÉΓòÉΓòÉ 19.3.1. Starting a Remote Upgrade ΓòÉΓòÉΓòÉ
When the REXX command file and necessary response files are ready, you can
start the remote upgrade procedure. This section briefly explains how this
works. Refer to the LAN CID Utility Guide for detailed information.
Because NetBIOS has already been installed on the target workstation, you can
run the LAN CID Utility without startup diskettes. You must run the LAN CID
Utility without startup diskettes if you are installing the THIN386 utility (as
in this example).
To Start a Remote Upgrade:
1. Make sure that the code server is running and the LAN CID Utility REXX
command file and any necessary response files for the target workstation
are properly configured and residing on the code server.
2. At the target workstation, run the THINIFS utility from the MPTS
Utilities diskette to install the Service Installable File System
(SRVIFS) on a hard disk on the target workstation (see the example at
the end of this section).
3. Use CASINSTL to install the LAN CID Utility on the target workstation
(see the example at the end of this section).
4. Shut down and restart the target workstation to initiate the remote
installation.
For convenience, you can create a .CMD file that performs steps 2 and 3, place
that file on the MPTS Utilities diskette, and use it to upgrade multiple
workstations; for example:
a:\srvifs\thinifs /T:c: /S:a:\srvifs /TU:c: /D:x /REQ:%1 /SRV:lidaa
a:\lcu\casinstl /TU:c /CMD:x:\client /PL:x:\dll;x:\img\lcu /PA:x:\img\lcu /0
/L2:x:\log\lcu\srvifs_req.log\
The command file is set up so that to start it you must type the target
workstation name after the command file name. The target workstation is
substituted for the %1 variable in the file. The LAN CID Utility then checks
the code server for the LAN CID Utility REXX command file that uses that name.
The REXX command file drives the actual installation.
ΓòÉΓòÉΓòÉ 20. Creating 386-HPFS Startup Diskettes ΓòÉΓòÉΓòÉ
You need to use 386-HPFS startup diskettes to start a 386-HPFS workstation that
can no longer be started, for example, in case of a hard-disk failure. A
regular HPFS startup diskette, such as an OS/2 installation diskette, cannot
access files or directories with access control profiles. Therefore, create
386-HPFS startup diskettes if you installed LAN Server-Advanced on your
workstation. You can create the 386-HPFS startup diskettes during installation
(you will be prompted), or manually after the installation using the steps in
this appendix. In the second case, create the startup diskettes immediately
after the installation before any hard-disk problems occur. Otherwise, you may
have to reformat the hard disk and reinstall OS/2 and LAN Server.
This appendix helps you create 386-HPFS startup diskettes and use them to start
a workstation.
Two startup diskettes are required to start a 386-HPFS workstation:
Startup Diskette 1 Replaces the OS/2/Installation Diskette of which it is
an unaltered copy.
Startup Diskette 2 Replaces OS/2 Installation/Diskette 1 of which it is a
modified copy.
Note:
If you installed OS/2 from CD-ROM, you must make diskettes from the
CD-ROM before beginning the following procedure.
After installing OS/2 and LAN Server on the workstation, create Startup
Diskette 2 in one of two ways: either use the MAKEDISK utility or create
Startup Diskette 2 manually. It is recommended you use the MAKEDISK utility.
ΓòÉΓòÉΓòÉ 20.1. Creating 386-HPFS Startup Diskettes with the MAKEDISK Utility ΓòÉΓòÉΓòÉ
After you have installed OS/2 and LAN Server on the workstation, proceed as
follows to create a backup copy of the OS/2/Installation Diskette and the OS/2
Installation/Diskette 1.
To Create 386-HPFS Startup Diskettes, Using the MAKEDISK Utility:
1. Make sure you have available two blank, formatted diskettes of the same
size as the diskettes in your OS/2 installation package. Insert the
original diskettes, one at a time, into drive A, and type at the OS/2
command prompt:
DISKCOPY A: A:
Press Enter and follow the instructions on the screen.
2. When copying is complete, label the copy of the OS/2/Installation
Diskette Startup Diskette 1, and put it aside. Use the copy of the OS/2
Installation/Diskette 1 to create Startup Diskette 2.
3. If, during the LAN Server installation, you selected Fault Tolerance,
you must run the FTSETUP command from the command line. When the
FTSETUP command finishes, restart your workstation.
4. Insert the copy of the OS/2 Installation/Diskette 1 into drive A and
start the MAKEDISK utility by typing at the OS/2 command prompt:
MAKEDISK
Specify a drive letter (for example, D:) only if you normally start your
workstation from a drive other than C.
Note:
The MAKEDISK utility makes a modified copy of the OS/2
Installation/Diskette 1 by altering some files and deleting others
to provide space for 386-HPFS system-related files, which are
copied from the workstation's root directory on the startup drive.
If you are using nonstandard hardware such as RAID technology or
non-IBM CD-ROM, make sure you copy necessary files to diskette 2
and make necessary changes in the CONFIG.SYS file (also on
diskette 2). Failure to do so may result in not being able to see
devices when starting your workstation from these diskettes.
Press Enter, and follow the instructions on the screen.
The MAKEDISK utility makes a modified copy of the OS/2
Installation/Diskette 1 by altering some files and deleting others to
provide space for 386-HPFS system-related files, which are copied from
the workstation's root directory on the startup drive.
Warning:
The MAKEDISK utility copies the \IBM386FS\DISKFT.SYS and
C:\FTCFG.SYS files to the diskette it creates. As a result, this
set of diskettes become unique to the system from which they were
created. Once a set of diskettes has been made, ANY change to the
disk configuration (for example, partition changes or mirroring)
requires an update to the FTCFG.SYS file on the 386-HPFS startup
diskettes. Use the MAKEDISK /FT command to update your 386-HPFS
diskettes. When the MAKEDISK utility copies Fault Tolerance
information to the diskettes, a message is displayed indicating
the uniqueness of the diskettes to the particular machine from
which the files have been copied. Refer to the MAKEDISK utility in
LAN Server Network Administrator Reference Volume 3: Network
Administrator Tasks.
5. When the MAKEDISK utility is complete, remove the diskette from drive A
and label it Startup Diskette 2.
6. To verify the startup diskettes, shut down your workstation, insert
Startup Diskette 1 into drive A, and press Ctrl+Alt+Del to restart the
workstation. When prompted, insert Startup Diskette 2 instead of OS/2
Installation/Diskette 1.
If you have Local Security installed, verify that an administrator ID
and a password can be validated by the startup diskettes.
If the workstation starts successfully, store the startup diskettes for
future use.
For more information about the MAKEDISK utility, see the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
ΓòÉΓòÉΓòÉ 20.2. Creating 386-HPFS Startup Diskettes Manually ΓòÉΓòÉΓòÉ
Use the following method to create the 386-HPFS startup diskettes if you cannot
use the MAKEDISK utility.
Note:
(This note does not apply to DBCS systems.) Use these steps also as a
general guide when creating diskettes for OEM workstations. On OEM
workstations, make sure to free enough space on Startup Diskette 2 so
that 386-HPFS-related files can be successfully copied onto the
diskette. In addition, you must make sure that the CONFIG.SYS file on
Startup Diskette 2 contains the following lines:
IFS=HPFS386.IFS /AUTOCHECK:*
PROTSHELL=BOOTSH.EXE CMD.EXE
After you have installed OS/2 and the LAN Server product on the workstation,
proceed as follows.
To Create 386-HPFS Startup Diskettes Manually:
1. Make a backup copy of the OS/2/Installation Diskette and the OS/2
Installation/Diskette 1.
2. When copying is complete, label the copy of the OS/2/Installation
Diskette Startup Diskette 1, and put it aside. Leave the copy of the
OS/2 Installation/Diskette 1 in drive A.
3. Delete the following files from the root directory of the backup
diskette:
Note:
You may not have all the listed files (SBCS systems only).
o FDISK.COM
o HPFS.IFS
o SIPANEL1.DLL
o SYSINST1.EXE
o SYSINST2.EXE
o SYSLEVEL.OS2
o BUNDLE
If you have the C:\OS2\VIOTBL.DCP file on your hard disk and you want to
use a code page other than 850, replace the VTBL850.DCP file on the
startup diskette with the VIOTBL.DCP file (does not apply to DBCS
systems) by running the following commands:
DEL A:VTBL850.DCP
COPY C:\OS2\VIOTBL.DCP
4. If a CONFIG.SYS file exists on the diskette, rename it (for example,
CONFIG.BAK), and use an ASCII text editor to create the following
CONFIG.SYS file on the startup diskette:
IOPL=YES
BUFFERS=30
MEMMAN=NOSWAP,MOVE
IFS=HPFS386.IFS A:\HPFS386.INI /A:*
SET PATH=A:\;
SET DPATH=A:\;
LIBPATH=.;A:\;
PROTSHELL=BOOTSH.EXE CMD.EXE
PROTECTONLY=YES
DEVINFO=SCR,EGA,VTBL850.DCP (for SBCS systems using the VTBL850.DCP file)
DEVINFO=SCR,VGA,VIOTBL.DCP (for SBCS systems using the VIOTBL.DCP file)
COUNTRY=001,COUNTRY.SYS
DEVINFO=KBD,US,KEYBOARD.DCP
CODEPAGE=850 (if you are using the VTBL850.DCP file)
CODEPAGE=437,850 (if you are using the VIOTBL.DCP file)
BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
BASEDEV=IBM1S506.ADD
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM2ADSK.ADD
BASEDEV=IBM2SCSI.ADD
BASEDEV=IBMINT13.I13
BASEDEV=OS2DASD.DMD
DEVICE=\TESTCFG.SYS
Note:
For non-US keyboards, use the appropriate COUNTRY, DEVINFO, and
CODEPAGE statements.
You can modify the LIBPATH, SET PATH, and SET DPATH statements if
you want.
5. Verify that the following files exist and copy them to the startup
diskette:
o d:\IBM386FS\HPFS386.INI
o d:\IBM386FS\HPFS386.IFS
o d:\IBM386FS\HFS.MSG
o d:\IBM386FS\BOOTSH.EXE
o d:\IBM386FS\BSH.MSG
o d:\IBM386FS\BSHH.MSG
o d:\OS2\DLL\UHPFS.DLL where d is the drive letter of the startup drive.
Note:
You may have to delete the OSO001.MSG file from a 5.25-inch
startup diskette to create space for all the listed files (SBCS
systems only).
6. When the startup diskette has been created, remove it from drive A and
label it Startup Diskette 2.
7. To verify the startup diskettes, shut down your workstation, insert
Startup Diskette 1 into drive A, and press Ctrl+Alt+Del to restart the
workstation. When prompted, insert Startup Diskette 2 instead of OS/2
Installation/Diskette 1.
If you have Local Security installed, verify that an administrator ID
and a password can be validated by the startup diskettes.
If the workstation starts successfully, store the startup diskettes for
future use.
ΓòÉΓòÉΓòÉ 20.3. Starting a Workstation with the 386-HPFS Startup Diskettes ΓòÉΓòÉΓòÉ
To start a workstation with the 386-HPFS startup diskettes, insert Startup
Diskette 1 into drive A and turn on the workstation. When prompted to insert
OS/2 Installation/Diskette 1, insert Startup Diskette 2.
If Local Security for the 386 HPFS is installed on your workstation, you are
prompted for an administrator ID and a password.
Administrator validation is incorporated into Startup Diskette 2 if Local
Security is detected on the workstation by the BOOTSH.EXE utility. (The
BOOTSH.EXE file was copied onto the startup diskette along with other
386 HPFS-related files when you created Startup Diskette 2.) When the
BOOTSH.EXE file runs, it determines whether Local Security is installed on the
hard disk by scanning all the CONFIG.SYS files in the root directory of each
logical drive, starting with drive C. Local security is detected if the
SECURESH.EXE file name is found in the PROTSHELL statement in a CONFIG.SYS
file. The information, which is kept in the NET.ACC file, is used by the system
to validate a user who is attempting to log on. The location of the NET.ACC
file is determined from the first CONFIG.SYS file found with the SECURESH.EXE
file name.
In the following situations, Local Security is installed on the workstation,
but Startup Diskette 2 does not prompt for an administrator ID:
o No CONFIG.SYS file is found in the root directory of any drive.
o The path to the NET.ACC file cannot be determined from the CONFIG.SYS file
with the SECURESH.EXE string.
o A NET.ACC file does not exist in the path determined from the CONFIG.SYS file
with the SECURESH.EXE string.
o Certain parts of the NET.ACC file are damaged.
A startup diskette with administrator validation is not meant to provide
security for the diskette drive. Instead, it provides a way to access a
workstation that has hard-disk problems. The CONFIG.SYS file on the startup
diskette is the file that determines what runs when a workstation is started
with the startup diskette. Users provided with a startup diskette can change
the CONFIG.SYS file and other system files on the startup diskette. Therefore,
a workstation that has been started from 386-HPFS startup diskettes is not
protected by the same level of security as a workstation started from the hard
disk.
To increase the effectiveness of a workstation with Local Security, an
administrator can prevent unauthorized use of the workstation by taking the
following additional precautions:
o Either lock or remove the diskette drive so that the workstation cannot be
started from it.
o Keep all 386-HPFS startup diskettes for workstations with Local Security in a
secure place.
o Have no FAT logical drives on the workstation.
o Install Local Security on all startup drives of a workstation that has
multistartup capabilities.
Because the startup diskettes do not start the Presentation Manager interface,
you cannot run Presentation Manager programs. Consequently, you cannot use a
Presentation Manager-based text editor to fix problems in system files. To
correct a damaged file (for example, the CONFIG.SYS file), copy the file to
diskette, edit the file at another workstation, and then copy it back to the
original hard disk.
ΓòÉΓòÉΓòÉ 20.4. Using the 386-HPFS Startup Diskettes to Run the PREPACL Utility ΓòÉΓòÉΓòÉ
If you install or reinstall OS/2 from diskette on a 386-HPFS workstation, you
must run the PREPACL utility to temporarily remove the access control profiles
on files required by OS/2 during its installation. If you must start your
workstation from 386-HPFS startup diskettes, complete the following steps
before running the PREPACL utility as described in Upgrading or Reinstalling on
386-HPFS Servers.
Note:
You can run the PREPACL utility on an OS/2 1.3, 2.0 or 2.1 386-HPFS
workstation.
To Run the PREPACL Utility, Using the 386-HPFS Startup Diskettes:
1. Use an ASCII text editor to add the following to the LIBPATH statement
in the CONFIG.SYS file on Startup Diskette 2:
d:\tempdll
where d is a fixed drive on the workstation, and tempdll is a valid name
for a subdirectory you create in step 4.
2. On any workstation that has LAN Server (server or requester) currently
installed, copy all the files under the MUGLIB\DLL directory on the
startup drive to a diskette.
3. Start your workstation from the 386-HPFS startup diskettes.
4. At the OS/2 command prompt, type:
MKDIR d:\tempdll
where d is the drive and tempdll is the subdirectory you specified in
step 1.
5. Copy all the .DLL files from the diskette you created in step 2. to the
d:\tempdll subdirectory.
6. Run the PREPACL utility as described in Upgrading or Reinstalling on
386-HPFS Servers.
Make sure you specify the path to the \IBMLAN subdirectory in the /LR
parameter so that the NET.ACC file can be found.
7. Remove the d:\tempdll subdirectory. The PREPACL utility does not remove
this subdirectory.
ΓòÉΓòÉΓòÉ 21. Response File Keywords Used in Remote Installation ΓòÉΓòÉΓòÉ
After you create a response file using the LAN Services
installation/configuration program, you may want to modify some of the keyword
values or add other keywords to the response file without running the LAN
Services installation/configuration program. This appendix assists you in this
task by providing the following information:
o Descriptions of response file keywords and keyword values as they are set by
the LAN Services installation/configuration program
o A detailed explanation for using the UpdateIBMLAN, DeleteIBMLAN, and
AddIBMLAN special keywords to modify the IBMLAN.INI file on the target
workstation
o Examples of server and requester response files
You can also use the information in this appendix to modify the LANINST.RSP
file on a custom installation diskette. The LANINST.RSP file contains the
installation and configuration selections made when the custom installation
diskette was created.
While you modify a response file with an ASCII text editor, remember the
following guidelines:
o Keywords and keyword values follow the format:
keyword=value
Embedded blanks are accepted:
keyword = value
o Keywords and keyword values are not case sensitive; you can use any
combination of uppercase or lowercase alphanumeric characters as long as they
are valid for the keyword.
o Comment lines are preceded by a semicolon. A comment statement can be added
anywhere in a file, as in:
;This is comment text
For detailed information on how the LAN Services installation/configuration
program validates response files and the errors generated by faulty response
files, see the LAN Server Problem Determination Guide. In general, keep the
following in mind:
o If a requester response file is used to install a server workstation or a
server response file is used to install a requester workstation, the LAN
Services installation/configuration program ends.
o If the response file contains a major inconsistency, an error is logged, and
the LAN Services installation/configuration program ends. For example, a
response file that indicates that an additional server be installed and also
specifies that the DCDB be initialized causes the LAN Services
installation/configuration program to end.
o If the response file is valid for certain workstations but not for others, a
warning is logged, and the LAN Services installation/configuration program
proceeds. For example, assume your response file specifies that the server
type be migrated and that the 386 HPFS be installed if required, and also
specifies a particular heap size for the 386 HPFS. If you use this response
file to reinstall a server workstation with no version of the 386 HPFS
currently installed, the 386 HPFS will not be installed (because it is not a
required component), the ConfigHeap setting causes a warning to be logged
(because the 386 HPFS is not installed), and the remote installation
proceeds.
ΓòÉΓòÉΓòÉ 21.1. Response File Keywords and Keyword Values ΓòÉΓòÉΓòÉ
When you follow the guided path provided by the LAN Services
installation/configuration program to create a response file (see Creating a
Response File for an OS/2 Client) or to create a custom diskette (see Creating
a Server Custom Diskette or Creating a Requester Custom Diskette), the program
sets keywords and keyword values as you make your selections on the various
windows. The following sections contain descriptions of all the keywords and
keyword values set by the LAN Services installation/configuration program.
Use this information to determine if you need to modify response files created
with the LAN Services installation/configuration program and, if so, how to do
this.
ΓòÉΓòÉΓòÉ 21.1.1. Common Keyword Values ΓòÉΓòÉΓòÉ
The following keyword values are the most commonly used in response files:
Note:
Keywords and keyword values are not case sensitive.
o MIGRATE
Indicates that the current setting at the target workstation be used for the
specified keyword.
Without existing target settings, keywords set to MIGRATE are set to the IBM
defaults of an initial Easy installation.
Note:
Because MIGRATE is a reserved word in response files, you cannot
specify the name MIGRATE or migrate (or a combination of uppercase
and lowercase characters) for the computername and domain parameters
by means of a response file (see Setting IBMLAN.INI Parameters in
Response Files for a discussion of these parameters). The same is
true for the workstation ID specified in the ConfigWsID keyword (see
Keywords Common to Both Servers and Requesters for a discussion of
this keyword).
o INSTALL
Indicates that the specified component be installed on the target workstation
unless the code already installed is at a later level.
o INSTALLIFREQUIRED
For an initial installation at the target workstation, indicates that the
component be installed if it is one of the default components installed
during an initial, diskette-based Easy installation. (See Easy Installation
and Easy Installation for a list of default server and requester components
respectively.)
For a reinstallation at the target workstation, this keyword indicates that
the component be installed only if one of the following situations applies:
- A previous version exists on the target workstation.
- No version exists on the target workstation and the component is required.
o REMOVE
Indicates that the specified component be removed from the target
workstation. If no version exists, no error is logged, and the LAN Services
installation/configuration program continues.
If a keyword is missing from the response file, the LAN Services
installation/configuration program assumes its default keyword value (MIGRATE,
if a target setting exists; INSTALLIFREQUIRED, if not).
If an empty response file or a response file with all the keyword values set to
either MIGRATE or INSTALLIFREQUIRED is used for an initial installation on the
target workstation, the effect is essentially that of an initial,
diskette-based Easy installation.
ΓòÉΓòÉΓòÉ 21.1.2. Missing Values for Keyword Entries ΓòÉΓòÉΓòÉ
In general, if a value is missing for a keyword entry (for example, if the
response file has the entry ConfigSourceDrive = ), the LAN Services
installation/configuration program does not validate the response file.
However, the following keyword entries for workstation-specific information are
valid when the response file is used for a lightly attended or custom diskette
installation:
ConfigWsType1 =
ConfigWsType2 =
ConfigWsSerial1 =
ConfigWsSerial2 =
ConfigWsID =
COMPUTERNAME =
DOMAIN =
Note:
See Keywords Common to Both Servers and Requesters for the meaning of
the ConfigWsxxx keywords; see Setting IBMLAN.INI Parameters in Response
Files for the computername and domain keywords.
The effect of leaving the value field blank for any of the listed keywords is
that the user at the target workstation is prompted to provide the missing
information in the Server or Domain Names window, Requester or Domain Names
window, or Hardware Vital Product Data window, even if previous target settings
exist.
Note:
For the effect of leaving a value blank after a specified IBMLAN.INI
parameter in the DeleteIBMLAN keyword, see DeleteIBMLAN.
ΓòÉΓòÉΓòÉ 21.1.3. Keywords Common to Both Servers and Requesters ΓòÉΓòÉΓòÉ
The following keywords are used in both server and requester response files:
o Include
Specifies a group response file to include within another response file. You
must supply the file name in the following format:
INCLUDE = filename
where filename does not include a drive or path name. In order for an Include
file name to be recognized, both the /R and the /G parameter must be
specified in the installation command statement. See Starting a Lightly
Attended Remote Installation for the full command syntax.
o ConfigSourceDrive
Specifies the drive where an existing copy of OS/2 LAN Server or OS/2 LAN
Requester (to use for updating) is located on the target workstation. This
keyword value is used only when the LAN Services installation/configuration
program cannot determine the correct drive letter.
Default value: NONE
Valid values: d | NONE
d Specifies a valid drive letter from C to Z
NONE Specifies that an existing copy of OS/2 LAN Server or OS/2
LAN Requester not be used for updates on the target
workstation.
o ConfigTargetDrive
Specifies the drive on which to install OS/2 LAN Server or OS/2 LAN
Requester.
Default value: MIGRATE
Valid values: d | MIGRATE
d Specifies a valid drive letter from C to Z
MIGRATE Specifies that OS/2 LAN Server or OS/2 LAN Requester be
installed where the current copy is installed on the target
workstation. The default is drive C for an initial
installation.
o ConfigAutoStartLS
Specifies that the server (if installing a server) or the requester (if
installing a requester) be started automatically when the workstation is
started.
Default value: MIGRATE
Valid values: YES | NO | MIGRATE
YES Specifies that the server or requester be started
automatically by adding one of the following statements to
the STARTUP.CMD file:
NET START REQUESTER
NET START SERVER
NO Specifies that the server or requester not be started
automatically. If this keyword is set to NO, the NET START
REQUESTER or NET START SERVER lines are removed from the
STARTUP.CMD file.
Note:
If the server or requester is started by a method other than NET
START statements, this setting will not prevent autostarting.
MIGRATE Specifies that this option be set to the autostart setting
on the target workstation. If this is an initial
installation, the server or requester will be autostarted.
o InstallInstallProgram
Specifies that the LAN Services installation/configuration program be
installed for either a requester or a server on the target workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the LAN Services installation/configuration
program be installed on the target workstation.
REMOVE Specifies that the LAN Services installation/configuration
program be removed if it exists on the target workstation.
INSTALLIFREQUIRED For an initial installation, specifies that the LAN
Services installation/configuration program be installed.
For a reinstallation, specifies that the LAN Services
installation/configuration program be installed if an older
version exists on the target workstation.
o InstallUPM
Specifies that UPM be installed on the target workstation.
Note:
REMOVE is not a valid value for this keyword because UPM can only be
removed if the entire product is removed. This is done by setting
the InstallServer or InstallRequester keyword to REMOVE.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | INSTALLIFREQUIRED
INSTALL Specifies that UPM be installed.
INSTALLIFREQUIRED Specifies that UPM be installed if an older version or no
version exists on the target workstation.
o InstallFFST
Specifies that FFST/2 be installed.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that FFST/2 be installed.
REMOVE Specifies that FFST/2 be removed if it exists on the target
workstation. The REMOVE value is valid only if the
Communications Manager/2 or DATABASE 2 OS/2 program has not
been installed.
INSTALLIFREQUIRED Specifies that FFST/2 be installed only if an older
version exists on the target workstation.
o ConfigDisplayMsg
Specifies that FFST/2 alerts be displayed as messages on the FFST/2 message
console. This keyword is not valid if InstallFFST is set to REMOVE.
Default value: ON
Valid values: ON | OFF | MIGRATE
ON Specifies that FFST/2 alerts be displayed as messages on
the console.
OFF Specifies that FFST/2 alerts not be displayed as messages
on the console.
MIGRATE Specifies that ConfigDisplayMsg be set to the current
setting on the target workstation. If FFST/2 is not
currently installed, the default for ConfigDisplayMsg is
ON.
o ConfigAutoStartFFST
Specifies that FFST/2 be automatically started when the workstation is
started. This keyword is not valid if InstallFFST is set to REMOVE.
Default value: MIGRATE
Valid values: YES | NO | MIGRATE
YES Specifies that FFST/2 be automatically started when the
workstation is started.
NO Specifies that FFST/2 not be automatically started when the
workstation is started.
MIGRATE Specifies that ConfigAutoStartFFST be set to the current
autostart setting for FFST/2 on the target workstation. If
FFST/2 is not currently installed on the workstation, the
default for ConfigAutoStartFFST is NO.
o ConfigRouteAlertsTo
Specifies that FFST/2 alerts be routed to a NetView host or IBM LAN Network
Manager when FFST/2 is autostarted. This keyword is not valid if
ConfigAutoStartFFST is set to NO.
Default value: MIGRATE
Valid values: NETVIEW | IBMLANMANAGER | MIGRATE
NETVIEW Specifies that FFST/2 alerts be routed to a NetView host
when FFST/2 is autostarted.
IBMLANMANAGER Specifies that FFST/2 alerts be routed to IBM LAN Network
Manager when FFST/2 is autostarted.
Note:
If a server is configured to route FFST/2 alerts to IBM LAN
Network Manager, IEEE 802.2 must be installed on the server.
MIGRATE Specifies that ConfigRouteAlertsTo be set to the current
route setting for FFST/2 on the target workstation. If
FFST/2 is not currently installed on the workstation, the
default is NETVIEW.
o ConfigSystemMaxDumps
Specifies the maximum number of system dumps for FFST/2 to create. This
keyword is not valid if InstallFFST is set to REMOVE.
Default value: MIGRATE
Valid values: 8 to 99 | MIGRATE
MIGRATE Specifies that ConfigSystemMaxDumps be set to the current
setting for FFST/2 on the target workstation. If FFST/2 is
not currently installed on the workstation, the default for
ConfigSystemMaxDumps is 32.
o ConfigSystemDumpPath
Specifies the path where the system dumps for FFST/2 are stored. This keyword
is not valid if InstallFFST is set to REMOVE.
Default value: MIGRATE
Valid values: d:\path | MIGRATE
d:\path Specifies the drive letter and fully qualified path to the
system dumps for FFST/2.
MIGRATE Specifies that the current path be used on the target
workstation, if it exists. If FFST/2 is not currently
installed on the workstation, the path of d:\OS2\is used,
where d is the OS/2 startup drive.
o ConfigApplMaxDumps
Specifies the maximum number of application dumps for FFST/2 to create. This
keyword is not valid if InstallFFST is set to REMOVE.
Default value: MIGRATE
Valid values: 8 to 99 | MIGRATE
MIGRATE Specifies that ConfigApplMaxDumps be set to the current
setting for FFST/2 on the target workstation. If FFST/2 is
not currently installed on the workstation, the default for
ConfigApplMaxDumps is 32.
o ConfigApplDumpPath
Specifies the path where the application dumps for FFST/2 are stored. This
keyword is not valid if InstallFFST is set to REMOVE.
Default value: MIGRATE
Valid values: d:\path | MIGRATE
d:\path Specifies the drive letter and fully qualified path to the
application dumps for FFST/2.
MIGRATE Specifies that the current path be used on the target
workstation, if one exists. If FFST/2 is not currently
installed, the path of d:\OS2\SYSTEM is used.
o ConfigMsgLogName
Specifies the path where the message log for FFST/2 is stored. This keyword
is not valid if InstallFFST is set to REMOVE.
Default value: MIGRATE
Valid values: d:\path | MIGRATE
d:\path Specifies the drive letter and fully qualified path to the
message log for FFST/2.
MIGRATE Specifies that the current path on the target workstation
be used, if one exists. If FFST/2 is not currently
installed, the path of d:\OS2\SYSTEM\OS2MLOG.DAT is used.
o ConfigWSType1
Specifies the first part of the machine type, for example, 8570 for a PS/2
workstation with the machine type 8570-E61, or 5580 for a PS/2 workstation
with the machine type 5580-Y0C. This keyword is not valid if InstallFFST is
set to REMOVE.
Default value: MIGRATE
Valid values: xxxx | MIGRATE
xxxx Specifies the first 4 characters of the machine type. The
characters must be in uppercase. If lowercase numbers are
entered, they are automatically changed to uppercase
characters. Valid characters are 0 through 9 and A through
Z.
MIGRATE Specifies that the current setting on the target
workstation be used, if one exists. If FFST/2 is not
currently installed, the user is prompted for this
information during a custom installation or lightly
attended remote installation.
o ConfigWSType2
Specifies the second part of the machine type, for example, E61 for a PS/2
workstation with the machine type 8570-E61, or 5560 for a PS/2 workstation
with the machine type 5560-Y0C. This keyword is not valid if InstallFFST is
set to REMOVE.
Default value: MIGRATE
Valid values: xxx | MIGRATE
xxx Specifies the last 3 characters of the machine type. The
characters must be in uppercase. If lowercase characters
are entered, they are automatically changed to uppercase
characters. Valid characters are 0 through 9 and A through
Z.
MIGRATE Specifies that the current setting on the target
workstation be used, if one exists. If FFST/2 is not
currently installed, the user is prompted for this
information during a custom installation or lightly
attended remote installation.
o ConfigWSSerial1
Specifies the first part of the machine serial number, for example, 72 for a
PS/2 workstation with the serial number 72-7076372, or 97 for a PS/2
workstation with the serial number 97-5122100. This keyword is not valid if
InstallFFST is set to REMOVE.
Default value: MIGRATE
Valid values: xx | MIGRATE
xx Specifies the first 2 characters of the machine serial
number. The characters must be in uppercase. If lowercase
characters are entered, they are automatically changed to
uppercase characters.
MIGRATE Specifies that the current setting on the target
workstation be used, if one exists. If FFST/2 is not
currently installed, the user is prompted for this
information during a custom installation or lightly
attended remote installation.
o ConfigWSSerial2
Specifies the second part of the machine serial number, for example, 7076362
for a PS/2 workstation with the serial number 72-7076362, or 7076362 for a
PS/2 workstation with the serial number 97-5122100. This keyword is not valid
if InstallFFST is set to REMOVE.
Default value: MIGRATE
Valid values: xxxxxxx | MIGRATE
xxxxxxx Specifies the last 7 characters of the machine serial
number. The characters must be in uppercase. If lowercase
characters are entered, they are automatically changed to
uppercase characters.
MIGRATE Specifies that the current setting on the target
workstation be used, if one exists. If FFST/2 is not
currently installed, the user is prompted for this
information during a custom installation or lightly
attended remote installation.
o ConfigWSID
Specifies the name by which the workstation will be known by FFST/2. This
keyword is not valid if InstallFFST is set to REMOVE.
Default value: MIGRATE
Valid values: xxxxxxxx | MIGRATE
xxxxxxxx Specifies a name consisting of from 1 to 8 characters (0-9,
A-Z).
MIGRATE Specifies that the current ID on the target workstation be
used, if one exists. If FFST/2 is not currently installed,
the user is prompted for this information during a custom
installation or lightly attended remote installation.
o InstallAPI
Specifies that the LAN Server Applications Development Toolkit be installed
on the target workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the LAN Server Applications Development
Toolkit be installed.
REMOVE Specifies that the LAN Server Applications Development
Toolkit be removed if it exists on the target workstation.
INSTALLIFREQUIRED For an initial server installation, specifies that the LAN
Server Applications Development Toolkit be installed on the
target workstation.
For a server reinstallation, specifies that the LAN Server
Applications Development Toolkit be installed only if an
older version exists on the target workstation or if the
target workstation is a domain controller.
For a requester initial installation or reinstallation,
specifies that the LAN Server Applications Development
Toolkit be installed only if an older version exists on the
target workstation.
o InstallDOSLANAPI
Specifies that Virtual DOS LAN API support be installed on the target
workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that Virtual DOS LAN API support be installed.
REMOVE Specifies that Virtual DOS LAN API support be removed if it
exists on the target workstation.
INSTALLIFREQUIRED Specifies that Virtual DOS LAN API support be installed
only if an older version exists on the target workstation.
o InstallMsgPopup
Specifies that the Message Popup service be installed on the target
workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the Message Popup service be installed.
REMOVE Specifies that the Message Popup service be removed if it
exists on the target workstation.
INSTALLIFREQUIRED Specifies that the Message Popup service be installed only
if an older version exists on the target workstation.
o InstallGUI
Specifies that the LAN Server Administration graphical user interface (GUI)
be installed on the target workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the LAN Server Administration GUI be
installed.
REMOVE Specifies that the LAN Server Administration GUI be removed
if it exists on the target workstation.
INSTALLIFREQUIRED Specifies that the LAN Server Administration GUI be
installed only if an older version exists on the target
workstation.
o InstallClipBoard
Specifies that Network DDE and Clipboard be installed on the target
workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that Network DDE and Clipboard be installed.
REMOVE Specifies that Network DDE and Clipboard be removed if it
exists on the target workstation.
INSTALLIFREQUIRED Specifies that Network DDE and Clipboard be installed only
if an older version exists on the target workstation.
o InstallDesktopIcons
Specifies that the Desktop Icons be installed on the target workstation.
Default value: YES
Valid values: YES | NO
YES Specifies that the Desktop Icons be installed.
NO Specifies that the Desktop Icons not be installed on the
target workstation.
ΓòÉΓòÉΓòÉ 21.1.4. Requester Keywords ΓòÉΓòÉΓòÉ
The following keywords are valid only when used in requester response files. If
any requester keywords are encountered during remote installation of a server,
they are logged to the error log and the LAN Services
installation/configuration program ends.
o InstallRequester
Specifies that requester code be installed for an initial installation, a
reinstallation, or an upgrade installation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that requester code be installed on the target
workstation.
REMOVE Specifies that the requester code and any associated
components be removed from the target workstation.
INSTALLIFREQUIRED Specifies that the requester code be installed only if an
older version or no version exists on the target
workstation.
o InstallPeerService
Specifies that the Peer service be installed to provide the requester with
some server capabilities.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the Peer service be installed on the target
workstation.
REMOVE Specifies that the Peer service be removed if it exists on
the target workstation.
INSTALLIFREQUIRED Specifies that the Peer service be installed only if an
older version exists on the target workstation.
o InstallRemoteFaultTolerance
Specifies that the Remote Fault Tolerance option be installed on the target
workstation. The option allows an administrator to administer remotely a
Fault Tolerance system installed on a server from the target workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the Remote Fault Tolerance option be
installed.
REMOVE Specifies that Remote Fault Tolerance option be removed, if
it exists.
INSTALLIFREQUIRED Specifies that the Remote Fault Tolerance option be
installed only if an older version exists on the target
workstation.
ΓòÉΓòÉΓòÉ 21.1.5. Server Keywords ΓòÉΓòÉΓòÉ
The following keywords are valid only when used in server response files. If
any server keywords are encountered during remote installation of a requester,
they are logged to the error log, and the LAN Services
installation/configuration program ends.
o InstallServer
Specifies that the server code be installed on the target workstation during
an initial installation, a reinstallation, or an upgrade installation. When
the server code is installed, the requester code is also installed.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the server code be installed on the target
workstation.
REMOVE Specifies that the server code and any associated
components that were installed with it be removed.
INSTALLIFREQUIRED Specifies that the server code be installed only if an
older version or no version currently exists on the target
workstation.
o ConfigServerType
Specifies that the server be defined as a domain controller, a backup domain
controller, or an additional server.
Default value: MIGRATE
Valid values: DOMAINCONTROLLER | ADDITIONALSERVER | BACKUPDC | MIGRATE
DOMAINCONTROLLER Specifies that the server be defined as a domain
controller.
BACKUPDC Specifies that the server be defined as a backup domain
controller.
ADDITIONALSERVER Specifies that the server be defined as an additional
server. If the workstation is currently a domain
controller, the domain control database (DCDB) is removed
during an unattended installation. During a lightly
attended installation, the user is asked whether to
continue the installation.
MIGRATE Specifies that the server should retain the same server
type (domain controller, backup domain controller, or
additional server) that exists on the target workstation.
An additional server is installed during an initial
installation if ConfigServerType is set to MIGRATE.
o InstallMigrationImportUtil
Specifies that the Migration Import Utility be installed on a target domain
controller.
This keyword is valid if ConfigServerType is set to DOMAINCONTROLLER or to
MIGRATE and the target workstation is a domain controller. If
ConfigServerType is set to ADDITIONALSERVER or BACKUPDC, the LAN Services
installation/configuration program ends. If ConfigServerType is set to
MIGRATE and the target workstation is an additional server or a backup domain
controller, a warning is logged, and the LAN Services
installation/configuration program continues.
If InstallMigrationImportUtil is set to REMOVE and ConfigServerType is set to
DOMAINCONTROLLER, the LAN Services installation/configuration program ends.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the Migration Import Utility be installed on
the target domain controller.
REMOVE Specifies that the Migration Import Utility be removed if
it exists on the target domain controller.
Note:
REMOVE is also valid if the target workstation is an additional
server or a backup domain controller.
INSTALLIFREQUIRED Specifies that the Migration Import Utility be installed
only if it exists on the target domain controller.
o ConfigInitializeDCDB
Specifies whether to initialize the domain control database (DCDB) if
installing on a workstation that is currently a domain controller.
This keyword is valid only if ConfigServerType is set to DOMAINCONTROLLER or
to MIGRATE and the target workstation is a domain controller. If
ConfigServerType is set to ADDITIONALSERVER or BACKUPDC, the LAN Services
installation/configuration program ends. If ConfigServerType is set to
MIGRATE and the target workstation is an additional server or a backup domain
controller, a warning is logged, and the LAN Services
installation/configuration program continues.
Default value: NO
Valid values: YES | NO
YES Specifies that the DCDB be initialized.
NO Specifies that the DCDB not be initialized if installing on
a domain controller.
o Install386HPFS (valid only for a LAN Server-Advanced response file)
Specifies whether to install the 386 HPFS on the target workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the 386 HPFS be installed on the target
workstation.
REMOVE Specifies that the 386 HPFS be removed if it exists on the
target workstation.
INSTALLIFREQUIRED For an initial installation, specifies that the 386 HPFS
be installed on the target workstation.
For a reinstallation, specifies that the 386 HPFS be
installed only if an older version exists on the target
workstation.
o Config386Cache (valid only for a LAN Server-Advanced response file)
Specifies the amount of cache space that the 386 HPFS is allowed to use. This
keyword is only valid if Install386HPFS is set to INSTALL.
Default value: MIGRATE
Valid values: xxx | WSDETERMINESIZE | MIGRATE
xxx Specifies the amount of memory (KB) to allocate to the
386HPFS cache. The minimum allowed is 256KB.
WSDETERMINESIZE Specifies that the workstation determines the cache size
for the 386 HPFS. The cache can use up to 20% of the
available memory on the workstation.
MIGRATE Specifies that the current setting on the target
workstation be used, if one exists. If the 386 HPFS is not
currently installed, the default is WSDETERMINESIZE.
o ConfigUseAllMem (valid only for a LAN Server-Advanced response file)
Specifies where memory for cache space is allowed to be allocated. This
keyword is only valid if Install386HPFS is set to INSTALL.
Default value: MIGRATE
Valid values: YES | NO | MIGRATE
YES Allows the cache space to be allocated above the 16MB
physical address boundary, if memory is available above
that boundary.
NO Prevents the cache space from being allocated above the
16MB physical address boundary.
MIGRATE Specifies that the existing setting on the target
workstation be used. If the 386 HPFS is not currently
installed, the default is NO.
o ConfigLazyWrite (valid only for a LAN Server-Advanced response file)
Specifies the amount of time to wait after a write request is received before
actually writing to the hard disk. This keyword is only valid if
Install386HPFS is set to INSTALL.
Default value: MIGRATE
Valid values: IMMEDIATE | DELAYED | MIGRATE
IMMEDIATE Indicates to write to the hard disk immediately after
receiving a write request.
DELAYED Indicates to delay a write to the hard disk using the
ConfigMaxCacheAge, ConfigMinBufferIdle, and ConfigLazyWrite
values.
MIGRATE Specifies that the existing setting on the target
workstation be used. If the 386 HPFS is not currently
installed, the default is IMMEDIATE.
o ConfigMaxCacheAge (valid only for a LAN Server-Advanced response file)
Specifies the maximum time, in milliseconds, a cache block can contain data
before the data is written to the hard disk. This keyword is only valid if
ConfigLazyWrite is set to DELAYED.
Default value: 5000 msec
Minimum value: 0
Maximum value: 1000000
o ConfigMinBufferIdle (valid only for a LAN Server-Advanced response file)
Specifies the minimum time a cache block with data must remain in the cache
without any read or write activity before it is written to the hard disk.
This keyword is only valid if ConfigLazyWrite is set to DELAYED.
Default value: 500 msec
Minimum value: 0
Maximum value: 500000
o ConfigHeap (valid only for a LAN Server-Advanced response file)
Specifies whether to let the workstation determine the amount of heap space
the 386 HPFS can use. This keyword is only valid if Install386HPFS is set to
INSTALL.
Default value: MIGRATE
Valid values: xxx | WSDETERMINESIZE | MIGRATE
xxx Specifies the amount of heap space (in KB) the 386 HPFS can
use. The minimum is 64KB, while the maximum is all of the
available memory on the workstation.
WSDETERMINESIZE Specifies that the workstation determine the amount of heap
space the 386 HPFS uses. It can use up to all of the
available memory on the workstation.
MIGRATE Specifies that the existing setting on the target
workstation be used. If the 386 HPFS is not currently
installed, the default becomes WSDETERMINESIZE.
o InstallFaultTolerance (valid only for a LAN Server-Advanced response file)
Specifies whether to install Fault Tolerance on the target workstation. This
keyword is only valid if InstallHPFS386 is set to INSTALL or
INSTALLIFREQUIRED.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that Fault Tolerance be installed.
REMOVE Specifies that Fault Tolerance be removed if it exists on
the target workstation.
INSTALLIFREQUIRED Specifies that Fault Tolerance be installed only if an
older version exists on the target workstation.
o InstallLocalSecurity (valid only for a LAN Server-Advanced response file)
Specifies whether to install Local Security for the 386 HPFS on the target
workstation. This keyword is only valid if InstallHPFS386 is set to INSTALL
or INSTALLIFREQUIRED.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that Local Security be installed on the target
workstation.
REMOVE Specifies that Local Security be removed if it exists on
the target workstation.
INSTALLIFREQUIRED Specifies that Local Security be installed only if an
older version exists on the target workstation.
o InstallDOSRemoteIPL
Specifies whether to install the DOS Remote IPL service on the target
workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the DOS Remote IPL service be installed on
the target workstation.
REMOVE Specifies that the DOS Remote IPL service and associated
user data be removed if it exists on the target
workstation.
INSTALLIFREQUIRED Specifies that the DOS Remote IPL service be installed
only if an older version exists on the target workstation.
o InstallOS2RemoteIPL
Specifies whether to install the OS/2 Remote IPL service on the target
workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the OS/2 Remote IPL service be installed on
the target workstation.
REMOVE Specifies that the OS/2 Remote IPL service be removed if it
exists on the target workstation.
INSTALLIFREQUIRED Specifies that the OS/2 Remote IPL service be installed
only if an older version exists on the target workstation.
o ConfigCopyDOS
This keyword specifies that a version of DOS be copied from diskettes to the
hard disk of the target workstation for use with the DOS Remote IPL service.
This keyword is not valid if InstallDOSRemoteIPL is set to REMOVE.
Default value: COPYIFREQUIRED
Valid values: COPY | REMOVE | COPYIFREQUIRED
COPY Specifies that a version of DOS be copied from diskettes to
the hard disk.
REMOVE Specifies that a version of DOS be removed if it exists on
the hard disk at the target workstation.
COPYIFREQUIRED Specifies that a version of DOS be copied to the hard disk
only if that version does not already exist on the target
workstation. The current version of DOS on the target
workstation, if any, is removed.
o ConfigDOSVersion
This keyword specifies which version of DOS to copy for use with the DOS
Remote IPL service on the target workstation. This keyword is not valid if
ConfigCopyDOS is set to REMOVE.
Default value: IBM_DOS63
Valid values: IBMDOS_50 | IBM_DOS33 | MS_DOS50 | MS_DOS_33 | MS_DOS60 |
IBM_DOS_61 | MS_DOS62 | IBM_DOS_63
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: PC DOS 6.3/V is the only Γöé
Γöé supported version for DOS Remote IPL. Valid values are as follows: Γöé
Γöé Γöé
Γöé DEFAULT VALUE: IBM_DOSJ6 Γöé
Γöé Γöé
Γöé VALID VALUES: IBM_DOSJ6 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
o ConfigDOSNumber (valid only for SBCS systems and only when creating a custom
diskette)
This keyword specifies the number of MS-DOS diskettes that the custom
diskette user needs to copy to the workstation. This keyword is required if
ConfigDOSVersion is valid and set to either MS_DOS33 or MS_DOS50.
Note:
The ConfigDOSNumber keyword is not required when creating a response
file for remote installation, because you already copied the MS-DOS
diskettes to the code server along with the other LAN Server product
diskettes when preparing for remote installation.
Valid values: 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8
o ConfigCopyDLR
Specifies whether to copy DOS LAN Services for use with the DOS Remote IPL
service on the target workstation. This keyword is not valid if
InstallDOSRemoteIPL is set to REMOVE.
Default value: COPYIFREQUIRED
Valid values: COPY | REMOVE | COPYIFREQUIRED
COPY Indicates to copy DOS LAN Services to the hard disk of the
target workstation.
REMOVE Specifies that DOS LAN Services be removed if it exists on
the hard disk of the target workstation.
COPYIFREQUIRED Specifies that DOS LAN Services be copied only if an older
version or no version exists on the target workstation.
o ConfigCopyLSP
Specifies whether to copy LAN Support Program for use with the DOS Remote IPL
service and OS/2 Remote IPL service on the target workstation. This keyword
is not valid if InstallDOSRemoteIPL and InstallOS2RemoteIPL are both set to
REMOVE.
Default value: COPYIFREQUIRED
Valid values: COPY | REMOVE | COPYIFREQUIRED
COPY Specifies that LAN Support Program be copied to the hard
disk of the target workstation.
REMOVE Specifies that LAN Support Program be removed if it exists
on the hard disk of the target workstation.
COPYIFREQUIRED Specifies that LAN Support Program be copied only if an
older version or no version exists on the target
workstation.
o ConfigCopyOS2Requester
Specifies that OS/2 LAN Requester be copied to the remote IPL subdirectory on
the target workstation. This keyword is not valid if InstallOS2RemoteIPL is
set to REMOVE.
Default value: COPYIFREQUIRED
Valid values: COPY | COPYIFREQUIRED
COPY Specifies that OS/2 LAN Requester be copied to the remote
IPL subdirectory on the target workstation.
COPYIFREQUIRED Specifies that OS/2 LAN Requester be copied to the remote
IPL subdirectory on the target workstation only if an older
version or no version exists on the target workstation.
o InstallLoopBackDriver
Specifies whether to install the loop back driver on the target workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the loop back driver be installed on the
target workstation.
REMOVE Specifies that the loop back driver be removed if it exists
on the target workstation.
INSTALLIFREQUIRED Specifies that the loop back driver be installed only if
an older version exists on the target workstation.
o InstallUPS
Specifies whether to install Uninterruptible Power Supply (UPS) on the target
workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Specifies that the UPS service be installed on the target
workstation.
REMOVE Specifies that the UPS service be removed if it exists on
the target workstation.
INSTALLIFREQUIRED Specifies that the UPS service be installed only if an
older version exists on the target workstation.
o ConfigUPSPort
Specifies what port the UPS service will use on the target workstation.
Default value: MIGRATE
Valid values: COM1 | COM2 | MIGRATE
COM1 Specifies that the COM1 port be used on the target
workstation for the UPS service.
COM2 Specifies that the COM2 port be used on the target
workstation for the UPS service.
MIGRATE Specifies that the current setting at the target
workstation be used for the keyword. If this is an initial
installation at the target workstation, and there is no
existing setting, the default is COM1.
o InstallGenericAlerter
Specifies whether to install the Generic Alerter service on the target
workstation.
Default value: INSTALLIFREQUIRED
Valid values: INSTALL | REMOVE | INSTALLIFREQUIRED
INSTALL Indicates that the Generic Alerter service be installed on
the target workstation.
REMOVE Specifies that the Generic Alerter service be removed if it
exists on the target workstation.
INSTALLIFREQUIRED Specifies that the Generic Alerter service be installed
only if an older version exists on the target workstation.
ΓòÉΓòÉΓòÉ 21.2. Keywords and Keyword Values That Affect the IBMLAN.INI File ΓòÉΓòÉΓòÉ
IBMLAN.INI parameters do not have unique response file keywords associated with
them. In response files, the following keywords can modify parameters in the
target workstation's IBMLAN.INI file:
o UpdateIBMLAN
o DeleteIBMLAN
o AddIBMLAN
The following keywords can modify sections in the target workstation's
IBMLAN.INI file that are not recognized by the LAN Services
installation/configuration program (for example, sections that the network
administrator named and defined):
o UpdateUnknown
o DeleteUnknown
o AddUnknown
These keywords follow the same rules and formatting as the UpdateIBMLAN,
DeleteIBMLAN, and AddIBMLAN keywords, except that they specify a user-defined
section name, and the specified changes are not validated by the LAN Services
installation/configuration program.
For detailed information about IBMLAN.INI parameters, refer to the LAN Server
Network Administrator Reference Volume 2: Performance Tuning.
Note:
During remote installation, the cleanup parameter is always set to Y if
the autodisconnect parameter value is set to -1, regardless of the
cleanup value specified by the user.
ΓòÉΓòÉΓòÉ 21.2.1. UpdateIBMLAN ΓòÉΓòÉΓòÉ
Syntax:
UPDATEIBMLAN = sectionname
< parmname=x
parmname= * >
Where:
sectionname Specifies the section in the IBMLAN.INI file containing the
parameters to update.
parmname Specifies a parameter to change or add in the named
IBMLAN.INI section. Multiple parameters must be listed on
separate lines.
For a listing of parameters in the IBMLAN.INI file, see the
LAN Server Network Administrator Reference Volume 2:
Performance Tuning.
x Specifies a new value for the parameter.
* Used in parameters that contain more than one value in a
string; indicates values in the string to leave unchanged.
Description:
Use UpdateIBMLAN in a response file to update specific parameter values in the
target workstation's IBMLAN.INI file. UpdateIBMLAN adds, deletes, and modifies
entire lines. A section name (for example, REQUESTER or SERVER) is required
after the UpdateIBMLAN keyword. The parameters to update are enclosed by the
less than and greater than signs (< >).
To update multiple sections in the IBMLAN.INI file, specify multiple instances
of the UpdateIBMLAN keyword. There is no limit to the number of UpdateIBMLAN
keywords that can be used within a response file. If the response file
contains duplicate keywords, only the last instance is accepted. If you
specify a keyword value that is not specified in the IBMLAN.INI file and it is
valid, it is added to the file.
Examples:
o The following entry updates the values for the computername and domain
parameters in the Requester section of the target workstation's IBMLAN.INI
file.
UPDATEIBMLAN = REQUESTER
<COMPUTERNAME = NANCY
DOMAIN = DEPT571>
o The following entry replaces the values in positions 3, 4, 7, 10, and 14
(with the values 1, 1, 3, 4, and 1 respectively) of the srvheuristics
parameter in the Server section of the IBMLAN.INI file. The other values
indicated by asterisks (*) are not changed.
UPDATEIBMLAN = SERVER < SRVHEURISTICS = **11**3**4***1**** >
o The following entry leaves the first and third net1 parameter values
unchanged, but replaces the second and last three values with 0, 10, 15, and
32 respectively. This net1 parameter is located in the Requester section of
the IBMLAN.INI file.
Note:
The net1 parameter always corresponds to adapter 0; the net2
parameter to adapter 1, and so on.
UPDATEIBMLAN = REQUESTER < NET1 = *,0,*,10,15,32 >
ΓòÉΓòÉΓòÉ 21.2.2. DeleteIBMLAN ΓòÉΓòÉΓòÉ
Syntax:
DELETEIBMLAN = sectionname
<parmname=x
parmname= > | < >
Where:
sectionname Specifies the section in the IBMLAN.INI file containing the
parameters to be deleted.
parmname Specifies a parameter to delete from the named IBMLAN.INI
section or a parameter from which values are to be deleted.
Multiple parameters must be listed on separate lines.
For a listing of parameters in the IBMLAN.INI file, see the
LAN Server Network Administrator Reference Volume 2:
Performance Tuning.
x Specifies the values to delete. If you list a nonexistent
value within a string, the value is ignored. If you
specify no value after a parameter name, all existing
values for the parameter are deleted and the parameter is
removed from the IBMLAN.INI file.
<> Deletes the entire section specified by sectionname.
Description:
Use DeleteIBMLAN in a response file to delete specific parameter values,
keywords, or entire sections in the target workstation's IBMLAN.INI file. A
section name (for example, REQUESTER or SERVER) is required after the
DeleteIBMLAN keyword. The parameter values to delete are enclosed by the less
than and greater than signs (< >). If you delete the last parameter value in a
keyword, the keyword remains in the IBMLAN.INI file.
To update multiple sections in the IBMLAN.INI file, specify multiple instances
of the DeleteIBMLAN keyword. There is no limit to the number of DeleteIBMLAN
keywords that can be used within a response file.
Examples:
o The following entry deletes the Messenger service from the Requester section
of the IBMLAN.INI file:
DELETEIBMLAN = REQUESTER < WRKSERVICES = MESSENGER>
o The following entry deletes the entire UPS section of an IBMLAN.INI file:
DELETEIBMLAN = UPS < >
o The following entry deletes the othdomains keyword from the IBMLAN.INI file:
DELETEIBMLAN = REQUESTER
<OTHDOMAINS= >
ΓòÉΓòÉΓòÉ 21.2.3. AddIBMLAN ΓòÉΓòÉΓòÉ
Syntax:
ADDIBMLAN = sectionname
<parmname=x>
Where: .
sectionname Specifies the section in the IBMLAN.INI file to which the
parameter values are to be added.
parmname Specifies a parameter in the named section of the
IBMLAN.INI file to which one or more values are to be
added. Multiple parameters must be listed on separate
lines.
For a listing of parameters in the IBMLAN.INI file, see the
LAN Server Network Administrator Reference Volume 2:
Performance Tuning.
x Specifies what values to add. If you specify a value for a
parameter that does not exist in the current IBMLAN.INI
file, the parameter is added along with the value.
Description:
Use AddIBMLAN in a response file to add specific parameter values to the target
workstation's IBMLAN.INI file. The AddIBMLAN keyword adds values to existing
parameters. (If you want to replace values, use the UpdateIBMLAN keyword.) A
section name (for example, REQUESTER or SERVER) is required after the AddIBMLAN
keyword. The parameters to which values are to be added are enclosed by the
less than and greater than signs (< >).
You can list multiple instances of the AddIBMLAN keyword. There is no limit to
the number of the AddIBMLAN keywords that can be used within a response file.
Example:
The following entry adds the Netrun service to the Server section of the target
workstation's IBMLAN.INI file:
ADDIBMLAN = SERVER < WRKSERVICES = NETRUN >
ΓòÉΓòÉΓòÉ 21.2.4. Setting IBMLAN.INI Parameters in Response Files ΓòÉΓòÉΓòÉ
The following IBMLAN.INI parameters are set by the LAN Services
installation/configuration program when you make selections from the menus.
Each selection adds either an UpdateIBMLAN, a DeleteIBMLAN, or an AddIBMLAN
keyword with an associated IBMLAN.INI section name, parameter names, and
parameter values to the response file. During the remote installation, the
values specified by these keywords override any values in the target
workstation's IBMLAN.INI file.
Note:
For more detailed information about any of the following IBMLAN.INI
parameters, refer to the LAN Server Network Administrator Reference
Volume 2: Performance Tuning.
o netx
This parameter specifies the logical adapters for use with OS/2 LAN Server or
OS/2 LAN Requester. For each selected adapter, the LAN Services
installation/configuration program generates a response-file entry of the
following format:
- For OS/2 LAN Server:
UPDATEIBMLAN = NETWORKS
<NET1 = NETBEUI$,0,LM10,#,#,#>
ADDIBMLAN = SERVER
<WRKNETS = NET1>
- For OS/2 LAN Requester:
UPDATEIBMLAN = NETWORKS
<NET1 = NETBEUI$,0,LM10,#,#,#>
ADDIBMLAN = REQUESTER
<WRKNETS = NET1>
These are the response-file entries created when you select adapter 0.
Selecting adapter 1 generates a response-file entry specifying NET2,
selecting adapter 2 generates an entry specifying NET3, and so on. You can
select up to four configured adapters (0 through 3). During an installation
at the target workstation, the corresponding netx statements in the
IBMLAN.INI file are updated.
Note:
If the target workstation's IBMLAN.INI file was created following a
different convention (for example, during a previous release), the
netx statements are modified to reflect this correspondence between
the netx statement number (1, 2, 3, and 4, respectively) and the
logical adapter number (0, 1, 2, and 3, respectively).
The response-file entries in the example update the net1 statement in the
target workstation's IBMLAN.INI file.
Similarly, entries containing the DeleteIBMLAN keyword are generated if you
select to remove an adapter. No entries are generated if you are migrating
adapter settings that exist on the target workstation.
If you do not configure NetBIOS, but instead select to install the loop back
driver to simulate network operation, the following response-file entry is
generated:
UPDATEIBMLAN = NETWORKS
<NETLB = LOOPDRV$,0>
UPDATEIBMLAN = REQUESTER
<WRKNETS = NETLB>
UPDATEIBMLAN = SERVER
<SRVNETS = NETLB>
The loop back driver can be installed on the server only.
o computername
This parameter specifies your workstation ID. The following entry is added
to the response file for a requester named NANCY:
UPDATEIBMLAN = REQUESTER
<COMPUTERNAME = NANCY>
Note:
Because MIGRATE is a reserved word in response files, you cannot
specify the name MIGRATE or migrate (or a combination of uppercase
and lowercase characters) for the computername parameter.
o domain
This parameter specifies the domain to which the workstation belongs. The
following entry is added to the response file for a requester belonging to a
domain named DINKY:
UPDATEIBMLAN = REQUESTER
<DOMAIN=DINKY>
Note:
Because MIGRATE is a reserved word in response files, you cannot
specify the name MIGRATE or migrate (or a combination of uppercase
and lowercase characters) for the domain parameter.
o rplx
This parameter specifies the logical adapters for use with the Remote IPL
service. For each selected adapter, the LAN Services
installation/configuration program generates a response-file entry of the
following format:
UPDATEIBMLAN = REMOTEBOOT
<RPL1 = RPLNET1.DLL RPLNET2.DLL RPLOEM.DLL 0>
This response-file entry is created when you select adapter 0 for use with
the Remote IPL service. Selecting adapter 1 generates a response-file entry
specifying RPL2, selecting adapter 2 generates an entry specifying RPL3, and
so on. You can select up to four configured adapters (0 through 3). During
an installation at the target workstation, the corresponding rplx statements
in the IBMLAN.INI file are updated.
Note:
If the target workstation's IBMLAN.INI file was created following a
different convention (for example, during a previous release), the
rplx statements are modified to reflect this correspondence between
the rplx statement number (1, 2, 3, and 4, respectively) and the
logical adapter number (0, 1, 2, and 3, respectively).
The response-file entry in the example updates the rpl1 statement in the
target workstation's IBMLAN.INI file.
Similarly, entries containing the DeleteIBMLAN keyword are generated if you
select to remove an adapter. No entries are generated if you are migrating
adapter settings that exist on the target workstation.
o wrkservices
This parameter specifies the requester services to be started automatically
when the workstation is started. For example, this entry is generated in the
response file if you specify that the Messenger service be started
automatically:
ADDIBMLAN = REQUESTER <WRKSERVICES = MESSENGER>
o srvservices
This parameter specifies the server services to be started automatically when
the workstation is started. For example, this entry is generated in the
response file if you specify that the Alerter, Replicator, Netlogon, UPS, and
Remote IPL services be started automatically:
ADDIBMLAN = SERVER <SRVSERVICES = ALERTER,REPLICATOR,NETLOGON,UPS,/
REMOTEBOOT>
Note:
The forward slash (/) indicates that the line is continued.
o security
This parameter specifies the security mode to be used by the Peer service
installed on a requester workstation. For example, the following entry is
generated in the response file if you specify that the user security mode be
set:
ADDIBMLAN = PEER <SECURITY = USER>
ΓòÉΓòÉΓòÉ 21.3. DOS LAN Services Keywords ΓòÉΓòÉΓòÉ
The following keywords are used in DOS LAN Services response files:
o computername
Specifies the name that identifies the workstation in the domain. The name
should be unique in the domain and cannot be the same as the domain name.
Default value: None
Valid values: This name can consist of up to 15 characters, including
letters, numbers, and the following characters: ! # $ % & (
) ^ _ ` { } ~
o domainname
Specifies the name of the domain to which the workstation belongs.
Default value: None
Valid values: This name can consist of up to 15 characters, including
letters, numbers, and the following characters: ! # $ % & (
) ^ _ ` { } ~
o username
Specifies the name that identifies the user in the domain. Choose a name that
is unique within the domain.
Default value: None
Valid values: This name can consist of up to 20 characters, including
letters, numbers, and the following characters: ! # $ % & (
) ^ _ ` { } ~
o configsys
Specifies the workstation drive containing the CONFIG.SYS file. DOS LAN
Services installation changes the CONFIG.SYS file.
Default value: C:
Valid values: C: is the only valid value.
o autoexecbat
Specifies the workstation drive containing the AUTOEXEC.BAT file. DOS LAN
Services installation may change the AUTOEXEC.BAT file.
Default value: C:
Valid values: C: is the only valid value.
o target
Specifies the drive and path where DOS LAN Services should be installed on
this workstation.
Default value: C:\NET
Valid values: Specify the full drive and directory path where DOS LAN
Services should be installed.
o peer
Specifies whether Peer services should be installed on this workstation.
Default value: Yes
Valid values: Yes | No
o redirector
Specifies which type of redirecter should be installed on this workstation.
Default value: Full
Valid values: Full | Basic
Full Installs the files necessary for advanced network functions
and increased performance on the workstation.
Basic Installs the files necessary for the standard requester
functions and smaller memory requirements on the
workstation.
o windowsupport
Specifies whether to install the files necessary for network support of
Microsoft Windows.
Default value: No
Valid values: Yes | No
o ddeclipboard
Specifies whether to install the files necessary to support the Network DDE
and Clipboard functions on the workstation. Network DDE and Clipboard
requires that Windows support is installed.
Default value: No
Valid values: Yes | No
o gui
Specifies whether to install the files necessary to support the graphical
user interface on the workstation.
Default value: Yes
Valid values: Yes | No
o install_802
Installs 802.2 support, which includes the LAN Support Program.
Default value: Yes
Valid values: Yes | No
o startupopt
Specifies the state of DOS LAN Services at workstation startup.
Default value: logon
Valid values: logon | nostartup
logon Starts DOS LAN Services when the workstation is started and
facilitates a logon using the username and domainname
values.
nostartup Does not start DOS LAN Services when the workstation is
started. The user must issue the NET LOGON command at the
workstation command line to start DOS LAN Services. The
command results in a logon prompt.
ΓòÉΓòÉΓòÉ 21.4. Example Response Files ΓòÉΓòÉΓòÉ
Use the following example files as a guide when creating or modifying response
files with an ASCII text editor.
ΓòÉΓòÉΓòÉ 21.4.1. Server Response File ΓòÉΓòÉΓòÉ
The following response file is intended for a remote installation of a domain
controller.
Topic 1 of 2
Server Response File
DELETEIBMLAN = Networks<
net1b =
>
UPDATEIBMLAN = Remoteboot<
rpldir = Migrate
rpluserdir = Migrate
>
UPDATEIBMLAN = Requester<
useallmem = No
>
ADDIBMLAN = Server<
srvservices = LSSERVER
>
Config386Cache = Migrate
ConfigApplDumpPath = Migrate
ConfigApplMaxDumps = Migrate
ConfigAutoStartFFST = Migrate
ConfigAutoStartLS = Migrate
ConfigCopyDLR = CopyIfRequired
ConfigCopyDOS = CopyIfRequired
ConfigCopyLSP = CopyIfRequired
ConfigCopyOS2Requester = CopyIfRequired
ConfigDisplayMSG = Migrate
ConfigDOSVersion = Migrate
ConfigHeap = Migrate
ConfigLazyWrite = Migrate
ConfigMsgLogName = Migrate
ConfigRouteAlertsTo = Migrate
ConfigServerType = Migrate
ConfigSourceDrive = C
ConfigSystemDumpPath = Migrate
ConfigSystemMaxDumps = Migrate
ConfigTargetDrive = Migrate
Server Response File
Topic 2 of 2
Server Response File
ConfigUpsPort = Migrate
ConfigUseAllMem = Migrate
ConfigWsId = Migrate
ConfigWsSerial1 = Migrate
ConfigWsSerial2 = Migrate
ConfigWsType1 = Migrate
ConfigWSType2 = Migrate
Install386HPFS = INSTALLIFREQUIRED
InstallAPI = INSTALLIFREQUIRED
InstallClipBoard = INSTALLIFREQUIRED
InstallDesktopIcons = INSTALLIFREQUIRED
InstallDosLanApi = INSTALLIFREQUIRED
InstallDosRemoteIPL = INSTALLIFREQUIRED
InstallFaultTolerance = INSTALLIFREQUIRED
InstallFFST = INSTALLIFREQUIRED
InstallGenericAlerter = INSTALLIFREQUIRED
InstallGUI = INSTALLIFREQUIRED
InstallInstallProgram = INSTALLIFREQUIRED
InstallLocalSecurity = INSTALLIFREQUIRED
InstallLoopBackDriver = INSTALLIFREQUIRED
InstallMigrationImportUtil = INSTALLIFREQUIRED
InstallMSGPopup = INSTALLIFREQUIRED
InstallOS2RemoteIPL = INSTALLIFREQUIRED
InstallServer = INSTALLIFREQUIRED
InstallUPM = INSTALLIFREQUIRED
InstallUps = INSTALLIFREQUIRED
Server Response File
ΓòÉΓòÉΓòÉ 21.4.2. Requester Response File ΓòÉΓòÉΓòÉ
The following response file is intended for a remote reinstallation of OS/2 LAN
Requester.
Requester Response File
DELETEIBMLAN = Networks<
net1b =
>
UPDATEIBMLAN = Peer<
security = Migrate
>
UPDATEIBMLAN = Requester<
useallmem = No
>
ConfigApplDumpPath = Migrate
ConfigApplMaxDumps = Migrate
ConfigAutoStartFFST = Migrate
ConfigAutoStartLS = Migrate
ConfigDisplayMSG = Migrate
ConfigMsgLogName = Migrate
ConfigRouteAlertsTo = Migrate
ConfigSourceDrive = C
ConfigSystemDumpPath = Migrate
ConfigSystemMaxDumps = Migrate
ConfigTargetDrive = Migrate
ConfigWsId = Migrate
ConfigWsSerial1 = Migrate
ConfigWsSerial2 = Migrate
ConfigWsType1 = Migrate
ConfigWsType2 = Migrate
InstallAPI = INSTALLIFREQUIRED
InstallClipBoard = INSTALLIFREQUIRED
InstallDesktopIcons = INSTALLIFREQUIRED
InstallDosLanApi = INSTALLIFREQUIRED
InstallFFST = INSTALLIFREQUIRED
InstallGUI = INSTALLIFREQUIRED
InstallInstallProgram = INSTALLIFREQUIRED
InstallMSGPopup = INSTALLIFREQUIRED
InstallPeerService = INSTALLIFREQUIRED
InstallRemoteFaultTolerance = INSTALLIFREQUIRED
InstallRequester = INSTALLIFREQUIRED
InstallUPM = INSTALLIFREQUIRED
Requester Response File
ΓòÉΓòÉΓòÉ 22. LAN Support Program Messages and Problem Solving ΓòÉΓòÉΓòÉ
This appendix lists all the messages that the LAN Support Program device driver
files can display when being loaded into memory. These messages start with DXM.
If you have NDIS adapters, three other types of messages may be displayed.
These NDIS messages are issued by files from the NDIS configuration, such as
PROTMAN.DOS (the protocol manager), the NDIS MAC driver, or NETBIND. Messages
generated by PROTMAN.DOS or NETBIND start with PRO00. Messages generated by
NDIS MAC drivers vary in format.
Many of the NDIS messages are displayed because of errors made during
configuration. If you have problems while installing NDIS adapters, make sure
that all necessary device drivers are loaded and that PROTOCOL.INI contains
valid configuration information. In particular, make sure that the module
names specified in the Bindings statement and the NDIS MAC drivers entered in
the CONFIG.SYS file match the adapters that are installed in your computer.
A description of some common configuration errors that may cause NDIS error
messages is found in Common NDIS Configuration Errors.
ΓòÉΓòÉΓòÉ 22.1. Format of the Device Driver Messages ΓòÉΓòÉΓòÉ
All LAN Support Program device driver messages have the following format:
The first 5 characters of the message (for example, DXMT0) identify the device
driver that originated the message. These drivers are as follows:
DXMA0MOD.SYS
DXMC0MOD.SYS
DXMC1MOD.SYS
DXMG0MOD.SYS
DXMG1MOD.SYS
DXMG2MOD.SYS
DXME0MOD.SYS
DXMT0MOD.SYS
DXMJ0MOD.SYS
For a description of these drivers, see the description at the beginning of
Customizing the LAN Support Program Device Driver Parameters.
ΓòÉΓòÉΓòÉ 22.1.1. Message Type ΓòÉΓòÉΓòÉ
The two types of messages are:
E Error
I Information
ΓòÉΓòÉΓòÉ 22.1.2. Message Text ΓòÉΓòÉΓòÉ
The message text is a phrase describing the message. For some messages, part of
the message varies. For example, the number of the adapter may be 0 or 1 (0
for the primary adapter, 1 for the alternate adapter). The variable portions of
the message are represented by symbols separated from the rest of the message
text by single quotation marks. The description of these symbols follows:
o The adapter number is represented by `n'.
o `data' is 24 bytes of the DEVICE = line in the CONFIG.SYS file. The bytes
begin with the abbreviation of the NetBIOS keyword in error, followed by the
"=" and the value of the parameter. For example, consider the following
message:
36E Invalid keyword value: SS=18
The `data' in this example is SS=18. The following command is entered in
CONFIG.SYS:
DEVICE=DXMT0MOD.SYS SS=18
SS is the incorrect keyword; you must replace it with a correct keyword
abbreviation, such as S. (Refer to Summary of the Keyword Values for the
NetBIOS New Parameters for a description of the keywords.)
o `retcode:', `keyword', and `parm' are used to represent the values of the
return codes, keywords, and parameters returned in some of the error
messages.
Messages 41 through 56 are generated only by DXMJ0MOD.SYS.
If an error message is displayed, you will be prompted by the device driver to
Press F1 to Continue. After pressing F1, wait for the DOS prompt to be
displayed. When it is, you can attempt to correct the problem by reading the
Explanation and following the directions provided in the User Response.
Information relating to parameters can be found in Customizing the LAN Support
Program Device Driver Parameters.
ΓòÉΓòÉΓòÉ 22.2. Device Driver Message Listings ΓòÉΓòÉΓòÉ
The messages appear in numerical order.
00I Please wait, opening adapter `n'
Explanation: Either a Token-Ring Adapter or a PC Network Adapter is
executing an open process.
User Response: This is an information message; no action is required.
02E DOS Version 3.3 or later required
Explanation: The DOS version is earlier than 3.3.
User Response: Update DOS to Version 3.3 or later.
03E Interrupt Arbitrator (DXMA0MOD.SYS) device driver required
Explanation: Module DXMA0MOD has not been loaded.
User Response: Check the CONFIG.SYS file to ensure that the DXMA0MOD
device driver is listed in the correct sequence. DXMA0MOD.SYS must
be loaded before any other LAN Support Program device driver.
04E Program already loaded
Explanation: This device driver was already installed into memory.
User Response:
o Check the CONFIG.SYS file to ensure that the device driver is not listed
twice.
o If you have two adapters in this computer, check to make sure that both
are not set as the primary adapter. See Using Two LAN Adapters for more
information.
05E Invalid node address parameter
Explanation: The address parameter is invalid, an invalid global
parameter was entered, or a comma was placed after a global
parameter. (A global parameter is a nonpositional parameter. See
Global and Positional Parameters.)
User Response: Edit the CONFIG.SYS file to correct the address
parameter or the global parameter for this device driver. See IBM
Token-Ring Network Adapter Addresses for more information about
configuring the address parameter, and Parameters with Special
Functions (W, N, CF, MINSAP, MINLINK, X, and R/T) for a description
of some of the global parameters.
06E Error reading message file (DXM.MSG)
Explanation: The message file, DXM.MSG, is not present or could not
be read for one or more of the following reasons:
o The Interrupt Arbitrator (DXMA0MOD.SYS) has not been loaded.
o The DXM.MSG file could not be located.
o The language type of the file does not correspond to the DOS language type
specified by the DXMA0MOD.SYS language parameter.
o The DXM.MSG file is the from the wrong version of the LAN Support Program.
Note:
This message is not translated. U.S. English is always displayed.
User Response:
o Make sure that the Interrupt Arbitrator is loaded. Edit the CONFIG.SYS
file to ensure that the DXMA0MOD.SYS device driver is listed in the
correct sequence. DXMA0MOD.SYS must be loaded before any other LAN
Support Program device driver, if no NDIS adapters are used.
o Make sure that the DXM.MSG file is present on the working diskette in the
same directory as the LAN Support Program device drivers.
o Be sure that you renamed DXMMSG.ccc to DXM.MSG on the working copy. (ccc
represents the DOS country code.)
o Make sure that the language type of the file matches the language type
specified by the DXMA0MOD.SYS language parameter.
o Make sure that you got the message file and the LAN Support Program device
drivers from the same version of the LAN Support Program.
10E Invalid shared RAM address
Explanation: The shared RAM address is invalid.
User Response:
o Edit the CONFIG.SYS file to correct the shared RAM parameter. Make sure
that the shared RAM is on the correct boundary. See Shared RAM for more
information.
o If you have a Token-Ring 16/4 Adapter, verify that the shared RAM page
size is set to 16KB. Refer to the guide to operations for your adapter for
instructions on setting or checking shared RAM page size.
11E DIR.INITIALIZE failed
Explanation: The Token-Ring Network Adapter initialization failed.
User Response: Refer to the section describing the adapter
diagnostics in the guide to operations for your adapter.
12E Token-Ring Adapter not installed
Explanation: A Token-Ring Network Adapter was not detected.
User Response:
o If you do not intend to use a Token-Ring Network Adapter, edit the
CONFIG.SYS file to remove this adapter support device driver.
o If you intend to use a Token-Ring Network Adapter, you do not need to
change your configuration. You must install a Token-Ring Network Adapter.
13I Token-Ring Network Adapter data rate = 4Mbps
13I Token-Ring Network Adapter data rate = 16Mbps
Explanation: Token-Ring Network Adapter data rate.
User Response: This is an information message; no action is required.
Note: This message is listed twice if there are two Token-Ring
Network Adapters installed. The first message refers to the primary
adapter; the second refers to the alternate adapter.
14E Invalid Early Token Release parameter
Explanation: The parameter is not correct.
User Response: Edit the CONFIG.SYS file to correct the Early Token
Release parameter. For a description of the Early Token Release
parameter, see Early Token Release.
20E Invalid work-size parameter
Explanation: The work space parameter is not correct.
User Response: Edit the CONFIG.SYS file to correct the work space
parameter. For a description of the work space parameter, see Work
Space.
16E Invalid minimum SAP parameter
Explanation: The parameter value is out of range.
User Response: Edit the CONFIG.SYS file to correct the parameter. For
a description of the minimum SAP parameter, see MINSAP.
17E Invalid minimum link station parameter
Explanation: The parameter value is out of range.
User Response: Edit the CONFIG.SYS file to correct the parameter. For
a description of the minimum link station parameter, see MINLINK.
20E Invalid work-size parameter
Explanation: The work space parameter is not correct.
User Response: Edit the CONFIG.SYS file to correct the work space
parameter. For a description of the work space parameter, see Work
Space.
21E Network error
Explanation: An error was detected on the PC Network Adapter. The
message will be followed by one of these additional messages:
Please record this number yyyy-yy
Adapter not found, have system serviced.
Please record this number yyyy-yy
Have system serviced.
Please record this number yyyy-yy
Have network serviced.
User Response:
o If you receive the Adapter not found message, first check to make sure
that your LAN Support Program configuration matches the adapters installed
in your computer. If they do not match, either install an adapter or
remove this adapter support device driver. Remove the device driver by
editing the CONFIG.SYS file. If the configuration matches the adapters
installed, record the error number and have your computer serviced.
o If you receive one of the other messages, record the error number and have
either the computer or the network serviced as indicated.
22E Error Communicating with Protocol Manager
Explanation: Protocol Manager (PROTMAN.DOS) has not been loaded or
DXME0MOD.SYS encountered an error while communicating with
PROTMAN.DOS.
User Response:
o Make sure that PROTMAN.DOS is listed in the CONFIG.SYS file before of any
other LAN Support Program device drivers.
o Check to be sure that PROTMAN.DOS can find PROTOCOL.INI. PROTOCOL.INI must
be copied to the LANMAN directory, or PROTMAN.DOS must be written in the
CONFIG.SYS file with the /I: parameter.
23E Error Reading PROTOCOL.INI
Explanation: DXME0MOD.SYS encountered an error while trying to parse
the PROTOCOL.INI memory image.
User Response:
o Check the section of the PROTOCOL.INI file named [DXME0_MOD] to make sure
that the DriverName = parameter is DXME0$ and that the Bindings =
parameters are set correctly.
o Check the PROTOCOL.INI file for a syntax error or irrelevant data.
31E Requested resources exceed capabilities on
adapter `n'
Explanation: The resources defined exceed the data area of the
adapter; for example, too many link stations are defined.
User Response: Edit the CONFIG.SYS file to ensure that the resource
requirements are not exceeded.
Note:
If you are running a PC Network Adapter and this message appears when
the adapter is opened at load time, increase the value for the work
space parameter. See Work Space for more information about the work
space parameter.
32E Initialization or open error on adapter `n'
Explanation: There was an adapter failure or the adapter was already
open.
User Response:
o PC Network Adapter
Have your computer serviced.
o Token-Ring Network Adapter
If the NetBIOS OPEN.ON.LOAD parameter is set, then the NetBIOS interface
tries to open the adapter at load time. See Summary of the Keyword Values
for the NetBIOS New Parameters for instructions about the parameter. If an
initialization or open error occurs, this message appears.
- Verify that the adapter data rate is the same as the ring data rate.
Your LAN administrator will know the ring data rate. If the rates are
different, refer to the guide to operations for your adapter for
instructions on changing the rate. See Data Rate for the IBM Token-Ring
Network Adapter for more information.
- Refer to the guide to operations for your adapter for diagnostic
information.
o NDIS adapter
The adapter cannot be opened by the NetBIOS interface at load time.
Specify the OPEN.ON.LOAD parameter as N (No). (See Setting the
OPEN.ON.LOAD Parameter for an NDIS Adapter (DXMT0MOD.SYS) and Summary of
the Keyword Values for the NetBIOS New Parameters for more information
about this parameter.)
33E Cannot mix OLD.PARMS.x and `new' keywords
Explanation: Both new and old parameters are mixed on the device
driver parameter line.
User Response: Edit the CONFIG.SYS file to ensure that the parameter
types are not mixed.
34E Invalid keyword: `data'
Explanation: The keyword used is invalid.
User Response: Edit the CONFIG.SYS file to ensure that the keyword is
correct.
35E Duplicate keyword: `data'
Explanation: This keyword is used twice on the device driver
parameter line.
User Response: Edit the CONFIG.SYS file to remove the keyword listed
twice.
36E Invalid keyword value: `data'
Explanation: The value listed is invalid for its keyword.
User Response: Edit the CONFIG.SYS file to ensure that the value is
correct.
37E Adapter support required
Explanation: No adapter support has been loaded.
User Response: Edit the CONFIG.SYS file to ensure that an adapter
support device driver is listed.
40E Invalid transmit/swap parameter
Explanation: The transmit/swap parameter is not correct.
User Response: Edit the CONFIG.SYS file to correct the transmit/swap
parameter. For a description of the transmit/swap parameter, see
Transmit/Swap.
41E The protocol manager could not be opened. The return code is
`retcode'.
Explanation: One of the following happened:
o The system service DosOpen request to the PROTMAN.DOS device driver
failed.
o Another device driver has opened PROTMAN with exclusive rights and failed
to close it.
User Response: Check your CONFIG.SYS file and ensure that the
PROTMAN.DOS device driver is active. For additional information
about the return code (`retcode') displayed with the message for a
specific cause, refer to the error codes for interrupt 21H function
calls listed in the DOS Technical Reference.
42E The protocol manager would not accept a request
Explanation: The protocol manager failed to honor a request from this
protocol stack.
User Response: Check for additional messages from the protocol
manager that indicate the cause for failure. Correct the error and
try the operation again.
43E The protocol manager would not supply a configuration image
Explanation: The protocol manager did not honor the request for the
configuration image.
User Response: Verify that the PROTOCOL.INI file exists and that it
is valid, and then retry the operation.
44E The protocol manager would not accept module registration
Explanation: An attempt to register the device name with the protocol
manager was unsuccessful.
User Response: Ensure that the bracketed names in the PROTOCOL.INI
file are unique, and retry the operation.
45E No MAC driver bindings were specified in PROTOCOL.INI
Explanation: There were no medium access control (MAC) names
specified on the Bindings = statement in the IBM NETBEUI section of
the PROTOCOL.INI file.
User Response: Check the section of the PROTOCOL.INI file named
[DXMJ0MOD_MOD] to ensure that a valid MAC driver name is specified on
the Bindings = statement.
46E System resources are not available to hold the current parameter
configuration in PROTOCOL.INI
Explanation: The sum of the configuration parameters requires more
memory than the amount available.
User Response: Refer to your network planning and administration
guides for additional information about suggested values. Reduce the
resources required by changing the PROTOCOL.INI file.
47E Will not fit in UMB - Try loading low
Explanation: There is not enough space in high memory to load the
device driver.
User Response: Change the DEVICEHIGH= statement in the CONFIG.SYS
file to DEVICE=.
48I Chaining multiple LAN drivers
Explanation: The protocol driver is configured to pass commands to
another INT5C handler. The commands will be passed to the INT5C
handler that is installed before DXMJ0MOD.SYS. Commands passed are
NCBs that specify an adapter to which NETBEUI is not bound, or a CCB.
User Response: This is an information message; no action is required.
49E Address error correcting for 386 processor
Explanation: An internal processing error has occurred.
User Response: Contact your IBM service representative.
50E There are too many MAC drivers to bind
Explanation: The number of MAC drivers specified on the Bindings =
statement in the PROTOCOL.INI file exceeds the maximum number of
devices to bind (MAXBIND).
User Response: Correct the PROTOCOL.INI file to ensure that the
number of MAC names specified in the Bindings = statement does not
exceed 2.
51E The unrecognized keyword `keyword' was found in PROTOCOL.INI
Explanation: A keyword (`keyword') that is not recognized as a valid
parameter was found in the PROTOCOL.INI file.
User Response: Review the PROTOCOL.INI file to locate the incorrect
parameter. Correct or delete the unrecognized keyword and retry the
operation.
52E A value is required for keyword `keyword' in PROTOCOL.INI
Explanation: The keyword (`keyword') specified has required
parameters. No parameter values were found for this keyword.
User Response: Add the correct value to the keyword and retry the
operation.
53E The value specified for parameter `parm' is not valid
Explanation: The value provided for the parameter (`parm') is not the
correct type or is not a valid value.
User Response: Change the value for the parameter in the PROTOCOL.INI
file.
54E The value specified for parameter `parm' is not valid
Explanation: The value specified for the parameter (`parm') is either
larger than the maximum allowed or smaller than the minimum allowed
for that parameter.
User Response: Correct the value specified and retry the operation.
55E Duplicate parameter `parm' found in PROTOCOL.INI
Explanation: The parameter (`parm') occurred more than once in the
PROTOCOL.INI file. Only one occurrence of the parameter is allowed.
User Response: Change the PROTOCOL.INI file so that it contains only
one reference to the parameter and retry the operation.
56E There is no section for NETBEUI in PROTOCOL.INI
Explanation: There are no configuration parameters defined for
NETBEUI in the PROTOCOL.INI file.
User Response: Change the PROTOCOL.INI file to add a section of
configuration information for NETBEUI. The minimum statements
required for this section are DriverName =, and Bindings =. These
statements are in the [DXMJ0MOD_MOD] section of PROTOCOL.INI. Retry
the operation.
ΓòÉΓòÉΓòÉ 22.3. Recommendations and Problem Solving ΓòÉΓòÉΓòÉ
The following information contains recommendations to help you prevent or
handle problems you may have while using the LAN Support Program. It also
outlines guidelines for adjusting the NetBIOS parameter values when using
DXMT0MOD.SYS. Adjusting these parameters can improve the performance of a
token-ring network and its attached computers.
If you do not find the information you need in this chapter, you may want to
consult other sections of the book, as follows:
o For planning recommendations, see Planning for the LAN Support Program.
o See Parameters with Special Functions (W, N, CF, MINSAP, MINLINK, X, and R/T)
if you are having trouble loading the LAN Support Program and do not find
help in the following information. Parameters with Special Functions (W, N,
CF, MINSAP, MINLINK, X, and R/T) describes some parameters that may be
affecting your configuration.
Where to Find Topics tells you where to find descriptions of the topics covered
in the following information.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 28. Where to Find Topics Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TOPIC Γöé SEE: Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Provide service information Γöé Service Information.. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Increase the work space for a PC Γöé Heavy Network Load Using PC Network Γöé
Γöé Network Adapter Γöé Adapters.. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Change parameters if an application Γöé Application Requests Too Many Γöé
Γöé requests too much buffer Γöé Buffers.. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Verify the operation of a non-NDIS Γöé Using OPEN.ON.LOAD to Verify Adapter Γöé
Γöé adapter using the OPEN.ON.LOAD param- Γöé Operation (Non-NDIS Adapters).. Γöé
Γöé eter for NetBIOS Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Change NetBIOS parameters to improve Γöé Tuning Performance When NetBIOS Γöé
Γöé the performance of a token-ring Γöé (DXMT0MOD.SYS) Is Used in a Token- Γöé
Γöé network that uses NetBIOS Γöé Ring Network.. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Set OPEN.ON.LOAD parameter for an Γöé Setting the OPEN.ON.LOAD Parameter Γöé
Γöé NDIS adapter Γöé for an NDIS Adapter (DXMT0MOD.SYS).. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Set OPEN.ON.LOAD parameter with DOS Γöé Using DOS LAN Services with NDIS Γöé
Γöé LAN Requester for an NDIS adapter Γöé Adapters and DXMT0MOD.SYS.. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Increase the work space for an NDIS Γöé Increasing Work Space for NDIS Γöé
Γöé adapter (return code X'30' or X'F8' Γöé Adapters.. Γöé
Γöé may be returned) Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Deal with a problem using TCP/IP with Γöé Increasing Work Space When Using Γöé
Γöé the IBM Token-Ring Network 16/4 Γöé TCP&slr.IP.. Γöé
Γöé Adapter II and DXME0MOD.SYS Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Set the Data Holding Buffer for Γöé Data Holding Buffer Size for Γöé
Γöé Ethernet adapters Γöé Ethernet Adapters.. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Use the SWITCH command with the Asian Γöé Using the SWITCH Command with Asian Γöé
Γöé versions of DOS Γöé Versions of DOS .. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Change the language in which load- Γöé Changing the Language in Which Load- Γöé
Γöé time messages are displayed Γöé Time Messages Are Displayed.. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Deal with common NDIS configuration Γöé Common NDIS Configuration Errors.. Γöé
Γöé errors Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Use more than one protocol driver Γöé Using Multiple Protocol Drivers with Γöé
Γöé with NDIS adapters (multiple protocol Γöé NDIS Adapters.. Γöé
Γöé stacks) Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Use an unsupported NDIS adapter Γöé Using Unsupported NDIS Adapters.. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 22.4. Service Information ΓòÉΓòÉΓòÉ
When you request service for the LAN Support Program, gather the following
information before you contact service support. The following facts enable your
service representative to help you better:
o Adapter name
o Other adapters in the computer
o LAN Support Program version number (displayed when the LAN Support Program is
loaded)
o Adapter speed
o PC type and model
o Monitor type and display adapter
o Version of DOS
o Which protocols you are using: NetBIOS, IEEE 802.2, IEEE 802.3, or Ethernet
DIX Version 2.0
o Which application software you are using
o A description of the problem
o The contents of the CONFIG.SYS file
o The contents of the AUTOEXEC.BAT and PROTOCOL.INI files if using NDIS
adapters.
ΓòÉΓòÉΓòÉ 22.5. Heavy Network Load Using PC Network Adapters ΓòÉΓòÉΓòÉ
If you are using PC Network Adapters, you may need to change some device driver
parameters when there is a large amount of data traffic or if many sessions are
defined in one computer, as in a disk server.
The PC Network Adapter device drivers (DXMGnMOD.SYS) have a work space
parameter to allow for this situation. This parameter, identified as wrk0 for
the primary adapter and wrk1 for the alternate adapter, has a value of from 8KB
to 64KB. You can enter this parameter by editing the CONFIG.SYS file.
In some situations where many computers are sending large amounts of
information to one computer, increasing the work space of the receiving adapter
is an incomplete solution. If the receiving adapter is receiving incoming
traffic faster than it can handle it, you may also have to reduce the size of
the transmit buffers in the sending computer. You can reduce the transmit
buffers of the sending computer using one of the following methods:
o If NetBIOS is being used, you can change the size of the transmit buffer by
altering the DHB.SIZE parameter on the NetBIOS device driver. See Summary of
the Keyword Values for the NetBIOS New Parameters for more information.
o If the application program issues a DIR.OPEN.ADAPTER command, the size of the
transmit buffer can be changed with that command. For example, with Personal
Communications/3270, you can change the size of the transmit buffer specified
in the DIR.OPEN.ADAPTER command by changing the path information unit (PIU)
size.
ΓòÉΓòÉΓòÉ 22.6. Application Requests Too Many Buffers ΓòÉΓòÉΓòÉ
If the application that opens the adapter requests too many transmit buffers,
too many link stations, or transmit buffers that are too large, the adapter
fails to open. The error message displayed depends on the application. For
example, if you are using the NetBIOS device driver DXMT0MOD.SYS, the adapter
will fail to open if the DS, DN, ST, ES, or EST parameters are set too high
(see NetBIOS Device Driver Keyword Parameter Descriptions for a description of
these parameters). If you are using Personal Communications/3270, the adapter
will fail to open if the PIU size or the number of network stations to be
supported by a gateway is too high.
ΓòÉΓòÉΓòÉ 22.7. Using OPEN.ON.LOAD to Verify Adapter Operation (Non-NDIS Adapters) ΓòÉΓòÉΓòÉ
You can use the DXMT0MOD.SYS NetBIOS parameter OPEN.ON.LOAD to verify the
function of a Token-Ring Network Adapter or PC Network Adapter. Choose NetBIOS
support for your configuration. Then, set O=Y. (See Summary of the Keyword
Values for the NetBIOS New Parameters for more information about this
parameter.) The NetBIOS device driver DXMT0MOD.SYS opens the adapter when the
LAN Support Program is activated. Adapter diagnostics are run and the LAN
cable connection is verified.
If you receive any error messages when you activate the LAN Support Program,
see LAN Support Program Messages and Problem Solving.
ΓòÉΓòÉΓòÉ 22.8. Tuning Performance When NetBIOS (DXMT0MOD.SYS) Is Used in a Token-Ring Network ΓòÉΓòÉΓòÉ
This section describes changing the NetBIOS device driver parameters to improve
the performance of a token-ring network and its attached computers. For a
description of the parameters discussed in this section, see NetBIOS Device
Driver Keyword Parameter Descriptions.
The current LAN Support Program default parameters were designed to support the
original 4Mbps Token-Ring Adapters with 8 or 16KB of memory. Today's 16/4Mbps
Token-Ring Adapters contain 64KB of memory. Because of this additional memory
and the faster processing speeds of today's PCs and PS/2 computers, you can
change some of the default NetBIOS parameters in the LAN Support Program for
better performance.
ΓòÉΓòÉΓòÉ 22.8.1. Performance Tuning ΓòÉΓòÉΓòÉ
No single set of parameters can be optimum for all configurations. You need to
experiment with the parameters to find the best ones for your configuration.
Performance tuning is the process of selecting parameter values to maximize the
performance of your token-ring network. The following guidelines offer some
suggestions to assist you.
ΓòÉΓòÉΓòÉ 22.8.2. Taking Advantage of Large Frame Sizes ΓòÉΓòÉΓòÉ
Transmitting a frame requires a certain overhead that is fairly constant
independent of the frame size. Therefore, using larger frame sizes increases
the efficiency of the computer using the LAN Support Program.
For applications that can take advantage of large frame sizes, you can improve
the performance of the computer by increasing the DHB.SIZE (DS) parameter.
Increasing this parameter increases the size of the transmit frame. Final
determination of the NetBIOS session transmit frame size is a function of the
value of DHB.SIZE, the number of receive buffers in the receiver, and the
maximum frame size that can pass through a bridge in the path. See the IBM
Local Area Network Technical Reference for a description of NetBIOS frame size
determination.
When you increase the DS parameter, you reduce the amount of memory that can be
used for receive buffers. However, reducing the memory for receive buffers may
not cause any performance problems if you are using 16/4Mbps Token-Ring Network
Adapters. [ IBM Token-Ring Network 16/4 Adapter IIs do not belong to this group
because they are not shared RAM adapters] These adapters contain 64KB of
memory.
ΓòÉΓòÉΓòÉ 22.8.3. Increasing the Number of Outstanding Frames ΓòÉΓòÉΓòÉ
The DLC.MAXOUT (MO) parameter allows you to influence the number of outstanding
frames in the network. You can increase the efficiency of the network by
allowing more data to be in transit in the network.
Setting the MO value to 4 increases the number of outstanding frames per
NetBIOS interface link station from 2 to 4. Increasing the value of MO can
improve the efficiency of your network, especially if bridges are in the link
station traffic path. However, in some rare cases, increasing the value of MO
may cause congestion at these bridges. You may also have congestion problems
when communicating with 8 or 16KB token-ring network adapters.
ΓòÉΓòÉΓòÉ 22.8.4. Decreasing the Number of Acknowledgment Frames ΓòÉΓòÉΓòÉ
The DLC.MAXIN (MI) parameter allows you to influence the number of LLC
acknowledgment frames on the network. Increasing the value of MI increases the
number of frames that are received before an acknowledgment is sent. It is
very important that the MI value of the receiving station be less than the MO
value of the sending station. If the MI value of the receiving station is
greater than the MO value of the sending station, the performance of the
network is significantly degraded. It is recommended that you increase MO and
MI in all the stations in the network (for example, set MO to 4 and MI to 2),
or else allow the MI value to default to 1.
ΓòÉΓòÉΓòÉ 22.8.4.1. Reducing the Amount of Broadcast Traffic ΓòÉΓòÉΓòÉ
Reducing the amount of broadcast traffic is especially valuable in networks
with bridges. The REMOTE.NAME.DIRECTORY (RND) parameter can help reduce
broadcast traffic. Setting RND to 17 is suggested. Using this value for RND
requires about 1KB of memory in the PC or PS/2 computer.
You can also change the values of the TRANSMIT.TIMEOUT (TT) and TRANSMIT.COUNT
(TC) parameters to reduce network traffic. For example, at the default value of
TC = 6, queries will be transmitted 6 times. If you change TC to equal 3,
queries will only be sent 3 times. Because queries are sent less frequently,
the traffic generated when setting up a NetBIOS session is decreased.
Similarly, if you increase TT, you can spread the traffic load. If you set TT
= 6, queries will only be generated at 3-second intervals. A combination of TT
= 6 and TC = 3 causes only 3 NetBIOS call queries to be generated at 3-second
intervals, instead of the default of 6 call queries at 1/2-second intervals.
ΓòÉΓòÉΓòÉ 22.8.4.2. Examples of NetBIOS Parameter Configurations ΓòÉΓòÉΓòÉ
As an example, the following device driver command line for DXMT0MOD.SYS may
improve performance for configurations containing 16/4Mbps token-ring network
adapters and using applications that can take advantage of large frames (in
this case, 4096-byte frames).
DEVICE=\LSP\DXMT0MOD.SYS DS=4096 MO=4 RND=17
For applications that do not use large frames, the following configuration may
improve performance:
DEVICE=\LSP\DXMT0MOD.SYS MO=4 RND=17
ΓòÉΓòÉΓòÉ 22.9. Setting the OPEN.ON.LOAD Parameter for an NDIS Adapter (DXMT0MOD.SYS) ΓòÉΓòÉΓòÉ
If an error message indicates that an error occurred while opening an NDIS
adapter, reconfigure the adapter, and then restart the LAN Support Program.
If NetBIOS is loaded (DXMT0MOD.SYS) and the following error message is
displayed:
DXMT0 32E: Initialization or open error on adapter 'n'
specify OPEN.ON.LOAD=NO (O=N) for the NetBIOS device driver (DXMT0MOD.SYS). If
no NetBIOS new parameter is showing in CONFIG.SYS, the default is O=N.
If O=Y, NetBIOS tries to open the adapter at load time, but fails because
NETBIND is not run until AUTOEXEC.BAT is run.
ΓòÉΓòÉΓòÉ 22.10. Using DOS LAN Services with NDIS Adapters and DXMT0MOD.SYS ΓòÉΓòÉΓòÉ
During the installation of DOS LAN Services, the command line parameters for
the NetBIOS device driver, DXMT0MOD.SYS, are added to or updated. The
OPEN.ON.LOAD parameter in NetBIOS must have the value O=N.
If O=N is not present, error message DXMT0 32E will be displayed and the
adapter will fail to open. (See Setting the OPEN.ON.LOAD Parameter for an NDIS
Adapter (DXMT0MOD.SYS).)
ΓòÉΓòÉΓòÉ 22.11. Increasing Work Space for NDIS Adapters ΓòÉΓòÉΓòÉ
When using NDIS adapters, you may need to change the environment when there is
a large amount of data traffic or if many sessions are defined in one computer,
as in a disk server. For certain NDIS adapters, such as IBM FDDI Adapters, you
may also need additional work space to accommodate the receive buffers
necessary to receive the largest frame.
One of the following events may indicate that more work space is required:
o You get the return code:
X'30' Inadequate receive buffers for adapter to open
from the CCB command DIR.OPEN.ADAPTER.
o You get the return code:
X'F8' Error on implicit DIR.OPEN.ADAPTER
on a NetBIOS command.
o The application program fails to open the adapter.
A work space parameter in the IEEE 802.2 protocol driver for NDIS MAC drivers
(DXME0MOD.SYS) enables you to change the work space for an Ethernet or other
NDIS adapter. You can increase the work space to a maximum of 64KB. Increment
the work space as little as possible, because it takes up additional
workstation memory. The same considerations apply as for PC Network Adapters
(see Work Space for more information about setting the work space parameter).
ΓòÉΓòÉΓòÉ 22.12. Increasing Work Space When Using TCP/IP ΓòÉΓòÉΓòÉ
When using the IBM Token-Ring 16/4 Adapter II with the protocol driver
DXME0MOD.SYS and running TCP/IP, increase the work space parameter from the
default value of 8 to 12. (See Work Space for more information about setting
the work space parameter. Note that the work space parameter is the same for
PC Network and NDIS adapters.)
ΓòÉΓòÉΓòÉ 22.13. Data Holding Buffer Size for Ethernet Adapters ΓòÉΓòÉΓòÉ
Because the maximum frame size on an Ethernet network is 1514 bytes, the
maximum Data Holding Buffer (DHB) size allowed for Ethernet adapters on a
DIR.OPEN.ADAPTER command is 1496 bytes. See NetBIOS Device Driver Keyword
Parameter Descriptions for a description of the DHB parameter.
ΓòÉΓòÉΓòÉ 22.14. Data Holding Buffer Size for FDDI Adapters ΓòÉΓòÉΓòÉ
Because the maximum FDDI frame size is 4491 bytes, the maximum Data Holding
Buffer (DHB) size allowed for FDDI adapters on a DIR.OPEN.ADAPTER command is
4456 bytes. See NetBIOS Device Driver Keyword Parameter Descriptions for a
description of the DHB parameter.
ΓòÉΓòÉΓòÉ 22.15. Using the SWITCH Command with Asian Versions of DOS ΓòÉΓòÉΓòÉ
If you plan to use the SWITCH command in DOS Version J4.0 or J5.0, you must
install the LAN Support Program two times: once in DOS 3.3 or higher and once
in DOS Version J4.0. or J5.0. Each configuration requires a separate
subdirectory, and each configuration must match the language specified by the
COUNTRY command in its version of DOS.
For example, install the program in SBCS mode (U.S. English) using DOS 3.3 or
later. Then, install it a second time in DBCS mode (one of the Asian languages,
such as Japanese or Chinese) using DOS J4.0, or J5.0.
If you do a manual configuration, you must also do two configurations. Each
configuration must be located in a separate subdirectory. For example, the
configuration for DOS 3.3 or higher might be in \LSP and the configuration for
DOS J4.0, or J5.0 might be in \DBLSP. One configuration is installed in SBCS
mode (U.S. English), using DOS 3.3 or higher. The other is installed in DBCS
mode using DOS J4.0 or J5.0. In each configuration, the language in the message
file must match the DOS COUNTRY code entered as a parameter on the DXMA0MOD.SYS
DEVICE= line.
If you use the SWITCH command and do not have a configuration of the LAN
Support Program that matches the new mode (whether single-byte or double-byte)
and language, the program does not run and you may get the following message:
06E Error reading message file (DXM.MSG).
ΓòÉΓòÉΓòÉ 22.16. Changing the Language in Which Load-Time Messages Are Displayed ΓòÉΓòÉΓòÉ
To change the language for load-time messages, you must first use the COUNTRY
command to change the language used by DOS in your computer. Then, reconfigure
the LAN Support Program.
If you change the language in DOS and do not reconfigure the LAN Support
Program, the program does not run and you may get the following message:
06E Error reading message file (DXM.MSG).
ΓòÉΓòÉΓòÉ 22.17. Common NDIS Configuration Errors ΓòÉΓòÉΓòÉ
This section describes some common NDIS configuration errors found when using
the protocol driver DXME0MOD.SYS. If reconfiguration does not work, try some of
the other suggestions included with the error descriptions.
The error messages from PROTMAN.DOS, NETBIND, DXME0MOD.SYS, and DXMT0MOD.SYS
are shown along with the descriptions of the errors. In the following examples,
messages generated by PROTMAN.DOS or NETBIND start with PRO00. Page LAN Support
Program Messages and Problem Solving contains a brief description of these NDIS
error messages. Refer to the descriptions of the error messages in LAN Support
Program Messages and Problem Solving, for more information about messages from
DXME0MOD.SYS or DXMT0MOD.SYS.
Use the following table to identify the problems associated with the error
messages. Error messages beginning with DXMT0 are displayed only if you have
configured for NetBIOS, and are not included in the table.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé FOR ERROR MESSAGE: Γöé SEE: Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé "DXME0 22E: Error communicating with Γöé The /I: Parameter Is Incorrectly Γöé
Γöé Protocol Manager" Γöé Entered;; Γöé
Γöé Γöé PROTMAN.DOS Is Not Entered in Γöé
Γöé Γöé CONFIG.SYS; Γöé
Γöé Γöé PROTOCOL.INI File Is Not Found. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé "DXME0 23E: Error reading Γöé Parameters in PROTOCOL.INI Are Γöé
Γöé PROTOCOL.INI" Γöé Missing.. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé "PRO0003E: PROTOCOL.INI file open Γöé PROTOCOL.INI File Is Not Found.. Γöé
Γöé failure" Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé "PRO0010E: Invalid option" Γöé The /I: Parameter Is Incorrectly Γöé
Γöé Γöé Entered.. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé "PRO0023E: Cannot find Protocol Γöé The /I: Parameter Is Incorrectly Γöé
Γöé Manager" Γöé Entered;; Γöé
Γöé Γöé PROTMAN.DOS Is Not Entered in Γöé
Γöé Γöé CONFIG.SYS; Γöé
Γöé Γöé PROTOCOL.INI File Is Not Found. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé "PRO0025E: Fail to bind" Γöé Error in Editing PROTOCOL.INI, or Γöé
Γöé Γöé Missing NDIS MAC Driver;; Γöé
Γöé Γöé Parameters in PROTOCOL.INI Are Γöé
Γöé Γöé Missing. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 22.17.1. Errors Involving the NDIS MAC Driver ΓòÉΓòÉΓòÉ
An error message from the NDIS MAC driver is displayed if:
o The NDIS adapter is not installed in the computer.
o The NDIS adapter is not functioning correctly.
o Your NDIS MAC driver does not support the adapter that is installed (for
example, you have a 3Com Adapter and the NDIS MAC driver for an IBM adapter).
o The NDIS MAC driver parameters are not specified correctly in the
PROTOCOL.INI file . (for example, the wrong adapter is specified for the
ADAPTERTYPE= parameter for the Ungermann-Bass NDIS MAC driver).
Refer to your adapter documentation for more information about the specific
error messages that your NDIS MAC driver generates.
ΓòÉΓòÉΓòÉ 22.17.2. The /I: Parameter Is Incorrectly Entered ΓòÉΓòÉΓòÉ
If you have made a syntax mistake entering the /I: parameter, you will receive
the following error messages:
PRO0010E: Invalid option
PRO0023E: Cannot find Protocol Manager
DXME0 22E: Error communicating with Protocol Manager
DXMT0 37E: Adapter support required
To correct this error, check the syntax of the DEVICE= statement for
PROTMAN.DOS. Make sure that the DEVICE= statement for PROTMAN.DOS is listed
before any other device driver statement in the CONFIG.SYS file, and make sure
that the /I: parameter is correct.
ΓòÉΓòÉΓòÉ 22.17.3. PROTMAN.DOS Is Not Entered in CONFIG.SYS ΓòÉΓòÉΓòÉ
If PROTMAN.DOS is not entered in CONFIG.SYS, you will receive the following
error messages:
DXME0 22E: Error communicating with Protocol Manager
DXMT0 37E: Adapter support required
PRO0023E: Cannot find Protocol Manager
To correct this error, make sure that the DEVICE= statement for PROTMAN.DOS is
in the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 22.17.4. Parameters in PROTOCOL.INI Are Missing ΓòÉΓòÉΓòÉ
Several errors can be made when entering the parameters for PROTOCOL.INI,
including:
o Failing to enter the Bindings parameter in the PROTOCOL.INI file
o Not setting the DriverName parameter equal to DXME0$ in the named section
[DXME0_MOD]
o Failing to enter the DriverName parameter in [DXME0_MOD].
If one of these errors has occurred, the following messages are displayed:
DXME0 23E: Error reading PROTOCOL.INI
DXMT0 37E: Adapter support required
PRO0025E: Fail to bind
Check the PROTOCOL.INI file if you receive these messages. Be sure the
Bindings = and DriverName parameters are entered correctly.
ΓòÉΓòÉΓòÉ 22.17.5. Error in Editing PROTOCOL.INI, or Missing NDIS MAC Driver ΓòÉΓòÉΓòÉ
If the value set for Bindings does not match the adapter and NDIS MAC driver
installed, or no NDIS MAC driver is installed, you will receive the following
error message:
PRO0025E: Fail to bind
Check the Bindings = statement and make sure you have installed the required
NDIS MAC driver.
ΓòÉΓòÉΓòÉ 22.17.6. PROTOCOL.INI File Is Not Found ΓòÉΓòÉΓòÉ
The PROTOCOL.INI file stores configuration and binding information for all the
device drivers in the system and for the NDIS MAC driver. If this file is not
found by PROTMAN.DOS, PROTMAN.DOS does not load. The following messages are
displayed:
PRO0003E: PROTOCOL.INI file open failure
PRO0023E: Cannot find Protocol Manager
DXME0 22E: Error communicating with Protocol Manager
DXMT0 37E: Adapter support required
To correct this situation, reconfigure the LAN Support Program. If
reconfiguration fails, check to see that the PROTOCOL.INI file is on the
current drive and that it is in the LANMAN directory (the default directory) or
in a directory that you have specified using the /I: parameter. You must add
the /I: parameter to the following statement:
DEVICE=\LSP\PROTMAN.DOS
in the CONFIG.SYS file if PROTOCOL.INI is not in the LANMAN directory.
If the problem persists, see the description of device driver error message 22E
on page Device Driver Message Listings.
ΓòÉΓòÉΓòÉ 22.18. Using Multiple Protocol Drivers with NDIS Adapters ΓòÉΓòÉΓòÉ
To configure for multiple protocol drivers, first configure your system for the
LAN Support Program. Then, update the PROTOCOL.INI file. Specify the other
protocol driver in CONFIG.SYS if it is a device driver or in AUTOEXEC.BAT if it
is a terminate-and-stay-resident (TSR) program.
In the following example, the LAN Support Program and another protocol stack
are configured to use the IBM Ethernet Adapter (IBM PS/2 Adapter/A for Ethernet
networks).
Configure the LAN Support Program for the IBM Ethernet Adapter. The resulting
PROTOCOL.INI file has the following named section:
[DXME0_MOD]
DriverName = DXME0$
Bindings = MACETH_MOD
The name in brackets (DXME0_MOD) identifies the named section. The driver name
is DXME0; the $ is added to it.
To add the other protocol driver to the LAN Support Program configuration, you
have to add a named section to the PROTOCOL.INI file. The information provided
with the other protocol stack should document the named section and protocol
driver names. You must know the name of the protocol driver before you can
proceed.
For this example, the other protocol driver name is IBMNDIS.SYS (the TCP/IP
NDIS protocol driver). The name of the named section (the name in brackets) can
be any word of 15 characters or less. In this example, the name of the named
section is also IBMNDIS.
The named section for the additional protocol driver is entered after the named
section for the LAN Support Program protocol driver, as follows:
[DXME0_MOD]
DriverName = DXME0$
Bindings = MACETH_MOD
[IBMNDIS]
DriverName = IBMNDIS$
Bindings = MACETH_MOD
If this protocol driver were a TSR program (for example, IBMNDIS.EXE), you
would update the AUTOEXEC.BAT file to place IBMNDIS.EXE before NETBIND, as
follows:
\path\IBMNDIS
\LSP\NETBIND
However, IBMNDIS.SYS is a device driver. To activate it, you must update the
CONFIG.SYS file to include the protocol driver after PROTMAN.DOS, as follows
(DXME0MOD.SYS is also included in the example):
DEVICE=\LSP\PROTMAN.DOS /I:\LSP
DEVICE=\LSP\MACETH.DOS
DEVICE=\LSP\DXMA0MOD.SYS
DEVICE=\LSP\DXME0MOD.SYS
DEVICE=\path\IBMNDIS.SYS
If both the other protocol driver and DXME0MOD.SYS bind to the same NDIS
adapter, and the other protocol driver opens the adapter before the LAN Support
Program is started, then the LAN Support Program cannot use a locally
administered address. The protocol driver that opened the adapter has obtained
the address from the NDIS MAC driver and is using that address. If the LAN
Support Program sets up a second address when it loads, the address used by the
protocol driver that was loaded first is no longer valid. It is recommended
that you use the universally administered adapter address when you have two
protocol drivers bound to the same adapter.
ΓòÉΓòÉΓòÉ 22.19. Using Unsupported NDIS Adapters ΓòÉΓòÉΓòÉ
Many adapters have DOS NDIS MAC drivers written to the NDIS interface that is
used by the LAN Support Program.
If you attempt to run the LAN Support Program with an unsupported NDIS adapter,
you can use the adapter if your adapter supplier has provided an IBM format NIF
on the adapter option diskette. If you do not have the NIF, you can edit the
CONFIG.SYS and PROTOCOL.INI files to add the unsupported adapter. In any case,
you must update the PROTOCOL.INI file to provide a named section for the
unsupported adapter.
To do this, be sure to copy the named section for each unsupported adapter to
the PROTOCOL.INI file in the LAN Support Program configuration. A sample named
section for the unsupported adapter should be provided in a sample PROTOCOL.INI
file found on the adapter option diskette, in the adapter documentation, or in
an information file on a diskette, such as a READ.ME file.
Then, you must edit the Bindings statement in the [DXME0_MOD] section to state
the module name for the unsupported adapter, and you must edit the CONFIG.SYS
file so that the unsupported NDIS MAC driver is loaded. You must also be sure
that the NDIS MAC driver required by the unsupported adapter is copied to the
same directory as the other LAN Support Program files or is located in a
directory where it can be accessed.
Configuration for an unsupported NDIS adapter is similar to configuration for a
supported NDIS adapter. The differences are as follows:
o The NDIS MAC driver for the unsupported adapter is different.
o The named section in the PROTOCOL.INI file is unique to the unsupported
adapter.
o The NDIS MAC driver name stated in the CONFIG.SYS command line and the module
name for the unsupported adapter are also unique.
It is possible to use unsupported adapters with a protocol driver that is not
supplied with the LAN Support Program. For this configuration, first configure
the computer separately for each protocol driver, as described in Using
Multiple Protocol Drivers with NDIS Adapters. Be sure to edit the PROTOCOL.INI
and CONFIG.SYS files as follows:
1. Copy the named sections for the NDIS MAC drivers for the unsupported
adapters to the PROTOCOL.INI file.
2. Copy the named section for the other protocol driver to the PROTOCOL.INI
file.
3. Be sure that the module name for each unsupported adapter is entered after
the Bindings statement in the named section for each protocol driver that
supports the adapter. If the other protocol driver and DXME0MOD.SYS both
are bound to the same adapter, put its module name after the Bindings =
statement for each of the protocol drivers.
4. Edit the CONFIG.SYS file to include the NDIS MAC driver names for the
unsupported adapters.
ΓòÉΓòÉΓòÉ 23. NetBIOS Over TCP/IP ΓòÉΓòÉΓòÉ
NetBIOS over TCP/IP provides a valuable functional enhancement to the LAN
Server product by enabling a workstation to be geographically isolated from its
domain and yet communicate with it transparently.
While the performance of NetBIOS over TCP/IP is very good, the TCP/IP component
must comply with architectural standards that were defined to satisfy
communication requirements over different physical networks at disparate
speeds. Another TCP/IP requirement was to provide universal connectivity at
the expense of optimized performance.
Consequently, the performance of NetBIOS over TCP/IP on local area networks is
not as good as that of the native NetBIOS protocol, NetBEUI, which has been
optimized for local area networks.
The MPTS shipped with LAN Server 4.0 provides the capability of configuring LAN
Requester (or LAN Server) workstations with both NetBEUI and NetBIOS over
TCP/IP on the same network interface card. This dual protocol stack
configuration allows local sessions to continue running with NetBEUI
performance while also providing Wide Area Network (WAN) connectivity with
NetBIOS over TCP/IP. For information on configuring with dual protocol stacks,
see MPTS - AnyNet for OS/2: Configuration Guide.
ΓòÉΓòÉΓòÉ 23.1. Configuring LAN Server 4.0 on a Wide-Area Network ΓòÉΓòÉΓòÉ
LAN Server 4.0 uses the NetBIOS application programming interface to accomplish
delivery and reception of data on a network. NetBIOS does not dictate what
underlying transport protocols are used. These protocols may or may not be
routeable.
ΓòÉΓòÉΓòÉ 23.1.1. Protocol Selection ΓòÉΓòÉΓòÉ
LAN Server 4.0 allows you to configure the underlying transport protocols. See
the MPTS configuration guide for detailed information on how to configure
protocols.
LAN Server 4.0's default protocol configuration is NetBIOS. IBM's NetBIOS
consists of the NetBIOS protocol plus the IEEE 802.2 transport protocol. You
can also configure LAN Server 4.0 to use NetBIOS over the TCP/IP protocol.
This configuration consists of the RFC 1001/1002 B-Node NetBIOS protocol plus
the TCP/IP transport protocol. Furthermore, you can use both NetBIOS and
NetBIOS over TCP/IP concurrently on the same workstation. This means that one
workstation can access local resources via NetBIOS and remote resources across
a wide-area network via NetBIOS over TCP/IP. If you use the LAN Server 4.0's
default protocol of NetBIOS, you will have a "classic" NetBIOS LAN. If you
configure for NetBIOS over TCP/IP as your only protocol, you will have a TCP/IP
network with the RFC 1001/1002 B-Node NetBIOS protocol being carried by TCP/IP
packets.
ΓòÉΓòÉΓòÉ 23.1.2. Understanding NetBIOS over TCP/IP ΓòÉΓòÉΓòÉ
NetBIOS over TCP/IP is IBM's OS/2 implementation of the RFC 1001/1002
standards. These standards describe how to enable NetBIOS applications over
TCP/IP. NetBIOS over TCP/IP is a high performance, ring zero device driver
implementation of a B-Node as defined in the RFC 1001/1002 standards. In
addition, three routing extensions have been added to allow NetBIOS over TCP/IP
nodes WAN access.
NetBIOS over TCP/IP provides NetBIOS semantics over TCP/IP. Just as NetBIOS
broadcasts a name query frame to establish a NetBIOS session, NetBIOS over
TCP/IP constructs a UDP broadcast frame to establish a NetBIOS session. A
NetBIOS broadcast domain is a bridged LAN and a NetBIOS over TCP/IP broadcast
domain is a TCP/IP subnet.
Three routing extensions have been implemented in NetBIOS over TCP/IP to allow
nodes to span subnets through IP routers:
o The first routing extension is the use of a broadcast file. A node's
broadcast file is loaded with IP broadcast addresses of other subnets. This
has the effect of extending a node's broadcast domain to its own subnet plus
any other subnets listed in the broadcast file.
o The second routing extension is the use of a names file. A node's names file
contains <NetBIOS name and IP address> pairs. On any NetBIOS name discovery
operation, NetBIOS over TCP/IP will search the names file first before
broadcasting to the network.
o The third routing extension is the use of a TCP/IP Domain Name Server (DNS).
A network administrator can enter NetBIOS names (in an encoded format) and IP
address pairs into a DNS. One of the steps NetBIOS over TCP/IP can take
during the name discovery process is to issue a gethostbyname function
request to the DNS to lookup an IP address for a NetBIOS name.
ΓòÉΓòÉΓòÉ 23.1.3. Configuration Tradeoffs ΓòÉΓòÉΓòÉ
When making LAN Server 4.0 wide-area networking configuration decisions,
consider that LAN Server 4.0 is a NetBIOS application. LAN Server 4.0 uses
NetBIOS's broadcasting capabilities for such operations as LOGON, NET LOGON,
NET VIEW (see the srvannounce and srvhidden parameters in IBM OS/2 LAN Server
Version 4.0 Network Administrator Reference Volume 2: Performance Tuning), and
server NET.ACC replication (see the pulse parameter in IBM OS/2 LAN Server
Version 4.0 Network Administrator Reference Volume 2: Performance Tuning). In a
LAN environment, NetBIOS broadcast frames are seen throughout the entire LAN.
This allows servers to see their clients and clients to see their servers. This
is no longer true in a WAN environment. TCP/IP does not propagate broadcast
frames through IP routers. If it did, network traffic would be prohibitive.
In a WAN environment, a LAN Server 4.0 domain comprises many IP subnets
connected by IP routers. For LAN Server 4.0 to operate without any loss of
function, a LAN Server 4.0 broadcast frame in one subnet must be seen by all of
the subnets comprising the LAN Server 4.0 domain. For example, a LAN Server
4.0 server broadcasts a server announce frame to its subnet. If this frame is
not propagated to the client's subnets, the client's NET VIEW command will not
show this server. The figure titled Example LAN Server Network describes an
example LAN Server network topology and examples of usage of the three routing
extensions.
Example LAN Server Network
ΓòÉΓòÉΓòÉ 23.1.4. Broadcast File Solution ΓòÉΓòÉΓòÉ
A simple solution to the broadcast differences between a LAN and WAN
environment is to create a broadcast file on every workstation, whether it is a
server or a client. The contents of the broadcast file are a list of every
other subnet broadcast address. The creation of a broadcast file can be
automated through the use of CID install. Using this method insures no loss of
LAN Server function, since the NetBIOS broadcast domain includes all subnets.
Following are the contents of the broadcast file for the example network:
LAN Server 4.0 DOMAIN CONTROLLER - Subnet A
IBMCOM\RFCBCST.LST
129.35.95.255 - Subnet B broadcast address
129.35.111.255 - Subnet C broadcast address
129.35.127.255 - Subnet D broadcast address
LAN Server 4.0 ADDITIONAL SERVER - Subnet B
IBMCOM\RFCBCST.LST
129.35.79.255 - Subnet A broadcast address
129.35.111.255 - Subnet C broadcast address
129.35.127.255 - Subnet D broadcast address
LAN Server 4.0 CLIENTS - Subnet C
IBMCOM\RFCBCST.LST
129.35.79.255 - Subnet A broadcast address
129.35.95.255 - Subnet B broadcast address
129.35.127.255 - Subnet D broadcast address
LAN Server 4.0 CLIENTS - Subnet D
IBMCOM\RFCBCST.LST
129.35.79.255 - Subnet A broadcast address
129.35.95.255 - Subnet B broadcast address
129.35.111.255 - Subnet C broadcast address
Notes:
1. Check your router documentation to insure the router will route directed
broadcast frames. That is, IP frames that have a specific netid for the
network portion of the IP address, and have the host portion of the IP
address set to all ones.
2. A maximum of 32 broadcast file entries are supported.
ΓòÉΓòÉΓòÉ 23.1.5. Names File Solution ΓòÉΓòÉΓòÉ
Before NetBIOS over TCP/IP broadcasts to the network to discover an IP address
for a NetBIOS name, it can search a local copy of a NetBIOS names file. The
NetBIOS names file is analogous in concept to a TCP/IP hosts file. To enable
this routing extension, set the PROTOCOL.INI parameter NAMESFILE = to a nonzero
integer that represents the number of names file entries. The creation of a
names file can be automated through the use of CID install. The advantage of
using a names file is the reduction of name query broadcast frames. For a LAN
Server environment, the clients would need a names file listing the "computer
name" IP address and "domain name" IP address of each server to be contacted.
The servers would need a names file listing the "computer name" IP address of
each connecting client. The computer name and domain name are found in the
IBMLAN.INI file. Following are names file contents for the example network:
LAN Server 4.0 DOMAIN CONTROLLER - Subnet A
IBMCOM\RFCNAMES.LST
"BRPKWY" 129.35.80.3
"c903_2" 129.35.96.2
"c903_3" 129.35.96.3
"c903_4" 129.35.96.4
"c903_5" 129.35.96.5
"c904_2" 129.35.112.2
"c904_3" 129.35.112.3
"c904_4" 129.35.112.4
"c904_5" 129.35.112.5
LAN Server 4.0 ADDITIONAL SERVER - Subnet B
IBMCOM\RFCNAMES.LST
"MitchellD" 129.35.64.2
"Mitchell" 129.35.64.2
"c903_2" 129.35.96.2
"c903_3" 129.35.96.3
"c903_4" 129.35.96.4
"c903_5" 129.35.96.5
"c904_2" 129.35.112.2
"c904_3" 129.35.112.3
"c904_4" 129.35.112.4
"c904_5" 129.35.112.5
LAN Server 4.0 CLIENTS - Subnet C
IBMCOM\RFCNAMES.LST
"MitchellD" 129.35.64.2
"Mitchell" 129.35.64.2
"BRPKWY" 129.35.80.3
LAN Server 4.0 CLIENTS - Subnet D
IBMCOM\RFCNAMES.LST
"MitchellD" 129.35.64.2
"Mitchell" 129.35.64.2
"BRPKWY" 129.35.80.3
Notes:
1. Because the NetBIOS broadcast domain is a single subnet, uniqueness of
NetBIOS names cannot be guaranteed.
2. NetBIOS over TCP/IP uses a prefix match in searching the names file. For
the above example, if the names file on a subnet C client is being
searched for "Mitch", a match would occur for the first string in the
names file containing the pattern "Mitch". In this case, it would be
"MitchellD" 129.35.64.2. Consequently, the order in which NetBIOS
names are listed in the names file is important.
ΓòÉΓòÉΓòÉ 23.1.6. TCP/IP Domain Name Server Solution ΓòÉΓòÉΓòÉ
The DOMAINSCOPE = PROTOCOL.INI parameter is the NetBIOS over TCP/IP third
routing extension. Enable this parameter by setting DOMAINSCOPE = "your TCP/IP
domain name". For this example, DOMAINSCOPE = "austin.ibm.com". For this
example, when NetBIOS over TCP/IP tries to discover the LAN Server domain name
"MitchellD" (which is a group NetBIOS name) and DOMAINSCOPE = "austin.ibm.com",
NetBIOS over TCP/IP would issue a sockets
gethostbyname("ENGJHEGDGIGFGMGMEECACACACACACAAA.austin.ibm.com") to your TCP/IP
domain name server.
If the domain name server knows this name, it will send back the IP address to
NetBIOS over TCP/IP. The advantage is that you could potentially have a
central repository for all NetBIOS names. But you have to update your domain
name server database file with NetBIOS Names in an encoded format.
An encoded format is necessary because the NetBIOS names are 16 bytes of any
bit pattern. A TCP/IP domain name server only accepts host names in the
character set эa..z and 0..9∙. NetBIOS over TCP/IP encodes the 16 byte NetBIOS
name into a 32 byte reversible, half-ASCII format. You can use the MAPNAME.EXE
command provided as an applet to encode/decode NetBIOS names.
The following example details the records you would add to your domain name
server database given the previous example:
;
ENGJHEGDGIGFGMGMEECACACACACACAAA 86400 IN A 129.35.79.255
IN HINFO MitchellD (0x00 in 16th byte)
;
ENGJHEGDGIGFGMGMCACACACACACACAAA 86400 IN A 129.35.64.2
IN HINFO Mitchell (0x00 in 16th byte)
;
ENGJHEGDGIGFGMGMCACACACACACACAAD 86400 IN CNAME
ENGJHEGDGIGFGMGMCACACACACACACAAA
IN HINFO Mitchell (0x03 in 16th byte)
;
ENGJHEGDGIGFGMGMCACACACACACACACA 86400 IN CNAME
ENGJHEGDGIGFGMGMCACACACACACACAAA
IN HINFO Mitchell (0x20 in 16th byte)
;
ECFCFAELFHFJCACACACACACACACACAAA 86400 IN A 129.35.80.3
IN HINFO BRPKWY (0x00 in 16th byte)
;
ECFCFAELFHFJCACACACACACACACACAAD 86400 IN CNAME
ECFCFAELFHFJCACACACACACACACACAAA
IN HINFO BRPKWY (0x03 in 16th byte)
;
ECFCFAELFHFJCACACACACACACACACACA 86400 IN CNAME
ECFCFAELFHFJCACACACACACACACACAAA
IN HINFO BRPKWY (0x20 in 16th byte)
;
GDDJDADDFPDCCACACACACACACACACAAA 86400 IN A 129.35.96.2
IN HINFO c903_2 (0x00 in 16th byte)
;
GDDJDADDFPDDCACACACACACACACACAAA 86400 IN A 129.35.96.3
IN HINFO c903_3 (0x00 in 16th byte)
;
GDDJDADDFPDECACACACACACACACACAAA 86400 IN A 129.35.96.4
IN HINFO c903_4 (0x00 in 16th byte)
;
GDDJDADDFPDFCACACACACACACACACAAA 86400 IN A 129.35.96.5
IN HINFO c903_5 (0x00 in 16th byte)
;
GDDJDADEFPDCCACACACACACACACACAAA 86400 IN A 129.35.112.2
IN HINFO c904_2 (0x00 in 16th byte)
;
GDDJDADEFPDDCACACACACACACACACAAA 86400 IN A 129.35.112.3
IN HINFO c904_3 (0x00 in 16th byte)
;
GDDJDADEFPDECACACACACACACACACAAA 86400 IN A 129.35.112.4
IN HINFO c904_4 (0x00 in 16th byte)
;
GDDJDADEFPDFCACACACACACACACACAAA 86400 IN A 129.35.112.5
IN HINFO c904_5 (0x00 in 16th byte)
ΓòÉΓòÉΓòÉ 24. LAN Manager 1.0 NetBIOS Interface ΓòÉΓòÉΓòÉ
The LAN Manager 1.0 (LM10) interface was developed by Microsoft Corporation and
extended by IBM. The protocol drivers for IBM NetBIOS (NETBEUI.OS2) and IBM
NetBIOS over TCP/IP support (TCPBEUI.OS2) support this LM10 interface, which is
an extended NetBIOS interface. IBM has not externalized this LM10 interface as
an API, but the interface document is available for use in developing LM10
interface drivers.
The NetBIOS described in IBM LAN Technical Reference is the NB30 (NetBIOS 3.0)
interface. MPTS includes both NB30 (both ring3 and ring1) and LM10 (protocol)
drivers. The NetBIOS NB30 is separated from session and link layer protocol
flows. This allows other LM10 protocol drivers to work with the NB30 driver,
allowing any NB30 NetBIOS applications to run on any LM10 interface-supported
protocol.
LAN Manager 1.0 (LM10) Interface
Each LM10 NetBIOS driver controls one or more NetBIOS networks and a single
system can have multiple LM10 NetBIOS drivers installed. This is, LM10 NetBIOS
protocol drivers can choose to support more than one adapter. For example, the
IBM NetBIOS protocol driver (NETBEUI.OS2) supports up to ten adapters.
ΓòÉΓòÉΓòÉ 24.1. Applications using the LM10 Interface ΓòÉΓòÉΓòÉ
NB30 NetBIOS API:
NB30 NetBIOS supports only four adapters, even though the LM10 NetBIOS protocol
drivers support more than four adapters. NetBIOS applications using the NB30
API can use more than four adapters but can use only a maximum of four LM10
NetBIOS protocols. The following example shows a NB30 NetBIOS configuration in
the PROTOCOL.INI file that uses LM10 NetBIOS protocols, using four adapters.
[NETBIOS]
drivername=NETBIOS$
adapter0=NETBEUI$, 0
adapter1=AILANBIO$, 1
adapter2=TCPBEUI$, 2
adapter3=ATTISO$, 3
The numbers after the LM10 NetBIOS protocol drivers refer to logical adapter
number. All these can be mapped to one or more physical adapters on the
system. Use the the figure titled LAPS Configuration Window to assign or
change the logical adapter numbers.
Using the LAPS MPTS configuration window, the LM10 NetBIOS can be turned on or
off with the "Enable NetBIOS Application Support" option while editing the
protocol driver parameters.
ΓòÉΓòÉΓòÉ 24.2. LAN Server and Requester ΓòÉΓòÉΓòÉ
The LAN server and requester also use this LM10 NetBIOS interface to interact
with the protocol drivers. The LAN server and requester support 10 adapters
and can be configured to use more than four LM10 protocols. An example of the
LAN server or requester configuration is:
[networks]
net1=netbeui$,0,LM10, 16, 16, 14
net2=tcpbeui$,0,LM10, 16, 16, 10
ΓòÉΓòÉΓòÉ 24.3. Installing Additional LM10 Protocol Drivers ΓòÉΓòÉΓòÉ
Other IBM and OEM LM10 NetBIOS interface-supported protocol drivers that are
not supplied by MPTS can be installed. These protocol drivers should comply
with the LM10 NetBIOS interface. Developers of LM10 NetBIOS interface
protocols, can request the NDIS package from IBM. To install additional
protocols, choose the "other protocols" pushbutton depicted in the figure
titled LAPS Configuration Window The LM10 NetBIOS protocol drivers and the
associated .NIF files are copied to the IBMCOM\PROTOCOL directory.
ΓòÉΓòÉΓòÉ 24.4. Configuring Additional LM10 Protocol Drivers ΓòÉΓòÉΓòÉ
The LAPS configuration can be used to configure OEM LM10 protocol drivers.
Create a .NIF file for the protocol drivers. The .NIF file should add the
keyword NBAPI, which notifies the LAPS configuration that the protocol is an
LM10 protocol. An example of this keyword section follows:
[NBAPI]
DISPLAY = Enable NetBIOS application support
Type = String
StrLength = 3
Set = Yes, NO
Nlsset = Yes, NO
Scope = global
Optional = yes
Editable = yes
Help = This parameter specifies whether NetBIOS applications
will be allowed to run over this protocol.
For more information about .NIF files, request the NDIS information package
from IBM.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Other than the IBM Token-Ring Network 16/4 Adapter II.