Consultor Eletrônico

Release notes for DOS 6.2m21

Version 6 Release Notes
Operating System: DOS
Version From: Release 6.2M21
July 1994

This document describes the features and limitations for the release of
PROGRESS Release 6.2M21.

o DISK SPACE NEEDED FOR INSTALL

The following is a minimum disk space requirement needed before installing
PROGRESS:

PROGRESS 4GL 26MB
PROGRESS 4GL/Fast Track/Results: 38MB
PROGRESS 4GL/Fast Track/Results/Toolkit: 49MB

Due to the new compressed media, this is the amount of space needed for
installation only; it does not reflect the amount of space PROGRESS needs
after installation.

o MERGE OPTION DURING INSTALL

If you use the MERGE option to install a client package over a dos server
package, the install will not work. If you are going to MERGE a client
package and a dos server package together, you must install the client
package first; then install the dos server package (merge) to the
same directory. If the dos server product is installed as an update,
the client progress.cfg file will be renamed to progress.cbk.

o INSTALLATION

If you choose to install PROGRESS in non-default directories (directories
other than \DLC and \DLCLOAD), PROGRESS can create only the destination
directories if the parent directories already exist. For example,
if you installed to \USR\DLC and \USR does not exist, then PROGRESS
returns the following error message:

INSTALL ERROR (06): Unable to make directory c:\usr\dlc

However, if you create the parent directory (in this example \usr) beforehand,
you can successfully install the software.

o NETWORK VERSION (-Nv 12) STARTUP PARAMETER

PROGRESS provides a switch to allow client access to older servers.
If you are connecting to a PROGRESS Version 5 or Version 6.2A-6.2F server,
you must set the -Nv startup parameter to 12 on the client. This is
documented in the Version 6 Documentation Bulletin's V and higher.

o R-CODE COMPATIBILITY

There is no r-code compatibility between 6.2M and any PROGRESS releases
lower than 6.2Hxx. Therefore, you must recompile previous applications
to use them with PROGRESS release 6.2M. However, PROGRESS r-code is
interchangeable among 6.2Hxx, 6.2J0x and 6.2Mxx DOS, OS/2, and Windows
products.

o MESSAGE BUFFER SIZE (-Mm) STARTUP PARAMETER

The Message Buffer Size (-Mm) startup parameter is fixed at 512 for a client
or server running on an SPX network with -N SPX. For example, specifying
-Mm 1024 is invalid.

o PROLOG UTILITY LIMITATION

There are upper and lower limits on the size of a log file in which the PROLOG
utility will work. The upper limit size is approximately 39K and the lower
limit is approximately 3K. If the size of the log file is outside of these
limits, the PROLOG utility will appear to have worked, but it will not change
the size of the log file.

o DBANALYS ON MULTI-VOLUME DATABASE

If your database is larger that 65.5 MB, an erronous message "free chain
is a circular list" appears when you run a DBANALYS. Ignore this
message.

o ERGO LIBRARY ENVIRONMENT

The PROGRESS protected-mode product uses a third-party product from ERGO
Computing. This is a DOS extender for accessing more than the 640k
of memory normally available for DOS programs. There is a built-in limitation
of approximately 1,500 bytes on the size of the environment in use that can be
passed to PROGRESS.

If the environment is close to this size or is close to the limits configured
in the config.sys file, then PROGRESS fails with a PLOADER error, requiring
a reboot. ERGO Computing has confirmed the problem still exists in the latest
release (2.10.06).

The work around is to enter the following line into the config.286 file or the
file identified by the environment variable AIA:

ldtsize=xxxx (where xxxx is between 128 and 8096; the default is 1024.)

See the DOS installation guide for more information on the
AIA environment variable and configuration file.

o FAST TRACK (500 File Limit)

Unlike lower releases, FAST TRACK Release 6.2Hxx and higher enables you to
choose from more than 500 files when creating QBFs, reports, menus, or forms.
Now there is no limit to the number of files you can select. However, because
of internal changes to the FAST TRACK code, you must recompile any QBFs,
reports, menus, or forms generated with lower releases of FAST TRACK to run
them under release 6.2Hxx.

o RESULTS INSTALL

When you install RESULTS as an add-on product, there are three ways to
implemented it. One is to reinstall PROGRESS with RESULTS. Another is
to install RESULTS as an update to PROGRESS. Yet another is to replace every
instance of DLC with the proper directory in every batch file where you
install RESULTS.

o INDEX DEACTIVATION

Deactivate indexes through the Index Editor. Deactivating indexes through
the Administration menu in the Data Dictionary deactivates the
top index. For example, in the customer file there are three indexes:
Cust-num, State, and Zip. If you use the Administration menu to deactivate
Zip, it deactivates Cust-num as well as Zip.

o LEAVE MEMORY (-lm) STARTUP PARAMETER

The Leave Memory (-lm) startup parameter is not supported in this release.
This
option is used with lower releases of PROGRESS because they allocate all
available memory at startup. Beginning with 6.2H13, PROGRESS allocates
memory dynamically.

o MULTI-VOLUME DATABASES - PROSTRCT ADD

