Consultor Eletrônico

Release Notes for Windows 6.2J01


Version 6 Release Notes

Operating System: DOS WINDOWS
Version From: Release 6.2J01
September, 1992


This document describes limitations and new features for the release
of PROGRESS Version 6.2J01 under Microsoft Windows.


o DLC ENVIRONMENT VARIABLE

In order for PROGRESS windows to work, the DLC environment
variable must be set. Be sure to include the drive letter and the complete
pathname. For example: SET DLC=C:\DLC


o USAGE INFORMATION FOR KEYCODES 651 THRU 654 UNDER WINDOWS

CODE NAME USAGE
651 LEFT-MOUSE-DOWN Sent when the Left Mouse button is pressed
inside a CHOOSE. This is sent before
the button is released.
652 LEFT-MOUSE-MOVE Sent if the mouse is moved while the left button
is down inside a CHOOSE.
Currently, this Key-code is not implemented.
653 MIDDLE-MOUSE-UP Sent when the middle button of a three button
mouse is released.
654 RIGHT-MOUSE-UP Sent when the right button is released.


o PIFS FOR PROGRESS DOS EXECUTABLES

The PROGRESS windows installation process creates Program Information Files
(PIFs) for the utilities. However, the tailoring of these files is incomplete.
If you choose to install PROGRESS somewhere other than c:\dlc, you must edit
the PIFs manually to indicate the start-up drive and directory.
Consult your windows documentation for the correct procedure for editing
PIFs. The files to edit are:

rundosmw.pif
prodb.pif
proutil.pif
prolib.pif
proshut.pif
quoter.pif
cmpdb.pif
prodel.pif
prolog.pif

Once you edit the files, save them in the DLC directory. See Section 8 of the
Installation Notes for other information.


o NETWORK VERSION (-Nv 12) START-UP OPTION

PROGRESS provides a new 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 start-up option to 12 on the client.
This is documented in the Version 6 Documentation Bulletins V and higher.


o R-CODE COMPATIBILITY

There is NO r-code compatibility between 6.2J and any PROGRESS versions
lower than 6.2H0x. Therefore, you have to re-compile previous applications
to use them with PROGRESS versions 6.2J. However, PROGRESS r-code is
interchangeable between 6.2H0x and 6.2J DOS, OS/2, WINDOWS and client
products.


o MESSAGE BUFFER SIZE (-Mm) START-UP OPTION

The Message Buffer Size (-Mm) start-up option is fixed at 512 for a client
or server running on an SPX network with -N SPX. For example, specifying
-Mm 1024 is ignored when used with -N SPX.


o PROLOG UTILITY LIMITATION

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


o FAST TRACK (500 FILE LIMIT)

Unlike lower versions, FAST TRACK Version 6.2Hx 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 re-compile any QBFs, reports, menus, or forms generated
with lower versions of FAST TRACK to run them under Version 6.2H01 or
higher.


o INDEX DEACTIVATION

If you are deactivating indexes, do it 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 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 (.st). 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 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. You receive a message telling you
that the tapes are out of sequence, but there is no warning about the data loss.


o PROGRESS APPLICATION DEVELOPMENT SYSTEM (PADS)

When you run PROBUILD, the application prompts you for the directory where you
want to install the load script (link script). Use the default directory (which
is your current directory). The configuration utility does not work properly if
you specify any directory other than the default directory.

The euc.p procedure used during the PROBUILD is now in an r-code library called
"euc.pl". Therefore, you must now place the r-code library in the propath.
For example:
PROPATH=%PROPATH%;%DLC%\dlcload\eucapp\euc.pl


o NETWORKING - SPX PROTOCOL.

Novell continues to update their support files for Microsoft Windows and
the IPX/SPX protocol. The following is a list of files required for the
effective operation of PROGRESS for MS-Windows Version 6.2J.

IPX.COM Version 3.10 or greater.
NWIPXSPX.DLL Version 1.31 or greater.
VNETWARE.386 Version 1.04 Build 92-045 or greater.
NETWARE.DRV Version 2.00 Release, Build 92-044 or greater.
VIPX.386 Version 1.11 (920213) or greater.

TBMI2.COM Version 2.1 or greater (MS-Windows 3.1 and DOS 5.0)
or
TBMI.COM Version 1.0 or greater.


For 386Enhanced Mode Windows verify the system.ini file has the following
line in the 386 Enhanced section:

network=*vnetbios,vnetware.386,vipx.386


For Standard Mode Windows execute either TBMI2.COM or TBMI.COM prior to
executing windows.

These files are a subset of the NetWare Workstation Kit
for DOS/Windows v2.0 available from Novell Corp.


o LANGUAGE - DOS STATEMENT.

It had been noticed that the PROGRESS for MS-Windows client can get
disconnected from a remote database if a non-windows application, a DOS
session or the DOS Statement is used while you are connected to the
remote PROGRESS server using the SPX Protocol.

This was resolved in 6.2J through the use of the latest NetWare
Workstation Kit for DOS/Windows v2.0 available from Novell Corp.

If this issue still occurs verify that the latest version of Netware's
MS-Windows toolkit is being used and refer to the section on
NETWORKING - SPX PROTOCOL in this document.


o PROLIB - LARGE NUMBERS OF .r FILES

Adding large numbers of .r files to an r-code library can result in
the user getting "STGET out of storage errors." Usually the number
involved is quite large (900+) and it is recommended that you place the
files in multiple libraries in this case.


o LANGUAGE (OUTPUT TO PRINTER)

