Kbase 11117: Release Notes for NLM 6.2M
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  5/10/1998 |
|
Release Notes for NLM 6.2M
?Version 6 Release Notes
Operating System: NLM
Version From: Release 6.2M
July, 1992.
This document describes features and limitations for the release of
PROGRESS Version 6.2M for the Netware NLM environment.
o NETWORKING - TLI SUPPORT.
There is now a second PROGRESS NLM executable: _MPROTLI.NLM.
This new executable will now allow the PROGRESS NLM the ability
to service both SPX and TLI (TCP/IP clients). To service SPX
clients, the "-N spx" startup option can be used. However, a new
startup option, "-N tli", has been added to provide service for
either SPX or TCP/IP clients. Although the default is SPX, both
SPX and TCP/IP clients can be supported simultaneously, depending
on NLMs loaded.
Note that the new PROGRESS NLM executable will only support Novell
3.11, and should be used if you are connecting TCP/IP clients.
However, because _MPROTLI.NLM requires additional NLMs to be loaded,
using _MPROSRVE.EXE when you have only SPX clients will require less
memory overhead than _MPROTLI.NLM.
In order to service PROGRESS TCP/IP clients, you must load
CLIB.NLM, SNMP.NLM, and TCPIP.NLM. Note that dependencies exist
between NLMs and the operating system will find a required NLM
and load it before loading an NLM that depends on the services it
provides. Additional information regarding the loading of NLMs can
be found in chapters two and three of the Novell TCP/IP Supervisor
Guide.
o START-UP PARAMETERS - autoexit
The new "-autoexit" start-up parameter will remove the pause and
message "<Press any key to close screen>" on the PROGRESS NLM
Server console screen upon shutdown of the PROGRESS server.
o START-UP PARAMETERS - yield
The new "-yield" start-up parameter "relinquishes control" to the
Netware operating system more frequently and therefore will provide
more accurate utilization data for the monitor.nlm utility. While
this option will cause the monitor to lower the utilization number
displayed, it will not provide additional CPU resources to other NLMs.
This parameter does not apply to the _MPROTLI.NLM.
NOTE: This parameter may adversly affect the performance of PROGRESS
and its use is not recommended.
o START-UP - PARAMETER FILES.
Parameter files created with edlin in the DOS line editor are not parsed
by the PROGRESS NLM server correctly. You get the following error from the
server when you try to load PROGRESS with -pf <filename>:
** Could not recognize argument:
The problem has to do with the last three bytes in the parameter file. While
parameter files created by PROGRESS and some other editors end with <return>
<new-line>, edlin files end with <return> <new-line> <space>. If you remove the
last byte <space>, then PROGRESS will read the parameter file correctly.
o MESSAGE BUFFER SIZE
The Message Buffer Size (-Mm) startup option is fixed at 512 bytes for a client
or server running on an SPX network with -N SPX. Since the server is incapable
of servicing multiple protocols with mixed message sizes, the largest Message
Buffer Size allowed for TCP/IP is also 512. For example, specifying -Mm 1024
for either _MPROSRV.EXE or _MPROTLI.NLM is invalid.
Progress Software Technical Support Note # 11117