Kbase 15593: Release Notes for 7.3C05 NLm product
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Release Notes for 7.3C05 NLm product
PROGRESS Version 7 Release Notes
Release: 7.3C05
Platforms: Novell NetWare v3.12, v4.1
Products: NLM Workgroup Database Server
Date: December 1995
For more information on how to run the PROGRESS database server as a
Netware Loadable Module (NLM), please see Chapter 5, "NetWare Loadable
Modules",the PROGRESS Networks Guide for more information.
1. CONFIGURATION INFORMATION
1.1 TLI Implementation
1.2 Message Buffer Size
1.3 Required Standard NetWare NLMs
1.4 Novell SPX Clients to the NLM Server
2. KNOWN ISSUES
2.1 Alloc Memory Check
2.2 Database Server Screen
2.3 NLM Server Unload and Shutdown
2.4 Synchronous Writes
2.5 Insufficient Disk Space
Configuration Information
The following section contains information about configuring
the PROGRESS NLM Server.
1.1 TLI Implementation
The PROGRESS Version 7.3C NLM Server uses the TLI (Transport Layer
Interface) to communicate with clients. The Network Type (-N)
startup parameter is no longer a valid startup option for
loading the PROGRESS NLM. Due to the TLI implementation,the
PROGRESS Version 7.3C NLM Server cannot service NetBIOS clients.
1.2 Message Buffer Size
The PROGRESS Version 7.3C NLM Server automatically starts up with
a message buffer size of 512 bytes to accommodate SPX clients.
TO connect TCP/IP clients the NLM Server successfully, you must set
the Message Buffer Size (-Mm) startup parameter to 512.
Note: The Message Buffer Size (-Mm) startup parameter is required
only for clients running PROGRESS Version 7.3 or earlier.
It is not required for PROGRESS Version 8 clients.
1.3 Required Standard NetWare NLMs
The PROGRESS Version 7.3C NLM Server requires that the TLI and
CLIB NLMs be loaded to service SPX clients. The TCP/IP NLM is also
required to service TCP/IP clients. The NWSNUT.NLM needs to be loaded
to provide the utility user interface for PROGRESS NLM. If these NLMs
were not previously loaded, the PROGRESS NLM Server automatically loads
them. Progress Software Corporation recommends you use CLIB.NLM
Version 3.12i.
For the PROGRESS NLM Server to service TCP/IP, TCP/IP must first be
fully operational on you NetWare file server. For example, you should
be able to PING the file server from a PC installed with TCP/IP. Be
sure this is the case before you try to connect to the NLM Server over
tcp/ip. A valid service name for the PROGRESS NLM Server must exist in
sys:\etc\services file. If a service name is not explicitly denoted
with the Service Name (-S) startup parameter upon loading the NLM,
the database name is used as the service name. If the database name
is not listed as a service in the sys:\etc\services file, the
PROGRESS NLM Server does not start up TCP/IP, but it does
start up SPX.
1.4 Novell SPX Clients to the NLM Server
Novell continues to update support files for MS-Windows and the
IPX/SPX protocol. The latest version (v1.21) of NetWare Client for DOS
and MS-Windows has been tested with the PROGRESS Version 7.3C NLM Srv.
No issues were encountered. Progress Software Corporation strongly
suggests that you use the latest support for MS-Windows and DOS
(v1.21) which can be acquired either from your local Novell
reseller or from the NetWare v4.1 Server Installation kit.
However, if you use a previous version of NetWare DOS/MS-Windows
Client, be aware of an issue described by Novell as "the black
screen of death syndrome," where the screen goes black with a cursor
left in the upper-left corner of the screen. This occurs only when
running applications that use SPX, such as a PROGRESS Version 7 client
connected to a PROGRESS Version 7.3C NLM Server over SPX. To avoid
this issue and any issue with similar symptoms, use the latest release
of these files and use the ODI implementation of IPX. Install the most
recent drivers that can be acquired either from your local Novell
reselleror from the NOVFILES forum on CompuServe, which you can
access with a GO NOVFILES.
If you are running MS-Windows in standard mode, load the TBM12.COM TSR
before you start MS-Windows.
If you are running MS-Windows in 386 Enhanced mode, verify that the
system.ini file has the following line in the [386Enh] section:
network=*vnetbios, vnetware.386, vipx.386
If you run a non-Windows application and open a DOS session or
execute a DOS command with DOS, DOS SILENT, or OS-COMMAND 4GL
statements, the SPX connection might be lost if you are not using
the proper versions of NetWare for MS-Windows support files.
KNOWN ISSUES
The following sections present current issues related to the PROGRESS
NLM Server. Progress Software Corporation is working with Novell
to resolve these isues.
2.1 Alloc Memory Check
If the Version 7.3C PROGRESS NLM Server is loaded onto a v4.1 server
that has "set alloc memory check flag=on," the Server will abend. This is
is a developer's debugging option as the default is set to off.
2.2 Database Server Screen
Because the PROGRESS NLM Server screen has a limit of 76 characters,
the whole stream for the database path might not be displayed.
2.3 NLM Server Unload and Shutdown
When you are in the process of shutting down or unloading your
Server at the same time as an abnormally terminated client
connection, the PROGRESS NLM Server could take approximately
fifteen minutes to complete the shutdown.
2.4 Synchronous Writes
Use of older versions of the Novell supplied CLIB.NLM could
cause corruption of after-image (AI) extents upon an abnormal
termination of the PROGRESS NLM Server. This only occurs with
multi-volume AI extents and Progress Software Corporation recommends
you use the following:
1. NetWare Server Version 3.12: CLIB.NLM Version 3.12i (June 15,1995")
2. NetWare Server Version 4.10: CLIB.NLM Version 4.10d (March 7,1995")
2.5 Insufficient Disk Space
When you attempt to unload the PROGRESS NLM Server, you might
encounter a Small Memory Allocation error if one of the following
conditions exists:
1. There is insufficient disk space during a write to an after image
(AI) extent.
2. After a Limbo transaction occurs using 2-phrase commit in a
distributed database environment.
Progress Software Technical Support Note # 15593