Release Notes for NLM Release 6.2M15
Version 6 Release Notes
Operating System: NLM
Version From: Release 6.2M15
This document describes features and limitations for the release of
Progress Version 6.2M15 for the Netware NLM environment.
* CLIB.NLM Needed
In order for 6.2M15 NLM to work, the following version of clib.nlm is
needed.
clib.nlm v3.11d file size: 267068 bytes Date: 12-16-92
This clib.nlm is the oldest version that can be used with Progress.
any version after 12-16-92 should work fine. This clib.nlm can be
obtained via Compuserv or your local Netware vendor. PROGRESS does
not have permission to distribute this file.
* _MPROTLI.NLM ONLY
Only the _mprotli.nlm executable is supported and shipped. You must
make sure that you incorporate the -N tli startup option on the NLM
load as well. If this is not done, the PROGRESS NLM will not be
stable.
Example load line: load _mprotil vol1:\database\testdb -N tli -B 2000
* AFTER IMAGING SUPPORT
If you are using after-imaging with your current NLM product, you will
have to disable after-imaging on your database, and restart
after-imaging again. Steps on how to do this are documented in the
System Administration II manual. This is needed in order to address
a problem in prior versions of the NLM product which have been fixed
in 6.2M15. If this is not done, you will not be able to roll forward
your after-image file when the time comes to do so.
*SUPPORT FOR 250 USERS
This release allows up to 250 simultaneous users to connect to the
NLM database engine. You must use the _MPROTLI.NLM with the
-N TLI startup parameter.
NOTE: Your server does NOT have to be configured to use TCP/IP.
If your server is NOT configured to use TCP/IP, you will see a
message on the NLM screen when loaded that states that it can not
find an entry in the /etc/services file for the -S startup parameter.
This can be ignored if you are only going to have SPX clients.
*NETWARE 4.01 SUPPORT
This is a release of our NLM product that, in addition to Netware 3.11
will work with Netware 4.01. We are currently in the process of
becoming Netware Certified on Netware 4.01.
The NLM will work in both ring 0 and ring 3.
*STARTUP 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.
*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.
*MESSAGE BUFFER SIZE
The Message Buffer Size (-Mn) 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 # 12500