|
|
|
4.0 Chapter 4. Customizing the Device Driver Parameters
This chapter describes the LAN Support Program Custom device driver
parameter values and tells you how to edit the parameter values in
CONFIG.SYS manually. Although manual configuration is described, IBM
recommends that you use the Installation Aid to view and modify the
parameter values. Using the Installation Aid is easier than manual
configuration and reduces the chance of errors. See Chapter 2, "Using the
Installation Aid" for more information.
NOTE: The highlighted letters in the names of the device drivers
distinguish one device driver from another.
4.1 Device Driver Summary
The LAN Support Program Custom Version 1.01 contains the device drivers
shown in Figure 4-1.
+------------------------------------------------------------------------+
| Figure 4-1. LAN Support Program Custom Version 1.01 Device Drivers |
+-------------+----------------------+-----------------------------------+
| Description | Device Driver | Function |
+-------------+----------------------+-----------------------------------+
| Interrupt | DXMA0MOD.SYS | Required driver that dispatches |
| arbitrator | | the other drivers in response to |
| | | a X'5C' interrupt. It has one |
| | | parameter that defines the |
| | | language in which load-time |
| | | messages are displayed. |
+-------------+----------------------+-----------------------------------+
| Device | DXMC0MOD.SYS | Required driver that provides the |
| driver | | IEEE 802.2 interface to support |
| | | the adapter. |
+-------------+----------------------+-----------------------------------+
| NETBIOS | DXMT0MOD.SYS | Is required to provide NETBIOS |
| interface | | application programs with a |
| device | | program interface to the adapter |
| driver | | device driver. It cannot be used |
| | | unless the device driver |
| | | DXMC0MOD.SYS has been configured. |
+-------------+----------------------+-----------------------------------+
4.2 Parameter for the Interrupt Arbitrator Device Driver (DXMA0MOD.SYS)
DXMA0MOD.SYS has one parameter (represented by ccc) that defines the
language in which load-time messages are displayed. This parameter
corresponds to one of the values defined as DOS country codes in the IBM
Personal Computer Disk Operating System user's guide for your version of
DOS and defines the message file that must be copied as DXM.MSG.
This parameter is entered in CONFIG.SYS using the following syntax:
DEVICE=\LSP\DXMA0MOD.SYS ccc
In this example, \LSP is a sample directory; you may substitute another
directory if you wish.
The following country codes are supported:
+---------+-----------------+---------+----------------------------------+
| Country | | Country | |
| Code | Language | Code | Language |
+---------+-----------------+---------+----------------------------------+
| 001 | U.S. English | 049 | German |
+---------+-----------------+---------+----------------------------------+
| 034 | Spanish | 081 | Japanese |
+---------+-----------------+---------+----------------------------------+
4.3 Parameters for DXMC0MOD.SYS
The sample directory provided in the examples showing you how to edit
CONFIG.SYS is \LSP. Substitute the name of your directory if it is
different. The parameters for DXMC0MOD.SYS are entered in CONFIG.SYS
using the following syntax:
DEVICE=\LSP\DXMC0MOD.SYS N ADDR,MEM,ETR,MINSAP,MINLINK
If a parameter is not listed in CONFIG.SYS, the LAN Support Program Custom
uses the default.
4.3.1 List of Parameters
The parameters for DXMC0MOD.SYS are listed in Figure 4-2. See the
sections referred to for detailed descriptions of the parameters.
+------------------------------------------------------------------------+
| Figure 4-2. Parameters for DXMC0MOD.SYS |
+-----------+----------------------------------------+-------------------+
| Parameter | Function | Reference: |
+-----------+----------------------------------------+-------------------+
| N | Required when the parameter MINSAP or | "The N Parameter" |
| | MINLINK is used. It enables | in topic 4.3.5 |
| | DXMC0MOD.SYS to interpret the MINSAP | |
| | and MINLINK parameters correctly. | |
| | This parameter is the letter N. | |
+-----------+----------------------------------------+-------------------+
| ADDR | Specifies a locally administered | "Token-Ring |
| | address for the adapter. The default | Network Adapter |
| | value is the universally administered | Address" in |
| | adapter address. | topic 4.3.6 |
+-----------+----------------------------------------+-------------------+
| MEM | Specifies the location of shared RAM | "Shared RAM" in |
| | in the host computer memory. The | topic 4.3.7 |
| | default is segment location D800 | |
| | (memory address D8000). | |
+-----------+----------------------------------------+-------------------+
| ETR | Specifies whether or not Early Token | "Early Token |
| | Release is being used. Early Token | Release" in |
| | Release can only be implemented on a | topic 4.3.8 |
| | 16-Mbps token ring. | |
+-----------+----------------------------------------+-------------------+
| MINSAP | Sets the minimum number of service | "MINSAP" in |
| | access points (SAPs). The N parameter | topic 4.3.9 |
| | must be present when this parameter is | |
| | used. The value of this parameter is | |
| | a number from 0-127. | |
+-----------+----------------------------------------+-------------------+
| MINLINK | Sets the minimum number of link | "MINLINK" in |
| | stations. The N parameter must be | topic 4.3.10 |
| | present when this parameter is used. | |
| | The value of this parameter is a | |
| | number from 0-254. | |
+-----------+----------------------------------------+-------------------+
4.3.2 Using the Installation Aid to Change Parameter Values
Chapter 2, "Using the Installation Aid" explains how to use the
Installation Aid to change the values of the parameters. If you plan to
use the Installation Aid, you do not need to read "Global and Positional
Parameters" in topic 4.3.3 or "Examples of Editing the Parameter List" in
topic 4.3.4.
4.3.3 Global and Positional Parameters
The N parameter is a global parameter. It must follow the device driver
name and precede the address, and be separated from them by spaces. This
global parameter, if used, must precede the positional parameters.
The parameters separated by commas are positional parameters. They must
be entered in the sequence shown in the syntax example in topic 4.3 .
Each positional parameter is always followed by a comma except when it is
at the end of the list. If a positional parameter is missing, the comma
that would follow it is used to mark its place.
The name of the device driver must always be followed by a space. For
more information about entering these parameters manually, see "Examples
of Editing the Parameter List" in topic 4.3.4.
4.3.4 Examples of Editing the Parameter List
To add parameters, edit the CONFIG.SYS file, as in the following examples:
° To specify a locally administered address for the adapter, use the
following line:
DEVICE=\LSP\DXMC0MOD.SYS 400000000001
In this example, 400000000001 is the new address for the adapter,
which overrides the default address encoded on the adapter. All other
defaults are retained.
° To set MINSAP and MINLINK, you must use the N parameter. In the
following example, the locally administered address for the adapter is
specified, MINSAP is set to 3, and MINLINK is set to 2.
DEVICE=\LSP\DXMC0MOD.SYS N 400000000001,,,3,2
Note that N is followed only by a space. Also note that three commas
are necessary to mark the locations of the parameters MEM and ETR. If
you do not use the N parameter, do not replace it with a comma. Be
sure there is a space between DXMC0MOD.SYS and the next parameter or
comma.
° To specify a new shared RAM address for the adapter, use the following
line:
DEVICE=\LSP\DXMC0MOD.SYS ,C400
In this example, C400 is the new shared RAM segment (the physical
address is C4000) for the adapter. The default location for the RAM
address on the adapter is overridden. All other defaults are
retained. Note the space and the comma before the RAM location. The
space is required and the comma indicates that a parameter (the
adapter address) has been omitted.
° To disable the Early Token Release option, use the following line:
DEVICE=\LSP\DXMC0MOD.SYS ,,1
In this example, the value 1 disables the Early Token Release option.
This parameter can be either 0 or 1, and is used only for adapters
with a data rate of 16 Mbps, not for adapters with a data rate of 4
Mbps. If the adapter data rate is 16 Mbps, the option is enabled by
default. You must change the parameter value to 1 to disable it.
4.3.5 The N Parameter
This parameter (the letter N) alerts the software to read values for
MINSAP and MINLINK. If you enter values for MINSAP and MINLINK, but do
not enter the N parameter, the MINSAP and MINLINK parameters will be
ignored.
4.3.6 Token-Ring Network Adapter Address
The universally administered address of the adapter is in the range that
is administered by the standards committees for LANs. This address is the
default address for the adapter if no other address is assigned, and is
often referred to as the burned-in address.
Your network administrator may assign a locally administered address that
will override the universally administered address. This address must
consist of 12 hexadecimal digits that range from X'4000 0000 0000' to
X'7FFF FFFF FFFF'. Values outside this range may be incompatible with
other products on the network.
IBM recommends that the address be restricted to decimal values. The
locally administered address ranges from X'4000 0000 0000' to X'4000 7999
9999' decimal.
Notes:
1. Make sure that the address is recorded on the physical and logical
address locator charts. These charts and an explanation of them can
be found in the IBM Token-Ring Network Introduction and Planning
Guide.
2. Each locally administered address should be unique throughout the
network.
To enter the adapter address, see "Parameters for DXMC0MOD.SYS" in
topic 4.3.
4.3.7 Shared RAM
The adapter with which the LAN Support Program Custom is shipped is a
token-ring network adapter. It contains RAM that is shared with the
computer. The default segment location for the adapter, where the
computer locates the RAM, is D800. (Note that segment D800 is memory
address D8000.) If other features installed on your system unit use this
location, you must assign another location. Valid locations must consist
of 4 hexadecimal digits that represent the upper 4 digits of a 5-digit
hexadecimal address.
The adapter allows you to set the shared RAM size to 8, 16, 32, or 64 KB.
The shared RAM address must be on a boundary that corresponds to the size
of the shared RAM. For most application programs, you should select the
shared RAM size to be 16 KB. For this size, the adapter uses a technique
called RAM paging to give you access to the entire 64-KB shared RAM. When
setting the shared RAM size, you must be sure that the address range does
not conflict with the address ranges of other features that may be in the
computer.
For more information about setting shared RAM size, refer to the adapter
installation and testing instructions.
4.3.8 Early Token Release
The Early Token Release option is supported only if the token-ring adapter
is operating at the data rate of 16 Mbps. Early Token Release increases
the use of the network by reducing the time between the release of tokens
on the token-ring. You can disable Early Token Release by changing the
value of the parameter ETR. The values of this parameter are 0 and 1. If
the value is 0, Early Token Release is implemented; if the value is 1,
Early Token Release is not used. The default is 0.
4.3.9 MINSAP
This parameter is used to define the minimum number of SAPs that the
adapter will support when opened. It enables multiple 802.2 applications
to coexist. For example, IBM Personal Communications/3270 and IBM
Application System/400 PC Support can run on the same workstation if
MINSAP is set to a high enough value to include the total number of SAPs
required by both application programs.
The N parameter must be present when this parameter is used. If MINSAP is
omitted, 0 is used as its value. The range is 0-127.
The value of this parameter influences the total number of SAPs required
when the adapter is opened. If the total number of SAPs and link stations
is too high, the LAN Support Program Custom Version 1.01 may not run. See
"Work Area Considerations for LAN Support Program Custom Version 1.01" in
topic 4.7 for more information.
4.3.10 MINLINK
This parameter sets the minimum number of link stations that the adapter
will support when opened. It enables multiple 802.2 applications to
coexist. For example, IBM Personal Communications/3270 and IBM
Application System/400 can run on the same workstation if MINLINK is set
to a high enough value to include the total number of link stations
required by both application programs. The MINSAP parameter must also be
set to a high enough value to include the total number of SAPs required by
both application programs.
The N parameter must be present when this parameter is used. If MINLINK
is omitted, 0 is used as its value. The range is 0-254.
The value of the MINLINK parameter influences the total number of link
stations required when the adapter is opened. However, if the total
number of SAPs and link stations is too high, the LAN Support Program
Custom Version 1.01 may not run. See "Work Area Considerations for LAN
Support Program Custom Version 1.01" in topic 4.7 for more information.
4.4 Device Driver Parameters for DXMT0MOD.SYS
The NETBIOS interface has many optional parameters available to customize
the driver for certain network application programs. Only one of the
parameters, the Enable parameter, is position dependent. If used, it must
be entered as the first parameter. For example:
DEVICE=\LSP\DXMT0MOD.SYS ENABLE
NOTE: ENABLE may be abbreviated as E.
The processing of a NETBIOS command occurs when the X'5C' interrupt is
issued. Because interrupts are disabled for a short time, some loss of
data may occur in an asynchronous adapter if it is used simultaneously
with a LAN adapter.
If the computer contains an asynchronous adapter that is used
simultaneously with a LAN adapter, you should use the Enable parameter.
In this case, the NETBIOS command will be processed at a later time,
during a LAN adapter appendage interrupt. Because interrupts are enabled,
data is not lost. But because of the short delay, there may be some loss
in performance.
4.4.1 The NETBIOS Old Parameters
The new releases of the NETBIOS device driver DXMT0MOD.SYS use keyword
parameters. The name of the parameter, called the keyword, is set equal
to its value. The keyword with its value can be placed at any position in
the list of parameters. However, in previous releases NETBIOS used
positional parameters. If you are upgrading from a previous NETBIOS
program release, a migration selection allows you to select the positional
parameters. To do this, see the following example:
DEVICE=\LSP\DXMT0MOD.SYS OLD.PARMS.0=x y z
OLD.PARMS.0 is the keyword indicating that the old form of positional
parameters will be used for the adapter. The x y z stand for values that
can be set for the old parameters:
x PC RAM used as internal work space. The default is 9 (9 KB) For
large systems, this value may have to be increased (the maximum value
is 64 [64 KB]).
y Extra SAPs. This indicates the number of extra (non-NETBIOS) SAPs
that will be defined when NETBIOS opens the adapter. The default
value is 0 and the maximum value is 99.
z Extra link stations. This indicates the number of extra
(non-NETBIOS) link stations that will be defined when NETBIOS opens
the adapter. The default value is 0 and the maximum value is 99.
+------------------------------------------------------------------------+
| Figure 4-3. NETBIOS (Default = OLD.PARMS) Parameters |
+-----------------------+------------------------+-----------------------+
| Load Parameters | Valid Values | Defaults |
+-----------------------+------------------------+-----------------------+
| Work area | 0 to 64 | 9 |
+-----------------------+------------------------+-----------------------+
| EXTRA.SAPs | 0 to 99(1) | 0 |
+-----------------------+------------------------+-----------------------+
| EXTRA.STATIONS | 0 to 99(1) | 0 |
+-----------------------+------------------------+-----------------------+
| (1) If this value is too large, the adapter will fail to open. The |
| maximum value allowed here typically exceeds current adapter maximum |
| values. |
+------------------------------------------------------------------------+
Notes:
1. If y is specified, x must be specified. If z is specified, both x and
y must be specified. Only these parameters can be changed by an entry
on the CONFIG.SYS command line.
2. The following table lists the old parameters whose default values
differ from those listed in Figure 4-5 in topic 4.4.2.1. Use the
NETBIOS RESET command to change the values for STATIONS, SESSIONS, and
COMMANDS.
+------------------------------------------------------------------------+
| Figure 4-4. NETBIOS Old Parameters Defaults |
+-----------------------+------------------------+-----------------------+
| Parameters | Defaults | Valid Values |
+-----------------------+------------------------+-----------------------+
| STATIONS | 6 | 1 to 32 |
+-----------------------+------------------------+-----------------------+
| SESSIONS | 6 | 1 to 32 |
+-----------------------+------------------------+-----------------------+
| COMMANDS | 12 | 1 to 32 |
+-----------------------+------------------------+-----------------------+
| OPEN.ON.LOAD | NO | Cannot be changed |
+-----------------------+------------------------+-----------------------+
4.4.2 Keyword Values for the NETBIOS New Parameters
Figure 4-5 in topic 4.4.2.1 shows all the new NETBIOS keywords for
DXMT0MOD.SYS and their default values. Each keyword is set equal to its
value. Keyword parameters are not position dependent. They need to be
separated by a blank as shown in the examples that follow, and they must
also be on the same line.
The following example shows how the parameters are specified in
CONFIG.SYS:
DEVICE=\LSP\DXMT0MOD.SYS E ST=4 S=4 N=3 C=3
In this instance, 4 sessions are defined and the Enable parameter is
activated. Remember that Enable is the parameter that activates the
Enable function, and that it is the only position-dependent NETBIOS new
parameter. If used, it must precede any other NETBIOS parameters listed.
(You can represent ENABLE with the abbreviation E.)
4.4.2.1 Characteristics of the NETBIOS New Parameters
These parameters are used to customize the system, if required. They have
the following characteristics:
° They cannot be used if OLD.PARMS.0 is used.
° Undefined keywords take the default value.
° If any of these keywords are used, all other keywords will assume the
default values indicated in Figure 4-5.
° With LAN Support Program Custom Version 1.01, you may not be able to
use the maximum values for these parameters. See "Work Area
Considerations for LAN Support Program Custom Version 1.01" in
topic 4.7 for more information.
° The keywords STATIONS, SESSIONS, and COMMANDS provide maximum values
that can be used; if a program issues a RESET command, and the RESET
indicates a value larger than the value indicated by one of these
keywords, the keyword value will be used.
+------------------------------------------------------------------------+
| Figure 4-5. NETBIOS Device Driver New Keyword Values |
+-----------------------+-------------+----------+---------+-------------+
| | Abbrev- | Valid | | |
| Keyword | iation | Values | Minimum | Default |
+-----------------------+-------------+----------+---------+-------------+
| | | 0 to 254 | | |
| STATIONS | ST | (1) | 1 | 16 |
+-----------------------+-------------+----------+---------+-------------+
| SESSIONS | S | 0 to 254 | 1 | 16 |
+-----------------------+-------------+----------+---------+-------------+
| COMMANDS | C | 0 to 255 | 1 | 12 |
+-----------------------+-------------+----------+---------+-------------+
| NAMES | N | 0 to 254 | 2 | 17 |
+-----------------------+-------------+----------+---------+-------------+
| | | Y (Yes)/ | | |
| OPEN.ON.LOAD | O | N (No) | - | Yes |
+-----------------------+-------------+----------+---------+-------------+
| | | Y (Yes)/ | | |
| DATAGRAM.MAX | DG | N (No) | - | No |
+-----------------------+-------------+----------+---------+-------------+
| | | Y (Yes)/ | | |
| CLOSE.ON.RESET | CR | N (No) | - | No |
+-----------------------+-------------+----------+---------+-------------+
| | | Y (Yes)/ | | |
| CALL.FAR | CF | N (No) | - | No |
+-----------------------+-------------+----------+---------+-------------+
| | | 0, 200 | | |
| | | to | | |
| | | 17 960 | | |
| DHB.SIZE | DS | (1) | 200 | (2) |
+-----------------------+-------------+----------+---------+-------------+
| | | 0 to 9 | | |
| DHB.NUMBER | DN | (1) | - | (2) |
+-----------------------+-------------+----------+---------+-------------+
| | | 0 to | | |
| RECEIVE.BUFFER.SIZE | R | 9999 (1) | (3) | (2) |
+-----------------------+-------------+----------+---------+-------------+
| TRANSMIT.TIMEOUT | TT | 0 to 20 | 0 | 1 |
+-----------------------+-------------+----------+---------+-------------+
| TRANSMIT.COUNT | TC | 0 to 10 | 0 | 6 |
+-----------------------+-------------+----------+---------+-------------+
| DLC.MAXOUT | MO | 0 to 9 | 0 | 2 |
+-----------------------+-------------+----------+---------+-------------+
| DLC.MAXIN | MI | 0 to 9 | 0 | 1 |
+-----------------------+-------------+----------+---------+-------------+
| RING.ACCESS | RA | 0 to 3 | 0 | 0 |
+-----------------------+-------------+----------+---------+-------------+
| | | 0 to 99 | | |
| EXTRA.SAPS | ES | (1) | 0 | 0 |
+-----------------------+-------------+----------+---------+-------------+
| | | 0 to 254 | | |
| EXTRA.STATIONS | EST | (1) | 0 | 0 |
+-----------------------+-------------+----------+---------+-------------+
| REMOTE.NAME.DIRECTORY | RND | 0 to 255 | 0 | 0 |
+-----------------------+-------------+----------+---------+-------------+
| REMOTE.DATAGRAM. | | Y (Yes)/ | | |
| CONTROL | RDC | N (No) | - | No |
+-----------------------+-------------+----------+---------+-------------+
| | | Y (Yes)/ | | |
| RESET.VALUES | RV | N (No) | - | No |
+-----------------------+-------------+----------+---------+-------------+
| | | Y (Yes)/ | | |
| ADAP.ADD.NOT.REVERSED | ANR | N (No) | - | No |
+-----------------------+-------------+----------+---------+-------------+
| DLC.RETRY.COUNT | RC | 0 to 255 | 0 | 8 |
+-----------------------+-------------+----------+---------+-------------+
| DLC.T1 | T1 | 0 to 10 | 0 | 5 |
+-----------------------+-------------+----------+---------+-------------+
| DLC.T2 | T2 | 0 to 11 | 0 | 2 |
+-----------------------+-------------+----------+---------+-------------+
| DLC.TI | TI | 0 to 10 | 0 | 10 |
+-----------------------+-------------+----------+---------+-------------+
| PIGGYBACKED. | | | | |
| ACKNOWLEDGMENTS | PBA | 0 to 5 | 0 | 0 |
+-----------------------+-------------+----------+---------+-------------+
| NOTE: On this table, (1) means see note 1, (2) means see note 2, and |
| (3) means see note 3. The notes follow. |
+------------------------------------------------------------------------+
Notes:
1. If this value is too large, the adapter fails to open. The maximum
value allowed here typically exceeds the maximum value supported by
LAN Support Program Custom Version 1.01.
2. The default value set by the NETBIOS interface device driver is based
on the number of stations. See "NETBIOS Adapter Transmit and Receive
Buffer Default Sizes" in topic 4.5.
3. If a value is specified for RECEIVE.BUFFER.SIZE, its value is not
checked by the NETBIOS interface device driver. The value is checked
by the adapter upon opening. Current adapters require a minimum value
of 96.
continue with >> NETBIOS Device Driver Keyword Parameter Description
Please see the LEGAL - Trademark notice.
Feel free - send a 
for any BUG on this page found - Thank you.