Under Windows, you can choose either of two possible printing modes:

- Default mode. In this mode, PROGRESS uses the Microsoft Windows
device drivers. This mode is sufficient for all basic printing
that does not use any printer access control codes (whether sent
by PUT, PUT CONTROL, or DISPLAY statements).

- Windows pass-through printing (WPP). In this mode, PROGRESS
by-passes the Windows device drivers. This means you can send
control codes (such as POSTSCRIPT commands) directly to the
printer with the PUT, PUT CONTROL, or DISPLAY statements.

NOTE: When you use WPP mode with a POSTSCRIPT printer, standard reports,
such as those produced by the Data Dictionary or RESULTS, do not
print properly.

WPP mode can be enabled in either of two ways. You can explicitly enable
WPP mode at PROGRESS start-up or PROGRESS automatically switches to WPP
mode when you perform certain operations.

To explicitly enable WPP mode at start-up, specify one of the following
PROGRESS start-up parameters:

-wpp Enables WPP mode for the session.

-wpconvert Enables WPP mode and automatically converts
OEM characters to the ANSI character set before
sending them to the printer. This conversion is
required to correctly print some international
character sets. (This conversion is also performed
in default mode.)

-wplf Enables WPP mode for the session and modifies
the end-of-line behavior. Normally, in WPP mode
each output line ends with a carriage return and
a linefeed character. When you specify the -wplf
parameter, only a linefeed character is sent at
the end-of-line.

When you enable WPP mode at PROGRESS start-up, the mode remains in effect for
the entire PROGRESS session.

PROGRESS automatically switches to WPP mode under the following conditions:

- The first output you perform after setting output to the printer
is a PUT CONTROL statement. You can switch to WPP mode, for example,
by executing the statement PUT CONTROL NULL.

- You execute a DISPLAY or PUT statement to the printer with ESC (ASCII
decimal 27) as the first character. This statement must be the first
output you perform to the printer; otherwise, you received an error
message that refers to mixed modes.

- You specify PAGE-SIZE 0 for a non-postscript printer.

In each of these cases, WPP mode remains in effect until OUTPUT CLOSE is
executed.

When using WPP mode, you must be aware that different print drivers send
different initialization sequences to the printer. For example, if you switch
to WPP mode for a POSTSCRIPT printer by executing a PUT CONTROL NULL statement,
the printer is left in an odd state. The "initmatrix" POSTSCRIPT command
fixes this. For further information on this command, refer to your POSTSCRIPT
documentation.

If you receive a printer error that refers to mixed modes, try using WPP mode
for the entire session.

For some printers, you must disable the Windows Print Manager when you use
WPP mode. This is the case, for example, if you are using an HP LaserJet
printer.

If you are using a POSTSCRIPT printer in default mode, you must ensure that
the Paper Size on the Configuration Setup menu is set to "note 8 1/2 X 11".
You must also set the Margins on the Options submenu to Default (not None).
Otherwise, you will lose some characters at the page top or left margin of
your printout.

PROGRESS for MS-Windows will send this output to the default printer
configured for windows. If a device other than the default printer
is the required destination it will be necessary to change the default
printer device for windows. Please refer to the documentation supplied
with windows for configuration details.


o WRITE CACHE UTILITIES

To ensure database integrity, place your database files, before-image file,
and after-image file on disk volumes where write caching is disabled. When
write caching is enabled, PROGRESS cannot be certain that database blocks
are written as planned. If a system failure occurs, database blocks may
be lost and your database may become corrupted.

Note: The latest version of the SmartDrive disk cache utility included with
MS-Windows 3.1 is now capable acting as a write cache.


o LANGUAGE - DISCONNECT STATEMENT

If you are connected to more than 5 SPX based PROGRESS Servers and attempt
to disconnect from each within the PROGRESS 4GL code after the last database
is disconnected any following 4GL code is ignored.


o AS/400 CLIENT: SCHEMA HOLDER - SPX PROTOCOL

If the AS/400 schema holder is to be connect via the SPX protocol it
will be necessary to start the AS/400 database with "-Mm 512" to
allow compatibility with the SPX protocol also being used.


o AS/400 CLIENT: MULTI-USER - EXCLUSIVE-LOCK

With multiple procedures accessing records with an EXCLUSIVE-LOCK some
unpredictable results or errors may be encountered.

Example:
Procedures which do block deletions while other users may be updating or
displaying records with EXCLUSIVE-LOCK from the same file.


o AS/400 CLIENT: INTERNAL - INDEX-CURSORS

When updating key fields the index cursor also gets updated.

Example:
The order in which procedures that update records sequentially may
change if the key index field is modified.


o AS/400 CLIENT: LANGUAGE - MULTIPLE EXTENTS

When modifying data within fields defined with multiple extents
unexpected results may occur if the array subscript reference is
not used in the data assignment.


o PROSHUT FOR DOS AND MS-WINDOWS

You can now use the PROSHUT utility from a DOS or MS-WINDOWS client
machine to disconnect users from or shut down any remote broker/server
(including DOS and NLM). You can use PROSHUT as described in the
PROGRESS SYSTEM ADMINISTRATION II manual, but you must also include the
client start-up parameters required to use the network protocol expected
by the remote broker/server.


o EXIT FROM MS-WINDOWS

This release of PROGRESS for MS-WIndows will notify the user if the
PROGRESS session is active against a database and prompt the user
to close the PROGRESS session before exiting Windows.

Progress Software Technical Support Note # 11116