home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
lsnata40.zip
/
LS40NAR2.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1995-04-20
|
260KB
|
8,501 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 Corporation 1988, 1994. All
rights reserved.
(C) Copyright Microsoft Corp. 1988, 1991.
Note to U.S. Government Users - Documentation 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 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 Avenue, Thornwood, NY 10594, USA.
Asia-Pacific users can inquire, in writing, to the IBM Director of Intellectual
Property and Licensing, IBM World Trade Asia Corporation, 2-31 Roppongi
3-chome, Minato-ku, Tokyo 106, Japan.
ΓòÉΓòÉΓòÉ 3.1. Trademarks ΓòÉΓòÉΓòÉ
The following terms, denoted by an asterisk (*) in this publication, are
trademarks of the IBM Corporation in the United States and/or other countries:
PS/2 Personal Computer AT
IBM Personal System/2
Operating System/2 PS/55
OS/2 LAN Server
The following terms, denoted by a double asterisk (**) in this publication, are
trademarks of other companies as follows:
NetWare Novell, Inc.
Pentium Intel Corporation
ΓòÉΓòÉΓòÉ 4. About This Book ΓòÉΓòÉΓòÉ
This book provides information concerning configuration parameters and
performance-related topics for the IBM(**) Operating System/2 (OS/2)(**) LAN
Server(**) Version 4.0 product. IBM OS/2 LAN Server Version 4.0 Network
Administrator Reference Volume 1: Planning, Installation, and Configuration
(hereafter referred to as the LAN Server Network Administrator Reference
Volume 1: Planning, Installation, and Configuration) introduces LAN Server,
briefly discusses its main features, and provides information about planning
and installing a network. IBM OS/2 LAN Server Version 4.0 Network Administrator
Reference Volume 3: Network Administrator Tasks (hereafter referred to as the
LAN Server Network Administrator Reference Volume 3: Network Administrator
Tasks) provides information about setting up and using LAN Server.
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 set occupies 1 byte. DBCS is a graphic character set in which each
character occupies 2 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. Entering, displaying, and printing DBCS
characters require special hardware and support. DBCS information is included
throughout this book. Restrictions for DBCS systems are indicated by shaded
notes, for example:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: The DOS workstations on Γöé
Γöé your network should have IBM DOS 5.0, IBM DOS 5.0/V, PC DOS 6.1/V, Γöé
Γöé MS DOS 6.2/V or PC DOS 6.3/V. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 4.1. Who Should Use This Book ΓòÉΓòÉΓòÉ
This book is intended as a reference for the network administrator, who is
responsible for installing, configuring, tuning, managing, and controlling a
network. The network administrator also defines resources to be shared and
user access to the shared resources.
Additional users of this book include network users, IBM technical support
personnel, marketing representatives, data processing professionals, and
application developers.
You should also be familiar with the following:
o OS/2
o DOS
o An ASCII text editor
ΓòÉΓòÉΓòÉ 4.2. How This Book Is Organized ΓòÉΓòÉΓòÉ
This book is organized according to the groups of parameters that affect the
performance of a network and the tasks that enable a network administrator to
improve the performance of a network.
This book has the following chapters and appendixes:
o LAN Server Design Concepts, "LAN Server Design Concepts," describes the major
factors in the LAN design that affect performance.
o Tuning LAN Server Performance Parameters, "Tuning LAN Server Performance
Parameters," describes the concepts that enable the network administrator to
tune LAN Server performance.
o IBMLAN.INI File Parameter Descriptions, "IBMLAN.INI File Parameter
"Descriptions," describes the IBMLAN.INI file and the parameters contained
within each section of the IBMLAN.INI file.
o NETWORK.INI File Parameter Descriptions, "NETWORK.INI File Parameter
Descriptions," describes the NETWORK.INI file and the parameters it contains.
o CONFIG.SYS File Parameter Descriptions, "CONFIG.SYS File Parameter
Descriptions," describes the CONFIG.SYS file and the parameters it contains.
Additional information about the use of the CONFIG.SYS file is also provided.
o Configuration Files, "Parameter Tables for Configuration Files," contains
parameter tables listing minimum, maximum, and default values for each
parameter. Some parameter dependencies are also indicated.
o File Examples, "File Examples," provides examples of the IBMLAN.INI,
CONFIG.SYS, and PROTOCOL.INI files.
ΓòÉΓòÉΓòÉ 4.3. Conventions ΓòÉΓòÉΓòÉ
This book uses the following terminology conventions unless otherwise noted:
o PC LAN Program refers to IBM PC LAN Program Version 1.3, a program which is
not used by Double-Byte Character Set (DBCS) Users.
o DOS LAN Services refers to the LAN Server Version 4.0 component that enables
DOS users to be members of an OS/2 local area network.
o DOS requester refers to a machine running DOS LAN Services.
o OS/2 requester refers to a machine running the OS/2 LAN Requester component
of LAN Server Version 4.0.
o Workstation refers to any Personal Computer AT(**) (requester only), Personal
System/2(**) (PS/2(**)), PS/55(**) or compatible computer (server or
requester) on the network.
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 Γöé o Configuration file parameters Γöé
Γöé Γöé Γöé
Γöé Γöé o Controls (when used in procedures), for Γöé
Γöé Γöé example: Γöé
Γöé Γöé Γöé
Γöé Γöé - Menu bar choices Γöé
Γöé Γöé - Radio buttons Γöé
Γöé Γöé - Push buttons Γöé
Γöé Γöé - List boxes Γöé
Γöé Γöé - Check boxes Γöé
Γöé Γöé - Entry fields Γöé
Γöé Γöé - 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 reader must type Γöé
Γöé Γöé o Text displayed on the computer screen Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Throughout this book the following command syntax is used.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 2. Command Syntax Used in Book Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYMBOL Γöé MEANING Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CAPITAL LETTERS Γöé The abbreviated form of a command or parameter Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé [ ] Γöé An optional parameter Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé { } Γöé A required parameter Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé | Γöé Choose only one parameter. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé [a|b] Γöé Choose either a or b, or neither a nor b. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé {a|b} Γöé Choose either a or b. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ... Γöé You can repeat the parameter on the command Γöé
Γöé Γöé line. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 4.4. Prerequisite Book ΓòÉΓòÉΓòÉ
The LAN Server Network Administrator Reference Volume 1: Planning,
Installation, and Configuration provides prerequisite information on the topics
discussed in this book. It contains an introduction to the LAN Server software
and provides the steps and basic information needed to install and configure
LAN Server. It also contains an introduction to the network hardware and basic
information needed to install and configure your network adapter cards.
ΓòÉΓòÉΓòÉ 4.5. Related Books ΓòÉΓòÉΓòÉ
The following is a list of books you might find helpful. For information on
ordering these publications, contact your IBM authorized dealer or IBM
marketing representative.
o IBM Extended Services for OS/2 Network Administration Guide
o IBM LAN Technical Reference
o IBM Extended Services for OS/2 Information and Planning Guide
o IBM System Performance Monitor/2 Reference
o IBM Token-Ring Network Technical Reference
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 OS/2 LAN Requester User's Guide
o IBM OS/2 LAN Server Problem Determination Guide
o IBM OS/2 LAN Server Version 4.0 Network Administrator Reference Volume 3:
Network Administrator Tasks
o Coexistence Guide of OS/2 LAN Server and NetWare(**) from IBM
o IBM OS/2 LAN Server Version 4.0 Network Administrator Reference Volume 1:
Planning, Installation, and Configuration
o OS/2 Technical Library, Programming Guide Volume 1
o OS/2 Technical Library, Programming Guide Volume 2
o OS/2 Technical Library, Programming Guide Volume 3
ΓòÉΓòÉΓòÉ 5. LAN Server Design Concepts ΓòÉΓòÉΓòÉ
This chapter describes the major features of the LAN Server design that affect
performance. It also describes the functions of the key performance parameters
in the IBMLAN.INI and CONFIG.SYS files, which are the files that hold
configuration information for LAN Server Version 4.0. Parameter descriptions
and tuning guidelines are located in other chapters.
LAN Server, a program that contains server and requester components, which
allow resources to be shared with other computers on the network, 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 or Entry server) supports server and requester functions for
386-, 486-, or Pentium(**)-based workstations.
o IBM OS/2 LAN Server Version 4.0-Advanced (hereafter referred to as LAN
Server-Advanced or Advanced server) supports the 386 high performance file
system functions, such as Fault Tolerance, Directory Limits, and Local
Security in addition to all functions available in Entry server. The
386HPFS is an installable system that provides fast access to very large disk
volumes. The 386-HPFS functions bypass most OS/2 kernel services (the OS/2
APIs), thereby improving response time. The Advanced server runs only with
OS/2 2.1 or higher on a 386-, 486-, or Pentium-based workstation. Hereafter
references to a 386 processor or system will also apply to 486- and
Pentium-based workstations.
: reftype=fn refid=intl.Pentium:elink.
Refer to the LAN Server Network Administrator Reference Volume 1: Planning,
Installation, and Configuration for a brief description of each installable
function and the default components installed with each package.
ΓòÉΓòÉΓòÉ 5.1. What's New for LAN Server 4.0 Performance and Capacity Tuning? ΓòÉΓòÉΓòÉ
o IBM LAN Server 4.0 Performance Tuning Assistant
This utility program assists in fine tuning the resources of the LAN Server
4.0 system to match the users' configuration requirements. This utility is,
with minor modifications, a stand-alone version of a configuration
spreadsheet tool that has been in use by LAN Server administrators for a long
time. It goes beyond the spreadsheet tool by actually updating the servers'
configuration files automatically. Start Tuning Assistant GUI at any time
after the install process has been completed with the command LS40TUNE from
any OS/2 command line. Or click on the Tuning Assistant icon in the LAN
Services container. It is strongly recommended that this utility be used in
order achieve the best performance possible from LAN Server 4.0.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: Γöé
Γöé Γöé
Γöé Additional features for DBCS users are as follows: Γöé
Γöé Γöé
Γöé o Remote Initial Program Load for users of DOS 6.3/V Γöé
Γöé Γöé
Γöé o DOS LAN Services through Windows for users of DOS 5.0/V and Γöé
Γöé higher Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
o New DOS Requester: DOS LAN Services (DLS)
The DOS LAN Requester (DLR) code has been completely updated with a new DOS
requester product called DOS LAN Services (DLS). This is a new code base
which provides many new features including Peer file and print sharing,
reduced RAM redirectors for both DOS and Windows, a new Graphical User
Interface (GUI), and several other significant enhancements. DOS users will
observe a significant performance improvement over past network experience in
many of their applications. This is accomplished primarily by retaining
information read from the server in workstation buffers more effectively.
o New LAN Server 4.0 Configuration Defaults
The Advanced version of LAN Server 3.0 is being used in much larger
configurations than the default settings of many parameters allow,
necessitating changes by the administrator before the server can be ready for
use by all intended clients. LAN Server 4.0 addresses this situation by
providing a new set of parameter defaults that support 100 users or clients
without modification. For systems with at least than 20MB of memory, the
default memory cache size will be 60% of available memory after OS/2 is
loaded. Because more memory is required for these defaults, the person who
installs LAN Server 4.0 should first run the Tuning Assistant. The utility
will calculate the memory requirements and warn if a memory shortage exists.
The Entry server will have defaults to support only 20 to 30 clients so that
it can run in a smaller memory machine than the Advanced server. The LAN
Server 4.0 installer should run the Tuning Assistant for Entry server also,
so that all available system memory will be used to optimize its performance
and capacity.
o LAN Server 4.0 Capacity Enhancements
As the number of clients connected to LAN Server 3.0 has grown to several
hundreds in some installations, some architectural limitations have been
found which are addressed in LAN Server 4.0. In particular, the numreqbufs
parameter was limited to about 350, and this limitation impacted performance.
This limit has now been removed, and the numreqbufs parameter can now be as
large as 2000 if sufficient system memory is available.
o LAN Server 4.0 support for Pentium and Symmetric Multi-Processor (SMP)
LAN Server 4.0 is enabled for Pentium processors, and when running under OS/2
for SMP, it supports SMP processor machines.
o DCDB Replication Performance
Some significant performance gains have been achieved by enhancing DCDB
replication routines.
o NetBIOS over TCP/IP Performance
TCPBEUI, a new device driver which runs at ring 0 privilege along with OS/2
NetBIOS over TCP/IP, is being shipped with LAN Server 4.0 and provides
improved performance over OS/2 NetBios for TCP/IP used by LAN Server 3.0.
o Original Equipment Manufacturer (OEM) Adapter Card Support
Support for additional OEM adapter cards both Token Ring and Ethernet, is
provided in LAN Server 4.0. Several of these cards are efficient
wide-data-path cards, that enable better LAN Server 4.0 system performance.
ΓòÉΓòÉΓòÉ 5.2. LAN Server-Entry Design Overview ΓòÉΓòÉΓòÉ
LAN Server-Entry, otherwise known as Entry server, runs at application
privilege level. It is well suited for multi-purpose servers running other
applications, and may also serve as a desktop workstation. The Entry server
uses OS/2 services to satisfy network file I/O requests, session setup, and
resource sharing. The Entry server handles ring 3 requests, which include
requests for files stored on a file allocation table (FAT) partition, print
requests, and serial device requests. For better performance, recommended uses
of version 4.0 include:
o As a shared system with a local user
o As a shared system with primarily ring 3 applications
o As a dedicated print or serial device server
o As a multipurpose server with plenty of memory to handle the anticipated
amount of traffic without requiring a high-performance file server
Network file I/O requests and responses are sent by way of server message
blocks (SMBs). The Entry server processes SMBs using internal network buffers.
The IBMLAN.INI file parameters that define the size and number of network
buffers on the server are sizreqbuf and numreqbuf. The IBMLAN.INI file
parameters that define the size and number of network buffers on the requester
are sizworkbuf and numworkbuf. For system architecture, see System
Architecture of the OS/2 Entry Server and OS/2 Requester.
An SMB received from the network is copied into the adapter receive buffers by
the network adapter. The NetBIOS device driver, using a global descriptor
table (GDT) selector, copies the data from the adapter's receive buffers into
an available server network buffer. The NetBIOS device driver can acknowledge
the message or piggyback the acknowledgment on a subsequent network message.
The PROTOCOL.INI file contains the configuration information for the NetBIOS
device driver.
The SMB is passed through the redirector to the server. The redirector is a
requester component that directs file system request traffic between the
server, the file system, and the network. There exists three types of SMB
protocols which may be used for transferring data between a requester and a
server:
o Core SMB protocol header and data reside within one network buffer. This SMB
protocol is used to transfer amounts of data that are less than or equal to
the buffer size specified by the sizworkbuf parameter.
o Read and Write (RAW) SMB protocol header and data reside within the first
network buffer. Subsequent data is transferred through big buffers without
header information. This flow continues until all requested data has been
received; no additional SMB requests are required. The RAW SMB protocol is
used if the amount of data to transfer exceeds the network buffer size and if
big buffers are available.
o Multiplexed SMB protocol header and data reside within the initial network
buffer. Subsequent data is sent in network buffers without header information
along with the SMB response protocol header. This flow continues until all
requested data has been received; no additional SMB requests are required.
Multiplexed SMB protocol is used if the amount of data to transfer exceeds
the requester buffer size and if either RAW SMB protocol is not supported or
big buffers are not available. The numbigbuf parameter in the IBMLAN.INI
file on the server specifies the number of big buffers. Both RAW and
Multiplexed protocols are used to transfer large amounts of data very
quickly.
Entry server is designed to optimize the movement of file I/O from the server
to the requester, and it supports both the file allocation table (FAT) file
system and the high performance file system (HPFS). Both the FAT file system
and the HPFS have a cache that is used to improve performance by keeping
frequently used data in memory. A cache is a high-speed storage buffer that
contains frequently accessed instructions and data. For more information about
caches, see Server CONFIG.SYS Performance Parameters. For performance and
functional comparisons between the FAT file system and the HPFS, see Comparison
between the FAT File System and the HPFS.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 3. Comparison between the FAT File System and the HPFS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CHARACTERISTIC Γöé OS/2 2.1 FAT FILE SYSTEM Γöé HPFS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Maximum file-name Γöé 11 (8.3 format) charac- Γöé 255 characters (bytes) Γöé
Γöé length Γöé ters (bytes) Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé File attributes Γöé Bit flags plus up to Γöé Bit flags plus up to Γöé
Γöé Γöé 64KB, text or binary Γöé 64KB, text or binary Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Maximum path length Γöé 64 characters (bytes) Γöé 260 characters (bytes) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Average wasted space Γöé 1/2 cluster (1KB) Γöé 1/2 sector (256 bytes) Γöé
Γöé per file Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Allocation information Γöé Centralized in FAT file Γöé Located near each file Γöé
Γöé for files Γöé system on home track Γöé in its FNODE Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Free disk-space infor- Γöé Centralized in FAT file Γöé Located near free space Γöé
Γöé mation Γöé system on home track Γöé in bit maps Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Directory structure Γöé Unsorted linear list, Γöé Sorted B-tree Γöé
Γöé Γöé must be searched exhaus- Γöé Γöé
Γöé Γöé tively Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Directory location Γöé Root directory on home Γöé Located near seek Γöé
Γöé Γöé track, others scattered Γöé center of volume Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Read-ahead Γöé Optional Γöé Entry: Cache reads in Γöé
Γöé Γöé Γöé 8KB blocks Γöé
Γöé Γöé Γöé Advanced: Sensitive Γöé
Γöé Γöé Γöé to data type Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Cache replacement Γöé Simple least recently Γöé Entry: Modified LRU Γöé
Γöé strategy Γöé used (LRU) algorithm Γöé Advanced: Sensitive Γöé
Γöé Γöé Γöé to data type Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Write-behind (lazy Γöé Optional, can be handled Γöé Optional, can be Γöé
Γöé write) Γöé on a per-file basis Γöé handled on a per-file Γöé
Γöé Γöé Γöé basis Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Caching program Γöé DISKCACHE Γöé Entry: CACHE.EXE Γöé
Γöé Γöé (in CONFIG.SYS file) Γöé Advanced: CACHE386.EXE Γöé
Γöé Γöé Γöé (values specified for Γöé
Γöé Γöé Γöé the IFS and RUN state- Γöé
Γöé Γöé Γöé ments in the CONFIG.SYS Γöé
Γöé Γöé Γöé file) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Maximum cache size Γöé 8MB Γöé Entry: 2MB Γöé
Γöé Γöé Γöé Advanced: Physical Γöé
Γöé Γöé Γöé memory available Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Cache threshold Γöé Variable, up to 64KB Γöé Entry: Variable, up to Γöé
Γöé Γöé 3.5KB default Γöé 64KB Γöé
Γöé Γöé Γöé Advanced: Sensitive Γöé
Γöé Γöé Γöé to data type Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The design of Entry server is optimized to handle three typical file accesses:
o Random file access is characterized by a request for a small amount of data
that may reside anywhere in the file. In this case, the core SMB protocol is
typically used by the requester. The data is cached in the file system to
minimize disk seeks.
o Sequential file access is characterized by successive requests for data that
is contiguous in the file. In this case, the core SMB protocol is used by
the requester as long as the requested amount of data is less than or equal
to the requester's network buffer size (sizworkbuf).
o Large file transfer is characterized by a request for an amount of data that
is greater than the size of the sizworkbuf. In this case, the multiplexed or
Read and Write (RAW) SMB protocol is used by the requester. In anticipation
of the next request, the Entry server performs read-ahead independently of
the file system, using one of its big buffers if the RAW SMB protocol is
used.
For the Entry server, I/O requests to the file system are made using OS/2 APIs.
Once an API call finishes, the server returns the SMB to the requester as an
SMB response.
System Architecture of the OS/2 Entry Server and OS/2 Requester shows the
components that may influence the performance of an Entry server and OS/2
requester. This figure also provides a reference for discussing individual
performance-related elements.
System Architecture of the OS/2 Entry Server and DOS LAN Services shows the
components that may influence the performance of Entry server and the DOS
workstation. This figure also provides a reference for discussing individual
performance-related elements.
Γöé
<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇServerΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>Γöé<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇRequesterΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Local Γöé Γöé Γöé Local Γöé
Γöé application Γöé Γöé Γöé application Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé
Γöé LAN Server 4.0 - Entry Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé
Γöé Request Γöé Big Γöé ΓöîΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé buffers Γöé buffers Γöé Γöé OS/2 API Γöé Γöé Γöé OS/2 API Γöé
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé Γöé Γöé Γöé Application
Γöé Γöé Γöé Γöé privilege
ΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Γöé Γöé Γöé Γöé System
Γöé Γöé Γöé Γöé privilege
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé OS/2 kernel Γöé Γöé Γöé OS/2 kernel Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ΓöîΓöÇΓöñ IFS Γöé FAT Γöé Γöé Γöé IFS Γöé
Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ Γöé Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé RedirectorΓöé Γöé Γöé Γöé Γöé Redirector Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöîΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé
Γöé Γöé File Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ΓöésystemΓö£ΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Work Γöé Work Γöé
Γöé ΓöédriverΓöé Γöé Γöé Γöé Γöé buffers Γöé cache Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÿ
Γöé Γöé Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé Γöé HPFS Γöé Γöé Γöé Γöé Γöé
Γöé Γöé cacheΓöé Γöé Γöé Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé Γöé Γöé
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÉ Γöé ΓöîΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéNetBIOS Γöé ΓöéDisk driverΓöé Γöé ΓöéNetBIOS Γöé
ΓöéprotocolΓöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöéprotocolΓöé
Γöé driver Γöé Γöé DISKCACHE Γöé Γöé Γöé driver Γöé
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Network adapter Γöé Γöé Γöé Γöé Network adapter Γöé
Γöé driver Γöé Γöé Γöé Γöé driver Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéReceive Γöé TransmitΓöé Γöé Γöé ΓöéReceive Γöé TransmitΓöé
Γöébuffers Γöé buffers Γöé Γöé Γöé Γöébuffers Γöé buffers Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ PC Processor
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéNetwork adapterΓöé ΓöéDisk adapterΓöé Γöé Γöé Network adapter Γöé
Γöé card Γöé Γöé card Γöé Γöé Γöé card Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
System Architecture of the OS/2 Entry Server and OS/2 Requester
Γöé
<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇServerΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>Γöé<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇRequesterΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Local Γöé Γöé Γöé Local ΓöéApplicationΓöé
Γöé application Γöé Γöé Γöéapplication Γöé memory Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé
Γöé LAN Server 4.0 - Entry Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé
Γöé Request Γöé Big Γöé ΓöîΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé buffers Γöé buffers Γöé Γöé OS/2 API Γöé Γöé Γöé DOS API Γöé
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé Γöé Γöé Γöé
Γöé Application privilege Γöé Γöé Γöé
ΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé
Γöé System privilege Γöé Γöé Γöé
Γöé Γöé Γöé Γöé
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÉ Γöé Γöé
Γöé Γöé OS/2 kernel Γöé Γöé Interrupt 2F
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé
Γöé ΓöîΓöÇΓöñ IFS Γöé FAT Γöé Γöé Γöé
Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ Γöé Γöé
ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ Γöé Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé RedirectorΓöé Γöé Γöé Γöé Γöé Redirector Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöîΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé
Γöé Γöé File Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ΓöésystemΓö£ΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Network Γöé Big Γöé
Γöé ΓöédriverΓöé Γöé Γöé Γöé Γöé buffers ΓöébuffersΓöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÿ
Γöé Γöé Γöé Γöé Γöé Γöé ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé Γöé HPFS Γöé Γöé Γöé Γöé Γöé
Γöé Γöé cacheΓöé Γöé Γöé Γöé Interrupt 5C
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé Γöé Γöé
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéNetBIOS Γöé ΓöéDisk driverΓöé Γöé ΓöéLAN SupportΓöé
ΓöéprotocolΓöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Program Γöé
Γöé driver Γöé Γöé DISKCACHE Γöé Γöé Γöé driver Γöé
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Network adapter Γöé Γöé Γöé Γöé Network adapter Γöé
Γöé driver Γöé Γöé Γöé Γöé driver Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéReceive Γöé TransmitΓöé Γöé Γöé ΓöéReceive Γöé TransmitΓöé
Γöébuffers Γöé buffers Γöé Γöé Γöé Γöébuffers Γöé buffers Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ PC Processor
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéNetwork adapterΓöé ΓöéDisk adapterΓöé Γöé Γöé Network adapter Γöé
Γöé card Γöé Γöé card Γöé Γöé Γöé card Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
System Architecture of the OS/2 Entry Server and DOS LAN Services
ΓòÉΓòÉΓòÉ 5.3. LAN Server-Advanced Design Overview ΓòÉΓòÉΓòÉ
LAN Server-Advanced, otherwise known as Advanced server, consists of an SMB
processor tightly coupled to a file system (the 386 HPFS). These components are
designed and optimized for 386-compatible and higher processors. Advanced
server provides an OS/2 file system driver, running at system privilege, which
requires minimal, if any, OS/2 services to satisfy network file I/O requests.
Performance is enhanced by the use of Busmaster disk and network device
drivers, which increase overlap of network and disk activity. The Advanced
server uses read-ahead and write-behind logic, which allows network file I/O to
occur at a rate approaching network bandwidth (when the data is fully cached)
or disk transfer rates (when disk I/O is required).
The 386 HPFS provides access control information within each file. The access
control information enables Local Security, provided with Advanced server, to
function consistently with remote access control. Local Security is the LAN
Server component that allows a network administrator to secure the file system
on the server workstation from local users. File I/O performance is enhanced
because of a much larger cache capacity and more intelligent caching
algorithms.
Server network buffers are passed to the server by the NetBIOS device driver.
The Advanced server is optimized for 386-HPFS and higher file I/O. It is
enabled to support Pentium as well. Requests destined for non-HPFS resources,
such as the FAT file system, character devices, and named pipes, are passed by
the Advanced server to the Entry server (which is provided with the Advanced
server). The requests are satisfied through OS/2 APIs.
The Advanced server and 386 HPFS run at the same privilege level as the OS/2
kernel (ring 0). The Advanced server is able to accomplish this by servicing
incoming requests for data or files in the HPFS partition without having to
make any transitions between ring 0 and ring 3.
The following are recommended uses of the Advanced version:
o As a dedicated high-performance file server
o As a remote IPL server
The Advanced server processes the three typical file accesses much like the
Entry server processes them. The 386-HPFS file I/O requests may be sent with
any of the three SMB protocol types discussed previously for the Entry server.
For information on the Entry server, see LAN Server-Entry Design Overview.
However, the Advanced server uses scatter/gather logic to enhance performance
if it is supported by network and disk device drivers.
ΓòÉΓòÉΓòÉ 5.3.1. Sideband ΓòÉΓòÉΓòÉ
Sideband is a set of enhancements designed to improve the performance of small
reads and writes to files on LAN Server 4.0. These enhancements are contained
in the DOS LAN Services and OS/2 LAN Requester components, in the Advanced
server components, and in the latest release of the LAN Adapter and Protocol
Support components.
If it is determined that an excessive number of frames are being lost on a
single session, Sideband is disabled for that particular session and stays
disabled until the session is ended. If you want to enable Sideband again,
delete and restart the session by disconnecting and then reconnecting all
connections to the server in question.
ΓòÉΓòÉΓòÉ 5.3.2. LAN Requester and 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 which 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 will not be as good as the native NetBIOS protocol,
NetBEUI, which has been optimized for local area networks.
The Multi-Protocol Transport Services (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 will allow local
sessions to continue running with NetBEUI performance while also proving Wide
Area Network connectivity with NetBIOS over TCP/IP. For information on
configuring with dual protocol stacks, see MPTS - AnyNet for OS/2:
Configuration Guide.
OS/2 Advanced Server and OS/2 Requester System Architecture shows the
components that may influence the performance of Advanced server and OS/2
requesters. This figure also provides a reference for discussing individual
performance-related elements.
Γöé
<─°°──────────Server─°°─────────────────────>°<─°°────Requester─°°──────>
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Local Γöé Γöé Γöé Local Γöé
Γöé application Γöé Γöé Γöé application Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé
Γöé LAN Server 4.0 - Entry Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé
Γöé Request Γöé Big Γöé ΓöîΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé buffers Γöé buffers Γöé Γöé OS/2 API Γöé Γöé Γöé OS/2 API Γöé
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé Γöé Γöé Γöé Application
Γöé Γöé Γöé Γöé privilege
ΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Γöé Γöé Γöé Γöé System
Γöé Γöé Γöé Γöé privilege
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé OS/2 kernel Γöé Γöé Γöé OS/2 kernel Γöé
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ΓöîΓöÇΓöñ IFS Γöé FAT Γöé Γöé Γöé IFS Γöé
Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ Γöé Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé RedirectorΓöé Γöé Γöé Γöé Γöé Redirector Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöñ File Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé system Γöé Γöé Γöé Γöé Work Γöé Work Γöé
Γöé Γöé driver Γöé Γöé Γöé Γöé buffers Γöé cache Γöé
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé LAN Server 4.0 Γö£ΓöÇΓöÇΓöÇΓöñ 386 Γöé Γöé Γöé ΓööΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé - Advanced Γöé Γöé HPFS Γöé Γöé Γöé Γöé
Γöé SMB processor Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé HPFS Γöé Γöé Γöé Γöé
Γöé Request buffersΓöé Γöé CACHE Γöé Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÿ Γöé Γöé Γöé
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÉ Γöé ΓöîΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéNetBIOS Γöé ΓöéDisk driverΓöé Γöé ΓöéNetBIOS Γöé
ΓöéprotocolΓöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöéprotocolΓöé
Γöé driver Γöé Γöé DISKCACHE Γöé Γöé Γöé driver Γöé
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Network adapter Γöé Γöé Γöé Γöé Network adapter Γöé
Γöé driver Γöé Γöé Γöé Γöé driver Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéReceive Γöé TransmitΓöé Γöé Γöé ΓöéReceive Γöé TransmitΓöé
Γöébuffers Γöé buffers Γöé Γöé Γöé Γöébuffers Γöé buffers Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ PC Processor
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéNetwork adapterΓöé ΓöéDisk adapterΓöé Γöé Γöé Network adapter Γöé
Γöé card Γöé Γöé card Γöé Γöé Γöé card Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé
OS/2 Advanced Server and OS/2 Requester System Architecture
System Architecture of the OS/2 Advanced Server and DOS LAN Services shows the
components that may influence the performance of the Advanced Server and DOS
requesters. This figure also provides a reference for discussing individual
performance-related elements.
Γöé
<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇServerΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>Γöé<ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇRequesterΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ>
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Local Γöé Γöé Γöé Local ΓöéApplicationΓöé
Γöé application Γöé Γöé Γöéapplication Γöé memory Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé
Γöé LAN Server 4.0 - Entry Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γöé Γöé
Γöé Request Γöé Big Γöé ΓöîΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé buffers Γöé buffers Γöé Γöé OS/2 API Γöé Γöé Γöé DOS API Γöé
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé Γöé Γöé Γöé
Γöé Application privilege Γöé Γöé Γöé
ΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé
Γöé System privilege Γöé Γöé Γöé
Γöé Γöé Γöé Γöé
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÉ Γöé Γöé
Γöé Γöé OS/2 kernel Γöé Γöé Interrupt 2F
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé
Γöé ΓöîΓöÇΓöñ IFS Γöé FAT Γöé Γöé Γöé
Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÿ Γöé Γöé
ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ Γöé Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé RedirectorΓöé Γöé Γöé Γöé Γöé Redirector Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé Γöé Γöé
Γöé ΓööΓöÇΓöÇΓöñ File Γöé Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé system Γöé Γöé Γöé Γöé Network Γöé Big Γöé
Γöé Γöé driver Γöé Γöé Γöé Γöé buffers ΓöébuffersΓöé
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé LAN Server 4.0 Γö£ΓöÇΓöÇΓöÇΓöñ 386 Γöé Γöé Γöé ΓööΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé - Advanced Γöé Γöé HPFS Γöé Γöé Γöé Γöé
Γöé SMB processor Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Interrupt 5C
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé HPFS Γöé Γöé Γöé Γöé
Γöé Request buffersΓöé ΓöéCACHE386Γöé Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÿ Γöé Γöé ΓöîΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÉ Γöé Γöé Γöé
ΓöéNetBIOS Γöé ΓöéDisk driverΓöé Γöé ΓöéNetBIOS Γöé
ΓöéprotocolΓöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé ΓöéprotocolΓöé
Γöé driver Γöé Γöé DISKCACHE Γöé Γöé Γöé driver Γöé
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Network adapter Γöé Γöé Γöé Γöé Network adapter Γöé
Γöé driver Γöé Γöé Γöé Γöé driver Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Γöé Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéReceive Γöé TransmitΓöé Γöé Γöé ΓöéReceive Γöé TransmitΓöé
Γöébuffers Γöé buffers Γöé Γöé Γöé Γöébuffers Γöé buffers Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé Γöé ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ Processor
ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöéΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéNetwork adapterΓöé ΓöéDisk adapterΓöé Γöé Γöé Network adapter Γöé
Γöé card Γöé Γöé card Γöé Γöé Γöé card Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé
System Architecture of the OS/2 Advanced Server and DOS LAN Services
ΓòÉΓòÉΓòÉ 6. Tuning LAN Server Performance Parameters ΓòÉΓòÉΓòÉ
This chapter describes how to tune LAN Server for capacity, performance, and
minimization of memory usage. The use of certain LAN Server functions to
assist in the collection of information about system activity is discussed.
The collected information is helpful when attempting to pinpoint the cause of a
capacity or performance problem. IBM System Performance Monitor/2 2.0 (SPM/2),
a separately sold product, enables the network administrator to monitor
additional network workstation performance parameters including:
o Processor utilization
o Hard-disk utilization
o Memory swapping status
o Percent of RAM available in the workstation
o RAM usage by an application
o Directory, subdirectory, and file sizings
To order SPM/2, contact your IBM authorized dealer or marketing representative.
Note LAN Server 4.0 provides a new tool, Tuning Assistant, which assists you
in configuring LAN Server 4.0 to your unique requirements. Its function
is to configure for the users' capacity requirements and to allocate
remaining memory for performance tuning.
All material in this chapter is applicable to both the Entry package and the
Advanced package unless specifically stated otherwise. More detailed
information about parameters listed in this chapter can be found in the
following chapters.
Capacity tuning should usually be done prior to performance tuning.
ΓòÉΓòÉΓòÉ 6.1. Capacity Tuning Considerations ΓòÉΓòÉΓòÉ
Entry server defaults provide for a maximum of 32 NetBIOS sessions. If you want
your server to connect to more than 32 workstations, you must increase the x1
and x2 variables on the corresponding netx statement in the IBMLAN.INI file.
Corresponding changes must be made to parameters in the IBM OS/2 NetBIOS
protocol section (NetBEUI_NIF) of the PROTOCOL.INI file.
Requirements for additional capacity parameter changes are determined by your
particular environment.
ΓòÉΓòÉΓòÉ 6.1.1. Server IBMLAN.INI Capacity Parameters ΓòÉΓòÉΓòÉ
The following IBMLAN.INI parameter list describes the parameters that most
affect LAN Server capacity, offers recommendations for adjustment, and lists
related parameters. The parameters are located in the Networks and Server
sections of the IBMLAN.INI file. Some of these parameters are related to
adding users to the network. Others are considered to be capacity parameters,
but they may also affect performance, because a lack of server resources forces
a user to wait for a resource to become available. The default values for these
parameters are set for an average LAN with 20 to 30 users. For a detailed
description of the IBMLAN.INI parameters, refer to IBMLAN.INI File Parameter
Descriptions.
If the server fails to start successfully after IBMLAN.INI parameter values are
changed, record the error reported and use the NET ERROR command to determine
the cause of the problem.
The following parameters affect LAN Server capacity:
Parameter Description
x1 Number of NetBIOS sessions the server or requester allocates
o Range [Default]: 2 - 254
[32 per adapter] Entry
[102 per adapter] Advanced
o Recommendation: See the LAN Server Network Administrator Reference
Volume 1: Planning, Installation, and Configuration.
o Related parameters: Maximum sessions (NetBEUI_NIF)
x2 Number of simultaneous NetBIOS commands a server or requester
can post
o Range [Default]: 16 - 255
[50 per adapter] Entry
[225 per adapter] Advanced
o Recommendation: Set to 2 x x1.
o Related parameters: Maximum commands (NetBEUI_NIF)
x3 Number of NetBIOS names the server or requester allocates
o Range [Default]: 5 - 254
[14 per adapter]
o Recommendation: No recommendation
o Related parameters: Maximum names (NetBEUI_NIF)
maxconnections Number of connections from requesters
o Range [Default]: 1 - 2000
[128] Entry
[300] Advanced
o Recommendation: Set larger than maxusers. 4 - 6 connections per user
o Related parameters: maxusers
maxlocks Number of records locked by server users
o Range [Default]: 1 - 8000
[64] Entry or Advanced
o Recommendation: 1 x maxopens
o Related parameters: maxopens
maxopens Number of files, pipes, and devices simultaneously open on the
server
o Range [Default]: 1 - 8000
[128] Peer
[160] Entry
[256] Advanced
o Recommendation: 3 x maxusers
o Related parameters: maxlocks maxsessopens
maxsearches Number of simultaneous directory searches on the server
o Range [Default]: 1 - 1927
[50] Peer
[150] Entry
[350] Advanced
o Recommendation: Increase for heavily used files on the server (DLS
requesters only; Entry only). Increase for print servers; if parameter is
not sufficient, jobs disappear in a print queue without printing.
o Related parameters: maxlocks maxusers srvheuristics (position 7)
maxsessopens Number of files, pipes, and devices simultaneously open for a
requester.
o Range [Default]: 1 - 8000
[80] Entry or Peer
[256] Advanced
o Recommendation: Increase for many server resources simultaneously used
from one requester (Entry server only).
o Related parameters: maxopens
maxsessreqs Number of resource requests for a requester
o Range [Default]: 1 - 65535 [50]
o Recommendation: Increase if users need multiple simultaneous resources.
o Related parameters: None
maxshares Number of server resources to share
o Range [Default]: 2 - 1000 [16] Peer, [32] Entry, [192] Advanced
o Recommendation: Increase if many server resources are shared.
o Related parameters: None
maxusers Number of simultaneous users (NetBIOS sessions) on the server
o Range [Default]: 1 - 1000
[5] Peer
[32] Entry
[101] Advanced
o Recommendation: Set less than maxconnections.
o Related parameters: maxconnections
srvpipes Number of pipes used by the server
o Range [Default]: 1 - 20 [3]
o Recommendation: Increase if many users log on simultaneously; maxusers /
40
o Related parameters: maxusers
ΓòÉΓòÉΓòÉ 6.1.2. Server PROTOCOL.INI Capacity Parameters ΓòÉΓòÉΓòÉ
The Maximum sessions (sessions), Maximum commands (ncbs), and Maximum names
(names) parameter values in the IBM OS/2 NetBIOS (NETBEUI_NIF) section of the
PROTOCOL.INI file must be set to a value that is greater than or equal to the
corresponding x1, x2, and x3 values on the associated netx statement in the
IBMLAN.INI file. For information on the parameters of the PROTOCOL.INI file,
see the LAN Server Network Administrator Reference Volume 1: Planning,
Installation, and Configuration.
ΓòÉΓòÉΓòÉ 6.1.3. Additional Related Parameters ΓòÉΓòÉΓòÉ
Several files contain related parameters that do not significantly affect
capacity and do not usually need to be adjusted. The files that contain
related parameters are as follows:
o Server CONFIG.SYS
o OS/2 LAN Requester IBMLAN.INI
o OS/2 LAN Requester PROTOCOL.INI
o OS/2 LAN Requester CONFIG.SYS
o DOS LAN Services NETWORK.INI
o DOS LAN Services PROTOCOL.INI
o DOS LAN Services CONFIG.SYS
ΓòÉΓòÉΓòÉ 6.2. Performance Tuning Considerations ΓòÉΓòÉΓòÉ
Performance can be viewed as either faster response time to individual
workstation requests or more data throughput from the server to the network as
a whole. It is strongly recommended that IBM LAN Server 4.0 Performance Tuning
Assistant be used to configure Entry or Advanced server to your system
requirements. Implementing its performance considerations may significantly
improve your performance. See LAN Server Commands and Utilities for more
information about how to use the LAN Tuning Assistant utility. The guidelines
in the following sections apply to both Entry server and Advanced server unless
otherwise noted.
The defaults for Entry Server are configured assuming small system memory on a
small-sized LAN in which 32 users are performing both small and large file I/O
operations using typical applications on the workstations. Advanced server
configuration defaults to provide capacity to support 100 users. This
configuration is provided with the assumption that a system running Advanced
server has adequate memory to support 100 users. See LAN Server Network
Administrator Reference Volume 1: Planning, Installation, and Configuration for
more information about distribution of memory.
After using Tuning Assistant and running LAN Server in your environment, you
will in most cases be experiencing good performance. If not, the following is
information about some facilities that can help you understand your
environment:
o Examine the server logs and statistics reports. Refer also to LAN Server
Network Administrator Reference Volume 3: Network Administrator Tasks for
more information about the logs and statistics reports. The statistics and
error information can also be accessed with the NET STATISTICS or NET ERROR
command from the command line on the server workstation. The reports include
important data, such as the number of times big buffers, request buffers, or
other resources were exhausted. After running a typical workload on the
server, examine the data to determine if the server is frequently running out
of big buffers, request buffers, or other resources. If so, the number of big
buffers, request buffers, or other resources should be increased unless there
are memory constraints in the server workstation.
o SPM/2 2.0 can provide detailed information about the workstation resource
utilization, which can help you identify specific performance bottlenecks.
SPM/2 2.0 can be used to analyze either server or requester performance while
imposing minimum overhead. One key piece of information is memory
utilization. If there is insufficient memory for the applications running,
swapping occurs and performance may be degraded significantly. If the server
workstation has heavy processor or disk utilization, typically greater than
80% for several minutes at a time, some of the server workload should be
moved to another server to improve performance.
For more information about SPM/2 2.0, see the IBM System Performance
Monitor/2 Reference.
o For the Advanced server, the CACHE386 utility can help you analyze server
performance. To display statistics about cache usage, type CACHE386 /STATS at
an OS/2 command prompt on the server. To achieve maximum benefit, use the
cache read-hit ratio to maximize the hit ratio with a minimum-sized cache.
Once you have collected information about the system activity, you can start to
pinpoint the cause of a performance problem. Required actions can include:
o Minor tuning of a few parameters
o Redistributing available memory in the workstation
o Adding memory to the workstation
o Redistributing the work load among servers
o Upgrading the servers with more powerful hardware
o Adding additional servers
ΓòÉΓòÉΓòÉ 6.2.1. Server IBMLAN.INI Performance Parameters ΓòÉΓòÉΓòÉ
IBMLAN.INI Parameters Affecting LAN Server Performance describes the IBMLAN.INI
file parameters that affect server workstation performance, offers
recommendations for adjustment, and lists related parameters. The parameters
are located in the Server section of the IBMLAN.INI file. In IBMLAN.INI
Parameters Affecting LAN Server Performance, the parameters listed first
generally have the greatest effect on performance.
The svrheuristics parameter can have a significant effect on performance.
However, in most cases changing the default settings results in minimal
performance fluctuation. For more information concerning the effects of the
srvheuristics parameter on read-ahead and write-behind activity, refer to
Adjusting Network Buffer Read-Ahead and Write-Behind Activity (OS/2 LAN
Requesters Only).
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 4. IBMLAN.INI Parameters Affecting LAN Server Performance Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé DESCRIPTION Γöé RANGE Γöé RECOMMENDATION Γöé RELATED Γöé
Γöé Γöé Γöé [DEFAULT] Γöé Γöé PARAMETERS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMBIGBUF Γöé Number of Γöé 0 - 80 Γöé Entry server Γöé SRVHEURISTICS Γöé
Γöé Γöé big buffers Γöé [4] Peer; Γöé only: 2 for Γöé (positions Γöé
Γöé Γöé Γöé [6] Entry; Γöé each simul- Γöé 13, 17, and Γöé
Γöé Γöé Γöé [12] Γöé taneous heavy- Γöé 18) Γöé
Γöé Γöé Γöé Advanced Γöé load user Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMREQBUF Γöé Number of Γöé 5 - 2000 Γöé 2 for each Γöé SIZREQBUF Γöé
Γöé Γöé request Γöé [10] Peer; Γöé requester Γöé MAXRUNS Γöé
Γöé Γöé buffers Γöé [48] Entry; Γöé actively Γöé Γöé
Γöé Γöé Γöé [250] Γöé sending Γöé Γöé
Γöé Γöé Γöé Advanced Γöé requests Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SIZREQBUF Γöé Size of Γöé 1024 - 32768 Γöé Set equal on Γöé NUMREQBUF Γöé
Γöé Γöé each Γöé [4096] Γöé all servers Γöé SIZWORKBUF Γöé
Γöé Γöé request Γöé Γöé and equal to Γöé MAXRUNS Γöé
Γöé Γöé buffer in Γöé Γöé SIZWORKBUF on Γöé Γöé
Γöé Γöé bytes Γöé Γöé requesters. Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SRVHEURISTICS Γöé Server Γöé Γöé See complete Γöé WRKHEURISTICS Γöé
Γöé Γöé fine-tuning Γöé Γöé description in Γöé NUMBIGBUF Γöé
Γöé Γöé options Γöé Γöé IBMLAN.INI Γöé Γöé
Γöé Γöé Γöé Γöé File Parameter Γöé Γöé
Γöé Γöé Γöé Γöé Descriptions.. Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
There are two key server performance parameters that require additional
discussion. These parameters are as follows:
o numbigbuf
The numbigbuf parameter may need to be adjusted differently, depending on the
LAN Server package installed.
For best results with LAN Server-Entry, the server should have enough big
buffers available to handle a peak request workload for large
sequential-file-access operations. This includes program loading as well as
file copy operations. Allocate two big buffers for each requester that might
concurrently send this type of request to the server. Because each big buffer
is 64KB in size, specify the minimum number required to handle the typical
environment.
Checking network statistics and error logs can help you determine an optimum
number of big buffers for a particular environment. To determine if the
server has enough big buffers to handle the incoming requests during peak
server workload periods, check network statistics and the error logs. If
necessary, increase the numbigbuf parameter value, and repeat this process
until the server has enough big buffers to handle the desired workload.
Digit positions 17 and 18 of the srvheuristics parameter enable you to modify
the dynamic use of big buffers. These digit positions enable the server to
request additional memory from the base operating system when all the big
buffers are in use and more big buffers are needed. Digit position 17 of the
srvheuristics parameter specifies the length of time that the server
maintains unused dynamic memory before freeing it. Digit position 18
determines the interval of time the server waits after failing to allocate a
big buffer before trying again. If the server has sufficient memory, set the
numbigbuf parameter value to ensure optimum performance.
Big buffers set with the numbigbuf parameter are not used in LAN
Server-Advanced unless files are accessed from a FAT file system drive.
Because big buffers are used only if needed or if network printing is done at
the server, leave the numbigbuf parameter value at the default value.
The LAN Server-Advanced server may allocate up to sixty-four 64KB buffers as
needed to handle network I/O. In cases where large file transfers are done
and the user has exclusive access to the file, you can use big buffers for
data transfer instead of using the cache. This will prevent the cache from
getting flushed for one-time accesses to files.
o numreqbuf
For best results, the server should have enough request buffers available to
handle a peak request workload. Allocate a minimum of two request buffers
for each requester that has a session established with the server.
Checking network statistics and error logs can help you determine an optimum
number of request buffers for a particular environment. To determine if the
server has enough request buffers to handle incoming requests during peak
server workload periods, check network statistics and the error logs. If more
request buffers are needed, increase the numreqbuf parameter value, and
repeat this process until the server has enough request buffers to handle the
desired workload. For more information, see the numreqbuf parameter in the
Tuning Parameters section Tuning Parameters.
ΓòÉΓòÉΓòÉ 6.2.2. Server Performance Considerations ΓòÉΓòÉΓòÉ
Because the needs of a particular workstation can change in a variety of ways,
the resources required to support various application programs may vary. The
following situations may require adjustment of the performance-related
parameters:
o Heavy random I/O environments need a large disk cache on the server.
o A large disk cache can improve performance in environments that use shared
applications.
o Heavy file-transfer environments need large numbers of 64KB buffers
(numbigbuf parameter) on the server. However, if the Advanced server accesses
only 386-HPFS hard disks, the numbigbuf parameter has no effect; in this
case, leave the numbigbuf parameter set at the default value.
Some additional points to consider include:
o The srvheuristics and wrkheuristics parameters can be changed to improve LAN
Server performance in some special instances. However, unless there is good
reason to suspect a performance problem in your environment, the
srvheuristics and wrkheuristics parameter values should not be changed. The
benefit is generally small compared to other changes previously recommended.
For more information concerning the effects of the srvheuristics and
wrkheuristics parameters on read-ahead and write-behind activity, refer to
Adjusting Network Buffer Read-Ahead and Write-Behind Activity (OS/2 LAN
Requesters Only). The srvheuristics and wrkheuristics parameters are also
described in IBMLAN.INI File Parameter Descriptions.
ΓòÉΓòÉΓòÉ 6.2.3. Server PROTOCOL.INI Performance Parameters ΓòÉΓòÉΓòÉ
The Maximum sessions (sessions), Maximum commands (ncbs), and Maximum names
(names) parameter values in the IBM OS/2 NetBIOS (NETBEUI_NIF) section of the
PROTOCOL.INI file must be set to a value that is greater than or equal to the
x1, x2, and x3 values on the associated netx statement in the IBMLAN.INI file.
If you are using the IBM 16/4 Token-Ring Adapter, the Transmit buffer size
(xmitbufsize) parameter value should be set to 128 + sizwrkbuf to improve data
transmission efficiency. The Transmit buffer size (xmitbufsize) parameter is
added to the IBM Token-Ring Network Adapter (IBMTOK_NIF) section of the
PROTOCOL.INI file. The default number of network control blocks (NCBs) is 225.
Use the NET ERROR command to determine if this number is sufficient for the
server workload.
If you are using the IBM 16/4 Token-Ring Adapter, you can set the Number of
adapter transmit buffers (xmitbufs) parameter to 2 to allow overlapped
buffering of transmitted data. The Number of adapter transmit buffers
(xmitbufs) parameter is in the IBM Token-Ring Network Adapter (IBMTOK_NIF)
section of the PROTOCOL.INI file.
Frames are sent to the protocol drivers in the reverse order from which the
protocol driver DEVICE statements are listed in the CONFIG.SYS file. For
information on the PROTOCOL.INI file, see the LAN Server Network Administrator
Reference Volume 1: Planning, Installation, and Configuration.
ΓòÉΓòÉΓòÉ 6.2.4. Server CONFIG.SYS Performance Parameters ΓòÉΓòÉΓòÉ
CONFIG.SYS Parameters Affecting LAN Server Performance describes the CONFIG.SYS
file parameters that affect server workstation performance, offers
recommendations for adjustment, and lists related parameters.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 5. CONFIG.SYS Parameters Affecting LAN Server Performance Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé DESCRIPTION Γöé RANGE [DEFAULT] Γöé RECOMMENDATION Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé /C Γöé Memory used to cache Γöé 64KB - 2MB Γöé 2MB. See the infor- Γöé
Γöé Γöé HPFS I/O for Entry Γöé [64KB] Γöé mation following the Γöé
Γöé Γöé package Γöé Γöé table. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DISKCACHE Γöé Memory used to cache Γöé 64KB - 8MB Γöé 64KB if no FAT file Γöé
Γöé Γöé FAT file system I/O Γöé [64KB] Γöé system directories Γöé
Γöé Γöé Γöé Γöé and files are being Γöé
Γöé Γöé Γöé Γöé shared-otherwise, as Γöé
Γöé Γöé Γöé Γöé much as possible. Γöé
Γöé Γöé Γöé Γöé See the information Γöé
Γöé Γöé Γöé Γöé following the table. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The /C (HPFS and 386 HPFS) and diskcache (FAT file system) parameters use most
of the available memory in the server after other memory requirements are
satisfied. It is recommended that you leave between 0.5MB and 1MB of free
memory in the server for efficient handling of peak workloads. SPM/2 2.0 can be
used to determine the server memory requirements. Refer to the LAN Server
Network Administrator Reference Volume 1: Planning, Installation, and
Configuration for information to help you determine the minimum memory
requirements.
ΓòÉΓòÉΓòÉ 6.2.4.1. Entry Server Guidelines ΓòÉΓòÉΓòÉ
Set the diskcache parameter to xxxx,128, where xxxx is the amount of memory
available for caching and 128 is the threshold (in sectors). Enabling the
diskcache lazy write option will improve performance in many cases. See topic
Tuning Parameters for more information. The HPFS cache has a maximum value of
2MB and a default threshold of 2KB. Unless your system is memory constrained,
the maximum value of 2MB will provide the best performance. See topic High
Performance File Systems for more information.
ΓòÉΓòÉΓòÉ 6.2.4.2. Advanced Server Guidelines ΓòÉΓòÉΓòÉ
If the Workstation determines size option was chosen at installation, the
default cache size is 20% of the total physical memory available. The 386-HPFS
cache has no threshold or capacity limitations. After determining the memory
requirements on the server, you can change the cache size by changing (or
adding) the /CACHE:xxxx value for the IFS statement in the CONFIG.SYS file,
where xxxx is the amount of memory available for caching.
ΓòÉΓòÉΓòÉ 6.2.4.3. Heap Considerations ΓòÉΓòÉΓòÉ
The heap contains various non-I/O file-related information. The maxheap
parameter in the filesystem section of the HPFS386.INI on the Advanced server
specifies the size of the heap. It is recommended that you let the heap size
remain at the default value. As the system runs, the heap grows as needed to a
maximum size limited only by available physical memory in the workstation. On
a very busy workstation, it is possible to run out of heap space. If this
occurs, there may be a noticeable degradation in performance, and service
requests may fail. Errors returned to the requester that specify the server is
out of a resource, especially on DOS searches, may indicate that the server has
run out of heap space. For more information about the maxheap parameter, refer
to High Performance File Systems.
In environments where physical memory is limited and more heap is required, it
is important to know that 386 HPFS preallocates 64KB for the heap initially.
For example, if no heap size is specified, and the heap needs to grow past the
initial 64KB and cannot because other applications are using the physical
memory, specifying a heap size would help. If a heap limit of 2MB is then
specified, 386 HPFS would allocate 25% of this, or 512KB, which may be enough
to satisfy the heap requirements. The downside is that if you set the heap
size larger than you need it, 386-HPFS can pre-allocate more than is needed,
taking excessive physical memory.
ΓòÉΓòÉΓòÉ 6.2.5. OS/2 LAN Requester IBMLAN.INI Performance Parameters ΓòÉΓòÉΓòÉ
Changes to the requester parameters are not recommended unless you suspect a
performance problem on the requester. Appendix B describes the parameters that
affect LAN Server performance on a requester workstation, offers
recommendations for adjustment, and lists related parameters. The parameters
are located in the Requester section of the IBMLAN.INI file. In File Examples,
the parameters listed first generally have the greatest effect on performance.
The wrkheuristics parameter can have a significant effect on performance.
However, in most cases minimal or negative performance changes result from
changing the default settings. Refer to Adjusting Network Buffer Read-Ahead
and Write-Behind Activity (OS/2 LAN Requesters Only) for more information
concerning the effects of the wrkheuristics parameter on read-ahead and
write-behind activity.
The following IBMLAN.INI parameters affect OS/2 requester performance:
Parameter Description
maxwrkcache Size of the work cache (KB)
o Range [Default]: 0 - 640 [64]
o Recommendation: Multiple of 64; increase if requesters run multiple
file-intensive applications from the server.
o Related parameters:
sizworkbuf Size of each work buffer (bytes)
o Range [Default]: 1024 - 16384 [4096]
o Recommendation: Multiple of 512; set equal on all requesters and equal to
sizreqbuf on servers.
o Related parameters: sizreqbuf
numworkbuf Number of work buffers
o Range [Default]: 3 - 50 [15]
o Recommendation: Increase if multiple applications running on the requester
access server resources.
o Related parameters: maxthreads maxcmds wrknets
wrkheuristics Requester fine-tuning options
o Range [Default]:
o Recommendation: See complete description in IBMLAN.INI File Parameter
Descriptions.
o Related parameters: srvheuristics sizworkbuf numbigbuf printbuftime
ΓòÉΓòÉΓòÉ 6.2.6. OS/2 LAN Requester PROTOCOL.INI Performance Parameters ΓòÉΓòÉΓòÉ
If you are using the IBM 16/4 Token-Ring Adapter, and you want to improve data
transmission efficiency, set the Transmit buffer size (xmitbufsize) parameter
value to sizworkbuf + 2, which at default value equals 128. The Transmit buffer
size (xmitbufsize) parameter is in the IBM Token-Ring Network Adapter
(IBMTOK_NIF) section of the PROTOCOL.INI file.
If you are using the IBM 16/4 Token-Ring Adapter, you can improve data
transmission efficiency by setting the Number of adapter transmit buffers
(xmitbufs) parameter to 2 to allow overlapped buffering of transmitted data.
The parameter is in the IBM Token-Ring Network Adapter (IBMTOK_NIF) section of
the PROTOCOL.INI file. For information on the PROTOCOL.INI file, see the LAN
Server Network Administrator Reference Volume 1: Planning, Installation, and
Configuration.
ΓòÉΓòÉΓòÉ 6.2.7. OS/2 LAN Requester CONFIG.SYS Performance Parameters ΓòÉΓòÉΓòÉ
The parameters in the CONFIG.SYS file usually do not require performance tuning
for OS/2 LAN Requesters.
ΓòÉΓòÉΓòÉ 6.2.8. DOS LAN Services NETWORK.INI Performance Parameters ΓòÉΓòÉΓòÉ
Table 22, NETWORK.INI [network] Section Parameter Values, in Parameter
Descriptions, describes the NETWORK.INI file parameters that affect DLS
requester performance, offers recommendations for adjustment, and lists related
parameters. The parameters listed first generally have the greatest effect on
performance. The default values have been chosen to provide good performance
for most users with minimal memory requirements. Change the default values
only if there is a performance problem. When one parameter value is changed,
related parameter values should also be adjusted. Although some of the
parameters listed do not directly affect performance, they do control the
amount of memory available.
ΓòÉΓòÉΓòÉ 6.2.9. DOS LAN Services PROTOCOL.INI Performance Parameters ΓòÉΓòÉΓòÉ
If you are using the IBM 16/4 Token-Ring Adapter, you can improve data
transmission efficiency by setting the adapter transmit buffer size to 4224 and
by setting the number of transmit buffers to 2. Using an ASCII editor, add
these two parameters to the IBM Token-Ring Network Adapter (IBM$IBMTRA.NIF)
section of the PROTOCOL.INI file:
XMITBUFSIZE=4224
XMITBUFS=2
ΓòÉΓòÉΓòÉ 6.2.10. Matching Server and Requester Buffers (OS/2 LAN Requesters Only) ΓòÉΓòÉΓòÉ
Previous sections have discussed matching buffer sizes in the network server
and workstation. When the buffers are not matched, the request-processing
overhead in the server increases, causing a degradation of performance in some
cases. In addition, the memory in the larger of the mismatched buffers is not
available for use and is wasted.
There are situations in which the 4KB default value for the server and
requester buffers is not optimum; for example, if the network administrator
monitors the traffic on the ring and determines that most frames are less than
the transmit buffer size on the workstations. In this case, buffers could be
reduced, providing a reduction in memory or an increase in the number of
buffers. Performance may improve because it is desirable to have two request
buffers for each active workstation.
ΓòÉΓòÉΓòÉ 6.2.11. Adjusting Network Buffer Read-Ahead and Write-Behind Activity (OS/2 LAN Requesters Only) ΓòÉΓòÉΓòÉ
LAN Server incorporates several design features that attempt to improve LAN
performance based on expected behavior of software applications used on the
network. However, the behavior of all possible applications cannot be
predicted and handled in an optimum manner. The srvheuristics and
wrkheuristics parameters enable you to deal with unusual behavior of
applications used on the network, even though the application may not be aware
of the network. The following information describes some of the digit
positions of the srvheuristics and wrkheuristics parameters that may help you
deal with specific application activity. In addition, read General Hints and
Tips.
LAN Server adds the ability to disable the RAW (read and write) protocol at the
server. This can be useful if you have a remote server and need to avoid using
RAW protocol to prevent session timeouts.
To identify some of the relationships that exist in the srvheuristics and
wrkheuristics parameters in the IBMLAN.INI file, refer to Heuristic
Relationships: OS/2 Requester Large-Record Buffering, Heuristic Relationships:
Entry Server Large-Record Buffering, Heuristic Relationships: Entry Server
Small-Record Buffering, and Heuristic Relationships: Requester Small-Record
Buffering. The srvheuristics parameter sets some fine-tuning options on the
Server workstation. The wrkheuristics parameter sets some fine-tuning options
on an OS/2 workstation. Except where noted, the figures show all possible
combinations of the parameter values, as well as the relationships they create.
The figures also may help you determine which buffering scheme is active.
The figures outline the effect of several fine-tuning options set by the
srvheuristics and wrkheuristics parameters. Possible values of specific digit
positions are shown at the bottom or side of each box. Each possible value
defines a relationship that determines which buffering scheme is active. To
use any of the heuristic relationship figures:
o At the bottom of the figure, locate the buffering scheme that you want to
activate. Follow the path to the top of the figure and record the parameter
values required to establish the chosen buffering scheme.
o To determine which buffering scheme is active, start at the top of the
figure. Follow the downward path determined by the parameter values that are
set in the existing IBMLAN.INI file. The path ends at the active buffering
scheme.
Heuristic Relationships: OS/2 Requester Large-Record Buffering outlines how
the wrkheuristics parameter value affects the requester buffering scheme for
large-record reads and writes. Large records are defined as those records
larger than the sizworkbuf parameter value.
Default ΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Other ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé Record size Γöé No Γöé Small record Γöé
Γöé larger than Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöé read/write Γöé
Γöé work buffer Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Yes *
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé wrkheuristics Γöé 0 Γöé Small record Γöé
Γöé 11 Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöé read/write Γöé
ΓöéUse RAW protocolΓöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
1 Γöé
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöîΓöÇΓöÇΓöÇΓöñAre big buffersΓö£ΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÉ
Γöé Γöé available? Γöé *
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Yes
NoΓöé Γöî*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓö┤*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ * *
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéwrkheuristicsΓöé ΓöéwrkheuristicsΓöé ΓöéwrkheuristicsΓöé ΓöéwrkheuristicsΓöé
Γöé 14 Γöé Γöé 15 Γöé Γöé 12 Γöé Γöé 13 Γöé
Γöé Γöé Γöé Γöé Γöé Γöé Γöé Γöé
Γöé Use read Γöé Γöé Use write Γöé ΓöéUse large RAWΓöé ΓöéUse large RAWΓöé
Γöé multiplex Γöé Γöé multiplex Γöé Γöé read-ahead Γöé Γöé write-behindΓöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤*ΓöÇ*ΓöÇ*ΓöÉ * ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇ*ΓöÇ*ΓöÇ*ΓöÇ*ΓöÉ *
0Γöé * 1 Γöé 0Γöé * 1 Γöé
ΓöîΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÉ * ΓöîΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÉ *
ΓöéUse Γöé Γöé Use Γöé Γöé Γöé No RAW Γöé Γöé RAW Γöé Γöé
Γöésmall Γöé Γöé read Γöé * Γöéread-aheadΓöé Γöéread-aheadΓöé *
ΓöérecordΓöé ΓöémultiplexΓöé Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé
Γöéread Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ * *
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤*ΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤*ΓöÉ
0Γöé * 1 0Γöé * 1
ΓöîΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéUse Γöé Γöé Use Γöé Γöé No RAW Γöé Γöé RAW Γöé
Γöésmall Γöé Γöé write Γöé Γöéwrite-behindΓöé Γöéwrite-behindΓöé
ΓöérecordΓöé ΓöémultiplexΓöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöéwrite Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Heuristic Relationships: OS/2 Requester Large-Record Buffering
Heuristic Relationships: Entry Server Large-Record Buffering outlines how the
srvheuristics parameter value affects the server buffering scheme for
large-record reads and writes. Large records are defined as those records
larger than the sizreqbuf parameter value.
Default ΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*
Other ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Record size Γöé No Γöé Small record Γöé
Γöé larger than Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöé read/write Γöé
Γöérequest buffer Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÿ
Γöé Yes
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöésrvheuristics 19Γöé No ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöé Read/write Γöé
Γöé Use RAW Γöé Γöé multiplex Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöéYes
Γöé
Γöé
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ No ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéAre big buffersΓö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöé Read/write Γöé
Γöé available? Γöé Γöé multiplex Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöéYes
*
Γöî*ΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓö┤ΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÉ
* *
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöésrvheuristics 1Γöé Γöésrvheuristics 2 Γöé
Γöé Γöé Γöé Γöé
ΓöéUse read-ahead Γöé ΓöéUse write-behindΓöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
* *
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÉ ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÉ
Γöé * Γöé *
0Γöé Γöé1 0Γöé Γöé1
ΓöîΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé No RAW Γöé Γöé Use RAW Γöé Γöé No RAW Γöé Γöé Use RAW Γöé
Γöéread-aheadΓöé Γöéread-aheadΓöé Γöéwrite-behindΓöé Γöéwrite-behindΓöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Heuristic Relationships: Entry Server Large-Record Buffering
Possible values for digit positions 1 and 2 of the srvheuristics parameter are
0, 1, and 2. Values 0 and 1 are the only ones dealt with in Heuristic
Relationships: Entry Server Large-Record Buffering. Values 1 and 2 are
functionally the same with regard to this figure, but they may have slightly
different performance characteristics.
Heuristic Relationships: Entry Server Small-Record Buffering outlines how the
srvheuristics parameter value affects the buffering scheme for small-record
reads and writes. Small records are defined as those records smaller than or
equal to the sizreqbuf parameter value.
Read ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Write Default ΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ Read or write Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Other ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé
Γöé Γöé
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé srvheuristics 1 Γöé Γöé srvheuristics 2 Γöé
Γöé Γöé Γöé Γöé
Γöé Use read-ahead Γöé Γöé Use write-behind Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
* *
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇ*ΓöÉ
Γöé * Γöé *
0Γöé Γöé1 0 Γöé Γöé1
ΓöîΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé No small Γöé Γöé Use Γöé Γöé No Γöé Γöé Use Γöé
Γöé record Γöé Γöésmall recordΓöé Γöéwrite-behindΓöéΓöÇΓöÇΓöÉ Γöéwrite-behindΓöé
Γöéread-aheadΓöé Γöé read-ahead Γöé Γöé buffering Γöé Γöé Γöé buffering Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöé *
Γöé Γöé 1
ΓöéΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéΓöésrvheuristics 9Γöé
ΓöéΓöé Γöé
0ΓööΓöñ Buffer Γöé
Γöé deny-write Γöé
Γöé access Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
*
Γöé 1
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Use write-behind Γöé
Γöé with deny-write Γöé
Γöé access Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Heuristic Relationships: Entry Server Small-Record Buffering
Possible values for digit positions 1 and 2 of the srvheuristics parameter are
0, 1, and 2. Values 0 and 1 are the only ones dealt with in Heuristic
Relationships: Entry Server Small-Record Buffering. Values 1 and 2 are
functionally the same with regard to this figure, but they may have slightly
different performance characteristics.
Heuristic Relationships: Requester Small-Record Buffering outlines how the
wrkheuristics parameter value affects the buffering scheme for small-record
reads and writes. Small records are defined as those records smaller than or
equal to sizworkbuf.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ Default value ΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*
ΓöéwrkheuristicsΓöé Other values ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ
Γöé 9 Γöé
ΓöéBuffer small Γöé
Γöé read/writes Γöé
ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
0Γöé Γöé1
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöö*ΓöÇΓöÇ*ΓöÇΓö¼*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéwrkheuristicsΓöé ΓöéwrkheuristicsΓöé ΓöéwrkheuristicsΓöé ΓöéwrkheuristicsΓöé
Γöé 17 Γöé Γöé 18 Γöé Γöé 24 Γöé Γöé 23 Γöé
ΓööΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÿ ΓööΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÿ ΓööΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ ΓööΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÿ
Γöé0 Γöé1 Γöé0 Γöé1 Γöé1 Γöé0 Γöé1 Γöé0
Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÉ Γöé ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÉ * ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÉ * ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé ΓöéUse Γöé Γöé Γöé Use Γöé Γöé Γöé Do not Γöé Γöé Γöé Do not Γöé
Γöé Γöéread- Γöé Γöé Γöéwrite- Γöé * Γöébuffer ifΓöé * Γöébuffer if Γöé
Γöé Γöéahead Γöé Γöé Γöébehind Γöé Γöé Γöéread-onlyΓöé Γöé Γöédeny-write Γöé
Γöé ΓöémultipleΓöé Γöé ΓöémultipleΓöé * ΓöéattributeΓöé * Γöé sharing Γöé
Γöé Γöérecords Γöé Γöé Γöérecords Γöé Γöé Γöé is set Γöé Γöé Γöéaccess modeΓöé
Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ * ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ * ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé No Γöé Γöé No Γöé ΓöéBuffer ifΓöé ΓöéBuffer if Γöé
Γöéread- Γöé Γöéwrite-Γöé Γöéread-onlyΓöé Γöédeny-write Γöé
Γöéahead Γöé ΓöébehindΓöé ΓöéattributeΓöé Γöé sharing Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé is set Γöé Γöéaccess modeΓöé
ΓööΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Γöö*ΓöÇ*ΓöÇ*ΓöÇ*ΓöÉ Γöî*ΓöÇ*ΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÉ
ΓöéwrkheuristicsΓöé
Γöé 10 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓö┤*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇ*ΓöÇΓöÇΓöÉ
0Γöé 1Γöé 2Γöé 3Γöé
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéFull buffer forΓöé ΓöéFull buffer ifΓöé ΓöéFull buffer forΓöé ΓöéFull buffer forΓöé
Γöésequential dataΓöé Γöé read/write Γöé Γöésequential dataΓöé Γöé all requests Γöé
Γöé reads only Γöé Γöé access mode Γöé Γöéand read/write Γöé Γöé(if hits occur)Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ Γöé access mode Γöé ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Heuristic Relationships: Requester Small-Record Buffering
ΓòÉΓòÉΓòÉ 6.3. General Hints and Tips ΓòÉΓòÉΓòÉ
This section provides certain tuning recommendations that may improve
performance for each specific environment. Review these recommendations and
follow those that apply to your specific networks.
o To improve performance of OS/2 .CMD and DOS .BAT files, the server opens the
files with opportunistic locks and does not close them immediately.
Opportunistic locking, or Oplock, is the buffering of network files on a
local workstation. However, this causes the files to remain open longer than
expected, possibly resulting in file I/O errors. In addition, when files are
copied from the DOS command prompt, the times and dates may change. To
disable batch-file performance optimization for OS/2 workstations, set digit
position 1 of the wrkheuristics parameter to 0.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé NOTE TO DOUBLE-BYTE CHARACTER SET (DBCS) USERS: DOS remote IPL is available Γöé
Γöé only when using DOS 6.3/V. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
o If keyboard response time is a concern on a heavily used server workstation
(Entry package only), the priority level on the server can be changed. Set
digit position 6 of the srvheuristics parameter to 5, which allows other
applications to access the processor more often. However, network response
time increases as the server keyboard response time decreases.
o If the workstation is a dedicated remote IPL server (Entry package only),
leave digit position 6 of the srvheuristics parameter at the default value of
4, which sets the server priority above other applications.
o If your network includes remote bridges, you may experience session
disconnects of the remote workstation. Refer to the description of digit
position 15 of the srvheuristics parameter in IBMLAN.INI File Parameter
Descriptions for information about increasing the NetBIOS timeout.
o If your network does not include multiple bridges, remote bridges,
telecommunication lines, or other demanding devices, and your network
exhibits infrequent retransmissions, you may obtain an improvement in logon
performance with the following actions:
- Reduce the netbiosretries parameter in the workstation's PROTOCOL.INI file
from its default to a value of 2. If this value is too low, you will
experience a successful logon followed by a session termination. Should
this occur, increase the value until the session no longer terminates. For
information about the PROTOCOL.INI file, see the LAN Server Network
Administrator Reference Volume 1: Planning, Installation, and
Configuration.
- If your network does not make use of the messaging facility, eliminate it
by removing messenger from the Services section of the OS/2 workstation's
IBMLAN.INI file. For a DOS workstation, the Messenger service is started
with the NET START RCV command. For no messaging, you can start DOS LAN
Services with the NET START RDR command.
ΓòÉΓòÉΓòÉ 6.4. Memory Minimization Considerations ΓòÉΓòÉΓòÉ
The LAN Server Network Administrator Reference Volume 1: Planning,
Installation, and Configuration recommends minimum memory sizes for the server
and requester workstations. Memory requirements are provided for the base
operating system, server, and requester installed with the defaults. You must
also include estimates for memory required by the applications running in the
requester workstation and the server workstation, if applicable. The
recommendations provided in IBMLAN.INI Parameters Affecting LAN Server
Performance increase the estimated server memory requirements, which are based
on the default parameter values.
If the workstations are configured with less than the recommended memory, the
following sections provide guidance in reducing the memory required by the
server and requester. To ensure that significant memory swapping does not
occur, it is recommended that you use the memory analysis capabilities of SPM/2
2.0.
ΓòÉΓòÉΓòÉ 6.4.1. Server IBMLAN.INI Memory Parameters ΓòÉΓòÉΓòÉ
The IBMLAN.INI file parameters that affect the amount of memory required in the
server are as follows:
o numbigbuf
In Entry server, the size of a big buffer is fixed at 64KB, so big buffers
can use a large amount of memory. To check how often the server has used all
the big buffers allotted, use the NET STATISTICS command. If the big buffers
resource is never exhausted, reduce the numbigbuf parameter value on the
server and check the network statistics again. Repeat this process until the
server occasionally uses all the big buffer resource during peak workload
times. The value that you set for the numbigbuf parameter involves a
memory-versus-performance trade-off. You must determine the value that best
satisfies the needs of your network.
In LAN Server-Advanced, 64KB buffers (up to 16) are allocated as needed.
Therefore, the numbigbuf parameter on the server should be set to 0 if the
server only accesses 386 HPFS files and does not do any printing.
o numreqbuf
To check how often the server has used all the request buffers allotted, use
the NET STATISTICS command. If the request buffers resource is never
exhausted, reduce the numreqbuf parameter value on the server and check the
network statistics again. Repeat this process until the server occasionally
uses all the request buffer resource during peak workload times. The value
that you set for the numreqbuf parameter involves a memory-versus-performance
trade-off. You must determine the value that best satisfies the needs of
your network. For more information, see numreqbuf in the Tuning Parameters
sectionin topic Tuning Parameters.
o sizreqbuf
The value of the sizreqbuf parameter can be reduced from the 4KB default
value to 2KB in some environments without causing significant performance
degradation. Compare the network performance for both settings before making
the final choice. Setting the sizreqbuf parameter to 2KB can affect the
number of big buffers needed because a request to read or write with a record
size greater than 2KB, instead of 4KB, will now attempt to use the big
buffers. It is strongly recommended that the sizreqbuf parameter value on
the server match the sizworkbuf parameter value on the requester.
ΓòÉΓòÉΓòÉ 6.4.2. Server PROTOCOL.INI Memory Parameters ΓòÉΓòÉΓòÉ
The Maximum sessions, Maximum commands, and Maximum names parameter values must
each be set to a value that is greater than or equal to the corresponding x1,
x2, and x3 values on the associated netx statement.
ΓòÉΓòÉΓòÉ 6.4.3. Server CONFIG.SYS Memory Parameters ΓòÉΓòÉΓòÉ
The cache, cache386, and diskcache parameters in the CONFIG.SYS file on the
server can be adjusted depending on the LAN Server package used.
In LAN Server-Entry, reduce the value of the diskcache and cache parameters.
The threshold for DISKCACHE should be no larger than 1/10 the size of the
cache. For example, set the diskcache parameter to 128,24. Reducing the cache
size can severely degrade performance.
In LAN Server-Advanced, use the CACHE386 utility with the /STATS option to
examine the read hit and miss ratio while changing the value that sets the size
of the cache in the IFS statement in the CONFIG.SYS file.
ΓòÉΓòÉΓòÉ 6.4.4. OS/2 LAN Requester IBMLAN.INI Memory Parameters ΓòÉΓòÉΓòÉ
The IBMLAN.INI file parameters that affect the amount of memory required in an
OS/2 requester are as follows:
o numworkbuf
Unless the requester workstation is running multiple OS/2 sessions with the
server, the numworkbuf parameter can usually be reduced from the default
value of 15 to 5 without severely degrading performance.
o sizworkbuf
The value of the sizworkbuf parameter can be reduced from the default value
of 4KB to 2KB without severely degrading performance. Compare the
performance of your network with both settings before making the final
choice. The sizworkbuf parameter value in the requester should match the
sizreqbuf parameter value in the server.
o maxwrkcache
Usually, you should not reduce the maxwrkcache parameter value because it
significantly affects program loading and file transfers. If the performance
degradation is acceptable, the maxwrkcache parameter value can be reduced
from the default value of 64KB to 0.
ΓòÉΓòÉΓòÉ 6.4.5. OS/2 LAN Requester CONFIG.SYS Memory Parameters ΓòÉΓòÉΓòÉ
To reduce the memory requirements on an OS/2 requester workstation, set the
protectonly parameter to YES if DOS real mode is not required. If DOS real
mode is required, set the memman parameter to SWAP,MOVE,SWAPDOS to enable
swapping of the DOS real-mode window.
ΓòÉΓòÉΓòÉ 6.4.6. Additional Related Parameters ΓòÉΓòÉΓòÉ
Several files contain related parameters that do not significantly affect
memory usage. The related parameters do not usually need to be adjusted. The
files that contain related parameters are as follows:
o OS/2 LAN Requester PROTOCOL.INI
o DOS LAN Services NETWORK.INI
o DOS LAN Services PROTOCOL.INI
o DOS LAN Services CONFIG.SYS
ΓòÉΓòÉΓòÉ 7. IBMLAN.INI File Parameter Descriptions ΓòÉΓòÉΓòÉ
You can adapt LAN Server to meet the needs of individual users on the network.
For example, a network with few users may require a network definition
different from that of a network with many users. You can alter the LAN Server
definition by changing parameter values in the IBMLAN.INI file, which is in the
\IBMLAN subdirectory. Refer to File Examples for an example IBMLAN.INI file.
Before changing any defaults, try running your network's workstations using the
default values in the IBMLAN.INI file. Default values are used for each
parameter that is not specified in the IBMLAN.INI file. If the default values
do not meet your network needs, adjust the parameter values.
ΓòÉΓòÉΓòÉ 7.1. Changing IBMLAN.INI Parameter Values ΓòÉΓòÉΓòÉ
Many entries in the IBMLAN.INI file can be overridden for a logon session using
the full-screen interface, the NET START command, or the NET CONFIG command.
Other parameters cannot be overridden. To change these parameters or make
permanent changes to any parameters, you must edit the IBMLAN.INI file. You
can edit the IBMLAN.INI file with an ASCII text editor.
When you edit the IBMLAN.INI file, keep in mind the following:
o Do not change any default values in the Services section.
o While you can change values in sections other than Services, do not delete
any parameters or attempt to change parameter names. Parameter entries have
the form parameter=value. Change only the value portion.
o You can add comments to the IBMLAN.INI file. Comments must begin with a
semicolon (;) in the first column.
o Entry values in lists are separated by commas. Exceptions are the Replicator
section and the auditing parameter in the Server section, where list values
are separated by semicolons.
ΓòÉΓòÉΓòÉ 7.2. Activating Changed Parameter Values ΓòÉΓòÉΓòÉ
Most changes in the IBMLAN.INI file take effect when the service corresponding
to the changed section is restarted. For example, changes to the computername
parameter value in the Requester section take effect the next time the
requester is started. (Restart network services using the NET START command.)
The following IBMLAN.INI file parameters are used when the workstation starts.
If you change the values of any of these parameters, you must restart your
workstation for the change to take effect.
o netx parameter in the Networks section
o maxcmds parameter in the Requester section
o maxthreads parameter in the Requester section
When LAN Server first starts, or when it needs more information, it checks the
IBMLAN.INI file, which contains all the default information needed by LAN
Server.
ΓòÉΓòÉΓòÉ 7.3. Parameter Descriptions ΓòÉΓòÉΓòÉ
The following sections reflect the organization of the IBMLAN.INI file:
o Networks
o Requester
o Messenger
o Server (for servers only)
o Alerter (for servers only)
o Netrun (for servers only)
o Replicator
o Netlogon (for servers only)
o UPS (for servers only)
o Remoteboot (for servers only)
o LSserver
o Services
o DCDB Replicator
o Peer (for OS/2 workstations only)
Note: DLS Peer parameters are in the NETWORK.INI file. The Generic Alerter
service and the Timesource service do not have separate sections in the
IBMLAN.INI file.
Parameters are listed with minimum, maximum, and default values. The maximum
value given for each parameter represents a level above which the related
service will not start successfully. Resource constraints can further reduce
the maximum value for each parameter. For example, the charcount parameter in
the Requester section has a maximum value of 65535; however, this may be an
unreasonably large value, depending on your server's serial devices. If you
specify a value over the maximum, the corresponding service will fail to start.
ΓòÉΓòÉΓòÉ 7.3.1. Networks Section ΓòÉΓòÉΓòÉ
The Networks section of the IBMLAN.INI file defines the network adapters that
the workstation can access. The Networks section contains the netx statements
that define the network adapters. If LAN Server is run on more than one
installed network adapter, there must be a netx statement in the Networks
section of the IBMLAN.INI file for each of the installed network adapters.
The netx parameter is the only parameter in the Networks section of the
IBMLAN.INI file. The x variable is a sequence number used to distinguish each
netx statement. The format of the netx statement is:
netx = drivername$, a, drivertype, x1, x2, x3
Additional variables in the netx statement define the name of the protocol
driver and the number of the network adapter driver that the workstation uses
when communicating on the network adapter defined by a particular netx
statement. The remaining variable values indicate the NetBIOS resources needed
to start the workstation. The number of resources indicated in the netx
statement must be available on the workstation.
If NetBIOS for TCP/IP is installed on a workstation, the netx parameter defines
TCPBEUI$ and LM10 values for a ring 0 server.
If a loop-back driver is installed on a workstation, the net1 statement defines
the loop-back driver and the associated variable values. Also, the loop-back
driver requires that the net1 parameter be listed first on the srvnets and
wrknets statements. For more information about the format of the statements,
refer to srvnets and wrknets parameters.
The following are the default netx statements:
o For a loop-back driver: net1=loopdrv$, 0
o For a server or requester: netx=netbeui$, 0, LM10, 32, 50, 14
The variables contained in the netx statements can be grouped into two
categories: system variables and capacity variables. netx Statement Variables
lists the variables on the netx statements in the Networks section of the
IBMLAN.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 6. netx Statement Variables Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM VARIABLES Γöé CAPACITY VARIABLES Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé x Γöé x1 Γöé
Γöé drivername$ Γöé x2 Γöé
Γöé a Γöé x3 Γöé
Γöé drivertype Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.1.1. System Variables ΓòÉΓòÉΓòÉ
The following list contains the system variables in the netx statements in the
Networks section of the IBMLAN.INI file:
o x
This variable is a sequence number used to distinguish each netx statement.
Default value: 1
Minimum value: 1
Maximum value: 5
o drivername$
This variable indicates the protocol driver name. The value of this variable
should be netbeui$, loopdrv$, snabeui$, or tcpbeui$.
o a
This variable indicates the number of the network adapter driver on the
bindings parameter statement in the specified protocol section of the
PROTOCOL.INI file. The protocol section is determined by the driver name
specified for the protocol$ variable. The a variable cannot have the same
value in two different netx statements that have the same driver name
specified.
Default value: 0
Minimum value: 0
Maximum value: 3
o drivertype
This variable indicates the protocol driver type. This value should be set
to LM10 or NB30 for TCP/IP.
ΓòÉΓòÉΓòÉ 7.3.1.2. Capacity Variables ΓòÉΓòÉΓòÉ
The following list contains the capacity variables in the netx statements in
the Networks section of the IBMLAN.INI file:
o x1
This variable indicates the number of NetBIOS sessions the requester or
server allocates. Changing this value increases or decreases the number of
users and servers on the network defined by the netx statement with which
this workstation can communicate. Each session can have multiple
connections. Connections include logons and NET USE commands. This parameter
must be set to a value that is less than or equal to the Maximum sessions
(sessions) parameter value in the NetBEUI_NIF section of the PROTOCOL.INI
file.
Default value: 32 (Entry); 102 (Advanced)
Minimum value: 2
Maximum value: 254
o x2
This variable indicates the number of simultaneous NetBIOS commands (network
control blocks) a requester or server can post. For a server, changing this
value can increase or decrease the number of requester requests it can
process at once. If a value less than 16 is specified, the value of 16 is
used. This parameter must be set to a value that is less than or equal to the
Maximum commands (ncbs) parameter value in the NetBEUI_NIF section of the
PROTOCOL.INI file.
Default value: 50 (Entry); 225 (Advanced)
Minimum value: 16
Maximum value: 255
o x3
This variable indicates the number of NetBIOS names the requester allocates.
The requester uses NetBIOS names for the computer name and messaging names.
To add more messaging names, increase the value of this variable. If this
value is greater than 10, start OS/2 LAN Requester and the Messenger service
before other NetBIOS applications. This parameter must be set to a value that
is less than or equal to the Maximum names (names) parameter value in the
NETBEUI_NIF section of the PROTOCOL.INI file.
Default value: 14
Minimum value: 5
Maximum value: 254
ΓòÉΓòÉΓòÉ 7.3.2. Requester Section ΓòÉΓòÉΓòÉ
Requester parameters specify configuration values for requester memory
allocation and for programs that start with the Requester service. The
parameters contained in the Requester section can be grouped into three
categories: system parameters, capacity parameters, and tuning parameters.
Requester Section Parameters lists the parameters contained in the Requester
section of the IBMLAN.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 7. Requester Section Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM Γöé CAPACITY Γöé TUNING Γöé
Γöé PARAMETERS Γöé PARAMETERS Γöé PARAMETERS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé COMPUTERNAME Γöé MAXCMDS Γöé CHARCOUNT NUMWORKBUF Γöé
Γöé DOMAIN Γöé MAXERRORLOG Γöé CHARTIME PRINTBUFTIME Γöé
Γöé OTHDOMAINS Γöé MAXTHREADS Γöé CHARWAIT SESSTIMEOUT Γöé
Γöé WRKNETS Γöé NUMALERTS Γöé KEEPCONN SIZWORKBUF Γöé
Γöé WRKSERVICES Γöé NUMDGRAMBUF Γöé KEEPSEARCH WRKHEURISTICS Γöé
Γöé Γöé NUMSERVICES Γöé MAXWRKCACHE Γöé
Γöé Γöé SIZERROR Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.2.1. System Parameters ΓòÉΓòÉΓòÉ
The following list contains the system parameters in the Requester section of
the IBMLAN.INI file:
o computername
This parameter indicates the requester workstation name. The workstation
name can be from 1 to 15 characters (bytes) in length and can contain any
characters except embedded blanks and the following:
" / \ [ ] ; : | < > + = , ? *
If two or more non-bridged networks have workstations (servers or requesters)
configured for multiple adapters, the computernameparameter of each
workstation residing on those networks must be unique in order to ensure
valid connections to those workstations.
o domain
This parameter indicates the default domain name used when logging on from a
requester. The domain name cannot be the same as any computer name on the
network, including the local workstation. The domain name can be from 1 to 8
characters (bytes) in length and can contain any characters except embedded
blanks and the following:
" / \ [ ] ; : | < > + = , ? *
The NET VIEW command lists all the servers on the domains that are listed on
the domain and othdomains parameter statements. The NET VIEW command also
lists the servers on the domain that the user logged on to before issuing the
command. For example, a user starts a requester that has the domain parameter
set to DOMAIN1 and the othdomains parameter set to DOMAIN2,DOMAIN3. Then the
user logs on to DOMAIN4 and issues the NET VIEW command. The workstation
lists all the servers on DOMAIN1, DOMAIN2, DOMAIN3, and DOMAIN4.
o othdomains
This parameter specifies up to four additional domains in which a requester
can participate. The requester receives messages and alerts that are
broadcast to these domains. For example, you can specify DOMAIN1,DOMAIN2.
The default IBMLAN.INI file includes the othdomains parameter without any
domains listed on the right side of the equal sign (=). For information about
the NET VIEW command, refer to the domain parameter or to the IBM OS/2 LAN
Server Version 4.0 Commands and Utilities.
o wrknets
This parameter lists names of networks, separated by commas, on which the
requester runs. Names of available networks are listed in the Networks
section of the IBMLAN.INI file.
Default value: net1
o wrkservices
This parameter specifies network services to start with the Requester
service. For example, the Messenger service, which sends and receives
network messages, can be started with the Requester service. Any valid
service defined in the Services section of the IBMLAN.INI file can be started
with the Requester service. Multiple services must be separated by commas.
This value is defined by the user at installation. For more information on
valid services, see Services Section.
ΓòÉΓòÉΓòÉ 7.3.2.2. Capacity Parameters ΓòÉΓòÉΓòÉ
The following list contains the capacity parameters in the Requester section of
the IBMLAN.INI file:
o maxcmds
This parameter sets the maximum number of NetBIOS commands the requester can
send to the workstation's network adapters simultaneously. Increase the value
of this parameter if you have multiple applications on the requester
simultaneously using LAN Server. Because command processing uses memory, do
not specify a number higher than you need. The recommended value is 1.6
times the value specified for the maxthreads parameter.
If you change this value, you must restart your workstation to make the
change effective.
Default value: 16
Minimum value: 5
Maximum value: 255
o maxerrorlog
This parameter sets the maximum size, in kilobytes, of the error log. The
maxerrorlog parameter keeps the error log from filling up your hard disk.
Reduce the maxerrorlog parameter value if you need disk space more than you
need extensive error information.
Default value: 100
Minimum value: 2
Maximum value: Restricted by the size of the hard disk.
o maxthreads
This parameter sets the maximum number of threads within a requester that are
available to handle simultaneous network requests. The actual number of
threads is based on the value of the maxthreads, maxcmds, and numworkbuf
parameters. If the requester has multiple applications simultaneously using
LAN Server, increase the value of the three parameters. Because each thread
reduces the amount of available memory, do not allocate more than you need.
The numworkbuf and maxcmds parameter values should be set greater than or
equal to the maxthreads parameter value.
If you change this value, you must restart your workstation to make the
change effective.
Default value: 10
Minimum value: 10
Maximum value: 254
o numalerts
This parameter sets the number of program tasks that can wait for an alert
condition. Increase the numalerts parameter value only if you are using a
server-based application with documentation directing you to increase the
value. Because a larger value takes more memory (approximately 280 bytes for
each increment), do not allocate more numalerts than you need.
Default value: 12
Minimum values: 5 for servers; 3 for requesters
Maximum value: 200
o numcharbuf
This parameter sets the number of character pipe and device buffers.
Increase this value if you are using several shared serial devices or
character pipes, or if you need to transmit large amounts of data across the
network to such devices. Since each buffer takes up memory, do not allocate
more than you need. Actual minimum and maximum values depend on the serial
device. See the documentation about your serial device for more information.
Default value: 10
Minimum value: 0
Maximum value: 15
o sizcharbuf
This parameter sets the size, in bytes, of special read-ahead buffers used by
the requester to improve the performance of read operations on character
devices (redirected EOM ports and byte mode network pipes).
Default value: 512
Minimum value: 64
Maximum value: 4096
o numdgrambuf
This parameter sets the number of buffers for processing datagrams. Servers
use datagrams to broadcast their presence on the domain. Datagrams are also
used for domain-wide broadcasts. If you are on a network with many servers or
with a large amount of domain-wide broadcasts, you may want more datagram
buffers to handle incoming announcements.
Default value: 14
Minimum value: 8
Maximum value: 112
o numservices
This parameter sets the size of the internal service table. Increase the
numservices parameter value if your requester runs many services. Because a
larger table takes up memory, do not allocate more space than you need.
Available services are listed in Services Section. The numservices parameter
value should be greater than or equal to the number of entries in the
Services section of the IBMLAN.INI file.
Default value: 7 (requesters); 16 (servers)
Minimum value: 4
Maximum value: 256
o sizerror
This parameter sets the size of the requester internal error buffer. Reduce
the sizerror parameter value if you need more available memory and your
network does not have frequent network errors.
Default value: 1024
Minimum value: 256
Maximum value: 4096
ΓòÉΓòÉΓòÉ 7.3.2.3. Tuning Parameters ΓòÉΓòÉΓòÉ
The following list contains the tuning parameters in the Requester section of
the IBMLAN.INI file:
o charcount
This parameter sets the number of characters, in bytes, that the requester
stores before sending data to a serial device queue. Increase the charcount
parameter value if you need to reduce traffic on your network. Actual
minimum and maximum values depend on the serial device. For more information,
see the documentation about your serial device.
Default value: 16
Minimum value: 0
Maximum value: 65535
o chartime
This parameter sets the time, in milliseconds, that the requester collects
data to send to a shared serial device queue. Increase the chartime
parameter value if you need to limit network use. If the chartime parameter
value is too low, network efficiency decreases. Actual minimum and maximum
values depend on the serial device. For more information concerning valid
minimum and maximum values, see your serial device documentation.
Default value: 250
Minimum value: -1 (This value means the contents of the requester buffer
are sent when the buffer has reached the size specified in the charcount
parameter.)
Maximum value: 65535
o charwait
This parameter sets the time, in seconds, that the requester waits for a
shared serial device to become available. Increase the charwait parameter
value if you have heavy use of shared serial devices and can afford to wait.
Actual minimum and maximum values depend on the serial device. For more
information, see your serial device documentation.
Default value: 3600
Minimum value: 0
Maximum value: 65535
o keepconn
This parameter sets the amount of time, in seconds, that the requester
maintains an inactive universal naming convention (UNC) connection to a
shared resource. The value of this parameter specifies the amount of time
that a UNC connection should remain dormant before the UNC connection is
actually disconnected. The keepconn parameter only applies to implicit UNC
connections (those resource connections called by an application without a
prior NET USE). If there are no accesses to this resource during the
interval specified by the keepconn parameter, the UNC connection is
disconnected.
Default value: 600
Minimum value: 1
Maximum value: 65535
o keepsearch
This parameter sets the amount of time, in seconds, that the requester
maintains an inactive file search request.
Default value: 600
Minimum value: 1
Maximum value: 65535
o maxwrkcache
This parameter sets the maximum size, in kilobytes, of the requester's
large-transfer buffers. Increase the maxwrkcache parameter value if you use
your requester for file-intensive projects, such as copying large files, and
need better performance. The value of this parameter must be a multiple of
64 in order to match the size of the corresponding big buffer on the server.
Big buffers on a server workstation have a set size of 64KB. The number of
big buffers on the server is specified by the numbigbuf parameter.
Increasing the maxwrkcache parameter value may only be effective when a
requester is running multiple applications against the server. In addition,
each increment uses an additional 64KB of the requester's memory. Therefore,
the default value of this parameter should usually be used.
Default value: 64
Minimum value: 0
Maximum value: 640
o numworkbuf
This parameter sets the number of buffers the requester can use to store data
for transmissions both to and from the server. These buffers are used in
constructing the SMBs that are sent to the server. These buffers also provide
data buffering between the application running in the requester and the
network adapter card.
This parameter does not have a large impact on performance and therefore
should rarely be changed. However, it may help requester performance to
increase the value of the numworkbuf, maxthreads, and maxcmds parameters if
there are multiple applications on the requester accessing server resources.
Because each buffer reduces the amount of available memory, do not allocate
more than you need. The numworkbuf and maxcmds parameter values should be set
greater than or equal to the maxthreads parameter value.
Default value: 15
Minimum value: 3
Maximum value: 50
o printbuftime
This parameter sets the time limit, in seconds, for truncating a DOS print
job.
Default value: 90
Minimum value: 0
Maximum value: 65535
o sesstimeout
This parameter specifies the time, in seconds, the requester waits before
disconnecting a session from a server that is not responding to a request. If
the server workload is extremely heavy, it may be necessary to increase the
value of this parameter to prevent an inappropriate session termination.
Default value: 45
Minimum value: 10
Maximum value: 65535
o sizworkbuf
This parameter sets the size, in bytes, of requester buffers. This value
should be a multiple of 512. It should be the same for every requester on the
network and equal to the sizreqbuf value used by servers. Because the value
of the sizworkbuf parameter should match all corresponding buffers on the
network, it is recommended that the default value not be changed in most
circumstances.
Default value: 4096
Minimum value: 1024
Maximum value: 16384
o wrkheuristics
This parameter sets a variety of requester fine-tuning options. Each digit
of the wrkheuristics parameter has an independent meaning. When digits are
missing from the right-hand side of the parameter value, the system supplies
the default specified for each missing digit.
Except where noted, each digit of the wrkheuristics parameter is a binary
digit: 0 means off (inactive); 1 means on (active). Other values are defined
following the description of each digit.
1 2 3 4
Digit position: 01234567890123456789012345678901234567890
Default value: 11111111213111111100010111201112211212111
The meanings of the digits of the wrkheuristics parameter are as follows:
Position Meaning
0 Requests opportunistic locking of files. The default is 1.
When digit position 0 is active, it allows a file opened in
deny-none sharing mode to be locked by the server. Buffering can
then be used to enhance performance. However, the server cannot
lock the file if there are outstanding access requests. The server
assumes that the first requester is the only active process using
that file and prevents a second requester from accessing the file
until buffered data is flushed (written to disk) and the file is
closed. For more information, refer to the srvheuristics parameter,
digit position 0 in topic Tuning Parameters and digit position 15
in topic Tuning Parameters.
1 Specifies performance optimization for batch (.CMD) files. Digit
position 0 of the wrkheuristics parameter (opportunistic locking)
must be set to 1. The default is 1.
When digit position 1 is active, a batch file on the server running
on the requester is kept in the requester's buffer to prevent a
request across the LAN for each line of the batch file. When digit
position 1 is inactive, the batch file is opened and closed with
each line processed. The buffer data is flushed when the batch
file is closed. The value of digit position 1 can be set to 0 if
two or more requesters want to run a batch file simultaneously.
However, file opens and closes across the LAN can greatly degrade
performance.
2 Specifies asynchronous unlock and asynchronous write-unlock, as
follows:
Value Meaning
0 Never
1 Always
2 Only on a LAN Server virtual circuit
The default is 1.
A virtual circuit is a NetBIOS session connection to another
workstation over a LAN. With digit position 2, files in the
requester buffer are unlocked in the buffer, and processing
continues without waiting for confirmation from the server. Any
errors occurring at the server are reported later. Generally, the
only errors that might occur are hard media errors, such as a full
disk or loss of power to the server.
Asynchronous lock and asynchronous write-unlock are not used if the
file was opened with the write-through flag set. The write-through
flag, when active, means that any writes to the file must be
written through the cache to the fixed disk before returning
control to the calling program. If data integrity is a primary
concern and the write-through flag is not used, digit position 2
can be set to 0. Values 1 and 2 are functionally equivalent in a
LAN Server environment.
3 Specifies asynchronous close and asynchronous write-close, as
follows:
Value Meaning
0 Never
1 Always
2 Only on a LAN Server virtual circuit
The default is 1.
Digit position 3 performs a function similar to digit position 2 of
the wrkheuristics parameter. The server sends a completion message
to the requester for close or write-close requests before writing
buffered file data to the hard disk. The user is warned if all the
data is not written to the hard disk. Asynchronous close and
asynchronous write-close are not used if the file was opened with
the write-through flag set.
If data integrity is a primary concern and the write-through flag
is not used, digit position 3 can be set to 0. Values 1 and 2 are
functionally equivalent in a LAN Server environment.
4 Buffers all named pipes and serial devices. The default is 1.
Digit position 4 causes named pipe and communication device
information to be buffered by the requester while the workstation
is reading the information. This provides a degree of protection
for the data as well as a potential performance improvement.
5 Specifies combined read-lock and write-unlock, as follows:
Value Meaning
0 Never
1 Always
2 Only on a LAN Server virtual circuit
The default is 1. When digit position 5 is active, the lock and
read requests are joined and sent as one command. The write and
unlock requests are joined similarly. Values 1 and 2 are
functionally equivalent in a LAN Server environment.
6 Specifies open and read. The default is 1.
When digit position 6 is active, a request to open a file also
performs a read of the size specified by the sizworkbuf parameter
from the beginning of the file to the requester's work buffer.
7 Reserved. This digit position is not used by LAN Server.
8 Specifies the use of the chain-send NetBIOS network control block
(NCB), as follows:
Value Meaning
0 Never
1 When a server's buffer is larger than the workstation's buffer
2 Always (to avoid copy)
The default is 2.
A chained-send enables the NetBIOS protocol driver to copy large
data blocks directly from the OS/2 LAN Requester user's buffer to
the network adapter card. An intermediate copy is not sent to the
network buffers, from which the NetBIOS protocol driver normally
copies the data to the network adapter card.
In order for the Netlogon service to replicate user and group
definitions across servers in a domain, digit position 8 of the
wrkheuristics parameter (on additional servers) and digit position
3 of the srvheuristics parameter (on domain controllers) must not
be set to 0. If these digit positions are set to 0, user and group
data may not be replicated from the domain controller, resulting in
unknown user IDs and group IDs on the additional servers.
9 Buffers small read and write requests until the buffer is full, as
follows:
Value Meaning
0 Never
1 Always
2 Only on a LAN Server virtual circuit
The default is 1.
When digit position 9 is active and file access mode allows,
requests to read or write data smaller than that specified by the
sizworkbuf parameter are performed locally in the requester's
buffer. Buffering avoids additional trips across the LAN. The
buffer is flushed when the file is closed or when the buffer is
needed to satisfy other requests.
Digit position 9 can enhance performance for applications that
read, modify, and write back small records. Values 1 and 2 are
functionally equivalent in a LAN Server environment. Digit position
9 can be set to 0 if data integrity is a primary concern.
10 Specifies buffer mode (assuming shared access is granted), as
follows:
Value Meaning
0 Always read buffer size amount of data if the request is smaller
than the buffer size (sizworkbuf) and data is being read
sequentially.
1 Use full buffer if file is open for reading and writing.
2 Use full buffer if reading and writing sequentially.
3 Buffer all requests smaller than the buffer size (if hits occur).
The default is 3.
Shared access means the file was opened in sharing mode. These
options allow selective tuning of the buffer mode if any
applications handle data in a manner conflicting with buffering.
11 Specifies RAW read and RAW write server message block (SMB)
protocols. The default is 1.
RAW read and RAW write SMB protocols transfer data across the LAN
without SMB headers. These protocols transfer large files directly
between the server memory and a work cache in the requester.
Digit position 11 can significantly improve performance of large
file transfers across the LAN. Digit position 11 must be active for
digit positions 12 and 13 to be functional.
12 Specifies large RAW read-ahead buffer. The default is 1.
Digit positions 12 and 13 provide independent control over the use
of RAW SMB protocol for read-ahead and write-behind, respectively.
Both are active by default, but they can be turned off to better
suit a particular environment. Digit position 11 must be active for
digit positions 12 and 13 to be functional.
13 Specifies large RAW write-behind buffer. The default is 1.
Digit position 11 must be active for digit positions 12 and 13 to
be functional. See digit positions 11 and 12 for more information.
14 Specifies read multiplexing SMB protocols. The default is 1.
This SMB protocol is used for large read requests if the RAW SMB
protocol (digit position 11) is inactive. This protocol breaks
transfers into buffer-size chunks (sizworkbuf) and chains them
together to satisfy the request.
15 Specifies write multiplexing SMB protocols. The default is 1.
This SMB protocol is used for large write requests if the RAW SMB
protocol (digit position 11) is inactive. This protocol divides
transfers into buffer-size chunks (sizworkbuf) and chains them
together to satisfy the request.
16 Specifies using big buffers for large core (non-RAW) reads. The
default is 1.
Digit position 16 is pertinent only to requests made to a core
server. An example of a core server is the PC LAN Program, which
does not recognize certain SMB types added to the SMB command set
by LAN Server. PC LAN Program is not supported for Double-Byte
Character Set (DBCS) machines.
17 Specifies same-size small record read-ahead or read-to-sector
boundary. The default is 1.
When digit position 17 is active, requests to read small data
records sequentially cause read-ahead in multiples of the data
record size, so a full buffer is read and sent to the requester.
For example, if the user is reading 50-byte records sequentially
from a 4096-byte buffer, LAN Server will read ahead to fill the
buffer to 4050 bytes. When digit position 17 is set to 0, data is
read up to the next sector boundary, usually 512 bytes.
Digit position 17 is significant only if digit position 9 of the
wrkheuristics parameter is inactive. If the requester detects
small data records of the same size being read sequentially, the
requester performs this small record read-ahead operation.
18 Specifies same-size small record write-behind or write-to- sector
boundary. The default is 0.
When digit position 18 is active, requests to write small data
records cause write-behind in multiples of the data record size, so
a full buffer is written to the server.
When digit position 18 is set to 0, data is written up to the next
sector boundary, usually 512 bytes.
Digit position 18 is significant only if digit position 9 of the
wrkheuristics parameter is inactive. If the server detects small
data records of the same size being written sequentially, the
server performs this small record write-behind operation.
19 Reserved. This digit position must be set to 0.
20 Flushes pipes and devices on a DosBufReset or DosClose operation.
The default is 0.
Digit position 20 gives the requester application more flexibility
regarding which files, pipes, or devices are flushed (written to
disk) following DosBufReset or DosClose operations.
Value Meaning
0 Flush only files and devices opened by the caller. Spin until
flushed. Wait for confirmation before proceeding with other tasks.
1 Flush only files and devices opened by the caller. Flush only
once. Do not wait for confirmation.
2 Flush all files and all input and output of short-term pipes and
devices. Spin until flushed.
3 Flush all files and all input and output of short-term pipes and
devices. Flush only once.
4 Flush all files and all input and output of all pipes and devices.
Spin until flushed.
5 Flush all files and all input and output of all pipes and devices.
Flush only once.
21 Supports LAN Server encryption of passwords. The default is 1.
22 Controls log entries for multiple occurrences of an error. A
recurring error can fill up the error log; use digit position 22 to
keep down the number of log entries. If the value is other than 0,
the 1st, 4th, 8th, 16th, and 32nd occurrences of an error are
logged. After that, every subsequent 32nd occurrence is logged.
If the value of digit position 22 is other than 0, the value also
defines the size of an error table. The table is a record of
errors that have occurred. Each table entry consists of an error ID
number and the number of occurrences of that error. If an error
does not match an existing entry in the table and the table is
full, the logging facility deletes the table entry that has the
lowest number of occurrences and records the new error information.
The table size refers to the number of different errors allowed at
one time in the table. The default is 0.
Set the value as follows:
Value Meaning
0 Log all occurrences.
1 Use error table, size 1.
2 Use error table, size 2.
3 Use error table, size 3.
4 Use error table, size 4.
5 Use error table, size 5.
6 Use error table, size 6.
7 Use error table, size 7.
8 Use error table, size 8.
9 Use error table, size 9. Typing NET ERROR at the command-line
prompt will display the errors in this table that have been written
to the error log.
23 Buffers all files opened with deny-write sharing mode. The default
is 1.
When digit position 23 is active, the server buffers all files
opened with deny-write sharing mode, regardless of the access mode
the requester used to open the file. The sharing mode and access
mode are two different parameters of a DosOpen command. Digit
position 23 deactivates buffering on this requester if an
application does not work correctly with it.
24 Buffers all files opened with the read-only (R) attribute set. The
default is 1.
When digit position 24 is active, the server buffers all files with
the read-only attribute set. Only read access mode will
successfully open a read-only file. The sharing mode and access
mode are two different parameters of a DosOpen command. Digit
position 24 deactivates buffering on this requester if an
application does not work correctly with it.
25 Reads ahead when opening for execution. Reading an executable file
sequentially is usually, but not always, faster. The default is 1.
The value of digit position 25 should be 1 if many executable files
are loaded across the LAN. The load time for some application
programs can decrease by more than 50%. Experiment with your
particular program to determine which value is better (0 or 1).
26 Handles the Interrupt (Ctrl+C) key, as follows:
Value Meaning
0 Allow no interrupts.
1 Allow interrupts only on long-term operations.
2 Always allow interrupts.
The default is 2.
27 Forces correct open mode when creating files on a core server,
which is a a DOS-based LAN server. The default is 0. Digit position
27 is reserved for a DBCS user.
28 Specifies the NetBIOS NoAck mode (transferring data without waiting
for an acknowledgment), as follows:
Value Meaning
0 NoAck is disabled.
1 NoAck is set on send only.
2 NoAck is set on receive only.
3 NoAck is set on send and receive.
The default is 1.
29 Sends data along with the SMB write-block RAW requests. The default
is 1.
When digit position 29 is active, the requester sends a requester
buffer of data (sizworkbuf) to the server with its request for RAW
mode protocol for large file transfers.
30 Sends a message to the screen when the requester logs an error, as
follows:
Value Meaning
0 Never
1 On write-fault errors only (no time out)
2 On write-fault and internal errors only (no time out)
3 On all errors (no time out)
4 Reserved
5 On write-fault errors only (time out)
6 On write-fault and internal errors only (time out)
7 On all errors (time out)
The default is 1.
Values other than 1 are normally used for debugging purposes only.
31 Reserved. This digit position is not used by LAN Server.
32 Establishes the behavior of the OS/2 API calls DosBufReset and
DosResetBuffer and the DOS INT21 API call, COMMIT FILE, on a
redirected file (not pipes or devices). When the call to the API
returns, the data in the buffer has been handled as follows:
Value Meaning
0 Changed data in the buffer was sent from the requester to the
server. The server has written the data to disk.
1 Changed data in the buffer was sent from the requester to the
server. The server has not yet written the data to disk.
2 DosBufReset was ignored for the files.
The default is 2.
33 Establishes the time interval for performing logon validation from
the domain controller. Digit position 33 can be set as follows:
Value Meaning
0 5 seconds
1 15 seconds
2 30 seconds
3 45 seconds
4 60 seconds
5 90 seconds
6 2 minutes
7 4 minutes
8 8 minutes
9 15 minutes
The default is 1.
34 There is a difference in date validation for older Microsoft and
IBM servers. This digit position establishes interoperabilty with
older servers. The default is 0.
Value Meaning
0 Attempts to validate dates with preference toward PCLP date
format.
1 Assumes the date is in the MSNET format.
2 Unchanged. Value 2 assumes the date is correct.
35 Many DOS applications behave incorrectly when more than two
gigabytes of free space is indicated by an API to be available on a
partition. This digit position allows these applications to operate
correctly.
Value Meaning
0 Return the true value for free disk space on the partition. The
default is 0.
1 Always return a value for free disk space that is less than two
gigabytes.
36 timesync performs time and date synchronization with the domain
controller at logon. Digit position 36 can be set as follows:
Value Meaning
0 no
1 yes
The default is 1 (yes).
37 logonverification specifies the type of verification that occurs
during LAN Server logon. Digit position 37 can be set as follows:
Value Meaning
0 Allows you to log on without your user ID and password being
verified. The user ID and password are only stored.
1 Validates your user ID and password on your local workstation
using the local copy of the user and definitions file (NET.ACC).
2 Validates your user ID and password on the domain logon server.
The user ID and password are sent to a domain controller or backup
server to be validated using the domain copy of the NET.ACC.
The default is 2 (domain).
38 logonwarningmsgs allows LAN Server logon warnings to be suppressed
in some cases when the messages may be irritating to a user. Digit
position 38 can be set as follows:
Value Meaning
0 No warning messages are displayed.
1 All warning messages are displayed.
2 LAN Server-specific warning messages are not displayed.
The default is 1 (all).
39 Buffers all files opened in compatibility mode. Digit position 39
can be set as follows:
Value Meaning
0 Buffer only files opened for read access in compatibility mode.
1 Buffer all files opened in compatibility mode.
The default is 1 (all files opened).
40 Multiple logons allow a user to log on multiple times in the same
domain. Note that the prevention of multiple logons is true only
when the user ID and the domain name are equal to or less than 8
characters each. For the longer user IDs or domain names, multiple
logons are always allowed no matter how this digit is set. Digit
position 40 can be set as follows:
Value Meaning
0 Prevent multiple logons. If this digit is set to 0, the logon
process will prevent a user from logging on more than once in the
same domain. This is done by concatenating the user ID and the
domain name and adding it as a unique NetBIOS name. A second user
cannot add the same NetBIOS name.
1 Allow multiple logons. The default is 1.
ΓòÉΓòÉΓòÉ 7.3.3. Messenger Section ΓòÉΓòÉΓòÉ
The parameters in the Messenger section specify the buffer size and file name
of the log file used to receive messages. The parameters contained in the
Messenger section can be grouped into two categories: system parameters and
capacity parameters. The following table lists the parameters contained in the
Messenger section of the IBMLAN.INI file.
Note: Ensure that the Messenger service is stopped before you delete the
message log file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 8. Messenger Section Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM PARAMETER Γöé CAPACITY PARAMETER Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LOGFILE Γöé SIZMESSBUF Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.3.1. System Parameter ΓòÉΓòÉΓòÉ
The following is the system parameter in the Messenger section of the
IBMLAN.INI file:
o logfile
This parameter specifies a file name within the \IBMLAN\LOGS subdirectory for
the message log.
Default value: MESSAGES.LOG
ΓòÉΓòÉΓòÉ 7.3.3.2. Capacity Parameter ΓòÉΓòÉΓòÉ
The following is the capacity parameter in the Messenger section of the
IBMLAN.INI file:
o sizmessbuf
This parameter sets the buffer size, in bytes, for receiving network
messages. If you receive numerous or long messages, increase the sizmessbuf
parameter value. Because larger buffers require more memory, do not allocate
larger buffers than you need.
Default value: 4096
Minimum value: 512
Maximum value: 62000
ΓòÉΓòÉΓòÉ 7.3.4. Server Section - Entry Server Function and Peer Function ΓòÉΓòÉΓòÉ
The parameters in the Server section establish values that affect the server
functions. If these parameters are set too high, the server may fail to start
and an error message indicating the possible configuration problems will be
displayed.
Some of the parameters in the Server section of the IBMLAN.INI file work
differently for the 386-HPFS server. The descriptions for all the Server
section parameters are provided in this section. For descriptions of the
parameters that function differently for a 386-HPFS server, see Server Section
- Advanced Package Function.
Note: When the Advanced server accesses a FAT file system partition, the
Advanced server functions like the Entry server.
The Server section parameters that function differently on a 386-HPFS
workstation are:
o maxconnections
o maxlocks
o maxopens
o maxsearches
o numbigbuf
o srvheuristics
The parameters contained in the Server section can be grouped into three
categories: system parameters, capacity parameters, and tuning parameters.
Server Section Parameters lists the parameters contained in the Server section
of the IBMLAN.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 9. Server Section Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM PARAMETERS Γöé CAPACITY PARAMETERS Γöé TUNING PARAMETERS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ACCESSALERT Γöé MAXAUDITLOG Γöé ALERTSCHED Γöé
Γöé ALERTNAMES Γöé MAXCHDEVJOB Γöé NUMBIGBUF Γöé
Γöé AUDITING Γöé MAXCHDEVQ Γöé NUMFILETASKS Γöé
Γöé AUTODISCONNECT Γöé MAXCHDEVS Γöé NUMREQBUF Γöé
Γöé AUTOPATH Γöé MAXCONNECTIONS Γöé SIZREQBUF Γöé
Γöé AUTOPROFILE Γöé MAXLOCKS Γöé SRVANNDELTA Γöé
Γöé DISKALERT Γöé MAXOPENS Γöé SRVANNOUNCE Γöé
Γöé ERRORALERT Γöé MAXSEARCHES Γöé SRVHEURISTICS Γöé
Γöé GUESTACCT Γöé MAXSESSOPENS Γöé Γöé
Γöé LOGONALERT Γöé MAXSESSREQS Γöé Γöé
Γöé MAXSESSVCS Γöé MAXSHARES Γöé Γöé
Γöé NETIOALERT Γöé MAXUSERS Γöé Γöé
Γöé SRVNETS Γöé Γöé Γöé
Γöé SRVSERVICES Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.4.1. System Parameters ΓòÉΓòÉΓòÉ
The following list contains the system parameters in the Server section of the
IBMLAN.INI file:
o accessalert
This parameter sets the number of attempted resource-access violations that
can occur before the server sends an alert message. Set this parameter to 1
for immediate notification of an attempted access violation.
Default value: 5
Minimum value: 0
Maximum value: 65535
o alertnames
This parameter specifies the user or machine IDs that receive administrative
alert messages. Do not specify group IDs. Separate IDs with commas.
Alert-related broadcasts can also be limited by reducing the number of names
specified by alertnames on the servers.
o auditing
This parameter specifies which events to audit when the server is started.
When you set the auditing parameter by using any of the following values,
information about the events they represent is collected.
NET START SERVER /AUDITING:YES means an audit log is begun. The default is
AUDITING=NO and there is no audit log. See the LAN Server Commands and
Utilities for further information regarding this command.
When you set the /AUDITING parameter to YES, the audit log records
information about all of the event types represented by the following
options. When you specify NO with this parameter, auditing is stopped (this
is the default). To record information about specific event types, you can
set the /AUDITING parameter with one or more of the following options:
Note: It is not valid to include two options together when one implies the
other (for example, Use and Gooduse).
Logon Includes the Netlogon and Sesslogon options. Records each time a user
starts or stops one of the server's services. The Logon option is a
superset of the Netlogon and Sesslogon options.
Logonlimit Records each time a user exceeds logon hours for the user
account.
Netlogon Includes the Badnetlogon and Goodnetlogon options. Records each
time a user logs on to the network. The Netlogon option is a superset
of the Badnetlogon and Goodnetlogon options.
Badnetlogon
Records each time a user fails in an attempt to log on to the
network.
Goodnetlogon
Records each time a user successfully logs on to the network.
Permissions Records each time a user makes changes to the list of
permissions for a file.
Resource Records each time a user accesses a resource in a way that is
defined in the auditing options for the resource.
Service Records each time a user starts or stops one of the server's
services.
Sesslogon Includes the Badsesslogon and Goodsesslogon options. Records each
time an attempt is made to start or end a session with the server. The
Sesslogon option is a superset of the Badsesslogon and Goodsesslogon
options.
Badsesslogon
Records each time a user fails to start a session with the server.
Goodsesslogon
Records each time a user starts a session with the server.
Use Includes the Baduse and Gooduse options. Records each time a user uses
a shared resource. The Use option is a superset of the Baduse and
Gooduse options.
Baduse
Records each time a user fails in an attempt to use a shared
resource.
Gooduse
Records each time a user successfully uses a shared resource, except
where the resource allows for an unlimited number of uses.
Userlist Records each time a user makes changes to the user accounts
database.
o autodisconnect
This parameter sets the time, in minutes, the server waits before
disconnecting inactive sessions. To specify that the server does not
disconnect inactive sessions automatically, set the autodisconnect value to
-1. Also, the cleanup parameter defaults to YES when autodisconnect = -1. If
you set the autodisconnect value to 0, unpredictable results occur.
Default value: 120
Minimum value: -1
Maximum value: 65535
o autopath
This parameter specifies the path to the profile that contains the OS/2
Remote IPL share information. The specified path can be an absolute path
beginning with a drive letter or name of a file that exists in the
\IBMLAN\PROFILES subdirectory. This parameter is not in the default
IBMLAN.INI file, but it is added by the OS/2 Remote IPL installation program.
The associated profile is also set up by the OS/2 Remote IPL installation
program. The profile should not be edited by the user.
Default value: C:\IBMLAN\PROFILES\SRVAUTO.PRO
o autoprofile
This parameter determines whether the profile specified by the autopath
parameter is run when the server starts. Specify Load to use the profile
when the server starts. Specify None to not use the profile when the server
starts.
Default value: Load
o diskalert
This parameter sets the minimum free disk space, in kilobytes, that the
server allows before sending an alert message. All hard disks and partitions
are monitored. If the server's disk space is a prime concern, increase the
value of this parameter.
Default value: 5000
Minimum value: 0
Maximum value: 65535
o erroralert
This parameter specifies the number of errors that can occur before the
server sends an alert message. If you need rapid notification of errors,
reduce the value of this parameter.
The following events increment the error count, causing an error alert to be
sent:
- An illegal server message block (SMB) sent from a client.
- A write-close error.
- Damage to the AT command schedule file.
- Running out of a predefined resource causes a resource error and
increments the error count by 1. Resource errors could result from one of
the following IBMLAN.INI file parameters being decreased:
o maxchdevjob
o maxchdevq
o maxchdevs
o maxconnections
o maxlocks
o maxopens
o maxsearches
o maxsessopens
o maxsessreqs
o maxshares
o maxusers
o numbigbuf
Default value: 5
Minimum value: 0
Maximum value: 65535
o guestacct
This parameter identifies a guest account that allows users to access
resources in this domain without having their user IDs defined to the domain.
Also, users can log on to the domain using the guest ID. The guest ID is
managed (through User Profile Management and LAN Server) as any other user
ID. This parameter is valid only on the domain controller.
Default value: GUEST
o logonalert
This parameter specifies the number of logon violations, during the interval
specified by the alertsched parameter, before an alert is issued. This
parameter is valid only on a domain controller or backup server.
Default value: 5
Minimum value: 0
Maximum value: 65535
o maxsessvcs
This parameter specifies the maximum number of virtual circuits the server
can accept from a requester. This parameter must be set to 1.
o netioalert
This parameter sets the number of network input and output errors allowed,
during the interval specified by the alertsched parameter, before the server
sends an alert message.
Default value: 5
Minimum value: 0
Maximum value: 65535
o srvnets
This parameter lists names of the networks on which the server runs. Names of
available networks are listed in the Networks section of the IBMLAN.INI file.
Default value: net1
o srvservices
This parameter specifies which network services to start with the Server
service. Its format is a list of services, separated by commas, and is
defined by the user at installation. For more information and the names of
the services that can be started with the srvservices parameter, see Services
Section.
ΓòÉΓòÉΓòÉ 7.3.4.2. Capacity Parameters ΓòÉΓòÉΓòÉ
The following list contains the capacity parameters in the Server section of
the IBMLAN.INI file:
o maxauditlog
This parameter sets the maximum size, in kilobytes, of the audit log file.
When the log file size reaches this value, no more entries are saved in the
file. Saving entries resumes as soon as the log file is cleared. If you do
not need extensive audit information, reduce the value of this parameter.
Default value: 100
Minimum value: 0
Maximum value: 65535
o maxchdevjob
This parameter specifies the maximum number of requests the server can accept
for all serial device queues combined. If your shared serial devices are
heavily used, increase the value of this parameter.
Default value: 6
Minimum value: 0
Maximum value: 65535
o maxchdevq
This parameter specifies the maximum number of shared serial device queues.
If you want to share many serial device queues, increase the value of this
parameter.
Default value: 2
Minimum value: 0
Maximum value: 65535
o maxchdevs
This parameter specifies the maximum number of shared serial devices. Set the
value of this parameter to the number of serial devices the server shares
with the network.
Default value: 2
Minimum value: 0
Maximum value: 16
o maxconnections
386 HPFS Users
Refer to Server Section - Advanced Package Function for the maxconnections
parameter description. The following description applies only to Entry
servers and Peer servers.
This parameter specifies the maximum number of connections that requesters can
have to the server. This is the number of NET USE commands the server can
handle. For example, a user issuing five NET USE commands needs 5
connections. Five users who each issue one NET USE command need 5
connections. Increase the value of this parameter if many users access the
server. The maxconnections parameter value must be greater than or equal to
the maxusers parameter value.
Default value: 26 (Peer); 128 (Entry)
Minimum value: 1
Maximum value: 2000
o maxlocks
386 HPFS Users
Refer to Server Section - Advanced Package Function for the maxlocks
parameter description. The following description applies only to Entry
servers and Peer servers.
This parameter specifies the maximum number of file locks on the server. This
is the maximum number of byte ranges (records) that may be locked by users on
the server. Increase the value of this parameter if there is a large number
of heavily used files. This parameter applies only to lock requests issued by
DOS requesters.
Note: This number applies only to networks that have DOS PC LAN Program
requesters, which do not have DBCS hardware.
Default value: 64
Minimum value: 1
Maximum value: 8000
o maxopens
386 HPFS Users
Refer to Server Section - Advanced Package Function for the maxopens
parameter description. The following description applies only to Entry
servers and Peer servers.
This parameter specifies the maximum number of files, pipes, and devices the
server can have open at one time. For example, the value of this parameter
must be greater than or equal to 5 for a user opening five files. The value of
this parameter must also be greater than or equal to 5 for five users opening
the same file. If many users access the server simultaneously, increase the
value of this parameter.
Default value: 128 (Peer); 160 (Entry)
Minimum value: 1
Maximum value: 8000
Note: The maximum number of open files is 8000. However, the maximum number
of unique open files is 1279. The first opening of a file counts
against the maximum of 1279. Additional openings of the same file
count against the maximum of 8000.
o maxsearches
386 HPFS Users
Refer to Server Section - Advanced Package Function for the maxsearches
parameter description. The following description applies only to Entry
servers and Peer servers.
This parameter specifies the maximum number of directory searches the server
can do simultaneously. These searches are executed when a user does a
wildcard search of a directory; for example, DIR Y:\TEXTFILE.*. If the
server's files are heavily used, increase the value of this parameter. See
digit position 7 of the srvheuristics parameter in topic Tuning Parameters for
more information about searches. The following equation can be used to
calculate a value for the maxsearches parameter. Do not use the calculated
value if it is less than the default value.
Default value: 50 (Peer); 150 (Entry)
Minimum value: 1
Maximum value: 1927
o maxsessopens
This parameter specifies the maximum number of files, pipes, and devices one
requester can have open on the server. If many of the server resources are
used simultaneously, increase the value of this parameter. The default for
Peer or Entry server functions is 80.
Note: The server uses some of the value specified with the maxsessopens
parameter for internal processing, so the entire value specified with
this parameter is not available to the user.
Default value: 80 (Peer, Entry)
Minimum value: 1
Maximum value: 8000 (must be less than maxopens)
o maxsessreqs
This parameter specifies the maximum number of resource requests one
requester can have pending on the server. If users need to perform multiple
tasks simultaneously on the server, increase the value of this parameter.
Default value: 50
Minimum value: 1
Maximum value: 65535
o maxshares
This parameter specifies the maximum number of resources the server can share
with the network. For example, if one user is using five resources on the
server, the value of this parameter must be at least 5; but if five users are
using the same server resource, the value of this parameter need only be set
to 1. If the server shares many resources, increase the value of this
parameter.
Default value: 16 (Peer); 64 (Entry); 192 (Advanced)
Minimum value: 2
Maximum value: 1000
Note: The number of shared resources displayed by the NET CONFIG SRV command
will be different from the number specified with the maxshares
parameter. This is because the number of shared resources displayed by
the NET CONFIG SRV command also includes default system shares
(ibmlan$, admin$, and so on), and one share for each partition on the
server (a$, b$, and so on).
o maxusers
This parameter sets the maximum number of users who can use the server
simultaneously. This equals the number of users who might issue a NET USE
command to the server. A user who issues up to five NET USE commands counts
as one user. Five users, each issuing a NET USE command to the same
resource, count as five users. This value is the number of NetBIOS sessions
on the server.
The maxusers parameter value cannot exceed the maxconnections parameter
value.
Default value: 5 (Peer); 32 (Entry); 100 (Advanced)
Minimum value: 1
Maximum value: 1000 (250 maximum for each adapter
netx specified in the IBMLAN.INI file)
ΓòÉΓòÉΓòÉ 7.3.4.3. Tuning Parameters ΓòÉΓòÉΓòÉ
The following list contains the tuning parameters in the Server section of the
IBMLAN.INI file:
o alertsched
This parameter sets the interval, in minutes, at which the server checks for
alert conditions and sends any needed alert messages. Because checking for
alert conditions uses memory and computing power, reduce the number only if
you need more frequent checking for alert conditions.
Default value: 5
Minimum value: 0
Maximum value: 65535
o numbigbuf
386 HPFS Users
Refer to Server Section - Advanced Package Function for the numbigbuf
parameter description. The following description applies only to Entry
servers or Peer.
This parameter specifies the number of 64KB buffers the server uses for moving
large files or large amounts of data. These buffers are used while loading
programs and copying files from the server to the requester. Increase the
value of this parameter if the server moves large files slowly. Because each
big buffer takes up 64KB, do not allocate more big buffers than the server can
support.
Ideally, you should have two big buffers for each simultaneous heavy-load
user. For example, if you have ten users and three of them are copying large
files at the same time, you should have six big buffers.
The numbigbuf parameter is related to digit positions 13, 17, and 18 of the
srvheuristics parameter. The server is initialized with three big buffers.
Digit position 13 specifies how many of the big buffers can be used for
read-ahead. Additional big buffers are dynamically allocated as needed, up to
the limit specified by the numbigbuf parameter. Digit position 17 of the
srvheuristics parameter specifies the amount of time that dynamically
allocated big buffers stay in memory. Digit position 18 of the srvheuristics
parameter determines the amount of time that the server waits after failing to
allocate additional big buffers before trying again. Dynamic allocation of
additional big buffers (greater than numbigbuf) can only occur for write
requests to the server, not for read requests.
Default value: 4 (Peer); 6 (Entry); 12 (Advanced)
Minimum value: 0
Maximum value: 80
o numfiletasks
This parameter specifies the number of concurrent processes that handle file
and print requests from requesters. The file tasks (processes) are
multithreaded, which allows multiple read/write requests to be processed
concurrently.
There is a maximum of 48 threads per file task, which is usually sufficient.
However, additional file tasks could be needed if about 45 requesters attempt
to simultaneously access the same range of a file. The server logs a message
in the error log if it exhausts its threads for a process. Specify the value
of this parameter as 1, unless a message is logged in the error log
indicating that the server exhausted its threads for a process.
Default value: 1
Minimum value: 1
Maximum value: 8
o numreqbuf
This parameter specifies the number of buffers (with a size determined by
sizreqbuf) the server uses to take requests from requesters. This parameter
should be one of the first parameters checked if there is a performance
problem in the LAN Server environment.
Determine the number of concurrent requesters served by the server. The
server should have enough request buffers available to handle a peak
requester workload. You should allocate two request buffers for each
requester connected to the server, with two additional buffers for each named
pipe being used. Allocating more than two buffers per requester will probably
not increase performance and will take up memory on the workstation.
Default value: 10 (Peer); 48 (Entry); 250 (Advanced)
Minimum value: 5
Maximum value: 2000
o sizreqbuf
This parameter sets the size, in bytes, of the buffers the server uses to
take requests from requesters. The value set for this parameter should be
the same for every server on the network. The value of the sizworkbuf
parameter on each requester should be set to the same value as the sizreqbuf
parameter on the server.
Default: 4096
Minimum value: 1024
Maximum value: 32768
o srvanndelta
This parameter specifies the time, in milliseconds, the server uses to vary
its announce rate. Varying the announce rate distributes network traffic.
Default value: 3000
Minimum value: 0
Maximum value: 65535
o srvannounce
This parameter specifies the rate, in seconds, at which the server announces
its presence on the network.
Default value: 180
Minimum value: 0
Maximum value: 65535
o srvhidden
This parameter specifies whether the server announces its presence on the
network. When the srvhidden value is set to YES, it overrides srvheuristic
20.
Default value: NO
o srvheuristics
This parameter sets a variety of server fine-tuning options. Each digit of
the srvheuristics parameter has an independent meaning. Except where noted,
each digit of the srvheuristics parameter is a binary digit: 0 means off
(inactive); 1 means on (active). Other values are defined following the
description of each digit.
386 HPFS Users
If 386-HPFS servers access only 386-HPFS disks, refer to the srvheuristics
parameter description in topic Tuning Parameters. The following
description applies only to Entry servers and to 386-HPFS servers that
access FAT file-system disks.
1 2
Digit position: 012345678901234567890
Default value: 111101411113110013311
The meanings of the digits of the srvheuristics parameter are as follows:
Position Meaning
0 Specifies opportunistic locking when opening files. Opportunistic
locking allows the server to assume that the first requester of the
file is the only active process using that file. The server
buffers reads and writes of the file while preventing a second
requester from accessing the file until the buffered data is
flushed and the file is closed. The buffering can occur even if the
user opened the file in deny-none sharing mode. The default is 1.
For opportunistic locking to occur, both digit position 0 of the
srvheuristics parameter on the server and digit position 0 of the
wrkheuristics parameter on the requester must be active. See digit
position 0 of the wrkheuristics parameter in topic Tuning
Parameters and digit position 15 of the srvheuristics parameter in
topic Tuning Parameters for more information.
1 Specifies read-ahead when the requester is performing sequential
access. Read-ahead means read additional data to attempt to
determine what the requester may need. The default is 1.
Digit position 1 pertains to reading ahead to the server's buffers
(big buffers and requester buffers) from the file system and cache.
Value Meaning
0 Do not use read-ahead.
1 Use single read-ahead thread.
2 Use asynchronous read-ahead thread.
2 Specifies write-behind. Write-behind means tell the requester that
a write is completed before actually performing the write. If the
write generates an error, the error appears on a subsequent write.
Files opened for write-through do not use write-behind. The
default is 1.
Digit position 2 pertains to writing behind from the server's
buffers (big buffers and requester buffers) to the file system and
cache.
3 Specifies the use of the NetBIOS network control block (NCB)
chain-send. The default is 1.
A chain-send enables the NetBIOS protocol driver to copy large data
blocks directly from server memory to the network adapter card. An
intermediate copy to the network buffers, from which the NetBIOS
protocol driver normally copies the data to the network adapter
card, is bypassed.
In order for the Netlogon service to replicate user and group
definitions across servers in a domain, digit position 8 of the
wrkheuristics parameter (on additional servers) and digit position
3 of the srvheuristics parameter (on domain controllers) must not
be set to 0. If these digit positions are set to 0, user and group
data may not be replicated from the domain controller, resulting in
unknown user IDs and group IDs on the additional servers.
4 Checks all incoming SMBs for correct format. This is useful with
mixed versions and brands of network software on the LAN. The
default is 0.
To prevent wasted processor cycles in an OS/2 LAN Server
environment, do not change the default value.
5 Supports file control block (FCB) opens (collapses all FCB opens
for a file to a single open). This is only useful for DOS
applications on the network. The default is 1.
6 Sets the priority for the server. The possible priority values
range from 0 for the highest priority to 9 for the lowest. For
DosSet priority, see the OS/2 Technical Library, Programming Guide
Volume 1. The default is 4.
Server priority determines how often other applications can access
the processor. For example, changing the priority from 4 to 5
causes applications on the server to respond more quickly but slows
response to requests from the network.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 10. Server Priority Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PRIORITY Γöé CLASS OF PRIORITY Γöé LEVEL OF CLASS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 0 Γöé 3 (Fixed High) Γöé 31 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1 Γöé 3 Γöé 23 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 2 Γöé 3 Γöé 15 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 3 Γöé 3 Γöé 7 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 4 Γöé 3 Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 5 Γöé 2 (Regular) Γöé 31 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 6 Γöé 2 Γöé 23 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 7 Γöé 2 Γöé 15 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 8 Γöé 2 Γöé 7 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 9 Γöé 2 Γöé 0 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
7 Automatically allocates additional memory (up to maxsearches) for
directory searches if the allocated memory is not sufficient. If
DOS requesters are on the network, set this position to 1. The
default is 1.
Digit position 7 pertains to directory searches (DosFindFirst).
Memory is allocated dynamically, instead of being committed when it
is not needed.
8 Writes records to the audit log only when the scavenger wakes up on
the interval set by digit position 10. The scavenger is a
high-priority server thread that monitors the network for errors,
writes to the error log and audit log, disconnects inactive
sessions, and sends alerts (see digit position 10 of the
srvheuristics parameter).
When digit position 8 is set to 0, any write to the audit log wakes
the scavenger. Digit position 10 controls the wake-up interval of
the scavenger. The default is 1.
9 Does full buffering (as controlled by digit positions 1 and 2 of
the srvheuristics parameter) when a file is opened with deny-write
sharing mode. When digit position 9 is set to 0, deny-write access
has no buffering for any requester using this server. For more
information, see digit position 23 of the wrkheuristics parameter
in topic Tuning Parameters The default is 1.
If an application breaks while buffering deny-write opened files,
use digit position 9 to disable buffering for all requesters.
10 Sets the interval for the scavenger to wake up. The scavenger is a
thread of the server process that performs the following tasks:
- Automatic disconnection of sessions (see the autodisconnect parameter
in topic System Parameters)
- Sending administrative alerts (see the alertsched parameter in topic
Tuning Parameters)
- Writing to the audit log (see the auditing parameter in topic System
Parameters and digit position 8 of the srvheuristics parameter)
Set this entry as follows:
Value Meaning
0 5 seconds
1 10 seconds
2 15 seconds
3 20 seconds
4 25 seconds
5 30 seconds
6 35 seconds
7 40 seconds
8 45 seconds
9 50 seconds
The default is 1. Digit position 8 can cause the scavenger to wake
up at other times.
11 Allows compatibility-mode opens of certain types of files by
translating them to sharing mode opens with deny-none. This is
useful for sharing executable and other types of files.
Digit position 11 controls how strictly the server enforces
compatibility opens for read-only. In the strictest sense of
compatibility opening, if any file is opened with a sharing mode
set, or if another session has that file open in compatibility
mode, a compatibility-mode open of that file fails.
The settings of digit position 11 relax the strictness of
compatibility opens. The first level allows different DOS LAN
Services workstations to run the same programs. The second level
extends to batch files. The third level translates
compatibility-mode opens into deny-none sharing mode while
maintaining access authority (read-only, write-only, or
read-write). Not all applications support this mode of operation.
Values for digit position 11 of the srvheuristics parameter
include:
Value Meaning
0 Always use compatibility-mode opens.
1 Use deny-none sharing mode if read-only access to .EXE or .COM
files is requested. Use compatibility mode for a .BAT file or if
write access to .EXE or .COM files is requested.
2 Use deny-none sharing mode if read-only access to .EXE or .COM
files is requested. Use deny-write sharing mode if read-only
access to .BAT files is requested. Use compatibility mode if
write access to .EXE, .COM, or .BAT files is requested.
3 Use deny-none sharing mode on all compatibility-mode opens. The
default is 3.
12 Allows DOS LAN Services workstations to use a second NetBIOS
session when sending printer requests. If digit position 12 is not
set to 1, a second NetBIOS session ends any previous sessions set
up for that DOS LAN Services workstation. If these sessions are
used, ensure that there are enough NetBIOS sessions available on
the server. Setting this parameter to 1 only allows the usage of
additional sessions, it does not configure for the use of those
sessions. The default is 1.
13 Sets the number of 64KB buffers (big buffers) used for read-ahead.
Possible values are 0 to 9, where 0 means read-ahead is disabled.
If set to a value larger than the numbigbuf parameter value, this
digit position is reset to the numbigbuf parameter value minus 1.
Each 64KB buffer is divided into sixteen 4KB read-ahead buffers. If
you are processing many files with small reads simultaneously,
allocate more than one big buffer. Increasing the value of this
parameter requires additional NetBIOS commands. The value of this
digit position usually should not be set above 4 or 5. The default
is 1.
Using 64KB (big buffers) for read-ahead involves a trade-off
between large file transfers and small-record read and write
operations. Provided there are two 64KB buffers remaining in the
server for each requester doing concurrent large file transfers,
you can use the remaining 64KB buffers for read-ahead without a
penalty.
14 Converts incoming path specifications into the most basic format
that LAN Server understands. This conversion includes changing
lowercase characters to uppercase characters and changing the
slashes used in path names to backslashes (/ to \). The default is
0.
15 This digit position has two functions:
- It sets the time the server waits before transmitting an error message
indicating accessed denied due to a previous opportunistic lock (see
digit position 0 of the srvheuristics parameter in topic Tuning
Parameters). Set a longer time when the network is subject to long
delays. The default value is 0. Digit position 15 values can be set as
follows.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 11. Srvheuristics Digit Position 15 Values and Meanings Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé VALUE Γöé OPLOCK TIMEOUT Γöé NETBIOS TIMEOUT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 0 (default) Γöé 35 seconds Γöé 34 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1 Γöé 70 seconds Γöé 69 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 2 Γöé 140 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 3 Γöé 210 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 4 Γöé 280 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 5 Γöé 350 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 6 Γöé 420 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 7 Γöé 490 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 8 Γöé 560 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 9 Γöé 640 seconds Γöé No NetBIOS timeout occurs Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
If a second requester requests opening an Oplocked file, the server
notifies the first requester to flush buffers and close the file. If
the first requester does not respond within the time defined by digit
position 15, the server sends an Access denied message to the second
requester.
The server can lock a file opened in deny-none sharing mode (as long as
there are no other requests to access the file), so that buffering can
be used to enhance performance. The server provides exclusive use of
the file to the first requester, preventing the second requester from
accessing the file until buffer data is flushed (written to disk) and
the file is closed.
- The NetBIOS timeout is the length of time the server waits for an
acknowledgment response from a requester being sent a NetBIOS message.
If a response is not received prior to this timeout, the server
disconnects the session to that requester. The default value of 34
seconds may not be long enough if the requester and server are
separated by a congested bridge or slow telecommunications lines.
16 Validates the input/output controls (IOCTLs) across the network.
When digit position 16 is set to 1, the server accepts only generic
device IOCTLs (categories 01H, 05H, and 0BH). For more
information, see the OS/2 Technical Library, Programming Guide
Volume 1. The default is 1.
Note: When digit position 16 is set to 0, the server can receive
incorrect IOCTL pointers because of differences in device
drivers between vendors. This can shut down the server.
Set digit position 16 to 0 when using certain device
drivers, such as custom-built drivers.
17 Determines how long the server maintains unused, dynamic big
buffers before freeing the memory. This digit can range from 0
through 9. The default is 3 (1 minute).
Value Meaning
0 0 seconds
1 1 second
2 10 seconds
3 1 minute
4 5 minutes
5 10 minutes
6 20 minutes
7 40 minutes
8 1 hour
9 Maintain big buffers indefinitely.
18 Determines how long the server waits after failing to allocate a
big buffer before trying again. The server processes the request it
received using the request buffers if no big buffers are currently
available. This digit can range from 0 to 5. The default is 3 (1
minute).
Value Meaning
0 0 seconds
1 1 second
2 10 seconds
3 1 minute
4 5 minutes
5 10 minutes
19 Specifies RAW read and RAW write server message block (SMB)
protocols. The default is 1.
RAW read and RAW write SMB protocols transfer data across the LAN
without SMB headers. These protocols transfer large files directly
between the server memory and a work cache in the requester.
Value Meaning
0 Neither Read Block RAW nor Write Block RAW is supported.
1 Both Read Block RAW and Write Block RAW are supported.
20 Server responds to anouncement requests.
Default is 1.
Value Meaning
0 Servers ignore requests to announce themselves.
1 Servers respond to announcement requests.
ΓòÉΓòÉΓòÉ 7.3.5. Server Section - Advanced Package Function ΓòÉΓòÉΓòÉ
Some of the parameters in the Server section of the IBMLAN.INI file function
differently for the 386-HPFS server. The descriptions of the parameters that
have the same function in both the Entry and Advanced servers are located in
Server Section - Entry Server Function and Peer Function. The following section
provides the 386-HPFS descriptions of the parameters that function differently
for a 386-HPFS server. See Appendix B for IBMLAN.INI file examples.
Note: In an Advanced server configuration which now supports 100 users, some
of the capacity parameter defaults have been increased.
The following parameter descriptions assume that the Advanced package is used
on a 386-based workstation. When a 386-HPFS server accesses FAT file system
partitions, the 386-HPFS server functions like an Entry server. Defaults are
provided for Advanced servers accessing FAT file systems.
The Server section parameters that function differently on a workstation using
the 386 HPFS can be grouped into two categories: capacity parameters and
tuning parameters.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 12. The 386-HPFS-Specific Server Section Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CAPACITY PARAMETERS Γöé TUNING PARAMETERS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXCONNECTIONS MAXOPENS Γöé NUMBIGBUF Γöé
Γöé MAXLOCKS MAXSEARCHES Γöé SRVHEURISTICS Γöé
Γöé MAXUSERS Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.5.1. Capacity Parameters ΓòÉΓòÉΓòÉ
The following list contains the capacity parameters specific to the 386 HPFS in
the Server section of the Advanced server version of the IBMLAN.INI files:
o maxconnections
This parameter does not count connections to 386-HPFS server shares. There
can be up to 2048 connections to 386-HPFS server shares, in addition to the
maxconnections parameter value. For FAT file system accesses, this default is
now 300.
o maxlocks
This parameter specifies the maximum number of locks the server can have on
non-386-HPFS files. The number of locks permitted on 386-HPFS files is
bounded by the amount of heap space the 386 HPFS has available. Each
386-HPFS file lock requires at least 30 bytes of heap space.
o maxopens
The 386-HPFS servers ignore this parameter and allocate handles dynamically.
The maximum number of opens permitted on 386-HPFS files are as follows:
Opens for files 64K
Opens for finds 8192
Opens for searches 6144
Note: The first open file instance takes approximately 300 bytes from the
heap. Each additional instance of the file opened takes approximately
60 bytes. For large numbers of open files, the lack of available
physical memory may reduce the maximum number of open files.
The space for the finds and searches comes out of the same 8KB table. So, if
you have allocated 6KB for searches, and the system uses all of that 6KB, then
there will only be 2KB left for finds.
For FAT file system accesses, this default is now 256.
o maxsearches
The 386-HPFS servers ignore this parameter. The maximum number of searches on
386-HPFS files is equal to the maximum number of opens for finds plus the
maximum number of opens for searches as defined in maxopens. For FAT file
system accesses, this default is now 350.
Maximum value: 4096
o maxusers
The number of simultaneous users on a 386-HPFS server. The maxusers cannot
exceed maxconnections.
Maximum value: 101
ΓòÉΓòÉΓòÉ 7.3.5.2. Tuning Parameters ΓòÉΓòÉΓòÉ
The following list contains the 386-HPFS-specific tuning parameters in the
Server section of the IBMLAN.INI file:
o numbigbuf
This parameter specifies the number of 64KB buffers the Entry server uses for
moving large files or large amounts of data.
As long as users of the 386-HPFS server access only 386-HPFS disks, the
386-HPFS server does not use big buffers for large data transfers. However,
some big buffer space is allocated if the numbigbuf parameter is not set to
0. Therefore, if users of the 386-HPFS server only perform file I/O on
386-HPFS disks, the numbigbuf parameter can be set to 0.
Printing operations are handled through the Entry server function that is
installed with both of the LAN Server packages. Therefore, 386-HPFS print
servers with an attached printer may need a few big buffers to handle print
operations.
If the 386-HPFS server accesses any FAT file system disks, the numbigbuf
parameter should be set as described in Server Section - Entry Server
Function and Peer Function.
Default value: 12
Minimum value: 0
Maximum value: 80
o srvheuristics
The following description applies to 386-HPFS servers that access only
386-HPFS disks. If the 386-HPFS server accesses FAT file system disks, refer
to the srvheuristics parameter description in topic Tuning Parameters.
1 2
Digit position: 012345678901234567890
Default value: 111101411113110013311
This parameter sets a variety of server fine-tuning options. Each digit of
the srvheuristics parameter has an independent meaning. Except where noted,
each digit of the srvheuristics parameter is a binary digit: 0 means off
(inactive); 1 means on (active). Other values are defined following the
description of each digit. The meanings of the digits of the srvheuristics
parameter are as follows:
Position Meaning
0 Specifies opportunistic locking when opening files. Opportunistic
locking allows the server to assume that the first requester of the
file is the only active process using that file. The server
buffers the reads and writes of the file while preventing a second
requester from accessing the file until the buffered data is
flushed and the file is closed. The buffering can occur even if the
user opened the file in deny-none sharing mode. The default is 1.
For opportunistic locking to occur, both digit position 0 of the
srvheuristics parameter on the server and digit position 0 of the
wrkheuristics parameter on the requester must be active. See digit
position 0 of the wrkheuristics parameter in topic Tuning
Parameters and digit position 15 of the srvheuristics parameter in
topic Tuning Parameters for more information.
1 Does not apply to 386-HPFS servers. The default is 1.
2 Does not apply to 386-HPFS servers. The default is 1.
3 Supports the use of deny-none sharing mode on all
compatibility-mode opens. The default is 1.
4 Does not apply to 386-HPFS servers. The default is 0.
5 Supports file control block (FCB) opens (collapses all FCB opens
for a file to a single open). This is only useful for DOS
applications on the network. The default is 1.
6 Does not apply to 386-HPFS servers. The default is 4.
7 Does not apply to 386-HPFS servers. The default is 1.
8 Does not apply to 386-HPFS servers. The default is 1.
9 Does not apply to 386-HPFS servers. The default is 1.
10 Does not apply to 386-HPFS servers. The default is 1.
11 Allows compatibility-mode opens of certain types of files by
translating them to sharing mode opens with deny-none. This is
useful for sharing executable and other types of files.
Digit position 11 controls how strictly the server enforces
compatibility-mode opens for read-only. In the strictest sense of
compatibility-mode opens, if any file is opened with a sharing mode
set, or if another session has that file open in compatibility
mode, a compatibility-mode open of that file fails.
The settings of digit position 11 relax the strictness of
compatibility-mode opens. The Advanced package handles this
function differently than the Entry package. There are effectively
only two settings for this digit position. Refer to the value
meanings described below. Not all applications support this mode of
operation. The default is 3.
Values for digit position 11 of the srvheuristics parameter
include:
Values Meaning
0 Always use compatibility-mode opens.
1, 2 Workstation requests for read-only access will have their
sharing mode translated to deny-write. Any requests for
write access will be translated to compatibility mode,
thereby preventing shared usage of the file.
3 Use deny-none sharing mode on all compatibility-mode opens.
12 Allows DOS LAN Services workstations to use a second NetBIOS
session when sending printer requests. If digit position 12 is not
set to 1, a second NetBIOS session ends any previous sessions set
up for that DOS LAN Services workstation. If these sessions are
used, ensure that there are enough NetBIOS sessions available on
the server. Setting this parameter to 1 only allows the usage of
additional sessions; it does not configure for the usage of those
sessions. The default is 1.
13 Does not apply to 386-HPFS servers. The default is 1.
14 Does not apply to 386-HPFS servers. The default is 0.
15 This digit position has two functions:
- It sets the time the server waits before transmitting an error message
indicating access denied due to a previous opportunistic lock (see
digit position 0 of the srvheuristics parameter in topic Tuning
Parameters). When the network is subject to long delays, set a longer
time. The default value is 0. Digit position 15 values can be set as
follows.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 13. 386 HPFS Server Srvheuristics Digit Position 15 Values and Γöé
Γöé Meanings Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé VALUE Γöé OPLOCK TIMEOUT Γöé NETBIOS TIMEOUT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 0 Γöé 35 seconds Γöé 34 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1 Γöé 70 seconds Γöé 69 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 2 Γöé 140 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 3 Γöé 210 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 4 Γöé 280 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 5 Γöé 350 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 6 Γöé 420 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 7 Γöé 490 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 8 Γöé 560 seconds Γöé 127 seconds Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 9 Γöé 640 seconds Γöé No NetBIOS timeout occurs Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
If a second requester requests opening an Oplocked file, the server
notifies the first requester to flush buffers and close the file. If
the first requester does not respond within the time specified, the
server sends an Access denied message to the second requester.
The server can lock a file opened in deny-none sharing mode (as long as
there are no other requests to access the file), so that buffering can
be used to enhance performance. The server provides exclusive use of
the file to the first requester, preventing the second requester from
accessing the file until buffer data is flushed (written to disk) and
the file is closed.
- The NetBIOS timeout is the length of time the server waits for an
acknowledgment response from a requester being sent a NetBIOS message.
If a response is not received prior to this timeout, the server
disconnects the session to that requester. The default value of 34
seconds may not be long enough if the requester and server are
separated by a congested bridge or slow telecommunications lines.
16 Does not apply to 386-HPFS servers. The default is 1.
17 Does not apply to 386-HPFS servers. The default is 3.
18 Does not apply to 386-HPFS servers. The default is 3.
19 Specifies RAW read and RAW write server message block (SMB)
protocols. The default is 1.
RAW read and RAW write SMB protocols transfer data across the LAN
without SMB headers. These protocols transfer large files directly
between the server memory and a work cache in the requester.
Digit Meaning
0 Neither Read Block RAW nor Write Block RAW is supported.
1 Both Read Block RAW and Write Block RAW are supported.
20 Server responds to announcement requests. The default is 1.
Digit Meaning
0 Servers ignore requests to announce themselves.
1 Servers respond to announcement requests.
ΓòÉΓòÉΓòÉ 7.3.6. Alerter Section ΓòÉΓòÉΓòÉ
The Alerter section of the IBMLAN.INI file contains the following capacity
parameter:
o sizalertbuf
This parameter sets the size, in bytes, of the buffer used for administrative
alerts.
Default value: 3072
Minimum value: 512
Maximum value: 16384
ΓòÉΓòÉΓòÉ 7.3.7. Netrun Section ΓòÉΓòÉΓòÉ
The Netrun section controls the service that allows other workstations to run a
program in this server's memory. The parameters contained in the Netrun section
can be grouped into two categories: system parameters and capacity parameters.
Netrun Section Parameters lists the parameters contained in the Netrun section
of the IBMLAN.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 14. Netrun Section Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM PARAMETER Γöé CAPACITY PARAMETER Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RUNPATH Γöé MAXRUNS Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.7.1. System Parameters ΓòÉΓòÉΓòÉ
The following is the system parameter in the Netrun section of the IBMLAN.INI
file:
o runpath
This parameter sets the server path in which Netrun requests can operate. To
run a program remotely on this server, the .EXE program file must exist in
the path defined by the runpath parameter. Only programs in this run path
can be run remotely. Path syntax is the same as for the OS/2 PATH command.
Default value: C:\ (root directory)
ΓòÉΓòÉΓòÉ 7.3.7.2. Capacity Parameter ΓòÉΓòÉΓòÉ
The following is the capacity parameter in the Netrun section of the IBMLAN.INI
file:
o maxruns
This parameter specifies the maximum number of netrun requests that can run
simultaneously in the server's memory. This parameter value affects the
numreqbuf parameter in the Server section. The numreqbuf parameter value must
be at least five times greater than the maxruns parameter value.
Default value: 3
Minimum value: 1
Maximum value: 10
ΓòÉΓòÉΓòÉ 7.3.8. Replicator Section ΓòÉΓòÉΓòÉ
The Replicator service lets you maintain identical sets of files and
directories on different workstations. Servers can replicate data to other
servers or requesters. The server sending the data is called an exporter. The
requester or server receiving the data is called an importer. You can have any
number of exporters and importers in your domain; however, two exporters should
not replicate the same set of files. A server can be both an exporter and an
importer, while a requester can only be an importer. For more information
concerning the Replicator service, refer to the LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
In the IBMLAN.INI Replicator section, you set up an export path on the exporter
and an import path on each importer. The Replicator service monitors the
export directory. When you add, delete, or change a directory or file in the
export path, the Replicator service sends an update notice to its importers.
The importer then obtains a copy of the changed files and directories.
Therefore, each import path is an up-to-date copy of the export path.
Each parameter listed in the Replicator section must have a corresponding
value, except the password parameter. Importer and Exporter Parameters shows
which parameters apply to importers and which to exporters.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 15. Importer and Exporter Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IMPORTER PARAMETERS Γöé EXPORTER PARAMETERS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé REPLICATE Γöé REPLICATE Γöé
Γöé IMPORTLIST Γöé EXPORTLIST Γöé
Γöé IMPORTPATH Γöé EXPORTPATH Γöé
Γöé LOGON Γöé GUARDTIME Γöé
Γöé PASSWORD Γöé INTERVAL Γöé
Γöé TRYUSER Γöé PULSE Γöé
Γöé Γöé RANDOM Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
The parameters contained in the Replicator section can be grouped into two
categories: system parameters and tuning parameters. Replicator Section
Parameters lists the parameters contained in the Replicator section of the
IBMLAN.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 16. Replicator Section Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM PARAMETERS Γöé TUNING PARAMETERS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé REPLICATE IMPORTPATH Γöé GUARDTIME Γöé
Γöé EXPORTLIST LOGON Γöé INTERVAL Γöé
Γöé EXPORTPATH PASSWORD Γöé PULSE Γöé
Γöé IMPORTLIST TRYUSER Γöé RANDOM Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.8.1. System Parameters ΓòÉΓòÉΓòÉ
The following list contains the system parameters in the Replicator section of
the IBMLAN.INI file:
o replicate
This parameter specifies whether the workstation is an importer, an exporter,
or both. Values are: Import, Export, and Both. If a server is an exporter,
this value must be either Export or Both. If a server is an importer, this
value must be either Import or Both. On requesters, only Import is valid.
Default value: Import
o exportlist
This parameter lists workstations and domains to receive announcements of
changes to the export directory. Each name is separated by a semicolon and
no spaces. For example:
exportlist = server1;server2; domain3
This parameter is not included in your default IBMLAN.INI file. You can add
it anywhere in the Replicator section.
- When no exportlist parameter is specified, update notices are sent to
importers in this exporter's domain.
- If a list is specified for this parameter, update notices are sent to each
workstation and domain on the list.
- If you include a domain name, the exporter sends updates to workstations
in that domain. In order to be able to receive the updates, those
workstations must be set up as importers and specify the exporter or
exporter's domain.
o exportpath
This parameter specifies the absolute path to the export directories. All
files to be replicated must be in this path.
This parameter is not included in your default IBMLAN.INI file. When this
parameter is missing, the default takes effect. You can add the parameter
anywhere in the Replicator section. The default path is created at
installation.
There is no restriction on the path name or location. If it does not already
exist, you must create the path and set up specific subdirectories in the
export path.
Default value: C:\IBMLAN\REPL\EXPORT
Note: When setting up a single server as both an exporter and an importer,
use different export and import paths and ensure that neither path is
a subdirectory of the other. Otherwise, files replicated to other
importers cannot be distinguished from files replicated from other
exporters.
o importlist
This parameter lists servers and domains that can send a directory to this
importer. Each name is separated by a semicolon and no spaces; for example:
importlist = server1;server2;domain3
This parameter is not included in your default IBMLAN.INI file. You can add
it anywhere in the Replicator section.
- When no importlist parameter is specified, the Replicator service checks
for updates from all servers set up as exporters in the importer's domain.
- If a list is specified for this parameter, update notices from any
specified exporters and domains are sent to the importer.
- If you include a domain name, the importer receives updates from servers
in that domain that are set up as exporters for the importer or the
importer's domain.
o importpath
This parameter specifies the absolute path to the import directories. All
files are replicated to a subdirectory of this path. This can also be a
remote path.
There is no restriction on the path name or location. If it does not already
exist, you must create the path and set up specific subdirectories in the
import path. The default path is created at installation.
Default value: C:\IBMLAN\REPL\IMPORT
Note: When setting up a single server as both an exporter and an importer,
use different export and import paths and ensure that neither path is
a subdirectory of the other. Otherwise, files replicated to other
importers cannot be distinguished from those replicated from other
exporters.
o logon
This parameter specifies the user ID that the Replicator service uses to
connect to the exporter when no one is logged on at the importer. This user
ID is used with the password specified by the password parameter. If the
logon parameter (the default) is not included, the Replicator service tries
logging on using the machine ID of the importer as a user ID.
Ensure the user ID (or machine ID if the logon parameter is not included) is
set up as a user through User Profile Management and has read and attributes
permissions to the replicated directories through LAN Server (using either
the full-screen interface or the NET ACCESS command).
This parameter is not included in your default IBMLAN.INI file. You can add
it anywhere in the Replicator section.
o password
This parameter specifies the password that the Replicator service uses to
connect to the exporter when no one is logged on to the importer. This
password is used with the user ID specified by the logon parameter. The
password parameter cannot be used unless the logon parameter is also
specified. If the default setup for the logon parameter is used (that is,
the logon parameter is not included and the Replicator service tries logging
on with the machine ID), then a password cannot be specified. If a password
is desired for the workstation, both the logon and password parameters must
be used.
o tryuser
This parameter specifies whether the importer automatically tries to connect
to the exporter when a user is logged on to the workstation.
If the tryuser parameter value is Yes, the importer tries connecting to the
exporter using the user ID and password of the user logged on at the
importer. The connection succeeds if the user has read and attributes
permissions to the directories to be replicated. If the connection attempt
fails, the importer cannot connect to the exporter until the user logs off.
If the tryuser parameter value is No, the importer does not connect to the
exporter until the user logs off.
Default value: Yes
ΓòÉΓòÉΓòÉ 7.3.8.2. Tuning Parameters ΓòÉΓòÉΓòÉ
The following list contains the tuning parameters in the Replicator section of
the IBMLAN.INI file:
o guardtime
This parameter specifies how long, in minutes, the export path must be stable
before importers can connect to it. The guardtime parameter prevents
importers from connecting to an export path while you are still changing it.
For example, if the guardtime parameter value is set to 10, importers cannot
copy new material from the exporter until at least 10 minutes after you
finish changing an export path.
This parameter is valid only if the integrity parameter in the REPL.INI file
is set to Tree. For more information concerning the REPL.INI file, refer to
the LAN Server Network Administrator Reference Volume 3: Network
Administrator Tasks.
Default value: 2
Minimum value: 0
Maximum value: interval / 2
o interval
This parameter specifies how often, in minutes, subdirectories and files in
the export path are checked for changes.
Default value: 5
Minimum value: 1
Maximum value: 60
o pulse
This parameter specifies how often the exporter sends extra updates to
importers, besides those sent when a change to the export path occurs. These
pulse updates are identical to the most recent change update and ensure that
files and subdirectories in import paths match those in the export path.
To reduce the number of broadcast frames, increase the value of pulse. The
risk of changing pulse is that it controls when new users and password
changes are replicated from the domain controller to additional servers.
This parameter value is multiplied by the interval parameter value to
determine how often updates are sent to importers. For example, if the
interval value is 5 and the pulse value is 3, redundant pulse updates are
sent every 15 minutes.
Default value: 3
Minimum value: 1
Maximum value: 10
o random
This parameter specifies the interval, in seconds, over which to distribute
importer connections. The exporter sends this value to importers, which wait
an interval of seconds between 0 and this value before connecting.
The random parameter controls network traffic of importers connecting to the
exporter. If an exporter replicates files to several importers, network
performance could be degraded if all importers try connecting to the exporter
at once. You can avoid this problem by requiring the importers to wait a
random amount of time before connecting.
For example, suppose you specify a random parameter value of 90. This value
tells each importer to randomly select a number between 0 and 90 and wait
that many seconds before connecting to the exporter.
Default value: 60
Minimum value: 1
Maximum value: 120
ΓòÉΓòÉΓòÉ 7.3.9. Netlogon Section ΓòÉΓòÉΓòÉ
The Netlogon service copies the master user and group definitions file
(NET.ACC) on the domain controller to servers. Netlogon is available only on
servers.
Passwords can become unsynchronized when using the Netlogon service if you:
o Reinstall a default or backup NET.ACC file onto an additional server
o Reinstall a default or backup NET.ACC file onto the domain controller
o Inadvertently change an additional server's password on the domain controller
without the new password being replicated to the additional server prior to
the next time Netlogon uses it
Resynchronizing the password for the additional server:
1. Ensure that the additional server on the domain controller is listed in the
GUI as a server.
2. On the domain controller, type NET USER servername newpassword and press
Enter.
3. Stop the Netlogon service on the additional server and then perform the
following steps:
a. Type NET ACCOUNTS /ROLE:STANDALONE and press Enter.
b. Ensure that the additional server has a user ID and is a member of the
SERVERS group.
c. On the additional server type NET USER servername newpassword and press
Enter.
Note: Use the same password for the additional server as you entered
for the server on the domain controller in step 2.
d. Type NET ACCOUNTS /ROLE:MEMBER and press Enter.
4. Restart the Netlogon service.
The parameters contained in the Netlogon section can be grouped into two
categories: system parameters and tuning parameters. Netlogon Section
Parameters lists the parameters contained in the Netlogon section of the
IBMLAN.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 17. Netlogon Section Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM PARAMETERS Γöé TUNING PARAMETERS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SCRIPTS Γöé PULSE SCANPERIOD Γöé
Γöé UPDATE Γöé RANDOMIZE SCANTIME Γöé
Γöé Γöé SCANPAUSE Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.9.1. System Parameters ΓòÉΓòÉΓòÉ
The following list contains the system parameters in the Netlogon section of
the IBMLAN.INI file:
o scripts
This parameter specifies the path where the Netlogon service searches for the
logon scripts. This parameter applies only to primary and backup domain
controllers and must be present with a valid path name. The path name can be
absolute or relative to the IBMLAN subdirectory.
Default value: C:\IBMLAN\REPL\IMPORT\SCRIPTS
o update
This parameter specifies whether to synchronize the Netlogon service with the
primary domain controller at the next pulse. This parameter applies only to
member and backup servers.
Default value: Yes
ΓòÉΓòÉΓòÉ 7.3.9.2. Tuning Parameters ΓòÉΓòÉΓòÉ
The following list contains the tuning parameters in the Netlogon section of
the IBMLAN.INI file:
o pulse
This parameter specifies the time interval, in seconds, between update
notices. This parameter is valid only if the server's role is primary (domain
controller). The server's role is set at installation or with the NET
ACCOUNTS command.
Default value: 60
Minimum value: 60
Maximum value: 3600
o randomize
This parameter specifies the time period, in seconds, during which the member
or backup servers should send a request at random to get changes after
receiving a change notice. This prevents overloading the primary domain
controller with multiple update requests. This parameter applies only to
primary domain controllers.
This parameter is not included in your default IBMLAN.INI file. You can add
it anywhere in the Netlogon section.
Default value: 30
Minimum value: 5
Maximum value: 120
o scanpause
This parameter specifies the amount of time, in seconds, that the domain
controller waits before polling each user. This parameter can be used to
slow down the pace of polling each user, thereby limiting the amount of
datagram traffic on the network at any one time. Refer to the scantime
parameter for more information about the domain controller polling.
Default value: 0
Minimum value: 0
Maximum value: 15
o scanperiod
This parameter specifies the time interval, in minutes, at which the domain
controller polls all the users. The minimum value is 0 at which the domain
controller does not poll users. This feature of polling users is not very
often needed and is even less necessary now that NET WHO checks the session
list. The scanperiod value is set to 5 automatically if the domain controller
poll response is 1 through 4. If this parameter is set to 1440, the domain
controller polls the users at the time specified by the scantime parameter.
Refer to the scantime parameter for more information about the domain
controller polling.
Default value: 15
Minimum value: 0 (the domain controller does not poll the users)
Maximum value: 1440 (24 hours)
o scantime
This parameter specifies the time at which polling occurs each day if the
scanperiod parameter is set to 1440.
The Netlogon service on the domain controller uses a polling technique to
determine whether users are still logged on to the domain. The polling
ensures that the output of the NET WHO command is as accurate as possible.
In a domain with many users logged on, the polling causes a large amount of
datagram traffic on the network. The scantime, scanperiod, and scanpause
parameters enable you to control how often the polling occurs.
Default value: 0:00 (midnight)
Minimum value: 0:00
Maximum value: 23:59
ΓòÉΓòÉΓòÉ 7.3.10. UPS Section ΓòÉΓòÉΓòÉ
The UPS section of the IBMLAN.INI file defines the Uninterruptible Power Supply
support. The UPS section cannot be the last section listed in the IBMLAN.INI
file. The parameters contained in the UPS section can be grouped into two
categories: system parameters and tuning parameters. UPS Section Parameters
lists the parameters contained in the UPS section of the IBMLAN.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 18. UPS Section Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM PARAMETERS Γöé TUNING PARAMETERS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CMDFILE Γöé BATTERYMSG Γöé
Γöé DEVICENAME Γöé BATTERYTIME Γöé
Γöé LOWBATTERY Γöé CMDTIMER Γöé
Γöé SIGNALS Γöé MESSDELAY Γöé
Γöé VOLTLEVELS Γöé MESSTIME Γöé
Γöé Γöé RECHARGE Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.10.1. System Parameters ΓòÉΓòÉΓòÉ
The following list contains the system parameters in the UPS section of the
IBMLAN.INI file.
o cmdfile
This parameter specifies the command file to run before the network services
are shut down. If the complete path name is not specified, the command file
is assumed to be in the \IBMLAN subdirectory.
Default value: "" (no command file should be run)
o devicename
This parameter specifies the name of the device to open. UPS_DEV must be a
valid OS/2 device name.
Default value: UPS_DEV
o lowbattery
This parameter specifies the action taken when the UPS signals that the
battery is low, but AC power is present. Possible values are:
Value Meaning
Warning The UPS service generates a warning to alert recipients on the
interval defined by the batterymsg parameter. The warning
informs the user that the UPS battery is low at the specified
server.
Shutdown The server is shut down when the UPS signals that the battery is
low.
Disable The UPS service ignores the signal from the UPS. This value
enables the user to discontinue the low battery alerts without
stopping the UPS service.
Default value: Warning
o signals
This parameter specifies which signals are available from the UPS. The value
of this parameter is a 3-digit number, where each digit indicates whether a
specific signal is available. A value of 0 for a digit indicates that the
signal is not available. A value of 1 for a digit indicates that the UPS can
generate the signal.
Value Signal
1 The UPS can signal when a power failure is detected.
2 The UPS can signal when there are 2 minutes or more until shutdown
due to a low battery. If the low-battery signal on the UPS occurs
when less than 2 minutes are remaining, this digit should be set to
0.
3 The UPS can accept a signal from the workstation that tells the UPS
to shut down.
Note: The UPS must support a signal either when a power failure is detected
or when the battery will run down in 2 or more minutes. If the first
2 digits of the signals parameter are set to 0, the UPS service will
not function.
Default value: 100
o voltlevels
This parameter specifies the voltage levels for the signals defined by the
signals parameter. The value of the voltlevels parameter is a 3-digit
number, where each digit indicates the voltage level for a specific signal.
A value of 0 for a digit indicates that a negative voltage is used to report
the associated signal. A value of 1 for a digit indicates that a positive
voltage is used to report the associated signal. For more information about
each specific signal, refer to the description of the signals parameter.
Default value: 100
ΓòÉΓòÉΓòÉ 7.3.10.2. Tuning Parameters ΓòÉΓòÉΓòÉ
The following list contains the tuning parameters in the UPS section of the
IBMLAN.INI file:
o batterymsg
This parameter specifies the number of seconds that the workstation waits
between low battery alerts. The value of this parameter is used only if a low
battery signal is received and the AC power is good.
Default value: 600 (10 minutes)
Minimum value: 30 (30 seconds)
Maximum value: 3600 (1 hour)
o batterytime
This parameter specifies the number of seconds that the workstation can run
on battery power before the UPS service initiates shutdown. The value of this
parameter is used only if the low battery signal is not available. Because
shutdown should take about 2 minutes, if the battery time is less than or
equal to two minutes, the value of this parameter should be set to 0.
Default value: 60
Minimum value: 0
Maximum value: 28800
o cmdtimer
This parameter specifies the number of seconds that the UPS service will give
the .CMD file to complete. The range is 0 to 600 seconds. The default is
30. If the .CMD file does not finish execution within the specified number
of seconds, an error is logged.
Default value: 30
Minimum value: 0
Maximum value: 600
o messdelay
This parameter specifies the number of seconds between the initial power
failure and the first message sent to the users. If power is restored within
the time specified by this parameter, no messages are sent to the users, but
the event is logged.
Default value: 5
Minimum value: 0
Maximum value: 120
o messtime
This parameter specifies the number of seconds between messages sent to the
users. The messages inform the users of the power failure.
Default value: 120
Minimum value: 30
Maximum value: 300
o recharge
This parameter specifies the number of minutes of recharge time required by
the UPS to gain 1 minute of battery run time.
Default value: 100
Minimum value: 5
Maximum value: 250
ΓòÉΓòÉΓòÉ 7.3.11. Remoteboot Section ΓòÉΓòÉΓòÉ
The Remoteboot section of the IBMLAN.INI file defines the Remote IPL service.
The parameters contained in the Remoteboot section can be grouped into two
categories: system parameters and tuning parameters. Remoteboot Section
Parameters lists the parameters contained in the Remoteboot section of the
IBMLAN.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 19. Remoteboot Section Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM PARAMETERS Γöé TUNING PARAMETER Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RPLn RPLDIR CONFIGFILE Γöé MAXTHREADS Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.11.1. System Parameters ΓòÉΓòÉΓòÉ
The following list contains the system parameters in the Remoteboot section of
the IBMLAN.INI file:
o rpln = dll1 dll2 dll3 adapternum
This parameter specifies the dynamic link libraries (DLLs) used to support
various network adapter cards. There is an rpln statement for each network
adapter card that the Remote IPL service uses. Each rpln statement provides
the names of the three DLLs to use for the associated network adapter card
and the number of the adapter card. The file names specified must be in the
user's LIBPATH statement in the CONFIG.SYS file.
The n variable is a sequence number used to distinguish each rpln statement.
The n variable can be from 1 to 4.
The adapternum variable specifies the number of the associated network
adapter card. This variable is optional and defaults to 0 if it is not
specified. The network adapter driver associated with the network adapter
card specified by this variable must be bound to the IBM IEEE 802.2 protocol
driver, or the Remote IPL service will fail.
Default value: RPLNET1.DLL RPLNET2.DLL RPLOEM.DLL
o rpldir
This parameter specifies the directory containing the remote IPL files. The
directory specified must contain the RPL.MAP file. If a full path name is not
specified, the path is assumed to be a subdirectory of the \IBMLAN
subdirectory.
Default value: C:\IBMLAN\RPL
o configfile
This parameter specifies the name of the DOS boot block configuration file.
If a full path name is not specified, the file is assumed to be in the RPLDIR
directory.
Default value: DOSBBTR.CNF
ΓòÉΓòÉΓòÉ 7.3.11.2. Tuning Parameter ΓòÉΓòÉΓòÉ
The following is the tuning parameter in the Remoteboot section of the
IBMLAN.INI file.
o maxthreads
This parameter specifies the number of threads that the Remote IPL service
starts in order to perform asynchronous reading of the configuration files.
Default value: 10
Minimum value: 0 (no asynchronous I/O)
Maximum value: Maximum number of threads permitted by the system.
ΓòÉΓòÉΓòÉ 7.3.12. hdref=lssrv.LSserver Section ΓòÉΓòÉΓòÉ
The LSserver service provides logical server support, which includes sharing
startup aliases, sharing the IBMLAN tree, and starting DOS LAN Services
support. The parameters contained in the LSserver section can be grouped into
two categories: system parameters and tuning parameters. LSserver Section
Parameters lists the parameters contained in the LSserver section of the
IBMLAN.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 20. LSserver Section Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM PARAMETER Γöé TUNING PARAMETER Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CLEANUP Γöé SRVPIPES Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.12.1. System Parameter ΓòÉΓòÉΓòÉ
The following is the system parameter in the LSserver section of the IBMLAN.INI
file:
o cleanup
This parameter specifies whether to clean up (disconnect) shares for dynamic
aliases. A dynamic alias is any alias that is shared with the As required by
user option in the interface. Typing NET USE x aliasname at a requester DOS
or OS/2 command prompt also creates a share for a dynamic alias. x is a local
device name and aliasname is the alias name for the shared resource.
If the autodisconnect parameter value is set to -1, the cleanup parameter
defaults to yes. The active cleanup parameter disconnects shares for dynamic
aliases that no longer have users. When the autodisconnect parameter is set
to -1, idle sessions are never ended by the server; therefore, if the cleanup
parameter is set to N, the number of shares outstanding for dynamic aliases
at the server may increase to a point where the value of the maxshares
parameter would need to be increased.
Setting the autodisconnect parameter to 0 is not advisable, as it leads to
numerous error messages.
For Configuration, Installlation, and Distribution (CID) users, CID
installation will always set cleanup to Yes if the autodisconnect parameter
is set to -1 regardless of what the user specifies. This prevents the
buildup of shares for aliases that are no longer being used.
If the autodisconnect parameter is not set to -1, you can set the cleanup
parameter to suit your requirements. If the autodisconnect parameter is not
-1 and the cleanup parameter is set to Y, cleanup of a dynamic alias share
will occur when there are no users using the alias. The server will also end
an idle session and the dynamic aliases shared for that session when the
autodisconnect timeout occurs (unless an alias is being used in another
session). If the cleanup parameter is set to N, you can remove dynamic alias
shares manually. Restarting the server also removes dynamic alias shares.
If the server is started and stopped frequently, users must disconnect and
reconnect to dynamic aliases. To avoid this extra activity, use the At
server startup option in the GUI to share critical alias resources. For
information about using the GUI to share aliases, see LAN Server Network
Administrator Reference Volume 3: Network Administrator Tasks.
Default value: Y
ΓòÉΓòÉΓòÉ 7.3.12.2. Tuning Parameter ΓòÉΓòÉΓòÉ
The following is the tuning parameter in the LSserver section of the IBMLAN.INI
file:
o srvpipes
This parameter sets the maximum number of pipes that the server uses. If
many users log on simultaneously, increase the value of this parameter. The
following equation can be used to calculate a value for the srvpipes
parameter. Do not use the calculated value if it is less than the default
value.
srvpipes = maxusers / 12 (up to the maximum value)
Default value: 3
Minimum value: 1
Maximum value: 20
ΓòÉΓòÉΓòÉ 7.3.13. Services Section ΓòÉΓòÉΓòÉ
The Services section lists the path to each LAN Server network service. Any
path used in this section that does not start with a drive or backslash (\) is
assumed to be relative to the IBMLAN directory.
Note: Do not edit the default values in the Services section.
ΓòÉΓòÉΓòÉ 7.3.13.1. System Parameters ΓòÉΓòÉΓòÉ
The following list contains the system parameters in the Services section of
the IBMLAN.INI file:
o alerter
This parameter specifies the path and file name of the program that sends
administrative alert messages. This parameter is valid only for servers.
Default value: SERVICES\ALERTER.EXE
o DCDBREPL
Stops the Domain Control Database (DCDB) Replicator service, which copies the
DCDB on the domain controller to designated backup servers. This parameter is
valid only for servers.
o genalert
This parameter specifies the path and file name of the Generic Alerter
service.
Default value: SERVICES\GENALERT.EXE
o lsserver
This parameter specifies the path and file name of the LSserver service.
Default value: SERVICES\LSSERVER.EXE
o messenger
This parameter specifies the path and file name of the message program. The
Messenger service allows your workstation to receive the messages sent across
the network by other users and servers.
Default value: SERVICES\MSRVINIT.EXE
o netlogon
This parameter specifies the path and file name of the Netlogon program. The
Netlogon service copies the master user-and-group definition file located on
the domain controller to network servers. This parameter is valid only for
servers.
Default value: SERVICES\NETLOGON.EXE
o netrun
This parameter specifies the path and file name of the NET RUN utility. The
Netrun service allows users at other workstations to run programs in this
server's memory. This parameter is valid only for servers.
Default value: SERVICES\RUNSERVR.EXE
o peer
This parameter specifies the path and file name of the peer server
initialization program. The Peer service allows a requester to share
resources with one user at a time.
Default value: SERVICES\NETPSINI.EXE
o remoteboot
This parameter specifies the path and file name of the DOS and OS/2 remote
IPL programs. The Remote IPL service allows DOS and OS/2 requesters to be
started by a server. This parameter is valid only for servers.
Default value: SERVICES\RPLSERVR.EXE
o replicator
This parameter specifies the path and file name of the replication program.
The Replicator service copies files from a master location to one or more
workstations requiring a copy of the data.
Default value: SERVICES\REPLICAT.EXE
o requester
This parameter specifies the path and file name of the requester
initialization program. The Requester service connects your workstation to
the network server as a requester, allowing access to shared network
resources.
Default value: SERVICES\WKSTA.EXE
o server
This parameter specifies the path and file name of the server initialization
program. The Server service allows the workstation to share its resources
with users on the network. This parameter is valid only for servers.
Default value: SERVICES\NETSVINI.EXE
o timesource
This parameter specifies the path and file name of the Timesource service.
Default value: SERVICES\TIMESRC.EXE
o ups
This parameter specifies the path and file name of the Uninterruptible Power
Supply initialization program. The UPS service provides protection against
loss of data during power failures. Upon power interruption, users with
active sessions to the affected server are notified of the impending
shutdown, and an orderly server shutdown is performed.
Default value: SERVICES\UPS.EXE
ΓòÉΓòÉΓòÉ 7.3.14. DCDB Replicator Section ΓòÉΓòÉΓòÉ
The DCDB Replicator service propagates domain control database (DCDB) updates
from the domain controller to other servers in the domain that are running with
ROLE=BACKUP. To change a server's role, see the LAN Server Network
Administrator Reference Volume 1: Planning, Installation, and Configuration.
The domain control database is a database that resides on the domain controller
and contains files that describe the domain's users, its resources, and the
users' access to those resources. This service runs on the domain controller,
and exports the \DCDB directory to the servers. Corresponding DCDB Replicator
services run on each server that receives the updated DCDB files. The domain
controller is the only machine in the domain that is an exporter, while all
other servers running the service are importers. The exportation is thus
confined within the domain.
Running the DCDB Replicator service does not conflict with running the
Replicator service in the same workstation.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 21. DCDB Replicator Section Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM PARAMETERS Γöé TUNING PARAMETERS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LOGON Γöé GUARDTIME PULSE Γöé
Γöé PASSWORD Γöé INTERVAL RANDOM Γöé
Γöé TRYUSER Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 7.3.14.1. System Parameters ΓòÉΓòÉΓòÉ
The following list contains the system parameters in the DCDB Replicator
section of the IBMLAN.INI file:
o logon
This parameter specifies the user ID that the DCDB Replicator service uses to
connect to the domain controller when no one is logged on at the server.
This user ID is used with the password specified by the password parameter.
If the logon parameter (the default) is not included, the DCDB Replicator
service tries logging on using the machine ID of the server as a user ID.
Ensure that the user ID (or machine ID if the logon parameter is not
included) is set up as a user through User Profile Management and has read
and attributes permissions to the DCDB through LAN Server (using either the
GUI or the NET ACCESS command).
This parameter is not included in your default IBMLAN.INI file. You can add
it anywhere in the DCDB Replicator section.
o password
This parameter specifies the password that the DCDB Replicator service uses
to connect to the domain controller when no one is logged on to the server.
This password is used with the user ID specified by the logon parameter. The
password parameter cannot be used unless the logon parameter is also
specified. If the default setup for the logon parameter is used (that is,
the logon parameter is not included and the DCDB Replicator service tries
logging on with the machine ID), then a password cannot be specified. If a
password is desired for the workstation, both the logon and password
parameters must be used.
o tryuser
This parameter specifies whether the server tries automatically connecting to
the domain controller when a user is logged on to the workstation.
If the tryuser parameter value is Yes, the server tries connecting to the
domain controller using the user ID and password of the user logged on at the
server. The connection succeeds if the user has read and attributes
permissions to the directories to be replicated. If the connection attempt
fails, the server cannot connect to the domain controller until the user logs
off. If the tryuser parameter value is No, the server does not connect to
the domain controller until the user logs off.
Default value: Yes
ΓòÉΓòÉΓòÉ 7.3.14.2. Tuning Parameters ΓòÉΓòÉΓòÉ
The following list contains the tuning parameters in the DCDB Replicator
section of the IBMLAN.INI file:
o guardtime
This parameter specifies how long, in minutes, the export path must be stable
before servers can connect to it. The guardtime parameter prevents servers
from connecting to an export path while you are still changing it. For
example, if the guardtime parameter value is set to 10, servers cannot copy
new material from the domain controller until at least 10 minutes after you
finish changing an export path.
This parameter is valid only if the integrity parameter in the REPL.INI file
is set to Tree. For more information concerning the REPL.INI file, refer to
the LAN Server Network Administrator Reference Volume 3: Network
Administrator Tasks.
Default value: 2
Minimum value: 0
Maximum value: interval / 2
o interval
This parameter specifies how often, in minutes, the \DCDB directory in the
export path is checked for changes.
Default value: 5
Minimum value: 1
Maximum value: 60
o pulse
This parameter specifies how often, in minutes, the domain controller sends
extra updates to servers, besides those sent when a change to the export path
occurs. These pulse updates are identical to the most recent change update
and ensure that the \DCDB directory in all import paths matches that in the
export path.
This parameter value is multiplied by the interval parameter value to
determine how often updates are sent to servers. For example, if the interval
value is 5 and the pulse value is 3, redundant pulse updates are sent every
15 minutes.
Default value: 3
Minimum value: 1
Maximum value: 10
o random
Specifies the interval, in seconds, over which to distribute server
connections. The domain controller sends this value to servers, which wait
an interval of seconds between 0 and this value before connecting.
The random parameter controls network traffic of servers connecting to the
domain controller. If a domain controller replicates the DCDB to several
servers, network performance could be affected if all servers try connecting
to the domain controller at once. You can avoid this problem by requiring
the servers to wait a random amount of time before connecting.
For example, suppose you specify a random parameter value of 90. This value
tells each server to randomly select a number between 0 and 90 and wait that
many seconds before connecting to the domain controller.
Default value: 60
Minimum value: 1
Maximum value: 120
ΓòÉΓòÉΓòÉ 7.3.15. Peer Section ΓòÉΓòÉΓòÉ
The Peer service allows requesters to share resources. During installation, the
Peer service can be defined to start when the requester starts.
The values for the Peer service parameters can be changed in the IBMLAN.INI
file. An option issued from the command line can override the values in the
IBMLAN.INI file.
For more information about the Peer service, see the LAN Server Network
Administrator Reference Volume 1: Planning, Installation, and Configuration and
LAN Server Network Administrator Reference Volume 3: Network Administrator
Tasks.
ΓòÉΓòÉΓòÉ 7.3.15.1. System Parameters ΓòÉΓòÉΓòÉ
Use the following parameters with the Peer service to override the parameters
in the IBMLAN.INI file:
o autodisconnect
For a description of this parameter, see the autodisconnect parameter in
topic System Parameters.
This parameter should always be set to -1 for no automatic disconnect.
Default value: -1
o security
This parameter indicates the security mode the peer server is using. Valid
values are user and share.
User level security controls access to resources shared by the peer server
through identifying users by a user ID and a password.
Share level security allows the peer server owner to specify both the
password and permissions associated with a shared resource.
Default value: User
o username
This parameter indicates the user ID of the peer server owner. This
parameter is relevant only if the peer server is using user level security.
The user ID listed in this parameter will be granted a session with the peer
server even if another user has a connection. This ensures that the owner
can always connect to the peer server. This parameter is ignored if the
security parameter is set to share.
Note: If a resource is shared with /USERS:1, this limit will be enforced.
That is, the owner cannot connect to the peer server if another user
is already connected.
Default value: " "
For additional information about the Peer service, see the following commands
in the online LAN Server Commands and Utilities:
o NET CONFIG
o NET CONTINUE
o NET PAUSE
o NET SESSION
o NET SHARE
o NET START
o NET STATISTICS
o NET STOP
o NET USE
ΓòÉΓòÉΓòÉ 8. NETWORK.INI File Parameter Descriptions ΓòÉΓòÉΓòÉ
This chapter describes the parameters in the NETWORK.INI file, which is on the
DOS requesters. This chapter has default, minimum, and maximum values for the
NETWORK.INI file parameters.
ΓòÉΓòÉΓòÉ 8.1. Changing NETWORK.INI Parameter Values ΓòÉΓòÉΓòÉ
The NETWORK.INI file can be edited with an ASCII text editor. Before you edit
the NETWORK.INI file, it is important to understand its structure. Refer to
Example NETWORK.INI File for an example NETWORK.INI file.
ΓòÉΓòÉΓòÉ 8.2. Activating Changed Parameter Values ΓòÉΓòÉΓòÉ
If you change the value of a parameter in the NETWORK.INI file, you must shut
down and restart the workstation for the change to take effect.
If the network is not started, type NET START without parameters to start DOS
LAN Services, using the NETWORK.INI file as the parameter default file.
However, if the network has been started, typing NET START displays the current
parameter settings.
If the network has been started, first type NET STOP to stop DOS LAN Services.
Next, type NET START without parameters to start DOS LAN Services, using the
NETWORK.INI file as the parameter default file.
ΓòÉΓòÉΓòÉ 8.3. Parameter Descriptions ΓòÉΓòÉΓòÉ
The parameter defaults have been chosen to enhance performance for most users.
Other values should be selected only for configuration needs. The parameters
contained in the NETWORK.INI file can be grouped into three categories: system
parameters, capacity parameters, and tuning parameters.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 22. NETWORK.INI [network] Section Parameter Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé DESCRIPTION Γöé VALID VALUES Γöé DEFAULT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé COMPUTERNAME Γöé The name that identifies Γöé Up to 15 alphanu- Γöé Name speci- Γöé
Γöé Γöé this workstation to the Γöé meric characters Γöé fied at Γöé
Γöé Γöé network Γöé or special charac- Γöé installation Γöé
Γöé Γöé Γöé ters including Γöé Γöé
Γöé Γöé Γöé "! # $ % & ( ) Γò£ _ Γöé Γöé
Γöé Γöé Γöé { } . ^ ` ~" Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LANROOT Γöé The directory where DOS Γöé A fully qualified Γöé C:\NET Γöé
Γöé Γöé LAN Services is Γöé path (drive letter Γöé Γöé
Γöé Γöé installed and starts Γöé and path) Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé AUTOLOGON Γöé Displays a window to log Γöé Yes, No Γöé Yes Γöé
Γöé Γöé on to a domain when DOS Γöé Γöé Γöé
Γöé Γöé LAN Services starts Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé AUTOSTART Γöé Indicates which services Γöé Netbeui, Basic, Γöé Basic Γöé
Γöé Γöé to start when "NET Γöé Full, Messenger, Γöé Γöé
Γöé Γöé START" is entered Γöé Netpopup, Peer Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé USERNAME Γöé The name that identifies Γöé Up to 20 alphanu- Γöé Name speci- Γöé
Γöé Γöé you to the network Γöé meric characters Γöé fied at Γöé
Γöé Γöé Γöé including Γöé installation Γöé
Γöé Γöé Γöé "! # $ % & ( ) Γò£ _ Γöé Γöé
Γöé Γöé Γöé { } . ^ ` ~" Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOMAIN Γöé Name of the domain to Γöé Up to 15 alphanu- Γöé Name speci- Γöé
Γöé Γöé which this workstation Γöé meric characters Γöé fied at Γöé
Γöé Γöé belongs Γöé including Γöé installation Γöé
Γöé Γöé Γöé "! # $ % & ( ) Γò£ _ Γöé Γöé
Γöé Γöé Γöé { } . ^ ` ~" Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RECONNECT Γöé Indicates to reconnect Γöé Yes, No Γöé Yes Γöé
Γöé Γöé persistent connections Γöé Γöé Γöé
Γöé Γöé when logging on Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LSLOGON Γöé Indicates to validate Γöé Yes, No Γöé Yes Γöé
Γöé Γöé the logon Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMBIGBUF(1, Γöé Indicates number of big Γöé 0 to 4096 Γöé 2 Γöé
Γöé 2) Γöé buffers to use in KB Γöé Γöé Γöé
Γöé Γöé (Full and Virtual redi- Γöé Γöé Γöé
Γöé Γöé rectors only) Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SIZEBIGBUF(1, Γöé Indicates the size of Γöé 4096 to 32768 Γöé 4096 Γöé
Γöé 2) Γöé big buffers to use in KB Γöé Γöé Γöé
Γöé Γöé (Full and Virtual redi- Γöé Γöé Γöé
Γöé Γöé rectors only) Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMWORKBUF(1) Γöé Indicates the number of Γöé 2 to 16 Γöé 2 Γöé
Γöé Γöé work buffers to use Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SIZWORKBUF(1) Γöé Indicates the size of Γöé 512 to 16384 Γöé 1024 Γöé
Γöé Γöé work buffers to use in Γöé Γöé Γöé
Γöé Γöé KB Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé EXTRAHEAP(1, Γöé Allocates extra heap Γöé 1023 to 32768 Γöé 0 Γöé
Γöé 2) Γöé space for the redi- Γöé Γöé Γöé
Γöé Γöé rector. This parameter Γöé Γöé Γöé
Γöé Γöé is needed when using Γöé Γöé Γöé
Γöé Γöé file intensive applica- Γöé Γöé Γöé
Γöé Γöé tions such as data Γöé Γöé Γöé
Γöé Γöé bases. Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé AUTOCACHE Γöé Automatically allocates Γöé Yes, No Γöé Yes Γöé
Γöé Γöé NumBigBuf, SizBigBuf, Γöé Γöé Γöé
Γöé Γöé and ExtraHeap based on Γöé Γöé Γöé
Γöé Γöé the amount of XMS Γöé Γöé Γöé
Γöé Γöé memory. Overrides Γöé Γöé Γöé
Γöé Γöé NumBigBuf, SizBigBuf, Γöé Γöé Γöé
Γöé Γöé and ExtraHeap parame- Γöé Γöé Γöé
Γöé Γöé ters. This parameter Γöé Γöé Γöé
Γöé Γöé improves performance. Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PRINTBUFTIME Γöé Amount of time, in Γöé 0 to 65535 Γöé 0 Γöé
Γöé Γöé seconds, before an end Γöé Γöé Γöé
Γöé Γöé of print job is sent to Γöé Γöé Γöé
Γöé Γöé the server after the Γöé Γöé Γöé
Γöé Γöé print job is submitted. Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 22. NETWORK.INI [network] Section Parameter Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé DESCRIPTION Γöé VALID VALUES Γöé DEFAULT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LANAS Γöé The number of LAN Γöé 0 to 7 Γöé 1 Γöé
Γöé Γöé adapter cards used by Γöé Γöé Γöé
Γöé Γöé your workstation. Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RIPL Γöé Identifies a remote IPL Γöé Yes, No Γöé No Γöé
Γöé Γöé workstation. Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PASSWORDCACHINΓöé Indicates to cache pass- Γöé Yes, No Γöé Yes Γöé
Γöé Γöé words in a file. This Γöé Γöé Γöé
Γöé Γöé saves passwords to Γöé Γöé Γöé
Γöé Γöé servers in a password Γöé Γöé Γöé
Γöé Γöé protected file so the Γöé Γöé Γöé
Γöé Γöé user will not have to Γöé Γöé Γöé
Γöé Γöé enter a password for Γöé Γöé Γöé
Γöé Γöé each server that is Γöé Γöé Γöé
Γöé Γöé accessed. Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé BROWSEALIAS(1,Γöé Indicates whether Γöé Yes, No Γöé Yes Γöé
Γöé 3) Γöé netnames or aliases are Γöé Γöé Γöé
Γöé Γöé displayed when using the Γöé Γöé Γöé
Γöé Γöé Browse option in the Γöé Γöé Γöé
Γöé Γöé Windows interface Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTES: Γöé
Γöé Γöé
Γöé 1. This parameter must be manually added to the NETWORK.INI file to change Γöé
Γöé the default. The installation program does not add this parameter to Γöé
Γöé the NETWORK.INI file. Γöé
Γöé 2. This parameter is overridden by "autocache=yes". Γöé
Γöé 3. Browsing for aliases is valid only on LAN Server domains. If this Γöé
Γöé parameter is set to YES, aliases are browsed. If no aliases exist on Γöé
Γöé the domain, netnames are browsed automatically. If this parameter is Γöé
Γöé set to NO, browsing for aliases is not attempted. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 8.4. NETWORK.INI Messenger Parameters ΓòÉΓòÉΓòÉ
The following table provides information about the parameters in the
[messenger] section of the NETWORK.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 23. NETWORK.INI [messenger] Section Parameter Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé DESCRIPTION Γöé VALID VALUES Γöé DEFAULT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LOGFILE Γöé The name of the file Γöé Alphanumeric char- Γöé MESSAGES.LOG Γöé
Γöé Γöé where received messages Γöé acters. See your Γöé Γöé
Γöé Γöé are logged Γöé DOS user's guide Γöé Γöé
Γöé Γöé Γöé for valid charac- Γöé Γöé
Γöé Γöé Γöé ters to use when Γöé Γöé
Γöé Γöé Γöé creating file Γöé Γöé
Γöé Γöé Γöé names Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SIZEMEMBUF Γöé Indicates the size of Γöé 512 to 4096 Γöé 512 Γöé
Γöé Γöé message buffers to use Γöé Γöé Γöé
Γöé Γöé in KB Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMMSGNAMES Γöé Indicates the number of Γöé 2 to 8 Γöé 2 Γöé
Γöé Γöé message names to be Γöé Γöé Γöé
Γöé Γöé added to the workstation Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 8.5. NETWORK.INI Netpopup Parameter ΓòÉΓòÉΓòÉ
The following table provides information about the parameter in the [netpopup]
section of the NETWORK.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 24. NETWORK.INI [netpopup] Section Parameter Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé DESCRIPTION Γöé VALID VALUES Γöé DEFAULT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MSGTIMEOUT Γöé Indicates the length of Γöé -1 to 1800 Γöé 60 Γöé
Γöé Γöé time, in seconds, a Γöé Γöé Γöé
Γöé Γöé message is displayed if Γöé Γöé Γöé
Γöé Γöé Esc is not pressed. If Γöé Γöé Γöé
Γöé Γöé the value is -1, a Γöé Γöé Γöé
Γöé Γöé message is displayed Γöé Γöé Γöé
Γöé Γöé until Esc is pressed. Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 8.6. NETWORK.INI Peer Parameters ΓòÉΓòÉΓòÉ
The following table provides information about the parameter in the [peer]
section of the NETWORK.INI file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 25. NETWORK.INI [peer] Section Parameter Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé DESCRIPTION Γöé VALID VALUES Γöé DEFAULT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé A20MONITER Γöé Saves the state of the Γöé 0 to 1 Γöé 1 Γöé
Γöé Γöé A20 line during task Γöé Γöé Γöé
Γöé Γöé switching. Some memory Γöé Γöé Γöé
Γöé Γöé managers fail when this Γöé Γöé Γöé
Γöé Γöé parameter is set to 1. Γöé Γöé Γöé
Γöé Γöé If you are using a Γöé Γöé Γöé
Γöé Γöé memory manager and expe- Γöé Γöé Γöé
Γöé Γöé rience hangs, set this Γöé Γöé Γöé
Γöé Γöé parameter to 0. Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMSHARES Γöé Indicates the maximum Γöé 2 to 256 Γöé 10 Γöé
Γöé Γöé number of resources you Γöé Γöé Γöé
Γöé Γöé can share. Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMREQ Γöé Indicates the number of Γöé 3 to 6 Γöé 3 Γöé
Γöé Γöé request buffers the Peer Γöé Γöé Γöé
Γöé Γöé service will use when it Γöé Γöé Γöé
Γöé Γöé starts. Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé XMITSIZE Γöé Indicates the size, in Γöé 512 to 32768 Γöé 2048 Γöé
Γöé Γöé bytes, of the transmit Γöé Γöé Γöé
Γöé Γöé buffers the Peer service Γöé Γöé Γöé
Γöé Γöé will use when trans- Γöé Γöé Γöé
Γöé Γöé ferring data. Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Γöé (NumReq * XmitSize < 48Γöé) Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TASKTIMESLICE Γöé Indicates the amount of Γöé 00 to 99 Γöé 54 Γöé
Γöé Γöé time (ticks) the fore- Γöé Γöé Γöé
Γöé Γöé ground and background Γöé Γöé Γöé
Γöé Γöé will each run Γöé Γöé Γöé
Γöé Γöé ("TimeSlice=FB"). The Γöé Γöé Γöé
Γöé Γöé default for the fore- Γöé Γöé Γöé
Γöé Γöé ground is 5, and the Γöé Γöé Γöé
Γöé Γöé default for the back- Γöé Γöé Γöé
Γöé Γöé ground is 4 Γöé Γöé Γöé
Γöé Γöé ("TimeSlice=54"). Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Γöé Value Ticks Γöé Γöé Γöé
Γöé Γöé ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇ Γöé Γöé Γöé
Γöé Γöé 0 2 Γöé Γöé Γöé
Γöé Γöé 1 4 Γöé Γöé Γöé
Γöé Γöé 2 6 Γöé Γöé Γöé
Γöé Γöé 3 10 Γöé Γöé Γöé
Γöé Γöé 4 14 Γöé Γöé Γöé
Γöé Γöé 5 22 Γöé Γöé Γöé
Γöé Γöé 6 30 Γöé Γöé Γöé
Γöé Γöé 7 42 Γöé Γöé Γöé
Γöé Γöé 8 56 Γöé Γöé Γöé
Γöé Γöé 9 72 Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 25. NETWORK.INI [peer] Section Parameter Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé DESCRIPTION Γöé VALID VALUES Γöé DEFAULT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OPENMODE Γöé Indicates the mode files Γöé 0 to 3 Γöé 3 Γöé
Γöé Γöé will be opened in when Γöé Γöé Γöé
Γöé Γöé an open request is Γöé Γöé Γöé
Γöé Γöé received. Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Γöé 0 User Open mode Γöé Γöé Γöé
Γöé Γöé requested by the Γöé Γöé Γöé
Γöé Γöé application that is Γöé Γöé Γöé
Γöé Γöé running. Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Γöé 1 DENY-NONE sharing Γöé Γöé Γöé
Γöé Γöé mode if read-only Γöé Γöé Γöé
Γöé Γöé access is granted Γöé Γöé Γöé
Γöé Γöé to .EXE or .COM Γöé Γöé Γöé
Γöé Γöé files. Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Γöé COMPATIBILITY mode Γöé Γöé Γöé
Γöé Γöé for .BAT files or Γöé Γöé Γöé
Γöé Γöé if write access is Γöé Γöé Γöé
Γöé Γöé granted to .EXE or Γöé Γöé Γöé
Γöé Γöé .COM files. Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Γöé 2 DENY-NONE sharing Γöé Γöé Γöé
Γöé Γöé mode if read-only Γöé Γöé Γöé
Γöé Γöé access is granted Γöé Γöé Γöé
Γöé Γöé to .EXE or .COM Γöé Γöé Γöé
Γöé Γöé files. Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Γöé DENY-WRITE sharing Γöé Γöé Γöé
Γöé Γöé mode if read-only Γöé Γöé Γöé
Γöé Γöé access is granted Γöé Γöé Γöé
Γöé Γöé to .BAT files. Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Γöé COMPATIBILITY mode Γöé Γöé Γöé
Γöé Γöé for .BAT files or Γöé Γöé Γöé
Γöé Γöé if write access is Γöé Γöé Γöé
Γöé Γöé granted to .EXE, Γöé Γöé Γöé
Γöé Γöé .COM, or .BAT Γöé Γöé Γöé
Γöé Γöé files. Γöé Γöé Γöé
Γöé Γöé Γöé Γöé Γöé
Γöé Γöé 3 DENY-NONE sharing Γöé Γöé Γöé
Γöé Γöé mode on all compat- Γöé Γöé Γöé
Γöé Γöé ibility mode opens. Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé FILESHARESIZE Γöé Indicates the bytes Γöé 512 to 32768 Γöé 2048 Γöé
Γöé Γöé allocated for the DOS Γöé Γöé Γöé
Γöé Γöé storage area used to Γöé Γöé Γöé
Γöé Γöé record file-sharing Γöé Γöé Γöé
Γöé Γöé information.(1) Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SHARELOCKS Γöé Defines the maximum Γöé 20 to 1000 Γöé 20 Γöé
Γöé Γöé number of active locked Γöé Γöé Γöé
Γöé Γöé ranges in files that you Γöé Γöé Γöé
Γöé Γöé can share with the Peer Γöé Γöé Γöé
Γöé Γöé service.(1) Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé FMSHARE Γöé Indicates whether you Γöé Yes, No Γöé Yes Γöé
Γöé Γöé want to be able to share Γöé Γöé Γöé
Γöé Γöé directories from the Γöé Γöé Γöé
Γöé Γöé Windows File Manager(2) Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTES: Γöé
Γöé Γöé
Γöé 1. If SHARE.EXE is started before the Peer Service, the values that were Γöé
Γöé specified when SHARE.EXE was started are used. Γöé
Γöé 2. This parameter must be manually added to the NETWORK.INI file to change Γöé
Γöé the default. The installation program does not add this parameter to Γöé
Γöé the NETWORK.INI file. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 8.7. Example NETWORK.INI File ΓòÉΓòÉΓòÉ
The following is a sample NETWORK.INI file.
[NETWORK]
computername=JIM
lanroot=C:\NET
autostart=netbeui
dospophotkey=N
username=JIM
domain=LAKE
reconnect=yes
printbuftime=3
[MESSENGER]
logfile=MESSAGES.LOG
sizemessbuf=512
nummsgnames=2
[NETPOPUP]
msgtimeout=60
[PASSWORD LISTS]
JIM=C:\NET\JIM000.PWL
[PEER]
openmode=3
xmitsize=4096
[DOMAIN LISTS]
LAKE=
EOM_DOM=
GOOFDOM=
[Local Applications]
EDIT=E editor 2.1
LOTUS=LOTUS 123 ver 3.3
[Network Applications]
WORD=WORD ver 2.0
ΓòÉΓòÉΓòÉ 9. CONFIG.SYS File Parameter Descriptions ΓòÉΓòÉΓòÉ
This chapter describes OS/2 functions that can improve overall system
performance. Additional information concerning OS/2 memory management and file
usage is provided to explain the various memory and hard disk space
requirements.
Default values are specified in the CONFIG.SYS file during system installation.
Additional parameters are specified in the CONFIG.SYS file during the
installation of some application programs. Refer to the application program
documentation for additional information concerning the parameter values that
can be changed. For the default, minimum, and maximum value of each parameter
in the CONFIG.SYS file, refer to Configuration Files.
ΓòÉΓòÉΓòÉ 9.1. Changing CONFIG.SYS Parameter Values ΓòÉΓòÉΓòÉ
The CONFIG.SYS file can be edited with an ASCII text editor. The structure of
the CONFIG.SYS file should be understood before editing it. The CONFIG.SYS file
is updated automatically during the install process. For an example CONFIG.SYS
file, refer to File Examples.
ΓòÉΓòÉΓòÉ 9.2. Activating Changed Parameter Values ΓòÉΓòÉΓòÉ
If you change the value of a parameter in the CONFIG.SYS file, you must shut
down and restart your workstation for the change to take effect.
ΓòÉΓòÉΓòÉ 9.3. Memory Management ΓòÉΓòÉΓòÉ
The CONFIG.SYS file parameters for memory and storage management can be grouped
into two categories: system parameters and tuning parameters. Memory- and
Storage-Related CONFIG.SYS File Parameters lists the memory- and
storage-related parameters contained in the CONFIG.SYS file.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 26. Memory- and Storage-Related CONFIG.SYS File Parameters Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SYSTEM PARAMETERS Γöé TUNING PARAMETERS Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MEMMAN Γöé BUFFERS Γöé
Γöé PROTECTONLY Γöé DISKCACHE Γöé
Γöé Γöé SWAPPATH Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 9.3.1. System Parameters ΓòÉΓòÉΓòÉ
The following list contains the memory- and storage-related system parameters
in the CONFIG.SYS file:
o memman
The memman parameter allows or prevents swapping and segment motion in your
system. The first value, Swap or Noswap, specifies whether you want the
system to swap memory segments to disk. If you want to run several large
programs simultaneously, or if you have a program that is too large for
available memory, set the first value to Swap. To prevent swapping, set the
first value to Noswap. When you prevent swapping, the OS/2 program requires
5MB of physical memory to restart your system.
The second value, Move or Nomove, specifies whether segment swapping and
storage compaction are permitted. Where timing is critical (for example,
when process-control tasks are being performed), it is a good idea to prevent
all swapping and segment motion in your system. By setting the second value
to Nomove, you can prevent storage compaction.
Default value: Swap, Move
o protectonly
This required parameter controls the use of memory under 640KB. If the
protectonly parameter is set to YES, memory under 640KB, which is usually
reserved for DOS programs, becomes available for OS/2 programs. When this
parameter is set to YES, you cannot run application programs in DOS (real)
mode. Set the protectonly parameter to NO to run DOS programs in the lower
640KB of memory. If this parameter is set to NO, you can use both DOS and
OS/2 programs.
ΓòÉΓòÉΓòÉ 9.3.2. Tuning Parameters ΓòÉΓòÉΓòÉ
The following list contains the memory- and storage-related tuning parameters
in the CONFIG.SYS file:
o buffers
Buffering, which deals with the timeliness of I/O devices, is a memory
management method. The disk buffer is a 512-byte portion of storage that the
OS/2 program uses to hold I/O information temporarily. It assists in helping
the I/O device and the processor to work at the same time.
OS/2 now uses buffers only for caching FAT and HPFS directory information.
This may provide a performance boost when using those file systems. Buffers
no longer cache partial sector reads.
By using the disk buffer, the operating system can read and write blocks of
information. Once the information is read into the buffer, the processor is
ready to process it. While the information is in the buffer or being
processed, the input device can begin reading new pieces of information so
the processor does not have to wait unnecessarily to process information and
program instructions. The processor can then complete its operation because
the next block of information to process is already in the buffer area.
If the processor completes its work and there is no information in the buffer
to process, the processor must wait until the next block of information is
read into memory by the input device. Similarly, if the input device reads
information into the buffer before the processor has time to process the
records, the buffer might reach its capacity and have to wait until the
processor accepts more information to process.
The buffers parameter determines the number of disk buffers that the OS/2
program keeps in memory. Depending on how many programs you work with
simultaneously, you may want to experiment with this number to maximize
performance on your system.
If you simultaneously run a large number of programs, you can increase the
speed of your system by increasing the buffers parameter value (for example,
buffers=70). However, remember that when you increase the number of disk
buffers, you decrease your available memory by 512 bytes for each buffer
specified. Additional buffers may cause some programs to run more slowly
because there is less memory available for the program. Also, memory
swapping may occur more often, which will slow down performance.
Default value: 60
o diskcache
Another method of improving system performance is disk caching, which allows
a portion of the workstation's memory to be used as an additional hard-disk
buffer. Disk caching assists the buffer area by holding the most frequently
used information, thus enabling the processor to continue processing with
fewer interruptions.
For example, suppose the input device is operating slower than the processor.
Without disk caching, the processor slowly empties the buffers of information
and eventually stops processing. The processor is delayed until the input
device supplies additional information. In this situation, the performance
of the input device, which should rely on the speed of the processor, is
seemingly independent of processor processing.
The disk cache speeds up workstation operations that read from the hard disk
by keeping frequently accessed information in a cache buffer. When a program
requests hard-disk information that is already in the cache buffer, the disk
cache sends the information directly to the program. This method of
accessing information is much faster than if the information has to be read
from the disk each time.
The proper setting for the caching threshold (128KB in the following example)
and for the diskcache parameter depends on your environment. For example, if
you want to cache shared programs, use a threshold of 128KB. If, however, you
want to cache only random I/O, use a threshold of 4KB. You can determine the
best size for the disk cache by experimenting with different values. The
disk cache normally needs to be several megabytes in size to achieve the best
performance.
An example of a diskcache statement is the following:
DISKCACHE=xxxx, 128, LW, AC:C
where:
xxxx Is the amount of memory in KB you want to allocate for
caching.
128 Specifies the maximum record size for caching, in number
of sectors.
LW Activates lazy writing (writing of cache memory during
disk idle time).
AC Defines the drives to be checked automatically at startup
to determine if the file system associated with a drive is
in an inconsistent state (for example, if files were left
open because of a loss of power). The operating system
runs CHKDSK with the /F option to correct any problems
caused by improper system shutdown.
For more information about DISKCACHE, refer to the LAN Server Commands and
Utilities.
o swappath
With advanced memory management techniques, the OS/2 program attempts to keep
only those portions of a program that are actually active in physical memory.
Inactive portions of a program are placed in a special swap file where they
remain until they are needed in physical memory.
The swappath parameter specifies the size and location of the swap area on
the fixed disk. Using a swap file allows the operating system to maintain a
greater number of programs in an active state than would be possible to fit
into physical memory if a non-virtual memory system were being used.
Pages swapped from running programs go to a temporary file named SWAPPER.DAT.
This file grows in size as you start or stop programs and load, modify, or
save data files. The SWAPPER.DAT file can sometimes be hundreds of thousands
of bytes in size, an indication that your system may need additional memory
to improve performance.
You can change the swappath parameter value so that the SWAPPER.DAT file
resides in another directory or on another logical drive. Placing the
SWAPPER.DAT file on a separate logical drive limits the size of the
SWAPPER.DAT file and can also improve swapper performance.
The swap file needs to be at least 512KB in size, so you must have at least
512KB of available storage on the swapping drive. The size of the swap file
increases as the operating system overcommits storage.
The swappath parameter has two options:
minfree Specifies the minimum amount of free space, in kilobytes, that you
want to remain on the disk. When the swap file has used up all other
space, the system generates a warning message.
initsize Specifies the initial size, in kilobytes, to be allocated for the
swap file.
The syntax of the swappath statement is:
swappath=d:\path minfree initsize
Default value: C:\OS2\SYSTEM 2048 2048
ΓòÉΓòÉΓòÉ 10. High Performance File Systems ΓòÉΓòÉΓòÉ
The high performance file system (HPFS) is an installable file system (IFS)
that provides better performance than the file allocation table (FAT) file
system. The HPFS is designed to provide extremely fast access to very large
disk volumes. The base operating system also supports the coexistence of
multiple, active file systems on a single workstation.
If you select the HPFS as your standard file system, the base operating system
installation procedure inserts an IFS statement as the first entry in the
CONFIG.SYS file.
The IFS statement has the following format:
IFS=x:\OS2\HPFS.IFS CACHE:nnnn[/AUTOCHECK:drivelist]
x: Specifies the drive letter of the partition from which the
OS/2 program is started.
/CACHE Specifies the amount of memory, in kilobytes, to use for the
HPFS cache. The nnnn value must be a multiple of 2, or it is
rounded down to a value that is a multiple of 2. If /CACHE
is omitted, the default value is 10% of the total physical
memory available. The minimum value is 64 and the maximum is
determined by the amount of physical memory available, up to
2048 (2MB). A cache of at least 512KB is recommended.
/AUTOCHECK Specifies a list of drive letters to be automatically
verified by the CHKDSK command at system startup time if the
HPFS detects that the drive may have been shutdown
unexpectedly. The CHKDSK command may also be executed for
the specified drives if hotfixes have taken place and need to
be cleaned up. The drivelist value is a string of letters
indicating the HPFS drives in the workstation. The drive
letters are not separated by commas or spaces. The IPL volume
is always checked if it is an HPFS volume. If any drive
specified is not a valid HPFS drive, the drive is not
checked. HPFS drives that are not specified are not checked,
except for the IPL volume as previously stated.
If you install the HPFS on your system, your system files are
replaced. If you want to restart DOS from diskette, the data
files are no longer accessible.
ΓòÉΓòÉΓòÉ 10.1. HPFS Caching ΓòÉΓòÉΓòÉ
Using the OS2.INI file, the system installation program sets up caching for the
primary partition. The HPFS 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 it can be used in satisfying future requests. This cache is
separate from the buffers and diskcache parameters.
When a user requests data that is not present in the cache, the HPFS selects
the least recently used (LRU) block, writes the data within that block to disk,
if necessary, and then fills the block with the requested data. This
significantly increases the chances that often-used data will be found in
memory, thus saving the expense of a disk-read operation.
In addition, the file system takes advantage of its knowledge of cache block
contents. Data not expected to be reused soon by the file system is placed in
cache blocks marked for immediate reuse. In most cases, when a write request is
received, it is not necessary to write the data immediately to disk. The HPFS
takes such data and copies it to the cache block without actually performing
the disk-write operation. Once the data is in the cache, it is written to disk
as a background activity.
Also, because these lazy-writes are performed during disk idle time, incoming
requests need not wait for large disk writes to complete. This optimizes
overall system throughput and response time for all requesting processes.
The HPFS also contains additional levels of caching that speed up access to
directories. The HPFS uses this cache to get quickly to the directory on which
the request is being made.
Note: Although the file system owns the cache memory, it is the cache driver
that manages lazy-writing of cache blocks. If the cache driver is not
loaded, no lazy-writing is performed, and all write requests are written
to the disk drive. For further information on the cache driver, refer to
the IBM OS/2 LAN Server Version 4.0 Commands and Utilities.
The HPFS cache (CACHE) is initialized by a RUN statement in the CONFIG.SYS
file. The RUN statement has the following format:
RUN=d:\OS2\CACHE.EXE [/LAZY:value]
[/MAXAGE:value]
[/DISKIDLE:value]
[/BUFFERIDLE:value]
where
d: Specifies the drive letter where OS/2 is installed. This
should be the boot drive.
/LAZY Enables and disables lazy-writing for the specified drive.
If lazy-writing is enabled, the contents of CACHE is written
to disk only during disk idle time. If no drive is
specified, lazy-writing is either enabled or disabled for all
drives serviced by the HPFS. If value is Off, lazy-writing
is disabled. If value is On, lazy-writing is enabled. The
default is On.
Warning: If you set the /LAZY option to On, always run
Shutdown from the desktop before turning off your
workstation. Failure to do so will cause loss of data if the
contents of the HPFS cache buffers have not been written to
the disk. For safety, and if performance is not a concern,
set the /LAZY option to Off, which causes a write, through
the cache, to the disk.
/MAXAGE Specifies the maximum time, in milliseconds, that a dirty
cache block for a drive can be in memory before it is flushed
(written to disk). The value can be from 0 through 65535,
with a default value of 5000. A value between 1000 and 20000
is recommended. The /MAXAGE value takes precedence over the
/BUFFERIDLE value. To ensure the effectiveness of
lazy-writes, specify a greater value for the /MAXAGE option
than for /BUFFERIDLE option. The /LAZY option must be set to
On for the /MAXAGE option to be effective.
/DISKIDLE Specifies the minimum time, in milliseconds, that a disk must
be idle before it can accept data from the CACHE. The value
can be from 0 through 500000, with a default value of 1000.
The value must be greater than the /BUFFERIDLE value. The
/LAZY option must be set to On for the /DISKIDLE option to be
effective.
/BUFFERIDLE Specifies the minimum time, in milliseconds, that a dirty
cache block for a drive must be idle before it is written
opportunistically when the disk subsystem is idle. The value
can be from 0 through 500000, with a default value of 500. A
value between 100 and 1000 is recommended. The /MAXAGE value
takes precedence over the /BUFFERIDLE value. To ensure the
effectiveness of lazy-writes, specify a greater value for the
/MAXAGE option than for the /BUFFERIDLE option. The /LAZY
option must be set to On for the /BUFFERIDLE option to be
effective.
ΓòÉΓòÉΓòÉ 10.1.1. Extended Attribute Support ΓòÉΓòÉΓòÉ
The file systems can support additional information, called extended
attributes, about files and directories. Through extended attributes, a program
can attach information to a file system object (a file or directory). The
information describes the object to another program, to the operating system,
or to the file system driver (FSD) managing that object.
For example, the name of the file's originator can be stored on a file object.
Other uses include categorizing file objects, such as icons or bit maps, and
describing formats of data in a file object, such as a data record.
A file object may have a list of extended attributes associated with it. These
are not part of a file object's data and are managed by the file system that
manages objects. An extended attribute must have a name and a value; the name
is restricted to the same character set as a file name.
The maximum size of an extended attribute is 64KB and the value is arbitrary
data. However, a standard set of conventions for extended attribute use is
provided so that data is more easily communicated between programs.
Warning: Extended attributes may be lost if the file is rewritten or copied by
a previous version of the OS/2 program, DOS, or an application written before
the latest version of the OS/2 program.
ΓòÉΓòÉΓòÉ 10.2. 386 High Performance File System Support ΓòÉΓòÉΓòÉ
The 386 HPFS server is an installable file system (IFS) designed for 386 and
higher workstations with large disk systems. The 386 HPFS is loaded by a
statement in the CONFIG.SYS file. The statement has the following format:
IFS=x:\IBM386FS\HPFS386.IFS
[/A:drivelist]
where:
d: Specifies the drive letter of the partition where the IBMLAN directory
for LAN Server resides.
x: Specifies the drive letter of the partition where the HPFS386.IFS
resides. This should be the boot drive.
/A Specifies a list of drive letters to be automatically verified by the
CHKDSK command at system startup if the HPFS detects that the drive may
have been shut down unexpectedly. The CHKDSK command may also be
executed for the specified drives if errors have been hotfixed and need
to be cleaned up. The drivelist value is a string of letters indicating
the HPFS drives in the workstation. The drive letters are not separated
by commas or spaces. An asterisk (*) after the /A can be used to specify
all drives on the system. The IPL volume is always checked if it is an
HPFS volume. If any drive specified is not a valid HPFS drive, the drive
is not checked. HPFS drives that are not specified are not checked,
except for the IPL volume as previously stated.
ΓòÉΓòÉΓòÉ 10.3. HPFS386.INI Parameter Descriptions ΓòÉΓòÉΓòÉ
This file contains the initialization parameters for the 386 HPFS. The
parameters are grouped into components. The component groups start with the
component name enclosed in square brackets. Each component name appears on a
line by itself (a comment is allowed). The components include the following:
[filesystem:] ; General file system parameters
[lazywriter:] ; Lazy writer parameters
[DASD_Limits:] ; Directory Limits parameters
General rules:
o The component names and parameters are not case-sensitive. They can be
entered in upper case, lower case, or a mixture of upper and lower case.
o Wherever a blank appears in the syntax for a parameter, it can be left out or
additional blanks can be added. For example, the following syntaxes are all
valid:
- cachesize = 4096
- cachesize=4096
- cachesize= 4096
o Any text after a semicolon (;) up to the end of the line is treated as a
comment.
o All components and parameters are optional. If you do not specify a
parameter, the 386 HPFS uses a default setting for the parameter.
The [filesystem:] section specifies general file system parameters. If you
make any changes to these parameters, they do not take effect until you reboot
the system.
o useallmem = [yes|no]
This parameter specifies whether the 386 HPFS should use memory above the
16MB boundary, provided this system is configured with more than 16MB. Some
adapters, for example the IBM Token Ring Busmaster Server/A, cannot do direct
memory access (DMA) to memory above the 16MB boundary. If you have a LAN or
disk adapter that cannot do DMA to memory above the 16MB boundary, the 386
HPFS must use only memory below 16MB so that the adapter can put data into
the file system buffers. Set the useallmem parameter to YES if all of your
adapters can access memory above the 16MB boundary. Set the useallmem
parameter to NO if any of your LAN or disk adapters cannot access memory
above the 16MB boundary. If useallmem is not specified, the default setting
is no.
The useallmem parameter indicates to the 386 HPFS that it should use memory
above 16MB as much as possible. The useallmem parameter has the following
effects:
- If the machine has less than 16MB of memory, then using /USEALLMEM on the
IFS line has no effect on the 386 HPFS.
- If the machine has more than 16MB of memory, and /USEALLMEM is not on the
IFS line, then the 386 HPFS does the following:
o Uses only memory below 16MB for cache blocks.
o Allocates all server buffers that can be used for transmission to the
network adapter of disk device drivers below 16MB.
o Any buffers used internally by the file system, as well as the heap,
will not be limited to their location, and may be located above 16MB as
determined by the OS/2 program.
- If the machine has more than 16MB of memory, and /USEALLMEM does exist on
the IFS line, then the 386 HPFS does the following:
o Allocates cache blocks without regard to memory location.
o Transfers buffers allocated by the server without regard to location.
o If the 386 HPFS attempts to mount a volume as directed by the OS/2
program and the disk device driver does not supply physical addresses
above 16MB, the volume is mounted for direct IOCTL read and write.
Normal file service operations are not allowed and an error message,
HFS0109, is displayed.
o On server startup, the server attempts to determine whether all
networks to which it belongs are capable of addressing 16MB of memory.
If it determines that the networks cannot support this, the server
fails to start and logs error message NET3183.
o If the original IBM 16/4 Token Ring Busmaster adapter is used, the
useallmem parameter cannot be used.
o cachesize = nnnn
This parameter specifies how many kilobytes of memory the 386 HPFS should
claim for its cache. The cachesize parameter must be a minimum of 256KB.
The maximum value is determined by the size of available memory. The default
is to use 20% of available memory.
o maxheap = nnnn
This parameter sets a limit on the size of the heap. nnnn is the maximum
number of kilobytes to which the heap can grow. The 386 HPFS allocates heap
memory as needed. If this parameter is used, the 386 HPFS only allocates
memory for the heap up to the amount specified. If this parameter is not
used, there is no limit on the heap size. Use this parameter only if you
need to reserve memory on the system for other applications that may be
running. The minimum value is 64KB. The maximum value is determined by the
size of available memory minus the size of the cache. If maxheap is not
specified, the default is to have no limit on the heap size.
o lanroot = d:\path
This parameter specifies the drive and path of the directory for the LAN
Server software. The installation program fills in this parameter for you.
You do not need to change this parameter.
o fsprealloc = nn
This parameter specifies how many big buffers to allocate when the file
system is initialized. If neither the fsprealloc nor srvprealloc parameters
are used, the file system allocates big buffers as needed. The allocation of
big buffers can take a little time. Allocating the big buffers at
initialization improves the performance of the first requests that need big
buffers. The buffers are not freed until the system is shut down. The
minimum value for fsprealloc parameter is 2. The maximum is 64. If both the
fsprealloc parameter and srvprealloc parameters are specified in this file,
the fsprealloc parameter is used and the srvprealloc parameter is ignored.
o srvprealloc = nn
This parameter specifies how many big buffers to allocate when the server is
started rather than when the file system is initialized. This parameter,
like the fsprealloc parameter, can improve the performance of the first
requests that need big buffers. The buffers are freed when the server is
stopped. The minimum value for the srvprealloc parameter is 2. The maximum
is 64. If both the fsprealloc and srvprealloc parameters are specified in
this file, the fsprealloc parameter is used and the srvprealloc parameter is
ignored.
The [lazywriter:] section specifies settings for the lazy writer. If you
make any changes to these parameters, they do not take effect until you
reboot the system. You can use the CACHE386 program to change the internal
setting of these parameters while the system is running. When you reboot the
system, the parameters are set to the values in this file.
o lazy = [drives:] on|off
This parameter specifies whether the lazy writer is to be turned on or off
for the specified drives. The [drives:] can be a series of drive letters.
For example, LAZY = CDFG: ON turns on the lazy writer on drives C:, D:, F:,
and G:. It would not change the settings for drive E: or H:. An asterisk
(*) can be used for the drive letter to indicate that all drives are to have
the setting. This line can be used multiple times to achieve the settings
you want for your drives. The default value is to turn the lazy writer off
for all drives.
o maxage = [drives:] nnnn
This parameter specifies the maximum number of milliseconds that can pass
before the lazy writer writes the contents of a buffer to the disk. The
[drives:] can be a series of drive letters. For example, maxage = cdfg: 5000
would set the maximum buffer age to 5000ms on drives C:, D:, F:, and G:. It
would not change the settings for drive E: or H:. An asterisk (*) can be
used for the drive letter to indicate that all drives are to have the
setting. This line can be used multiple times to achieve the settings you
want for your drives. The minimum value is 0. The maximum value is 1000000.
If maxage is not specified, the default value is 10000.
o bufferidle = [drives::] nnnn
This parameter specifies the maximum number of milliseconds during which a
buffer is not used before the lazy writer writes the buffer contents to the
disk. The [drives:] can be a series of drive letters. For example,
bufferidle = cdfg: 500 would set the buffer idle time to 500ms on drives C:,
D:, F:, and G:. It would not change the settings for drive E: or H:. An
asterisk (*) can be used for the drive letter to indicate that all drives are
to have the setting. This line can be used multiple times to achieve the
settings you want for your drives. The minimum value is 0. The maximum
value is 500000. If the bufferidle parameter is not specified, the default
value is 1000 for all drives.
The [DASD_Limits:] section specifies settings of parameters for the Directory
Limits function. If you make any changes to these parameters they do not
take effect until you restart the server. (To stop and restart the server,
at an OS/2 command prompt, enter the command NET STOP SERVER and then the
command NET START SERVER.)
o ThreshAlertNames = [drives:] [user1] [user2] [group1] [group2] ...
This parameter lists the users or groups that are to be notified when a
Directory Limits threshold is crossed on the specified drives. Any mixture
of user names or group names can be used. All of the names must appear on
one line. This line can be used multiple times to achieve the settings you
want for your drives. If the ThreshAlertNames parameter is not specified,
the default is to have no user or group names.
o ThreshAlertDelay = [drives:] nn
This parameter specifies how many minutes to wait before sending another
alert for a threshold that was previously crossed on the specified drives.
If a threshold is crossed more than once within the delay period, an alert is
sent only for the first occurrence. An alert is sent if a higher threshold
is crossed during the delay period. This parameter is used to cut down on
the number of alerts that can be generated when there is a lot of disk
activity and the disk size is within the threshold. This line can be used
multiple times to achieve the settings you want for your drives. If the
parameter ThreshAlertDelay is not specified, the default is 10 minutes on all
drives.
o ThreshAlertUser = [drives::] yes|no
This parameter specifies whether to send an alert to the user whose disk
usage caused a threshold to be crossed on the specified drives. This line
can be used multiple times to achieve the settings you want for your drives.
The default is yes for all drives.
o DirFullAlertNames = [drives:] [user1] [user2] [user3] ...
This parameter lists the users or groups that are to be notified when a
Directory Limit is reached. Any mixture of user names or group names can be
used. All of the names must appear on one line. This line can be used
multiple times to achieve the settings you want for your drives. The default
is to have no user or group names.
o FullAlertDelay = [drives:] nn
This parameter specifies how many minutes to wait before sending another
alert for a Directory Limit that was previously reached. If a Directory
limit is reached more than once within the delay period, an alert is sent
only for the first occurrence. This parameter is used to cut down on the
number of alerts that can be generated when there is a lot of disk activity
and the Directory Limit is reached several times. This line can be used
multiple times to achieve the settings you want for your drives. The default
is 10 minutes on all drives.
o DirFullAlertUser = [drives:] yes|no
This parameter specifies whether to send an alert to the user whose request
failed because a Directory Limit was reached. This line can be used multiple
times to achieve the settings you want for your drives. The default is yes
for all drives.
ΓòÉΓòÉΓòÉ 10.4. 386 HPFS Caching ΓòÉΓòÉΓòÉ
The 386 HPFS cache (CACHE386) is initialized by a RUN statement in the
CONFIG.SYS file. The RUN statement has the following format:
RUN=x:\IBMLAN\NETPROG\CACHE386.EXE [/STATS: value]
[/OPTIONS:d:]
[/LAZY:d:value]
[/MAXAGE:d:value]
[/BUFFERIDLE:d:value]
where
x: Specifies the drive letter where LAN Server is installed.
/STATS Displays cache statistics. The value variable can be set to
CLEAR or DYNAMIC. If value is CLEAR, the current statistics
are reset. If value is DYNAMIC, the statistics displayed are
updated approximately once per second. Press Ctrl+C to stop
displaying statistics that are dynamically updated.
/OPTIONS Displays current configuration parameters. If no drive is
specified, the options for all the drives are displayed.
/LAZY Enables and disables lazy-writing for the specified drive.
Warning: If you set the /LAZY option to ON, always run
shutdown from the desktop before turning off your
workstation. Failure to do so will cause loss of data if the
contents of the HPFS cache buffers have not been written to
the disk. For safety, and if performance is not a concern,
set the /LAZY option to OFF, which causes a write, through
the cache, to the disk.
If lazy-writing is enabled, the contents of the cache are
only written to disk during disk idle time. If no drive is
specified, lazy-writing is either enabled or disabled for all
drives serviced by the HPFS. If value is OFF, lazy-writing
is disabled. If value is ON, lazy-writing is enabled. The
default is ON.
/MAXAGE Specifies the maximum time, in milliseconds, that a dirty
cache block for a drive can be in memory before it is flushed
(written to disk). The value can be from 0 through 1000000,
with a default value of 5000. A value between 1000 and 20000
is recommended. The /MAXAGE value takes precedence over the
/BUFFERIDLE value. To ensure the effectiveness of
lazy-writes, specify a greater value for the /MAXAGE
parameter than for the /BUFFERIDLE parameter. The /LAZY
option must be set to ON for the /MAXAGE parameter to be
effective.
/BUFFERIDLE Specifies the minimum time, in milliseconds, that a dirty
cache block for a drive must be idle before it will be
written opportunistically when the disk subsystem is idle.
The value can be from 0 through 500000, with a default value
of 500. A value between 100 and 1000 is recommended. The
/MAXAGE value takes precedence over the /BUFFERIDLE value.
To ensure the effectiveness of lazy-writes, specify a greater
value for the /MAXAGE parameter than for the /BUFFERIDLE
parameter. The /LAZY option must be set to ON for the
/BUFFERIDLE parameter to be effective.
Note: The size of the cache is specified on the IFS statement for the
386 HPFS. See the online LAN Server Commands and Utilities for further
information on the NET RUN statement.
ΓòÉΓòÉΓòÉ 10.5. Local Security Support ΓòÉΓòÉΓòÉ
On 386 HPFS servers with Local Security installed, all processes are subject to
file access permissions. While a process is running, different users may log
on and log off locally. Each time a user logs off locally, the process loses
the permissions granted to that user and has only the permissions given to the
group LOCAL. When another user logs on, the active process gains the
permissions given to that user, in addition to the permissions granted to the
group LOCAL.
Local Security is initialized by the PROTSHELL statement in the CONFIG.SYS
file. The PROTSHELL statement has the following format:
PROTSHELL=path\SECURESH.EXE [/N] [/F:pathname] shellcmd
where:
path Specifies the path to the SECURESH.EXE file. If the IBMLAN
directory is installed on C:\, the default path would be
C:\IBMLAN\NETPROG.
/N Indicates that the system should not be put in secure mode. The /N
option allows consistent behavior in the processing of the
PRIVINIT.CMD file without forcing the user to use two completely
different PROTSHELL statements in the CONFIG.SYS file. If /N is
specified, all processes in the system are considered privileged.
The default does not specify this option.
/F Specifies a path and file name other than \PRIVINIT.CMD as the
command file containing OS/2 commands to start privileged
processes. The default does not specify this option.
shellcmd Specifies the user shell program and the associated arguments for
the shell program. An example value for shellcmd is:
C:\OS2\PMSHELL.EXE.
Omitting SECURESH.EXE from the PROTSHELL statement in the CONFIG.SYS file and
just starting the normal user shell does not secure the file system. Instead,
the workstation runs in unsecured mode. Therefore, the CONFIG.SYS file must be
a protected file to prevent unprivileged users from editing it. If
SECURESH.EXE is not included on the PROTSHELL statement, the \PRIVINIT.CMD file
will not be executed.
ΓòÉΓòÉΓòÉ 10.6. DOS LAN Services Support ΓòÉΓòÉΓòÉ
The CONFIG.SYS file parameter for DOS LAN Services support is:
o lastdrive
The lastdrive parameter specifies the last valid drive letter that DOS can
accept. Each unused drive letter requires approximately 80 bytes of memory.
Default value: Z
Minimum value: F or the last letter assigned plus two positions.
Maximum value: Z
Refer to the IBM OS/2 LAN Server Version 4.0 Network Administrator Reference
Volume 1: Planning, Installation, and Configuration for more information about
the LAN Support Program 1.35. Increase sessions and commands using the install
program. Default may not be enough. You may need to increase parameters and
modify NetBIOS parameters.
ΓòÉΓòÉΓòÉ 11. Configuration Files ΓòÉΓòÉΓòÉ
The tables in this appendix contain information on parameter ranges and default
values for the CONFIG.SYS and PROTOCOL.INI files. Use these tables as a
reference when you make changes to the IBMLAN.INI, NETWORK.INI, or CONFIG.SYS
file. If any of the parameters are changed, you should run through the
resource-constraint calculations to ensure that the modified configuration
starts properly.
Note to non-U.S. users:
These samples are for U.S. versions.
ΓòÉΓòÉΓòÉ 11.1. CONFIG.SYS Parameters ΓòÉΓòÉΓòÉ
The following table describes the parameter values in the CONFIG.SYS file. The
parameters are listed in alphabetic order.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 27. CONFIG.SYS Parameter Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé MINIMUM Γöé MAXIMUM Γöé DEFAULT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé BUFFERS Γöé Γöé Γöé 60 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DISKCACHE Γöé 64KB, 1 Γöé 14.4MB, Γöé 64KB, 7 Γöé
Γöé Γöé Γöé 128 Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LASTDRIVE Γöé F Γöé Z Γöé Z Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MEMMAN Γöé Γöé Γöé Swap, Protect Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SWAPPATH Γöé Γöé Γöé C:\OS2\SYSTEM 2048 2048 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé THREADS Γöé 256 Γöé 4095 Γöé 256 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 11.2. PROTOCOL.INI File for OS/2 LAN Server ΓòÉΓòÉΓòÉ
[PROT_MAN]
DRIVERNAME = PROTMAN$
[IBMLXCFG]
NETBEUI_nif = NETBEUI.NIF
TCPBEUI_nif = TCPBEUI.nif
TCPIP_nif = TCPIP.NIF
IBMTOK_nif = IBMTOK.nif
[NetBIOS]
DriverName = netbios$
ADAPTER0 = netbeui$,0
ADAPTER1 = tcpbeui$,1
[NETBEUI_nif]
DriverName = netbeui$
Bindings = IBMTOK_nif
ETHERAND_TYPE = "I"
USEADDRREV = "YES"
OS2TRACEMASK = 0x0
SESSIONS = 130
NCBS = 225
NAMES = 21
SELECTORS = 15
USEMAXDATAGRAM = "NO"
ADAPTRATE = 1000
WINDOWERRORS = 0
MAXDATARCV = 4168
TI = 30000
T1 = 1000
T2 = 200
MAXIN = 1
MAXOUT = 1
NetBIOSTIMEOUT = 500
NetBIOSRETRIES = 2
NAMECACHE = 1000
RNDOPTION = 0
PIGGYBACKACKS = 1
DATAGRAMPACKETS = 10
PACKETS = 350
LOOPPACKETS = 8
PIPELINE = 5
MAXTRANSMITS = 6
MINTRANSMITS = 2
DLCRETRIES = 10
FCPRIORITY = 5
NETFLAGS = 0x0
[TCPBEUI_nif]
DriverName = tcpbeui$
Bindings = ,IBMTOK_nif
OS2TRACEMASK = 0x0
SESSIONS = 40
NCBS = 95
NAMES = 21
SELECTORS = 5
USEMAXDATAGRAM = "NO"
NetBIOSTIMEOUT = 500
NetBIOSRETRIES = 2
NAMECACHE = 0
PRELOADCACHE = "NO"
NAMESFILE = 0
DATAGRAMPACKETS = 20
PACKETS = 50
[TCPIP_nif]
DriverName = TCPIP$
Bindings = ,IBMTOK_nif
[IBMTOK_nif]
DriverName = IBMTOK$
ADAPTER = "PRIMARY"
MAXTRANSMITS = 6
RECVBUFS = 2
RECVBUFSIZE = 256
XMITBUFS = 1
ΓòÉΓòÉΓòÉ 11.3. PROTOCOL.INI File for DOS LAN Services ΓòÉΓòÉΓòÉ
[network.setup]
version=0x3100
netcard=ibm$ibmtra,1,IBM$IBMTRA
transport=ibm$netbeui,IBM$NETBEUI
lana0=ibm$ibmtra,1,ibm$netbeui
[protman]
DriverName=PROTMAN$
PRIORITY=ibm$NETBEUI
[IBM$IBMTRA]
DriverName=IBMTOK$
[IBM$NETBEUI]
DriverName=netbeui$
SESSIONS=20
NCBS=20
BINDINGS=IBM$IBMTRA
LANABASE=0
ΓòÉΓòÉΓòÉ 12. File Examples ΓòÉΓòÉΓòÉ
Examples of IBMLAN.INI files follow for the OS/2 requester, the Entry server,
and the Advanced server. Additionally, an Advanced server with HPFS 386 comes
with the HPFS386.INI file. In these INI files, explanations and comments are
indicated by a semicolon (;) in the first column.
ΓòÉΓòÉΓòÉ 12.1. IBMLAN.INI File Parameters ΓòÉΓòÉΓòÉ
The following two-part table describes the parameter values for the IBMLAN.INI
file. The parameters are listed in alphabetic order.
Note to non-U.S. users:
These samples are for U.S. versions.
o Table 28. IBMLAN.INI Parameter Values (Part 1)
o Table 28. IBMLAN.INI Parameter Values (Part 2)
ΓòÉΓòÉΓòÉ 12.1.1. Table 28. IBMLAN.INI Parameter Values (Part 1) ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 28. IBMLAN.INI Parameter Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé SECTION Γöé MINIMUM Γöé MAXIMUM Γöé DEFAULT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ACCESSALERT Γöé Server Γöé 0 Γöé 65535 Γöé 5 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ALERTER Γöé Services Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ALERTNAMES Γöé Server Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ALERTSCHED Γöé Server Γöé 0 Γöé 65535 Γöé 5 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé AUDITING Γöé Server Γöé Γöé Γöé No Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé AUTODISCONNECT Γöé Server, Γöé -1 Γöé 65535 Γöé 120 Γöé
Γöé Γöé Peer Γöé -1 Γöé -1 Γöé -1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé AUTOPATH Γöé Server Γöé Γöé Γöé See note 7 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé AUTOPROFILE Γöé Server Γöé Γöé Γöé Load Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé BATTERYTIME Γöé UPS Γöé 0 Γöé 28800 Γöé 60 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CHARCOUNT Γöé Requester Γöé 0 Γöé 65535 Γöé 16 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CHARTIME Γöé Requester Γöé -1 Γöé 65535000 Γöé 250 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CHARWAIT Γöé Requester Γöé 0 Γöé 65535 Γöé 3600 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CLEANUP Γöé LSserver Γöé Γöé Γöé Yes Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CMDFILE Γöé UPS Γöé Γöé Γöé " " Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé COMPUTERNAME Γöé Requester Γöé 0 Γöé 65535 Γöé 3600 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé CONFIGFILE Γöé Remoteboot Γöé Γöé Γöé DOSBB.CNF Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DEVICENAME Γöé UPS Γöé Γöé Γöé UPS_DEV Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DISKALERT Γöé Server Γöé 0 Γöé 65535 Γöé 5000 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé DOMAIN Γöé Requester Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé ERRORALERT Γöé Server Γöé 0 Γöé 65535 Γöé 5 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé EXPORTLIST Γöé Replicator Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé EXPORTPATH Γöé Replicator Γöé Γöé Γöé See note 2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé GUARDTIME Γöé DCDB Γöé 0 Γöé INTERVAL/2 Γöé 2 Γöé
Γöé Γöé Replicator, Γöé Γöé Γöé Γöé
Γöé Γöé Replicator Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé GUESTACCT Γöé Server Γöé Γöé Γöé GUEST Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IMPORTLIST Γöé Replicator Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé IMPORTPATH Γöé Replicator Γöé Γöé Γöé See note 2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé INTERVAL Γöé DCDB Γöé 1 Γöé 60 Γöé 5 Γöé
Γöé Γöé Replicator, Γöé Γöé Γöé Γöé
Γöé Γöé Replicator Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé KEEPCONN Γöé Requester Γöé 1 Γöé 65535 Γöé 600 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé KEEPSEARCH Γöé Requester Γöé 1 Γöé 65535 Γöé 600 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LOGFILE Γöé Messenger Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LOGON Γöé DCDB Γöé Γöé Γöé Γöé
Γöé Γöé Replicator, Γöé Γöé Γöé Γöé
Γöé Γöé Replicator Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LOGONALERT Γöé Server Γöé 0 Γöé 65535 Γöé 5 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé LSSERVER Γöé Services Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXAUDITLOG Γöé Server Γöé 0 Γöé 65535 Γöé 100 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXCHDEVJOB Γöé Server Γöé 0 Γöé 65535 Γöé 6 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXCHDEVQ Γöé Server Γöé 0 Γöé 65535 Γöé 2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXCHDEVS Γöé Server Γöé 0 Γöé 16 Γöé 2 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXCMDS Γöé Requester Γöé 5 Γöé 255 Γöé 16 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXCONNECTIONS Γöé Server Γöé 1 Γöé 2000 Γöé 128 Γöé
Γöé Γöé (see note 1) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXERRORLOG Γöé Requester Γöé 2 Γöé disk size Γöé 100 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXLOCKS Γöé Server Γöé 1 Γöé 8000 Γöé 64 Γöé
Γöé Γöé (see note 1) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXOPENS Γöé Server Γöé 1 Γöé 8000 Γöé 50 Γöé
Γöé Γöé (see note 1) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXRUNS Γöé Netrun Γöé 1 Γöé 10 Γöé 3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXSEARCHES Γöé Server Γöé 1 Γöé 1927 Γöé 50 Γöé
Γöé Γöé (see note 1) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXSESSOPENS Γöé Server Γöé 1 Γöé 8000 Γöé 80 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXSESSREQS Γöé Server Γöé 1 Γöé 65535 Γöé 50 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXSESSVCS Γöé Server Γöé 1 Γöé 1 Γöé 1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXSHARES Γöé Server Γöé 2 Γöé 500 Γöé 16 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXTHREADS Γöé Requester Γöé 10 Γöé 254 Γöé 10 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXTHREADS Γöé Remoteboot Γöé 0 Γöé See note 9 Γöé 10 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXUSERS Γöé Server Γöé 1 Γöé 1000 Γöé 45 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MAXWRKCACHE Γöé Requester Γöé 0 Γöé 640 Γöé 64 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MESSDELAY Γöé UPS Γöé 0 Γöé 120 Γöé 5 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MESSENGER Γöé Services Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MESSTIME Γöé UPS Γöé 30 Γöé 300 Γöé 120 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé MULTILOGON Γöé wrkheuristic - Γöé Γöé Γöé Yes Γöé
Γöé Γöé 40 Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NETIOALERT Γöé Server Γöé 0 Γöé 65535 Γöé 5 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NETLOGON Γöé Services Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NETRUN Γöé Services Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NETx= Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé x (net Γöé Networks Γöé 1 Γöé 5 Γöé 1 Γöé
Γöé statement Γöé Γöé Γöé Γöé Γöé
Γöé number) Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé drivername$ Γöé Networks Γöé Γöé Γöé netbeui$ Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé a (adapter Γöé Networks Γöé 0 Γöé 3 Γöé 0 Γöé
Γöé used) Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé drivertype Γöé Networks Γöé Γöé Γöé LM10 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé x1 (sessions) Γöé Networks Γöé 0 Γöé 254 Γöé 16 Γöé
Γöé for a Γöé Γöé Γöé Γöé Γöé
Γöé requester Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé x1 (sessions) Γöé Networks Γöé 0 Γöé 254 Γöé 32 Γöé
Γöé for a server Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé x2 (commands) Γöé Networks Γöé 0 Γöé 255 Γöé 16 Γöé
Γöé for a Γöé Γöé Γöé Γöé Γöé
Γöé requester Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé x2 (commands) Γöé Networks Γöé 0 Γöé 255 Γöé 50 Γöé
Γöé for a server Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé x3 (names) Γöé Networks Γöé 0 Γöé 254 Γöé 14 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMALERTS for a Γöé Requester Γöé 3 Γöé 200 Γöé 12 Γöé
Γöé requester Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMALERTS for a Γöé Requester Γöé 5 Γöé 200 Γöé 12 Γöé
Γöé server Γöé Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMBIGBUF Γöé Server Γöé 0 Γöé 80 Γöé 12 Γöé
Γöé Γöé (see note 1) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMCHARBUF Γöé Requester Γöé 0 Γöé 15 Γöé 10 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMDGRAMBUF Γöé Requester Γöé 8 Γöé 112 Γöé 14 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMFILETASKS Γöé Server Γöé 1 Γöé 8 Γöé 1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMREQBUF Γöé Server Γöé 5 Γöé 408 Γöé 36 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMSERVICES Γöé Requester Γöé 4 Γöé 256 Γöé 12 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NUMWORKBUF Γöé Requester Γöé 3 Γöé 50 Γöé 15 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé OTHDOMAINS Γöé Requester Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PASSWORD Γöé DCDB Γöé Γöé Γöé Γöé
Γöé Γöé Replicator, Γöé Γöé Γöé Γöé
Γöé Γöé Replicator Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PRINTBUFTIME Γöé Requester Γöé 0 Γöé 65535 Γöé 90 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PULSE Γöé Netlogon Γöé 60 Γöé 3600 Γöé 60 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PULSE Γöé DCDB Γöé 1 Γöé 10 Γöé 3 Γöé
Γöé Γöé Replicator, Γöé Γöé Γöé Γöé
Γöé Γöé Replicator Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RANDOM Γöé DCDB Γöé 1 Γöé 120 Γöé 60 Γöé
Γöé Γöé Replicator, Γöé Γöé Γöé Γöé
Γöé Γöé Replicator Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RANDOMIZE Γöé Netlogon Γöé 5 Γöé 120 Γöé 30 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RECHARGE Γöé UPS Γöé 5 Γöé 250 Γöé 100 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé REMOTEBOOT Γöé Services Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé REPLICATE Γöé Replicator Γöé Γöé Γöé IMPORT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé REPLICATOR Γöé Services Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé REQUESTER Γöé Services Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RPLn Γöé Remoteboot Γöé Γöé Γöé See note 4 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RPLDIR Γöé Remoteboot Γöé Γöé Γöé See note 5 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé RUNPATH Γöé Netrun Γöé Γöé Γöé C:\ Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 12.1.2. Table 28. IBMLAN.INI Parameter Values (Part 2) ΓòÉΓòÉΓòÉ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Table 28. IBMLAN.INI Parameter Values Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PARAMETER Γöé SECTION Γöé MINIMUM Γöé MAXIMUM Γöé DEFAULT Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SCANPAUSE Γöé Netlogon Γöé 0 Γöé 15 Γöé 0 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SCANPERIOD Γöé Netlogon Γöé 0 Γöé 1440 Γöé 15 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SCANTIME Γöé Netlogon Γöé 0:00 Γöé 23:59 Γöé 0:00 (mid- Γöé
Γöé Γöé Γöé Γöé Γöé night) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SCRIPTS Γöé Netlogon Γöé Γöé Γöé See note 3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SECURITY Γöé Peer Γöé Γöé Γöé User Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SERVER Γöé Services Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SESSTIMEOUT Γöé Requester Γöé 10 Γöé 65535 Γöé 45 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SIGNALS Γöé UPS Γöé Γöé Γöé 100 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SIZALERTBUF Γöé Alerter Γöé 512 Γöé 16384 Γöé 3072 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SIZERROR Γöé Requester Γöé 256 Γöé 4096 Γöé 1024 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SIZMESSBUF Γöé Messenger Γöé 512 Γöé 62000 Γöé 4096 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SIZREQBUF Γöé Server Γöé 1024 Γöé 32768 Γöé 4096 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SIZWORKBUF Γöé Requester Γöé 1024 Γöé 16384 Γöé 4096 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SRVANNDELTA Γöé Server Γöé 0 Γöé 65535 Γöé 3000 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SRVANNOUNCE Γöé Server Γöé 0 Γöé 65535 Γöé 60 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SRVHEURISTICS Γöé Server Γöé Γöé Γöé Γöé
Γöé Γöé (see note 1) Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SRVHIDDEN Γöé Server Γöé Γöé Γöé No Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SRVNETS Γöé Server Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SRVPIPES Γöé LSserver Γöé 1 Γöé 20 Γöé 3 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé SRVSERVICES Γöé Server Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TIMESOURCE Γöé Server Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé TRYUSER Γöé DCDB Γöé no Γöé yes Γöé yes Γöé
Γöé Γöé Replicator, Γöé Γöé Γöé Γöé
Γöé Γöé Replicator Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé UPDATE Γöé Netlogon Γöé no Γöé yes Γöé yes Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé UPS Γöé Services Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé USERNAME Γöé Peer Γöé Γöé Γöé See note 8 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé VOLTLEVELS Γöé UPS Γöé Γöé Γöé 100 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé WRKHEURISTICS Γöé Requester Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé WRKNETS Γöé Requester Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé WRKSERVICES Γöé Requester Γöé Γöé Γöé net1 Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé NOTES: Γöé
Γöé Γöé
Γöé 1. Values given are for Server Section - Entry Package Function. If you Γöé
Γöé have the Advanced package, some values will be different. See Server Γöé
Γöé Section - Advanced Package Function for more information. Γöé
Γöé 2. Default value is: C:\IBMLAN\REPL\EXPORT Γöé
Γöé 3. Default value is: C:\IBMLAN\REPL\IMPORT Γöé
Γöé 4. Default value is: C:\IBMLAN\REPL\IMPORT\SCRIPTS Γöé
Γöé 5. Default value is: RPLNET1.DLL RPLNET2.DLL RPLOEM.DLL Γöé
Γöé 6. Default value is: C:\IBMLAN\RPL Γöé
Γöé 7. Default value is: C:\IBMLAN\PROFILES\SRVAUTO.PRO Γöé
Γöé 8. Default values are: Γöé
Γöé ALERTER - SERVICES\ALERTER.EXE Γöé
Γöé GENALERT - SERVICES\GENALERT.EXE Γöé
Γöé LSSERVER - SERVICES\LSSERVER.EXE Γöé
Γöé MESSENGER - SERVICES\MSRVINIT.EXE Γöé
Γöé NETLOGON - SERVICES\NETLOGON.EXE Γöé
Γöé NETRUN - SERVICES\RUNSERVR.EXE Γöé
Γöé REMOTEBOOT - SERVICES\RPLSERVR.EXE Γöé
Γöé DCDB REPLICATOR - SERVICES\DCDBREPL.EXE Γöé
Γöé REPLICATOR - SERVICES\REPLICAT.EXE Γöé
Γöé REQUESTER - SERVICES\WKSTA.EXE Γöé
Γöé SERVER - SERVICES\NETSVINI.EXE Γöé
Γöé TIMESOURCE - SERVICES\TIMESRC.EXE Γöé
Γöé UPS - SERVICES\UPS.EXE Γöé
Γöé 9. Maximum value is the maximum amount allowed by the system. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 12.2. IBMLAN.INI for the OS/2 Requester ΓòÉΓòÉΓòÉ
; OS/2 LAN Requester initialization file
[networks]
; This information is read by the redirector at device initialization time.
[requester]
COMPUTERNAME =
DOMAIN = DOMAIN
; The following parameters generally do not need to be
; changed by the user.
charcount = 16
chartime = 250
charwait = 3600
keepconn = 600
keepsearch = 600
maxcmds = 16
maxerrorlog = 100
maxthreads = 10
maxwrkcache = 64
numalerts = 12
numcharbuf = 10
numservices = 7
numworkbuf = 15
numdgrambuf = 14
othdomains =
printbuftime = 90
sesstimeout = 45
sizcharbuf = 512
sizerror = 1024
sizworkbuf = 4096
useallmem = no
; The wrkheuristics parameter sets a variety of requester fine-tuning
; options. Brief descriptions are provided here for each digit. More
; complete descriptions, along with explanations of relationships between
; digits can be found in the LAN Server Network Administrator
; Reference: Performance Tuning.
;
; When not otherwise specified, a value of 0 means off (inactive) and 1 means
; on (active).
;
; 0 opportunistic locking of files (default is 1)
; 1 performance optimization for batch (.CMD) files (default is 1)
; 2 asynchronous unlock and asynchronous write-unlock
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 3 asynchronous close and asynchronous write-close
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 4 buffer all named pipes and serial devices (default is 1)
; 5 combined read-lock and write-unlock
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 6 open and read optimization (default is 1)
; 7 reserved
; 8 use of the chain-send NetBIOS NCB
; 0 = never
; 1 = when a server's buffer is larger than the workstations buffer
; 2 = always (default)
; 9 buffer small read and write requests until the buffer is full
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 10 buffer mode
; 0 = always read buffer size amount of data if the request is smaller
; than the buffer size (sizworkbuf) and data is being read
; sequentially
; 1 = use full buffer if file is open for reading and writing
; 2 = use full buffer if reading and writing sequentially
; 3 = buffer all requests smaller than the buffer size (if hits occur)
; (default)
; 11 RAW read and RAW write SMB protocols (default is 1)
; 12 RAW read-ahead buffer (default is 1)
; 13 RAW write-behind buffer (default is 1)
; 14 read multiplexing SMB protocols (default is 1)
; 15 write multiplexing SMB protocols (default is 1)
; 16 use of big buffers for large core (non-RAW) reads (default is 1)
; 17 same-size read-ahead or read-to-sector boundary (default is 1)
; 18 same-size small record write-behind or write-to-sector boundary
; (default is 0)
; 19 reserved and must be 0
; 20 flush pipes and devices on a DosBufReset or DosClose operation
; 0 = Flush only files and devices opened by the caller. Spin until
; flushed. Wait for confirmation before processing with other
; tasks. (default)
; 1 = Flush only files and devices opened by the caller. Flush only
; once. Do not wait for confirmation.
; 2 = Flush all files and all input and output of short-term pipes
; and devices. Spin until flushed.
; 3 = Flush all files and all input and output of short-term pipes
; and devices. Flush only once.
; 4 = Flush all files and all input and output of all pipes and devices.
; Spin until flushed.
; 5 = Flush all files and all input and output of all pipes and devices.
; Flush only once.
; 21 LAN Server encryption of passwords (default is 1)
; 22 control log entries for multiple occurrences of an error
; 0 = log all occurrences (default)
; 1-9 = limit occurrences that are logged (1-9 define size of table
; that is used to track errors)
; 23 buffer all files opened with deny-write sharing mode (default is 1)
; 24 buffer all files opened with the read-only attribute set (default is 1)
; 25 read ahead when opening for execution (default is 1)
; 26 handle the interrupt (ctrl+c) key
; 0 = allow no interrupts
; 1 = allow interrupts only on long-term operations
; 2 = always allow interrupts (default)
; 27 force correct open mode when creating files on a core server (reserved
; for DBCS users) (default is 1)
; 28 NetBIOS NoAck mode
; 0 = NoAck is disabled.
; 1 = NoAck is set on send only. (default)
; 2 = NoAck is set on receive only.
; 3 = NoAck is set on send and receive.
; 29 send data along with SMB write-block RAW requests (default is 1)
; 30 send a message to the screen when the requester logs an error
; 0 = never
; 1 = on write-fault errors only (no time out) (default)
; 2 = on write-fault and internal errors only (no time out)
; 3 = on all errors (no time out)
; 4 = reserved
; 5 = on write-fault errors only (time out)
; 6 = on write-fault and internal errors only (time out)
; 7 = on all errors (time out)
; 31 reserved
; 32 behavior of DosBufReset on a redirected file (not pipes or devices).
; When the call to the API returns, the data in the buffer has been
; handled as follows:
; 0 = Changed data in the buffer was sent from the requester to the
; server. The server has written the data to disk.
; 1 = Changed data in the buffer was sent from the requester to the
; server. The server has not yet written the data to disk.
; 2 = DosBufReset was ignored. (default)
; 33 time interval for performing logon validation from the domain
; controller
; 0 = 5 seconds 4 = 60 seconds 8 = 8 minutes
; 1 = 15 seconds (default) 5 = 90 seconds 9 = 15 minutes
; 2 = 30 seconds 6 = 2 minutes
; 3 = 45 seconds 7 = 4 minutes
; 34 date validation
; 0 = PCLP date format (default)
; 1 = MSNET date format
; 2 = assume date is correct
; 35 free disk space reported to DOS and Windows applications
; 0 = return true value (default)
; 1 = return a value less than two gigabytes
; 36 time and date synchronization with the domain controller at logon
; (default is 1)
; 37 type of verification for the LAN Server logon
; 0 = no verification
; 1 = verify against local NET.ACC
; 2 = verify against domain NET.ACC (default)
; 38 display warning messages for the LAN Server logon
; 0 = do not display warning messages
; 1 = display all warning messages (default)
; 2 = do not display LAN Server specific warning messages
; 39 buffer all files opened in compatibility mode
; 0 = buffer only files opened for read access in compatibility mode
; 1 = buffer all files opened in compatibility mode (default)
; 40 allow a user to logon multiple times in the same domain (default is 1)
;
; The next lines help you to locate bits in the wrkheuristics entry.
; 1 2 3 4
; 01234567890123456789012345678901234567890
wrkheuristics = 11111111213111111100010111201112210012111
wrkservices = MESSENGER,PEER
wrknets =
[messenger]
logfile = messages.log
sizmessbuf = 4096
[peer]
security = user
username =
auditing = no
; The following parameters generally do not need to be
; changed by the user. NOTE : srvnets= is represented in
; the server info struct as a 16-bit lan mask. Srvnet names
; are converted to indexes within [networks] for the named
; nets.
guestacct = guest
autodisconnect = -1
maxauditlog = 100
maxchdevjob = 2
maxchdevs = 1
maxconnections = 26
maxlocks = 64
maxopens = 128
maxsearches = 50
maxsessopens = 80
maxsessreqs = 25
maxsessvcs = 1
maxshares = 16
maxusers = 5
numbigbuf = 4
numfiletasks = 1
numreqbuf = 10
sizreqbuf = 4096
; The srvheuristics parameter sets a variety of server fine-tuning
; options. Brief descriptions are provided here for each digit. More
; complete descriptions, along with explanations of relationships between
; digits can be found in Chapters 2 and 3.
;
; When not otherwise specified, a value of 0 means off (inactive) and 1 means
; on (active).
;
; 0 opportunistic locking of files (default is 1)
; 1 read-ahead when the requester is performing sequential access
; 0 = do not use read-ahead
; 1 = use single read-ahead thread (default)
; 2 = use asynchronous read-ahead thread
; 2 write-behind (default is 1)
; 3 use of the chain-send NetBIOS NCB (default is 1)
; 4 check all incoming SMBs for correct format (default is 0)
; 5 support FCB opens (default is 1)
; 6 set priority of server (default is 4)
; 0-9 = 0 is highest priority, 9 is lowest priority
; 7 automatically allocate additional memory for directory searches
; (default is 1)
; 8 write records to the audit log only when the scavenger wakes up
; (default is 1)
; 9 do full buffering when a file is opened with deny-write sharing mode
; (default is 1)
; 10 set the interval for the scavenger to wake up
; 0 = 5 seconds 4 = 25 seconds 8 = 45 seconds
; 1 = 10 seconds (default) 5 = 30 seconds 9 = 50 seconds
; 2 = 15 seconds 6 = 35 seconds
; 3 = 20 seconds 7 = 40 seconds
; 11 allow compatibility-mode opens of certain types of files by translating
; them to sharing mode opens with deny-none
; 0 = Always use compatibility-mode opens.
; 1 = Use deny-none sharing mode if read-only access to .EXE or .COM
; files.
; 2 = Use deny-none sharing mode if read-only access to .EXE or .COM
; files. Use deny-write sharing mode if read-only access to .BAT
; files is requested.
; 3 = Use deny-none sharing mode on all compatibility-mode opens.
; (default)
; 12 allow DOS LAN Services workstations to use a second NetBIOS session when
; sending printer requests (default is 1)
; 13 number of 64KB buffers used for read-ahead
; 0-9 = number of buffers (default is 1)
; 14 convert incoming path specifications into most basic format (default is 0)
; 15 Oplock Timeout and NetBIOS Acknowledgment Timeout (default is 0)
; 0 = 35 second Oplock Timeout; 34 second NetBIOS Acknowledgment Timeout
; 1 = 70 second Oplock Timeout; 69 second NetBIOS Acknowledgment Timeout
; 2 = 140 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 3 = 210 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 4 = 280 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 5 = 350 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 6 = 420 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 7 = 490 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 8 = 560 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 9 = 640 second Oplock Timeout; no NetBIOS Acknowledgment Timeout
; 16 validate IOCTLs (default is 1)
; 17 how long the server maintains unused, dynamic big buffers before freeing
; the memory.
; 0 = 0 seconds 4 = 5 minutes 8 = 1 hour
; 1 = 1 second 5 = 10 minutes 9 = indefinitely
; 2 = 10 seconds 6 = 20 minutes
; 3 = 1 minute (default) 7 = 40 minutes
; 18 how long the server waits after failing to allocate a big buffer before
; trying again.
; 0 = 0 seconds 3 = 1 minute (default)
; 1 = 1 second 4 = 5 minutes
; 2 = 10 seconds 5 = 10 minutes
; 19 RAW read and RAW write SMB protocols (default is 1)
; 20 server responds to announcement requests (default is 1)
;
; The next lines help you to locate bits in the srvheuristics entry.
; 1 2
; 012345678901234567890
srvheuristics = 111101411113110013311
SRVSERVICES =
srvnets =
[replicator]
replicate = IMPORT
importpath = c:\ibmlan\repl\import
tryuser = yes
password =
[services]
; Correlates name of service to pathname of service program.
; The pathname must be either
; 1) an absolute path (including the drive specification)
; OR
; 2) a path relative to the IBMLAN root
messenger = services\msrvinit.exe
peer = services\netpsini.exe
replicator = services\replicat.exe
requester = services\wksta.exe
ΓòÉΓòÉΓòÉ 12.3. IBMLAN.INI for Entry Server ΓòÉΓòÉΓòÉ
; OS/2 LAN Server Entry initialization file
[networks]
; This information is read by the redirector at device initialization time.
[requester]
COMPUTERNAME =
DOMAIN =
; The following parameters generally do not need to be
; changed by the user.
charcount = 16
chartime = 250
charwait = 3600
keepconn = 600
keepsearch = 600
maxcmds = 16
maxerrorlog = 100
maxthreads = 10
maxwrkcache = 64
numalerts = 12
numcharbuf = 10
numservices = 16
numworkbuf = 15
numdgrambuf = 14
othdomains =
printbuftime = 90
sesstimeout = 45
sizcharbuf = 512
sizerror = 1024
sizworkbuf = 4096
useallmem = no
; The next lines help you to locate bits in the wrkheuristics entry.
; 1 2 3 4
; 01234567890123456789012345678901234567890
wrkheuristics = 11111111213111111100010111201112210012111
; The wrkheuristics parameter sets a variety of requester fine-tuning
; options. Brief descriptions are provided here for each digit. More
; complete descriptions, along with explanations of relationships between
; digits can be found in Chapters 2 and 3.
;
; When not otherwise specified, a value of 0 means off (inactive) and 1 means
; on (active).
;
; 0 opportunistic locking of files (default is 1)
; 1 performance optimization for batch (.CMD) files (default is 1)
; 2 asynchronous unlock and asynchronous write-unlock
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 3 asynchronous close and asynchronous write-close
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 4 buffer all named pipes and serial devices (default is 1)
; 5 combined read-lock and write-unlock
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 6 open and read optimization (default is 1)
; 7 reserved
; 8 use of the chain-send NetBIOS NCB
; 0 = never
; 1 = when a server's buffer is larger than the workstations buffer
; 2 = always (default)
; 9 buffer small read and write requests until the buffer is full
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 10 buffer mode
; 0 = always read buffer size amount of data if the request is smaller
; than the buffer size (sizworkbuf) and data is being read
; sequentially
; 1 = use full buffer if file is open for reading and writing
; 2 = use full buffer if reading and writing sequentially
; 3 = buffer all requests smaller than the buffer size (if hits occur)
; (default)
; 11 RAW read and RAW write SMB protocols (default is 1)
; 12 RAW read-ahead buffer (default is 1)
; 13 RAW write-behind buffer (default is 1)
; 14 read multiplexing SMB protocols (default is 1)
; 15 write multiplexing SMB protocols (default is 1)
; 16 use of big buffers for large core (non-RAW) reads (default is 1)
; 17 same-size read-ahead or read-to-sector boundary (default is 1)
; 18 same-size small record write-behind or write-to-sector boundary
; (default is 0)
; 19 reserved and must be 0
; 20 flush pipes and devices on a DosBufReset or DosClose operation
; 0 = Flush only files and devices opened by the caller. Spin until
; flushed. Wait for confirmation before processing with other
; tasks. (default)
; 1 = Flush only files and devices opened by the caller. Flush only
; once. Do not wait for confirmation.
; 2 = Flush all files and all input and output of short-term pipes
; and devices. Spin until flushed.
; 3 = Flush all files and all input and output of short-term pipes
; and devices. Flush only once.
; 4 = Flush all files and all input and output of all pipes and devices.
; Spin until flushed.
; 5 = Flush all files and all input and output of all pipes and devices.
; Flush only once.
; 21 LAN Server encryption of passwords (default is 1)
; 22 control log entries for multiple occurrences of an error
; 0 = log all occurrences (default)
; 1-9 = limit occurrences that are logged (1-9 define size of table
; that is used to track errors)
; 23 buffer all files opened with deny-write sharing mode (default is 1)
; 24 buffer all files opened with the read-only attribute set (default is 1)
; 25 read ahead when opening for execution (default is 1)
; 26 handle the interrupt (ctrl+c) key
; 0 = allow no interrupts
; 1 = allow interrupts only on long-term operations
; 2 = always allow interrupts (default)
; 27 force correct open mode when creating files on a core server (reserved
; for DBCS users) (default is 1)
; 28 NetBIOS NoAck mode
; 0 = NoAck is disabled.
; 1 = NoAck is set on send only. (default)
; 2 = NoAck is set on receive only.
; 3 = NoAck is set on send and receive.
; 29 send data along with SMB write-block RAW requests (default is 1)
; 30 send a message to the screen when the requester logs an error
; 0 = never
; 1 = on write-fault errors only (no time out) (default)
; 2 = on write-fault and internal errors only (no time out)
; 3 = on all errors (no time out)
; 4 = reserved
; 5 = on write-fault errors only (time out)
; 6 = on write-fault and internal errors only (time out)
; 7 = on all errors (time out)
; 31 reserved
; 32 behavior of DosBufReset on a redirected file (not pipes or devices).
; When the call to the API returns, the data in the buffer has been
; handled as follows:
; 0 = Changed data in the buffer was sent from the requester to the
; server. The server has written the data to disk.
; 1 = Changed data in the buffer was sent from the requester to the
; server. The server has not yet written the data to disk.
; 2 = DosBufReset was ignored. (default)
; 33 time interval for performing logon validation from the domain
; controller
; 0 = 5 seconds 4 = 60 seconds 8 = 8 minutes
; 1 = 15 seconds (default) 5 = 90 seconds 9 = 15 minutes
; 2 = 30 seconds 6 = 2 minutes
; 3 = 45 seconds 7 = 4 minutes
; 34 date validation
; 0 = PCLP date format (default)
; 1 = MSNET date format
; 2 = assume date is correct
; 35 free disk space reported to DOS and Windows applications
; 0 = return true value (default)
; 1 = return a value less than two gigabytes
; 36 time and date synchronization with the domain controller at logon
; (default is 1)
; 37 type of verification for the LAN Server logon
; 0 = no verification
; 1 = verify against local NET.ACC
; 2 = verify against domain NET.ACC (default)
; 38 display warning messages for the LAN Server logon
; 0 = do not display warning messages
; 1 = display all warning messages (default)
; 2 = do not display LAN Server specific warning messages
; 39 buffer all files opened in compatibility mode
; 0 = buffer only files opened for read access in compatibility mode
; 1 = buffer all files opened in compatibility mode (default)
; 40 allow a user to logon multiple times in the same domain (default is 1)
;
; The next lines help you to locate bits in the wrkheuristics entry.
; 1 2 3 4
; 01234567890123456789012345678901234567890
wrkheuristics = 11111111213111111100010111201112210012111
WRKSERVICES = MESSENGER
wrknets =
[messenger]
logfile = messages.log
sizmessbuf = 4096
[netlogon]
SCRIPTS = C:\IBMLAN\REPL\IMPORT\SCRIPTS
pulse = 60
update = yes
[replicator]
replicate = IMPORT
IMPORTPATH = C:\IBMLAN\REPL\IMPORT
tryuser = yes
password =
interval = 5
guardtime = 2
pulse = 3
random = 60
[dcdbrepl]
tryuser = yes
password =
interval = 5
guardtime = 2
pulse = 3
random = 60
[server]
alertnames =
auditing = no
autodisconnect = 120
maxusers = 32
; The following parameters generally do not need to be
; changed by the user. NOTE: srvnets= is represented in
; the server info struct as a 16-bit lan mask. Srvnet names
; are converted to indexes within [networks] for the named nets.
guestacct = guest
accessalert = 5
alertsched = 5
diskalert = 5000
erroralert = 5
logonalert = 5
maxauditlog = 100
maxchdevjob = 6
maxchdevq = 2
maxchdevs = 2
maxconnections = 128
maxlocks = 64
maxopens = 160
maxsearches = 150
maxsessopens = 80
maxsessreqs = 50
maxsessvcs = 1
maxshares = 64
netioalert = 5
numbigbuf = 6
numfiletasks = 1
numreqbuf = 48
sizreqbuf = 4096
srvanndelta = 3000
srvannounce = 60
; The srvheuristics parameter sets a variety of server fine-tuning
; options. Brief descriptions are provided here for each digit. More
; complete descriptions, along with explanations of relationships between
; digits can be found in Chapters 2 and 3.
;
; When not otherwise specified, a value of 0 means off (inactive) and 1 means
; on (active).
;
; 0 opportunistic locking of files (default is 1)
; 1 read-ahead when the requester is performing sequential access
; 0 = do not use read-ahead
; 1 = use single read-ahead thread (default)
; 2 = use asynchronous read-ahead thread
; 2 write-behind (default is 1)
; 3 use of the chain-send NetBIOS NCB (default is 1)
; 4 check all incoming SMBs for correct format (default is 0)
; 5 support FCB opens (default is 1)
; 6 set priority of server (default is 4)
; 0-9 = 0 is highest priority, 9 is lowest priority
; 7 automatically allocate additional memory for directory searches
; (default is 1)
; 8 write records to the audit log only when the scavenger wakes up
; (default is 1)
; 9 do full buffering when a file is opened with deny-write sharing mode
; (default is 1)
; 10 set the interval for the scavenger to wake up
; 0 = 5 seconds 4 = 25 seconds 8 = 45 seconds
; 1 = 10 seconds (default) 5 = 30 seconds 9 = 50 seconds
; 2 = 15 seconds 6 = 35 seconds
; 3 = 20 seconds 7 = 40 seconds
; 11 allow compatibility-mode opens of certain types of files by translating
; them to sharing mode opens with deny-none
; 0 = Always use compatibility-mode opens.
; 1 = Use deny-none sharing mode if read-only access to .EXE or .COM
; files.
; 2 = Use deny-none sharing mode if read-only access to .EXE or .COM
; files. Use deny-write sharing mode if read-only access to .BAT
; files is requested.
; 3 = Use deny-none sharing mode on all compatibility-mode opens.
; (default)
; 12 allow DOS LAN Services workstations to use a second NetBIOS session when
; sending printer requests (default is 1)
; 13 number of 64KB buffers used for read-ahead
; 0-9 = number of buffers (default is 1)
; 14 convert incoming path specifications into most basic format (default is 0)
; 15 Oplock Timeout and NetBIOS Acknowledgment Timeout (default is 0)
; 0 = 35 second Oplock Timeout; 34 second NetBIOS Acknowledgment Timeout
; 1 = 70 second Oplock Timeout; 69 second NetBIOS Acknowledgment Timeout
; 2 = 140 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 3 = 210 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 4 = 280 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 5 = 350 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 6 = 420 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 7 = 490 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 8 = 560 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 9 = 640 second Oplock Timeout; no NetBIOS Acknowledgment Timeout
; 16 validate IOCTLs (default is 1)
; 17 how long the server maintains unused, dynamic big buffers before freeing
; the memory.
; 0 = 0 seconds 4 = 5 minutes 8 = 1 hour
; 1 = 1 second 5 = 10 minutes 9 = indefinitely
; 2 = 10 seconds 6 = 20 minutes
; 3 = 1 minute (default) 7 = 40 minutes
; 18 how long the server waits after failing to allocate a big buffer before
; trying again.
; 0 = 0 seconds 3 = 1 minute (default)
; 1 = 1 second 4 = 5 minutes
; 2 = 10 seconds 5 = 10 minutes
; 19 RAW read and RAW write SMB protocols (default is 1)
; 20 server responds to announcement requests (default is 1)
;
; The next lines help you to locate bits in the srvheuristics entry.
; 1 2
; 012345678901234567890
srvheuristics = 111101411113110013311
SRVSERVICES = NETLOGON,LSSERVER
srvnets =
[alerter]
sizalertbuf = 3072
[netrun]
maxruns = 3
runpath = C:\
[lsserver]
cleanup = yes
srvpipes = 3
[ups]
batterymsg = 600
batterytime = 60
cmdfile =
cmdtimer = 30
devicename = UPS_DEV
lowbattery = warning
messdelay = 5
messtime = 120
recharge = 100
signals = 100
voltlevels = 100
[services]
; Correlates name of service to pathname of service program.
; The pathname must be either
; 1) an absolute path (including the drive specification)
; OR
; 2) a path relative to the IBMLAN root
alerter = services\alerter.exe
dcdbrepl = services\dcdbrepl.exe
genalert = services\genalert.exe
lsserver = services\lsserver.exe
messenger = services\msrvinit.exe
netlogon = services\netlogon.exe
netrun = services\runservr.exe
remoteboot = services\rplservr.exe
replicator = services\replicat.exe
requester = services\wksta.exe
server = services\netsvini.exe
timesource = services\timesrc.exe
ups = services\ups.exe
ΓòÉΓòÉΓòÉ 12.4. IBMLAN.INI for Advanced Server ΓòÉΓòÉΓòÉ
; OS/2 LAN Server Advanced initialization file
[networks:]
; This information is read by the redirector at device initialization time.
[requester]
COMPUTERNAME =
DOMAIN = DOMAIN
; The following parameters generally do not need to be
; changed by the user.
charcount = 16
chartime = 250
charwait = 3600
keepconn = 600
keepsearch = 600
maxcmds = 16
maxerrorlog = 100
maxthreads = 10
maxwrkcache = 64
numalerts = 12
numcharbuf = 10
numservices = 16
numworkbuf = 15
numdgrambuf = 14
othdomains =
printbuftime = 90
sesstimeout = 45
sizcharbuf = 512
sizerror = 1024
sizworkbuf = 4096
useallmem = no
; The wrkheuristics parameter sets a variety of requester fine-tuning
; options. Brief descriptions are provided here for each digit. More
; complete descriptions, along with explanations of relationships between
; digits can be found in Chapters 2 and 3.
;
; When not otherwise specified, a value of 0 means off (inactive) and 1 means
; on (active).
;
; 0 opportunistic locking of files (default is 1)
; 1 performance optimization for batch (.CMD) files (default is 1)
; 2 asynchronous unlock and asynchronous write-unlock
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 3 asynchronous close and asynchronous write-close
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 4 buffer all named pipes and serial devices (default is 1)
; 5 combined read-lock and write-unlock
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 6 open and read optimization (default is 1)
; 7 reserved
; 8 use of the chain-send NetBIOS NCB
; 0 = never
; 1 = when a server's buffer is larger than the workstations buffer
; 2 = always (default)
; 9 buffer small read and write requests until the buffer is full
; 0 = never 2 = only on a LAN Server virtual circuit
; 1 = always (default)
; 10 buffer mode
; 0 = always read buffer size amount of data if the request is smaller
; than the buffer size (sizworkbuf) and data is being read
; sequentially
; 1 = use full buffer if file is open for reading and writing
; 2 = use full buffer if reading and writing sequentially
; 3 = buffer all requests smaller than the buffer size (if hits occur)
; (default)
; 11 RAW read and RAW write SMB protocols (default is 1)
; 12 RAW read-ahead buffer (default is 1)
; 13 RAW write-behind buffer (default is 1)
; 14 read multiplexing SMB protocols (default is 1)
; 15 write multiplexing SMB protocols (default is 1)
; 16 use of big buffers for large core (non-RAW) reads (default is 1)
; 17 same-size read-ahead or read-to-sector boundary (default is 1)
; 18 same-size small record write-behind or write-to-sector boundary
; (default is 0)
; 19 reserved and must be 0
; 20 flush pipes and devices on a DosBufReset or DosClose operation
; 0 = Flush only files and devices opened by the caller. Spin until
; flushed. Wait for confirmation before processing with other
; tasks. (default)
; 1 = Flush only files and devices opened by the caller. Flush only
; once. Do not wait for confirmation.
; 2 = Flush all files and all input and output of short-term pipes
; and devices. Spin until flushed.
; 3 = Flush all files and all input and output of short-term pipes
; and devices. Flush only once.
; 4 = Flush all files and all input and output of all pipes and devices.
; Spin until flushed.
; 5 = Flush all files and all input and output of all pipes and devices.
; Flush only once.
; 21 LAN Server encryption of passwords (default is 1)
; 22 control log entries for multiple occurrences of an error
; 0 = log all occurrences (default)
; 1-9 = limit occurrences that are logged (1-9 define size of table
; that is used to track errors)
; 23 buffer all files opened with deny-write sharing mode (default is 1)
; 24 buffer all files opened with the read-only attribute set (default is 1)
; 25 read ahead when opening for execution (default is 1)
; 26 handle the interrupt (ctrl+c) key
; 0 = allow no interrupts
; 1 = allow interrupts only on long-term operations
; 2 = always allow interrupts (default)
; 27 force correct open mode when creating files on a core server (reserved
; for DBCS users) (default is 1)
; 28 NetBIOS NoAck mode
; 0 = NoAck is disabled.
; 1 = NoAck is set on send only. (default)
; 2 = NoAck is set on receive only.
; 3 = NoAck is set on send and receive.
; 29 send data along with SMB write-block RAW requests (default is 1)
; 30 send a message to the screen when the requester logs an error
; 0 = never
; 1 = on write-fault errors only (no time out) (default)
; 2 = on write-fault and internal errors only (no time out)
; 3 = on all errors (no time out)
; 4 = reserved
; 5 = on write-fault errors only (time out)
; 6 = on write-fault and internal errors only (time out)
; 7 = on all errors (time out)
; 31 reserved
; 32 behavior of DosBufReset on a redirected file (not pipes or devices).
; When the call to the API returns, the data in the buffer has been
; handled as follows:
; 0 = Changed data in the buffer was sent from the requester to the
; server. The server has written the data to disk.
; 1 = Changed data in the buffer was sent from the requester to the
; server. The server has not yet written the data to disk.
; 2 = DosBufReset was ignored. (default)
; 33 time interval for performing logon validation from the domain
; controller
; 0 = 5 seconds 4 = 60 seconds 8 = 8 minutes
; 1 = 15 seconds (default) 5 = 90 seconds 9 = 15 minutes
; 2 = 30 seconds 6 = 2 minutes
; 3 = 45 seconds 7 = 4 minutes
; 34 date validation
; 0 = PCLP date format (default)
; 1 = MSNET date format
; 2 = assume date is correct
; 35 free disk space reported to DOS and Windows applications
; 0 = return true value (default)
; 1 = return a value less than two gigabytes
; 36 time and date synchronization with the domain controller at logon
; (default is 1)
; 37 type of verification for the LAN Server logon
; 0 = no verification
; 1 = verify against local NET.ACC
; 2 = verify against domain NET.ACC (default)
; 38 display warning messages for the LAN Server logon
; 0 = do not display warning messages
; 1 = display all warning messages (default)
; 2 = do not display LAN Server specific warning messages
; 39 buffer all files opened in compatibility mode
; 0 = buffer only files opened for read access in compatibility mode
; 1 = buffer all files opened in compatibility mode (default)
; 40 allow a user to logon multiple times in the same domain (default is 1)
;
; The next lines help you to locate bits in the wrkheuristics entry.
; 1 2 3 4
; 01234567890123456789012345678901234567890
wrkheuristics = 11111111213111111100010111201112210012111
WRKSERVICES = MESSENGER
wrknets =
[messenger]
logfile = messages.log
sizmessbuf = 4096
[netlogon]
SCRIPTS = C:\IBMLAN\REPL\IMPORT\SCRIPTS
pulse = 60
update = yes
[replicator]
replicate = IMPORT
IMPORTPATH = C:\IBMLAN\REPL\IMPORT
tryuser = yes
password =
interval = 5
guardtime = 2
pulse = 3
random = 60
[dcdbrepl]
tryuser = yes
password =
interval = 5
guardtime = 2
pulse = 3
random = 60
[server]
alertnames =
auditing = no
autodisconnect = 120
maxusers = 101
; The following parameters generally do not need to be
; changed by the user. NOTE: srvnets= is represented in
; the server info struct as a 16-bit lan mask. Srvnet names
; are converted to indexes within [networks] for the named nets.
guestacct = guest
accessalert = 5
alertsched = 5
diskalert = 5000
erroralert = 5
logonalert = 5
maxauditlog = 100
maxchdevjob = 6
maxchdevq = 2
maxchdevs = 2
maxconnections = 300
maxlocks = 64
maxopens = 256
maxsearches = 350
maxsessopens = 256
maxsessreqs = 50
maxsessvcs = 1
maxshares = 192
netioalert = 5
numbigbuf = 12
numfiletasks = 1
numreqbuf = 250
sizreqbuf = 4096
srvanndelta = 3000
srvannounce = 60
; The srvheuristics parameter sets a variety of server fine-tuning
; options. Brief descriptions are provided here for each digit. More
; complete descriptions, along with explanations of relationships between
; digits can be found in the LAN Server Network Administrator Reference
; Volume 2: Performance Tuning.
;
; When not otherwise specified, a value of 0 means off (inactive) and 1 means
; on (active).
;
; 0 opportunistic locking of files (default is 1)
; 1 read-ahead when the requester is performing sequential access
; 0 = do not use read-ahead
; 1 = use single read-ahead thread (default)
; 2 = use asynchronous read-ahead thread
; 2 write-behind (default is 1)
; 3 use of the chain-send NetBIOS NCB (default is 1)
; 4 check all incoming SMBs for correct format (default is 0)
; 5 support FCB opens (default is 1)
; 6 set priority of server (default is 4)
; 0-9 = 0 is highest priority, 9 is lowest priority
; 7 automatically allocate additional memory for directory searches
; (default is 1)
; 8 write records to the audit log only when the scavenger wakes up
; (default is 1)
; 9 do full buffering when a file is opened with deny-write sharing mode
; (default is 1)
; 10 set the interval for the scavenger to wake up
; 0 = 5 seconds 4 = 25 seconds 8 = 45 seconds
; 1 = 10 seconds (default) 5 = 30 seconds 9 = 50 seconds
; 2 = 15 seconds 6 = 35 seconds
; 3 = 20 seconds 7 = 40 seconds
; 11 allow compatibility-mode opens of certain types of files by translating
; them to sharing mode opens with deny-none
; 0 = Always use compatibility-mode opens.
; 1 = Use deny-none sharing mode if read-only access to .EXE or .COM
; files.
; 2 = Use deny-none sharing mode if read-only access to .EXE or .COM
; files. Use deny-write sharing mode if read-only access to .BAT
; files is requested.
; 3 = Use deny-none sharing mode on all compatibility-mode opens.
; (default)
; 12 allow DOS LAN Services workstations to use a second NetBIOS session when
; sending printer requests (default is 1)
; 13 number of 64KB buffers used for read-ahead
; 0-9 = number of buffers (default is 1)
; 14 convert incoming path specifications into most basic format (default is 0)
; 15 Oplock Timeout and NetBIOS Acknowledgment Timeout (default is 0)
; 0 = 35 second Oplock Timeout; 34 second NetBIOS Acknowledgment Timeout
; 1 = 70 second Oplock Timeout; 69 second NetBIOS Acknowledgment Timeout
; 2 = 140 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 3 = 210 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 4 = 280 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 5 = 350 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 6 = 420 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 7 = 490 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 8 = 560 second Oplock Timeout; 127 second NetBIOS Acknowledgment Timeout
; 9 = 640 second Oplock Timeout; no NetBIOS Acknowledgment Timeout
; 16 validate IOCTLs (default is 1)
; 17 how long the server maintains unused, dynamic big buffers before freeing
; the memory.
; 0 = 0 seconds 4 = 5 minutes 8 = 1 hour
; 1 = 1 second 5 = 10 minutes 9 = indefinitely
; 2 = 10 seconds 6 = 20 minutes
; 3 = 1 minute (default) 7 = 40 minutes
; 18 how long the server waits after failing to allocate a big buffer before
; trying again.
; 0 = 0 seconds 3 = 1 minute (default)
; 1 = 1 second 4 = 5 minutes
; 2 = 10 seconds 5 = 10 minutes
; 19 RAW read and RAW write SMB protocols (default is 1)
; 20 server responds to announcement requests (default is 1)
;
; The next lines help you to locate bits in the srvheuristics entry.
; 1 2
; 012345678901234567890
srvheuristics = 111101411113110013311
SRVSERVICES = NETLOGON,LSSERVER
srvnets =
[alerter]
sizalertbuf = 3072
[netrun]
maxruns = 3
runpath = C:\
[lsserver]
cleanup = yes
srvpipes = 5
[ups]
batterymsg = 600
batterytime = 60
cmdfile =
cmdtimer = 30
devicename = UPS_DEV
lowbattery = warning
messdelay = 5
messtime = 120
recharge = 100
signals = 100
voltlevels = 100
[services]
; Correlates name of service to pathname of service program.
; The pathname must be either
; 1) an absolute path (including the drive specification)
; OR 2) a path relative to the IBMLAN root
alerter = services\alerter.exe
dcdbrepl = services\dcdbrepl.exe
genalert = services\genalert.exe
lsserver = services\lsserver.exe
messenger = services\msrvinit.exe
netlogon = services\netlogon.exe
netrun = services\runservr.exe
remoteboot = services\rplservr.exe
replicator = services\replicat.exe
requester = services\wksta.exe
server = services\netsvini.exe
timesource = services\timesrc.exe
ups = services\ups.exe
ΓòÉΓòÉΓòÉ 12.5. HPFS386.INI ΓòÉΓòÉΓòÉ
Refer to HPFS386.INI Parameter Descriptions for further explanations about the
parameters of this file. The HPFS386.INI with just its parameters is as
follows:
useallmem = [yes|no]
cachesize = nnnn
maxheap = nnnn
lanroot = d:\path
fsprealloc = nn
srvprealloc = nn
[filesystem]
useallmem = no
lanroot = C:\IBMLAN
lazy = [drives:] on|off
maxage = [drives:] nnnn
bufferidle = [drives:] nnnn
lazy = [drives:] on
maxage = [drives:] 5000
bufferidle = [drives:] 500
[lazywriter]
[Directory Limits]
ThreshAlertNames = *: ADMINS
ThreshAlertDelay = *: 10
ThreshAlertUser = *: yes
DirFullAlertNames = *: ADMINS
DirFullAlertDelay = *: 10
DirFullAlertUser = *: yes
lazy = *: on
maxage = *: 5000
bufferidle = *: 500
ThreshAlertNames = [drives:] user1 user2 group1 group2
ThreshAlertDelay = [drives:] nn
ThreshAlertUser = [drives:] yes|no
DirFullAlertDelay = [drives:] nn
DirFullAlertUser = [drives:] yes|no
[Directory Limits]
ThreshAlertNames = *: ADMINS
ThreshAlertDelay = *: 10
ThreshAlertUser = *: yes
DirFullAlertNames = *: ADMINS
DirFullAlertDelay = *: 10
DirFullAlertUser = *: yes
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Trademark of IBM. See Trademarks for a list of trademarks.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Trademark. See Trademarks for a list of trademarks.