|
|
|
4.4.3 NETBIOS Device Driver Keyword Parameter Descriptions
Each keyword has an abbreviated version, which is indicated in parentheses
following the keyword:
STATIONS= (ST=)
° Indicates the maximum number of NETBIOS interface link
stations that can be defined.
° Must be a decimal number from 0 to 254.
- The realistic maximum is affected by the size of the
shared RAM on the adapter.
- The EXTRA.STATIONS value reduces the maximum for the
NETBIOS interface.
- The value of this parameter influences the total number
of link stations required when the adapter is opened.
If the parameters STATIONS, EXTRA.STATIONS, EXTRA.SAPS,
MINLINK and MINSAP result in too high a total number of
SAPs and link stations, the configuration may require
more work area than is supported by the LAN Support
Program Custom. In this case, the program will not run.
See "Work Area Considerations for LAN Support Program
Custom Version 1.01" in topic 4.7 for more information.
° If other than the default is used, CLOSE.ON.RESET must be
set to Y (Yes).
° If omitted or 0, the default value is 16.
SESSIONS= (S=)
° Indicates the maximum number of NETBIOS interface device
driver sessions that can be defined.
° Must be a decimal number from 0 to 254.
° If omitted or 0, the default value is 16.
If the value is less than the value of STATIONS, it will be
set to the value of STATIONS.
COMMANDS= (C=)
° Indicates the maximum number of NETBIOS interface commands
node control block (NCB) that can be outstanding at one
time.
° Must be a decimal number from 0 to 255.
° If omitted or 0, the default value is 12.
NAMES= (N=)
° Indicates the maximum number of NETBIOS interface device
driver names that can be defined, including NAME_NUMBER_1.
° Must be a decimal number from 0 to 254.
° If omitted or 0, the default value is 17.
° If 1, the value will be set to 2.
OPEN.ON.LOAD= (O=)
° If Y (YES), the NETBIOS interface will open the adapter at
load time. Having NETBIOS open the adapter eliminates the
delay caused by opening the adapter later when an
application program is loaded and the first NCB is issued.
° Must be specified as either Y (Yes) or N (No).
° If you are using the NETBIOS new parameters and this
parameter is omitted, the default is Y (Yes).
DATAGRAM.MAX= (DG=)
° Indicates that the maximum length datagram transmitted by
the NETBIOS interface device driver will be based on the
size of the transmit buffer or data hold buffer (DHB) of the
adapter. Usually, a datagram is limited to 512 bytes.
° Must be specified as either Y (Yes) or N (No).
° If the maximum length of a datagram is:
DHB length - 86 (the size of the transmit buffer minus
86 bytes).
° If omitted or N, this function is not performed.
CLOSE.ON.RESET= (CR=)
° Indicates that the NETBIOS interface will close the adapter
and reopen it when a RESET is issued.
° Must be specified as either Y (Yes) or N (No).
° Must be specified as Y if you want to change the number of
link stations when the adapter is re-opened.
° If omitted or N, this function will not be performed.
CALL.FAR= (CF=)
° Prevents an application program from intercepting the X'5C'
interrupt issued by the NETBIOS device driver DXMT0MOD.SYS.
If an application program intercepts this interrupt
incorrectly, LAN Support Program Custom processing is
terminated.
° Must be specified as either Y (Yes) or N (No). The default
value is N.
° Must be specified as Y when Windows or DOS memory managers
are used with the LAN Support Program Custom. This keyword
must also be set to Y for any other application programs
that may intercept X'5C' interrupts.
° If omitted or N, this function will not be performed. The
default value is N.
DHB.SIZE= (DS=)
° Indicates the size of the DHB (the transmit buffers of the
adapter).
° Must be a decimal number within the range acceptable to the
adapter. Note that the minimum size allowed by the NETBIOS
interface is 200. Therefore, the value entered must be
either 0 or a number from 200 to 17 960.
° If omitted or 0, the value is determined by the NETBIOS
interface. See "NETBIOS Adapter Transmit and Receive Buffer
Default Sizes" in topic 4.5 for information about the
NETBIOS default values.
DHB.NUMBER= (DN=)
° Indicates the number of DHBs allocated by the adapter.
° Must be a decimal number within the range acceptable to the
adapter.
° If omitted or 0, the value is determined by the NETBIOS
interface device driver. See "NETBIOS Adapter Transmit and
Receive Buffer Default Sizes" in topic 4.5 for information
about the NETBIOS default values.
RECEIVE.BUFFER.SIZE= (R=)
° Indicates the size of the receive buffers of the adapter. A
minimum of 8 adapter buffers of the specified size will be
allocated.
° Must be a decimal number within the range acceptable to the
adapter.
° If omitted or 0, the value is determined by the NETBIOS
interface. See "NETBIOS Adapter Transmit and Receive Buffer
Default Sizes" in topic 4.5 for information about the
NETBIOS default values.
TRANSMIT.TIMEOUT= (TT=)
° Indicates the time between transmission of queries (for
example, CALL).
° Is indicated in 1/2-second periods.
° Must be a decimal number from 0 to 20.
° If omitted or 0, the default is 1 (1/2 second).
TRANSMIT.COUNT= (TC=)
° Indicates the number of times queries (for example, CALL)
are transmitted.
° Must have a decimal value from 1 to 10. If a number from 1
to 10 is specified, that number is the value.
° If omitted or 0, the default is 6.
DLC.MAXOUT= (MO=)
° Sets the MAXOUT value for all NETBIOS interface link
stations. The MAXOUT value indicates the number of I-frames
sent before waiting for an acknowledgment.
° The sender's MAXOUT value must always be greater than the
receiver's MAXIN value.
° Must have a decimal value from 1 to 9. If a number from 1
to 9 is specified, that number is the value.
° If omitted or 0, the default is 2.
DLC.MAXIN= (MI=)
° Sets the MAXIN value for all NETBIOS interface link
stations. The MAXIN value indicates the number of I-frames
received before sending an acknowledgment.
° The receiver's MAXIN value must always be less than the
sender's MAXOUT value.
° Must have a decimal value from 1 to 9. If a number from 1
to 9 is specified, that number is the value.
° If omitted or 0, the default is 1.
RING.ACCESS= (RA=)
° Indicates the ring access priority for this adapter for
NETBIOS device driver interface messages. This parameter is
valid for token-ring adapters only.
° Must be a decimal number from 0 to 3.
° If omitted or 0, the default is 0.
° The higher the number, the higher the priority.
EXTRA.SAPS= (ES=)
° Indicates additional SAPs requested by the NETBIOS interface
when it opens the adapter. These SAPs may be needed when
another application program is using the 802.2 interface.
° 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 will not be able to open the adapter.
See "Work Area Considerations for LAN Support Program Custom
Version 1.01" in topic 4.7 for more information.
° Must be a decimal number from 0 to 99.
° If omitted or 0, no additional SAPs are requested.
NOTE: If this value is less than the value of MINSAP, the value
of MINSAP will be used.
EXTRA.STATIONS= (EST=)
° Indicates additional link stations requested by the NETBIOS
interface when it opens the adapter. These stations may be
needed when another application program is using the 802.2
interface.
° The value of this parameter influences the total number of
link stations required when the adapter is opened. If the
total number of SAPs and link stations is too high, the LAN
Support Program Custom will not be able to open the adapter.
See "Work Area Considerations for LAN Support Program Custom
Version 1.01" in topic 4.7 for more information.
° Requesting extra stations reduces link stations available
for the use on the NETBIOS interface.
° Must be a decimal number from 0 to 254.
° If omitted or 0, no additional stations are requested.
NOTE: If this value is less than the value of MINLINK, the
value of MINLINK will be used.
REMOTE.NAME.DIRECTORY= (RND=)
° Can be coded as a number from 0 to 255.
° If omitted or 0, the REMOTE.NAME.DIRECTORY (RND) function is
not implemented. All CALLS, STATUS QUERIES, and SEND
DATAGRAMS will operate as in previous levels of NETBIOS and
broadcast messages to all NETBIOS nodes.
° If a nonzero value is coded, the RND function is implemented
with the value indicating the number of remote names that
can be saved by the local node. Note that 4 is the minimum
number of name entries; if coded as 1, 2, or 3, the value of
4 is used. When RND is implemented (after the local station
has located a remote name), the remote node address is saved
and subsequent messages to that name will be broadcast to a
specific node rather than to all nodes. This is true for
CALLS, STATUS QUERIES, and SEND DATAGRAMS (see next keyword
REMOTE.DATAGRAM.CONTROL).
NOTE: Using the RND function can significantly improve
performance in situations where large numbers of DATAGRAMS,
CALLS, and REMOTE_ADAPTER_STATUS commands are used.
Important: When the RND function is being used, a duplicate
network name will not be detected by a CALL function unless
it is the first time that the remote (CALL) name has been
used.
REMOTE.DATAGRAM.CONTROL= (RDC=)
° Is meaningless if REMOTE.NAME.DIRECTORY is omitted or coded
as 0.
° If omitted or coded as N (No), SEND DATAGRAMS will not use
the RND function.
° If coded as Y (Yes), SEND DATAGRAMS will also use the RND
for sending to remote nodes. Note that if a bridge in the
transmission path drops out, datagrams give no indication
that the path is no longer valid. Therefore, if this
function is used, you may want to update the RND if you
become aware that the remote node is not receiving
datagrams. You can update the RND by having the application
program issue a FIND_NAME command with a receive buffer
length of 0. This function allows an application to update
the RND without having to execute either a CALL or REMOTE
ADAPTER STATUS.
RESET.VALUES= (RV=)
° If omitted or coded as N (No), RESET works as it does in
earlier releases of NETBIOS.
° If coded as Y (Yes) when a RESET is issued, one of the
following possibilities occurs:
- If the number of sessions is coded as 0 in the RESET,
the default will be the value defined by the keyword
SESSIONS= rather than the normal default value of 6.
- If the number of commands is coded as 0 in the RESET,
the default will be the value defined by the keyword
COMMANDS= rather than the normal default value of 12.
ADAP.ADDR.NOT.REVERSED= (ANR=)
° If omitted or coded as N (No), the universally administered
address of the adapter as used in the ADAPTER_STATUS command
and in NAME_NUMBER_1 will be byte-reversed (that is, if the
value is X'010203040506', it will be saved as
X'060504030201'). N is the default.
° If coded as Y (Yes), the universally administered address of
the adapter as used in the ADAPTER_STATUS command and in
NAME_NUMBER_1 will not be byte-reversed (that is, if the
value is X'010203040506', it will be saved as
X'010203040506').
DLC.RETRY.COUNT= (RC=)
° Determines the number of retry attempts to be made by the
logical link control (LLC) code.
° Must be a decimal value from 0 to 255. If a number from 1
to 255 is specified, that number is the value.
° If omitted or 0, the default value of 8 is used. The
default value is equal to 9 seconds. Refer to the LAN
Technical Reference for more information.
DLC.T1= (T1=)
° Determines the value of the T1 response timer in the LLC
code. The T1 timer sets the maximum time to wait for an
acknowledgment before retransmitting a link-level frame.
° Must be a decimal value from 0 to 10. See Figure 4-6 for
correlations between parameters and seconds.
° If omitted or 0, the default value of 5 is used.
DLC.T2= (T2=)
° Determines the value of the T2 acknowledgment timer in the
LLC code. The T2 timer sets the maximum delay before
sending an acknowledgment.
° Must be a decimal value from 0 to 11. See Figure 4-6 for
correlations between parameters and seconds.
° If 11, the T2 timer function is not implemented.
° If omitted or 0, the default value of 2 is used.
DLC.TI= (TI=)
° Determines the value of the TI inactivity timer in the LLC
code. The TI timer sets how long to wait before generating
a data link control (DLC) status if there is no link station
traffic.
° Must be a decimal value from 0 to 10. If a number is
specified, that number is the value. See Figure 4-6 for
correlations between parameters and seconds.
° If omitted or 0, the default value of 10 is used.
PIGGYBACKED.ACKNOWLEDGMENTS= (PBA=)
° Specifies whether the NETBIOS protocol sends and receives
acknowledgments piggybacked with incoming data. If PBA is
enabled, the acknowledgment of the frame received is sent as
a piggyback on the next frame transmitted. If PBA is
disabled, a separate acknowledgment frame is sent.
° Must be a decimal value from 0 to 5.
° When set to 0, the workstation neither sends nor requests
piggybacked acknowledgments.
° If omitted, the default value of 0 is used.
+------------------------------------------------------------------------+
| Figure 4-6. DLC Timer Values |
+-----------------------+------------------------+-----------------------+
| DLC.T1 | DLC.T2 | DLC.TI |
| (RESPONSE) | (ACKNOWLEDGMENT) | (INACTIVITY) |
+---------+-------------+---------+--------------+---------+-------------+
| Parm | Seconds | Parm | Seconds | Parm | Seconds |
+---------+-------------+---------+--------------+---------+-------------+
| T1=1 | 0.2-0.4 | T2=1 | 0.04-0.08 | TI=1 | 1-2 |
+---------+-------------+---------+--------------+---------+-------------+
| T1=2 | 0.4-0.6 | T2=2(1) | 0.08-0.12(1) | TI=2 | 2-3 |
+---------+-------------+---------+--------------+---------+-------------+
| T1=3 | 0.6-0.8 | T2=3 | 0.12-0.16 | TI=3 | 3-4 |
+---------+-------------+---------+--------------+---------+-------------+
| T1=4 | 0.8-1.0 | T2=4 | 0.16-0.20 | TI=4 | 4-5 |
+---------+-------------+---------+--------------+---------+-------------+
| T1=5(1) | 1.0-1.2(1) | T2=5 | 0.20-0.24 | TI=5 | 5-6 |
+---------+-------------+---------+--------------+---------+-------------+
| T1=6 | 1-2 | T2=6 | 0.4-0.8 | TI=6 | 5-10 |
+---------+-------------+---------+--------------+---------+-------------+
| T1=7 | 2-3 | T2=7 | 0.8-1.2 | TI=7 | 10-15 |
+---------+-------------+---------+--------------+---------+-------------+
| T1=8 | 3-4 | T2=8 | 1.2-1.6 | TI=8 | 15-20 |
+---------+-------------+---------+--------------+---------+-------------+
| T1=9 | 4-5 | T2=9 | 1.6-2.0 | TI=9 | 20-25 |
+---------+-------------+---------+--------------+---------+-------------+
| T1=10 | 5-6 | T2=10 | 2.0-2.4 | TI=10(1)| 25-30(1) |
+---------+-------------+---------+--------------+---------+-------------+
| | | T2=11 | Disabled | | |
+---------+-------------+---------+--------------+---------+-------------+
| (1) Default value |
+------------------------------------------------------------------------+
4.5 NETBIOS Adapter Transmit and Receive Buffer Default Sizes
When the adapter is opened by NETBIOS, transmit and receive buffer sizes
of the adapter are determined by NETBIOS, unless specifically overridden.
The adapter type and the number of link stations are used to determine
these values, as shown in the following tables.
NOTE: The Data Holding Buffer (DHB) = the adapter transmit buffer size.
The Number of DHBs (DHB.NUMBER) = the number of transmit buffers.
+------------------------------------------------------------------------+
| Figure 4-7. Token-Ring Network Adapter with 8 KB of Shared RAM |
+-----------------+------------------+-----------------+-----------------+
| | | Transmit | |
| Number of Link | Number of | Buffers in | Receive Buffers |
| Stations | Transmit Buffers | Bytes | in Bytes |
+-----------------+------------------+-----------------+-----------------+
| 1 to 6 | 2 | 1048 | 280 |
+-----------------+------------------+-----------------+-----------------+
| 7 to 12 | 1 | 1048 | 192 |
+-----------------+------------------+-----------------+-----------------+
| 13 to 18 | 1 | 600 | 144 |
+-----------------+------------------+-----------------+-----------------+
| 19 to 24 | 1 | 600 | 112 |
+-----------------+------------------+-----------------+-----------------+
| More than 24 | 1 | 600 | 96 |
+-----------------+------------------+-----------------+-----------------+
+------------------------------------------------------------------------+
| Figure 4-8. Token-Ring Network Adapter with More Than 16 KB and Less |
| Than 64 KB of Shared RAM |
+-----------------+------------------+-----------------+-----------------+
| | | Transmit | |
| Number of Link | Number of | Buffers in | Receive Buffers |
| Stations | Transmit Buffers | Bytes | in Bytes |
+-----------------+------------------+-----------------+-----------------+
| 1 to 32 | 2 | 4192 | 280 |
+-----------------+------------------+-----------------+-----------------+
| 33 to 48 | 2 | 4192 | 280 |
+-----------------+------------------+-----------------+-----------------+
| 49 to 64 | 1 | 4192 | 280 |
+-----------------+------------------+-----------------+-----------------+
| More than 64 | 2 | 2040 | 280 |
+-----------------+------------------+-----------------+-----------------+
+------------------------------------------------------------------------+
| Figure 4-9. Token-Ring Network Adapter with 64 KB of Shared RAM |
+-----------------+------------------+-----------------+-----------------+
| | | Transmit | |
| Number of Link | Number of | Buffers in | Receive Buffers |
| Stations | Transmit Buffers | Bytes | in Bytes |
+-----------------+------------------+-----------------+-----------------+
| 1 to 32 | 2 | 4192 | 280 |
+-----------------+------------------+-----------------+-----------------+
| 33 to 48 | 2 | 4192 | 280 |
+-----------------+------------------+-----------------+-----------------+
| 49 to 64 | 2 | 4192 | 280 |
+-----------------+------------------+-----------------+-----------------+
| More than 64 | 2 | 2040 | 280 |
+-----------------+------------------+-----------------+-----------------+
4.6 NETBIOS Determination of Session Data Transmit Frame Size
When a session is established between two NETBIOS nodes, the length of the
largest data frame sent between the two sessions is determined by three
factors:
1. The size of the sender's transmit buffer
2. The amount of receive-buffer space in the receiver
3. The maximum frame that can pass any bridge in the path.
On each side (node) the receive-buffer space calculation is made in the
following way:
° The number of receive buffers is calculated.
° One-half of the number of receive buffers is multiplied by the data
size of one buffer. This determines the maximum size frame that can
be transmitted to the session. The purpose of this is to ensure that
one adapter can hold two maximum-size received frames.
4.7 Work Area Considerations for LAN Support Program Custom Version 1.01
The LAN Support Program Custom Version 1.01 allocates 282 bytes of work
area for the IEEE 802.2 interface device driver, DXMC0MOD.SYS. For most
configurations, this should be sufficient. However, this work area can be
used up when many additional SAPs and link stations are configured using a
combination of the parameters MINSAP and MINLINK with DXMC0MOD.SYS and
STATIONS, EXTRA.STATIONS, and EXTRA.SAPS with DXMT0MOD.SYS. If you have
received the error message DXMT0 31E:, if your application program fails
to run, or if you want to know whether the work area can support the
number of SAPs and STATIONs that you need, use the following formula:
Work Area = 48 + (SAPS x 36) + (STATIONS x 6)
If the work area is greater than 282 bytes, you must either reduce the
required number of SAPs and link stations, or use one of the stand-alone
versions of the program. See "Using a Stand-Alone Version of the LAN
Support Program" in topic 1.1 for information about the stand-alone
versions.
Please see the LEGAL - Trademark notice.
Feel free - send a 
for any BUG on this page found - Thank you.