If you define a variable-length extent and then use the PROSTRCT ADD command
to add another variable length extent, the command does not work correctly. It
should convert the previous variable-length to a fixed-length extent, but it
does not. To work around this problem, do not use the PROSTRCT ADD command.
Instead, create a new structure file. Define all of the extents you want
to use, including any new extents. Create a new empty multi-volume database and

use the PROCOPY command (or the PROBKUP and PROREST commands) to copy the
contents of the old multi-volume database to the new one.

o PROREST UTILITY

Restoring an incremental backup out of sequence causes you to lose data.
For example, if you restore incremental 2, then restore incremental 1, you
lose the data restored from incremental 2. PROGRESS returns a message that
tells
the tapes are out of sequence, but there is no warning about the data loss.

o PRODB UTILITY

The PRODB command does not work properly on a network drive when the source
and target names are the same.

o PROBUILD AND MICROSOFT C v7.00

PROGRESS 6.2M21 supports the PROBUILD utility with Microsoft C v7.00 and
Microsoft C++ v1.0. You may only build real mode executables with these
versions of Microsoft C. If you require to build a protected mode executable,
it is required that you obtain Microsoft C v6 and Ergo's Dos Extender SDK.


o PROBUILD AND PCNFS FOR PROGRESS IN REAL MODE

Due to the size of the PCNFS libraries, when you choose PCNFS you must limit
the
User Configurable Elements (UCE) you choose via the PROBUILD utility. Choosing
the PCNFS option along with too many other elements causes the data size of the
PROGRESS executable to exceed 64K. The following run-time error results when
you exceed this limit:

run-time error R6000
- stack overflow

It is recommended that you include no more than one gateway in any module
containing PCNFS. Also, if the NETBIOS or SPX network protocols are not
needed,
eliminate them from the link process.

o NLM AND "DATABASE UNAVAILABLE" ERROR

If you have problems connecting to a NLM server and recieve either
"Database unavailable" or "Cannot located database" errors, try using the
(-S) startup parameter on both the NLM startup and client startup.

o NEW NETBIOS WARNING MESSAGE

There is a new error message that can occur during Multi-user startup:
"Netbios not proven, PROGRESS continues."
This is a warning message that implies either you are running a Netbios that
Progress does not recognize at startup or that Netbios is not loaded. Progress
should work if Netbios is loaded. This message will occur if you are using
IBM's Netbios or a Netbios that uses interupt 5c.

o TASK SWITCHING AND PROGRESS (MULTI-USER MODE)

You will be disconnected from a remote database if you switch from
PROGRESS to another task.

o PROTECTED MODE PROGRESS AND HP-TCP/IP / DECNET TCP/IP

If you try to restart a PROGRESS session a second time using
HP ARPA Services or DECNET TCP/IP, the machine hangs. The first session
works fine.

o PUT CONTROL AND FORM HEADER (PAGE-TOP)

If you use PUT CONTROL out to a printer, and you also have a FORM
HEADER (PAGE-TOP), the FORM header will NOT display on the first page of
output.

o PROSHUT AND TCP/IP

The supplied PROSHUT executable supports SPX, NETBIOS, and FTP
TCP/IP. If PROSHUT is needed for another type of TCP/IP, you must perform
a PROBUILD for that specific flavor of TCP/IP.

o FTP PC/TCP AND PERFORMANCE

In order to get optimal performance with Progress and FTP's PC/TCP product,
we require that you use FTP v2.3 or greater.

o FTP PC/TCP CONNECTION

The "get_ipx:jet ipconfig:noerror" message appears when you connect
to a UNIX database using FTP. This is a normal status message.

o PROTECTED MODE PROGRESS AND PCNFS

For PCNFS and protected mode PROGRESS to work correctly,
you must use the config.286 file with the pspswitch=0 entry included. The AIA
environment variable is used to point to the config.286 file.

o LAN WORKPLACE FOR DOS: THE EXCELAN ENVIRONMENT VARIABLE

PROGRESS uses the EXCELAN environment variable to look for the hosts and
services files when connecting via LAN Workplace for DOS (-N TCP).
See the EXCELAN/LAN Workplace for DOS documentation for information on the
EXCELAN environment variable.

o DOS CLIENTS TO RDB GATEWAY

All 6.2Mxx clients going to RDB Gateway on VMS have to upgrade their VMS
PROGRESS release to 6.2L10 or higher. There have been significant changes
to the RDB Gateway on both the VMS and DOS sides.

o REMOTE NET ISAM

Remote NET ISAM is not supported in this release of PROGRESS.

o 6.2MXX REMOTE CLIENT WITH C-ISAM GATEWAY

Be aware of the following behavior with 6.2M client and 6.2L server using
the C-ISAM gateway:

- Use exlusive locks when updateing, otherwise a disconnection will
occur.
- If you press Ctrl+Break at any time during a client session, a
disconnection will occur.

All transactions that take place prior to the disconnection are not backed
out. These behaviors are not present with PROGRESS 6.3 server.

o ADDING DECIMAL FIELD WITH C-ISAM GATEWAY

If you add a decimal field using 6.2Mxx client against a 6.2L server C-ISAM
gateway, you must restart the PROGRESS session in order for the changes
to take place.

Progress Software Technical Support Note # 13245