Kbase 12528: Release Notes for V7.2A for MS-Windows
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Release Notes for V7.2A for MS-Windows
PROGRESS V7.2A RELEASE NOTES
PLATFORM: MS-Windows v3.1
MEDIA TYPE: 3 1/2" Diskette
SOFTWARE RELEASE: 7.2A
EXTRACT COMMAND: Not Applicable
INSTALL COMMAND: WIN DRIVE_LETTER:INSTALL
** IMPORTANT **
Any PROGRESS version 6 databases *MUST* have its before image file
truncated prior to converting it to a V7.2A database. Refer to the
System Administration section of the documentation for details on
truncating the PROGRESS before image file. There is other important
information included in this document. Be sure to read this
entire document prior to working with PROGRESS v7.2A. Please note
that this a developer's release of PROGRESS Version 7 and is not
intended for application deployment.
CONTENTS:
1) Installation Issues
2) Networking Issues
3) Add-on Products
4) PROGRESS Data Dictionary Issues
5) GUI (Graphical User Interface) Issues
6) ISO Latin Character Set 8859-1 Support in the Sports Database
7) Batch Mode Processing Issues
8) Known Problems:
A) Networking Related
B) GUI/Widget Related
C) Language Related
D) User Interface Builder Related
E) Debugger Related
F) Procedure Editor Related
G) Freeze Frame Related
H) Procedure Librarian Related
I) Application Compiler Related
J) Utilities Related
K) Miscellaneous
INSTALLATION ISSUES
-------------------
* Disk Caching
Please disable disk caching software before attempting to install
PROGRESS 7.2A. For installation, it was discovered that a disk
cache may interfere with the installation process.
Many DOS and Windows systems are configured to use disk caching
software, such as SmartDrive provided with MS-DOS and MS-Windows,
to improve performance of applications. PROGRESS should work well
with disk cache software. However, if a write cache is being used,
please be sure that the disk caching software fulfills the
following two technical requirements:
1. It must flush all dirty buffers associated with the specified
handle on a Commit File (INT 21h Function 68h) system call.
2. It must flush all dirty buffers on a Disk Reset (INT 21h
Function 0Dh) system call.
SmartDrive meets both these requirements when operating from DOS
and Windows. For other disk cache software, please contact the
vendor to determine if it meets the above requirements.
Please note that the latest release of the SmartDrive disk cache
utility included with MS-Windows 3.1 and MS-DOS 6.0 default
to a write cache as a result of the MS-DOS and MS-Windows
installation process.
* Disk Compression
If you are using a disk compression utility on your system such as
Stacker or DoubleSpace, the determination of whether or not there
is enough free disk space to install PROGRESS V7 may not be
reliable. The PROGRESS V7 Installation utility requires additional
disk space to expand compressed files. This space is not accounted
for when a disk compression utility is being used. If a disk
compression utility is being used, there should be at least 40MB of
free disk space.
Progress recommends that you do not store databases (.db), before
image (.bi) files or after image (.ai) files on compressed disks.
Database integrity cannot be maintained. Your database may become
damaged.
* Remote File Systems
Progress recommends that you do not store databases, before image
(.bi) files or after image (.ai) files on remote file systems, such
as NFS mounted disks. Database integrity cannot be maintained. Your
database may become damaged.
* Environment Variables
All environment variables setup for prior versions of PROGRESS
should be removed before running PROGRESS V7.2A.
The PROPATH environment variable is, by default, defined to include
the %DLC%\BIN directory and working directory denoted for the
properties of the PROGRESS icon. Other directories which need to be
included in the PROPATH environment variable should be appended to
the current definition of PROPATH in the PROGRESS.INI file, which
is located in the %DLC%\BIN directory. If user specific PROPATHs
are necessary, place unique versions of PROGRESS.INI in the user's
working directory.
Placing %DLC%\SRC in the PROPATH environment variable before the
PROGRESS supplied r-code directories can yield unpredictable
results. Please note that, at runtime, the following directories
are appended onto the current PROPATH definition: %DLC%, %DLC%\GUI
and %DLC%\BIN. These directory segments in the PROPATH are used to
find key r-code files used to run the ADE tools. Exclusion or
superceding of these directories will result in either the
inability to run an ADE tool or serious performance degradation.
* Other applications should not be run during the installation
process.
* The installation process should not be started from the MS-Windows
File Manager. Either use the File-Run menu options from the Program
Manager or enter "WIN DRIVE_LETTER:INSTALL" from DOS.
* The receipt of a "Cannot read from drive b:" error while files are
being read off of a disk other than the Installation Disk may
indicate that the installation is temporarily out of memory and
needs to reload portions of the installation utility. If this occurs,
place the Installation Diskette in the disk drive and proceed with
the installation process.
NETWORKING ISSUES
-----------------
* The Windows Network Database Server
The Windows Network Database Server product provides a development-
only version of the PROGRESS server called WPROSERV.EXE. This
program is NOT meant to be used in a production environment, but
exists to allow development teams to write and test programs in a
multi-user environment. WPROSERV supports NetBIOS, SPX and DDE.
There also exists a program called WPROSHUT.EXE to shutdown a
server started by WPROSERV. WPROSHUT.EXE also supports TCP/IP, in
addition to the above protocols, to remotely shutdown a Unix based
database server.
To start a database server using the WPROSERV facility, edit the
properties of the WPROSERVE icon to denote the database name, the
networking protocol (via -N) and the service name (-S), if
applicable. Please see the Networks Guide manual for additional
information.
* SPX PROTOCOL
Novell continues to update support files for MS-Windows and
the IPX/SPX protocol. These files are a subset of the NetWare
Workstation Kit for DOS/Windows v2.0 available from Novell
Corporation. The following is a list of files required for the
effective operation of PROGRESS for MS-Windows Release 7.2A.
IPX.COM Version 3.10 or higher
NETX.COM Version 3.26 or higher
NWIPXSPX.DLL Version 1.31 or higher
VNETWARE.386 Version 1.04 Build 92-045 or higher
NETWARE.DRV Version 2.00 Build 92-044 or higher
VIPX.386 Version 1.11 (920213) or higher
TBMI2.COM Version 2.10 or higher (for standard mode only)
If MS-Windows is being run in standard mode, load the TBMI2.COM
TSR prior to starting MS-Windows.
If MS-Windows is being run in 386 Enhanced mode, verify that the
SYSTEM.INI file has the following line in the [386Enh] section:
network=*vnetbios,vnetware.386,vipx.386
* TCP/IP PROTOCOL
The _PROWIN.EXE module supports only TCP/IP software packages for
Windows that include support for WINSOCK specification Version 1.1
(WINSOCK.DLL).
These include but are not limited to:
PC-NFS v5.0
NetManage v3.10
Wollongong v1.2.01
FTP TCP/IP v2.2
Novell's LAN Workplace for DOS is supported via the _PROWINL.EXE
module. To run this executable, change the command line for the
properties of the PROGRESS icon to specify _PROWINL.EXE. Remote
database shutdown using Lan Workplace for DOS is supported via
the WPRSHUTL.EXE module. To run this executable, change the command
line for the properties of the Server Shutdown icon to specify
WPRSHUTL.EXE.
ADD-ON PRODUCTS
---------------
The following products are not part of this development release
of PROGRESS Version 7:
* Embedded SQL for C (HLI)
* DataServers (Gateways)
* RESULTS
* Probuild
* Toolkit
PROGRESS Data Dictionary Issues
-------------------------------
* The GUI Data Dictionary requires the use of a mouse to select the
"Tables", "Sequences", "Fields" and "Indexes" icons.
GUI ISSUES
----------
* The use of FTP Software's PC/TCP's telnet utility will change the
default font, which will then be used by the PROGRESS Application
Development tools. FTP Software is aware of this issue.
* If you are using bitmap images that have been saved in 256 color
mode, MS-Windows will try to create an accommodating color palette
each time the image is realized within your PROGRESS application.
The effects of this are:
- The background will flash as the color palette is loaded as each
image is realized (unless the color pallets of the images are the
same).
- You will experience significant performance degradation as these
images are displayed/realized.
If you are using 256 color mode bitmaps you should consider
recreating the images or converting them to 16 color mode bitmaps.
Please note that this phenomenon is not PROGRESS specific, but
occur within MS-Windows applications.
ISO LATIN CHARACTER SET 8859-1 SUPPORT IN THE DEMONSTRATION DATABASE
------------------------------------------------------------------------
* To work against a version of the SPORTS demonstration database
which contains ISO Latin characters, copy the ISPORTS database
in the %DLC% directory to a database named SPORTS. The standard
SPORTS database contains only seven-bit characters.
BATCH MODE PROCESSING ISSUES
----------------------------
To enhance performance during batch mode processing, we suggest
that the "MultitaskingInterval=100" parameter in the [Startup]
section of the PROGRESS.INI file be uncommented by removing the
semicolon and the value be changed to either 0 or 1000. Use a value
of 0 if no other applications will be running under MS-Windows. Use
a value of 1000 if you wish to be able to run another applications
while running PROGRESS in batch mode. Another option is to set the
equivalent session handle by adding the following line at the top
of the main procedure:
SESSION:MULTITASKING-INTERVAL=0.
KNOWN PROBLEMS:
---------------
The following items represent both problem reports and functionality
issues. The discussion of an issue does not necessarily imply that it is
a PROGRESS specific problem which will be corrected in subsequent
release.
* Networking Related
Progress is currently investigating the generation of the following
error messages that may be seen as a result of intensive database
activity in a client-server configuration.
- "Client's recvcnt ## is not equal to the server's sendcnt ##"
error message received by the client.
- "Error reading socket=11, ret=-1, errno=54. (795)" error messages
populated in the database log file.
- "Partial write, socket=12 msglen=767 ret=16 user 2 disconnected
(797) Begin transaction backout (2252)
Transaction backout completed (2253)
Logout usernum 18, userid smith, on hostname batch (739)"
received by the client.
Attempting to connect to V6 database server without the -b startup
parameter will result in the client being left in a hung state.
Error messages are not sent back to the client.
If a database server is shutdown while a client is in an update
routine, the use of the end-error key by the client will result
in an "Error reading socket, ret:-1, errno=6. (778)" error message.
Attempting to start or shutdown a local SPX server while running
MS-Windows in standard mode will result in an error message
indicating that SPX is not loaded. MS-Windows must be run in
386 enhanced to start a local SPX server using the WPROSERV.EXE
module.
The WPROSHUT.EXE module counts itself as a user during the shutdown
of a V6 database. This prevents the use of the -bn parameter since
it requires that no users are logged into the database server.
Only one local SPX server can be started using the WPROSERV.EXE
module. Subsequently started servers will automatically shutdown
shortly after startup. Other protocol types (DDE, NetBIOS, TCP/IP)
can be used to start multiple local database servers.
The use of WPROSHUT.EXE to shut down a server running over FTP
Software's PC/TCP NetBIOS generates a "This application was
communicating over the network when you terminated it" error
message. When you attempt to shutdown MS-Windows, the system then
hangs, requiring you to reboot the PC. This does not occur with
other vendor's NetBIOS.
Connecting to the same database twice using unique logical database
names via the -ld startup parameter will result in a hung state
followed by a system error.
The running of a non-Windows application, the opening of a DOS
session or the execution of a DOS command via "DOS", "DOS SILENT"
or "OS-COMMAND" 4GL statements may cause the loss of a SPX
connections if the proper versions of NetWare for MS-Windows
support files are not being used. Please see the above section on
the SPX PROTOCOL in the Networking Issues section for details.
Pressing CTRL-ALT-SHIFT-F1 to view the PROGRESS information screen
will result in the loss of a TCP/IP connection to a database server and
will cause the database server to hang.
* GUI/Widget Related
Pressing the page-down key while viewing a browse may result in the
browse advancing two page lengths.
The statement "DEFINE VAR X AS INT VIEW-AS TEXT" will generate an
error message indicating that this an invalid variable definition
following a memory violation.
Leading blanks will be accepted in a fillin field until the first
non-blank character is entered. At that point an error condition is
raised, requiring the user to backspace to the beginning of the
field.
Radio button labels are not case sensitive. Therefore, if a radio-set
contains two buttons whose labels differ only by case ("A" and "a",
for example), PROGRESS cannot properly distinguish them.
If a button has an image rather than text and is set as a default
button then at run time the image does not appear on the button.
The cursor is placed in the middle of a date field in update
mode.
It is not possible to resize down-frames that have been set as
sizable.
Column-labels in a down frame may "bleed" into each other.
There are display performance issues with down frames that will
be addressed in subsequent releases.
It is not possible to dynamically set the BGCOLOR and FGCOLOR
attributes of a browse widget.
Decimal fields are not aligned by the decimal when displayed in a
browse widget.
A Radio-set contained in a frame which has a dithered background
will not inherit the frame's dithered background, but rather one of
the component colors of the dither. Radio-sets that have been
defined without a BGCOLOR or a FGCOLOR attribute will have a white
box around the textual portion of the radio-set.
Values assigned to a character field containing an ampersand (&)
will be stored with two ampersands. For example, the string "Alias
Smith & Jones" will be stored and displayed as "Alias Smith &&
Jones".
The lack of a status area in a window will cause down frames not to
pause. However, PAUSE <n> NO-MESSAGE will work.
The highlight bar displayed with the use of a CHOOSE statement will
only be as wide as the text of the currently highlighted selection.
Alert boxes with multiple lines of text may result in the loss of
the buttons.
The size of the box surrounding a fill-in does not change to
reflect the size of a different font.
* Language Related
The desired colors may not be displayed as denoted in a CHOOSE
statement.
Correlated SQL subqueries against views do not work. The following
SQL code is an example of such a query:
/*
* create view foo as select cust-num, st from customer.
* create view bar as select cust-num from order.
*/
select *
from foo
where cust-num in
(select cust-num
from bar
where foo.st = bar.st).
Temporary tables defined like a database table will not inherit the
indexes of that table if an additional field is defined for the
temporary table.
LEAVE triggers that generate user interaction (e.g an alert box)
will prevent subsequent ENTRY and CHOOSE triggers from firing *if*
a mouse event is used to leave the widget with the LEAVE trigger
and enter a widget which has an ENTRY or CHOOSE trigger.
A DISPLAY with the STREAM-IO frame phrase does not translate FILL-INs
to TEXT (the USE-TEXT functionality) when DISPLAYed to the screen
on MS-Windows. Output to file works fine.
The statement "ON END-MOVE ANYWHERE MESSAGE "this is a test"" for a
widget defined as markable and moveable will cause the PROGRESS
session to hang. This is also true for the START-MOVE event.
System triggers written with the "ANYWHERE" argument will fire only
while the procedure in which the trigger resides is active. These
triggers must be made persistent in order to be active in called
procedures. For example,
"ON "F11" ANYWHERE RUN PROC1."
should be changed to
"ON "F11" ANYWHERE PERSISTENT RUN PROC1."
Validation placed on an entire array will cause the update of the
array to fail. Array validation must be subscript specific.
A leading asterisk in the string passed to the CONTAINS function
is ignored. For example, "FOR EACH customer WHERE customer.name
CONTAINS ("*abc*")" will result in a query for customer names
that contain "abc*", not "*abc*".
Include filenames may not include ISO Latin characters (those
greater than ASCII 127).
* User Interface Builder Related
Opening a .W file that contains a window with a blank title (title
attribute is set to yes, but the window has no actual text in its
title) will result in substring error messages.
Changes made to a window's menu bar will not be seen in design mode
until the .W file is run or the property sheet for the window is
accessed.
When you duplicate a widget, the "new" widget is placed directly
over the "old" widget. You have to move the "new" widget to even
realize that there's an "old" widget still there.
Down Frames created via the UIB may generate scrollbars in the
frame.
Please note that the 'check syntax' feature in the UIB's section
editor does not check for runtime bugs.
Exiting the UIB under low memory condition may result in a
memory violation.
Adding database fields to a down frame that had these same fields
deleted from the design window will generate a "`More than one w_U
records found by a unique FIND.' error message.
A browse widget created in the UIB may not contain more than 20
fields.
Adding the same sort by field twice for a browse widget may
generate a memory violation error.
Database fields are painted onto a design window starting in the
upper-left-hand corner. It is not possible to denote the location
of the fields until after they are initially placed onto the design
window.
It is not possible to create a "WHERE TABLE.field = variable"
clause using "point-and-click" in the UIB Query Builder. Use the
"edit" feature to change the WHERE clause directly in the UIB Query
Builder screen.
It is not possible to get a browse widget in a frame such that the
bottom of the browser is at (or very near) the bottom of the
Frame/Dialog Box. Note that the design window shows the browse at
the bottom, but at run-time, the Browse is elevated.
The error message "SYSTEM ERROR: bfx: field too large for ditem."
may be received and followed by a system shutdown when attempting
to store a large trigger in the UIB's section editor. Increase the
-s startup parameter if this error message is received.
It is not possible to set the tabbing order in a user interface
screen via the property sheet for those widgets. However, this can be
achieved in the 4GL using the LAST-TAB-ITEM and FIRST-TAB-ITEM
attributes and the MOVE-AFTER-TAB-ITEM and MOVE-BEFORE-TAB-ITEM
methods.
Adding 'DefaultFont=Fixedsys' to the [Default Window] section of
PROGRESS.INI causes the UIB to generate errors on startup.
Pressing Ctrl-Break twice in succession while in the UIB may hang
the entire PROGRESS session. The hourglass cursor will display
when the cursor is placed over a PROGRESS window but MS-Windows
will be otherwise operational. MS-Windows should be restarted to
address this situation.
The UIB may create "lost allocation units" on disk when it writes
a temporary workfile for a new work window. This is not a PROGRESS
specific problem and will not occur unless MS-Windows is exited
while PROGRESS is still running. If this occurs, run "CHKDSK /F"
from DOS. Say yes to the question concerning converting the lost
allocation unit(s) to a file. This file can then be deleted.
If you use the following syntax when creating a WHERE clause for
the Browse widget, you will get a syntax error from within the
browser.
Where Builder:
WHERE dbfield = screenfield:SCREEN-VALUE IN FRAME framename.
To work around this problem, disable the syntax checker in the
Where Builder and then debug the code in the UIB, Procedure Editor
or Debugger.
A message area will not be added to a design window by selecting
the MESSAGE-AREA attribute in the Runtime Characteristics in the
Property Sheet for the window until runtime.
Pressing ALT-M to go to the Main Block while the cursor is inside
the 'Procedure' field in the Section Editor will result in an error
message indicating that the widget already has a procedure with the
same name.
Array fields "VIEWed-AS" as any widget type other than fill-in
cannot be brought into the UIB. Arrays "VIEWed-AS" fill-in can be
brought into the UIB.
A .W file containing quoted strings may not be properly read by the
UIB. If this occurs, place a leading space in front of the initial
quotation (e.g. change "FILL("test",3)" to "FILL( "test", 3)").
* Debugger Related
The Debugger may display the cursor 2 lines behind the actual
internal location of the debugger when stepping through a
large procedure.
If you attempt to RUN another procedure in the Debugger after using
the hotkey (Ctrl-Break) or Debug->Interrupt menu-item to interrupt
the execution of another procedure, the message "Operation number 0
not supported in this release. (1987)" repeats in the message area.
You have to use the Debugger hotkey again to get out of
the loop. It will then be necessary to restart the machine.
The debugger may generate a "stack overflow" error when debugging
a job stream of procedures nested 32 deep.
The Debugger cannot view widget attributes.
If the Debugger is initiated as a "stand-alone" utility (-debug),
a procedure is run from the debugger, and that procedure is waiting
for input (Press Space Bar...), and the operator EXITS the debugger,
the child procedure will not cease execution. The debugger will
terminate correctly, but the child procedure will display the error
message "SYSTEM ERROR: Lost connection to Progress Debugger (4348)"
when control is returned to the child procedure.
* Procedure Editor Related
Printing a procedure from within the Procedure Editor that contains a
TAB will result in output with a vertically centered period in
place of the TAB.
When executed in the Procedure Editor or UIB, the 4GL function
PROGRAM-NAME() behaves incorrectly by returning the temporary file
name used by the editor or UIB. This may cause problems if you use
PROGRAM-NAME() to enforce runtime security.
* Procedure Librarian Related
Running some of the procedures provided with the Librarian will
result in a "Cannot execute UPDATE statement while DIALOG-BOX is
active (4015)" error message.
Searching for a string that does not exist in the Librarian with
the "File Contents" toggle-box selected may result in the search
getting stuck in an infinite loop.
The Procedure Librarian erroneously lists files for a PROTERMCAP
application. These files relate to PROGRESS Version 7 for Unix
only and do not exist in the MS-Windows version.
* Freeze Frame Related
The main window of Freeze Frame does not fit in a 640x480 screen.
The button bar containing the Freeze, Run and Exit buttons are
located below the bottom of the visible portion of the window.
Reposition the window to access the button bar.
The use of the V6DISPLAY option when using Freeze Frame will cause
text to be temporarily removed from fields that are TABbed into.
Scrollbars are displayed even with the use of the V6DISPLAY
option.
* Application Compiler Related
An alias database reference after a normal table reference may
generate a GPF when the procedure is compiled via the Application
Compiler. Fully qualifying all table references via the following
syntax will address this problem:
database_name.table_name.field_name
* Utilities Related
The command "PROLIB procedure_library -LIST" will fail on procedure
libraries flagged as read-only and generate a "** Cannot find or
open file path\proclib.pl, errno = 13 (43)" error message.
Procedure libraries need to be marked as writeable if their content
need to be listed. If this is done, be careful not to overwrite or
otherwise damage the contents of the procedure library.
The PROBKUP utility does not properly verify that the media is in
place prior to writing to the device. Be sure to have media onto
which the database is being backed up properly loaded in its drive
before starting the backup procedure.
Be sure to truncate the before image file prior to running "proutil
demo -C convchar" against a database.
"Proutil demo -C convchar" always generates a warning message about
the -stream setting. This erroneous message may be ignored.
If the bi block size is greater than the -bf (backup buffer block
size) parameter, then the backup process will generate a GPF.
Backing up a database to a write-protected diskette via the PROBKUP
utility will cause a hung state. Remove the diskette and disable
write-protection and continue the backup procedure.
If a Version 6 database has index numbers 1000, 1020, 1021, 1024, and
1025, "PROUTIL DBNAME -C Convert67" will fail to convert the schema
needed to make the database a v7 database. In this case, the
database must be dumped in V6 and loaded into V7.
The mouse cursor does not change to an hour glass when the
Translation Manger is processing.
Quoter will not create an output file when a " is used as the
delimiter.
The command "rfutil dbname -C aimage scan" fails when used with ai
extents with following error: "** Cannot find or open file
aiex3.a2.ai, errno = 2 (43)".
The use of the Data Administration export facility to output data
in MS-Word format will generate an ASCII formatted file.
* Miscellaneous
Denoting a value larger than the allowable maximum (500) for the -D startup
parameter will result in a memory violation.
Improper termination of the PROGRESS session during the deletion of a large
quantity of records may corrupt database indexes. The symptom of
this is the receipt of a "System Error: bksteal: attempt to read
block # above high water mark # (3636)" error message upon
attempting to access the database for the first time after the
records have been deleted and the improper termination. The
corrupted indexes can be fixed by doing an index rebuild using the
following command: proutil dbname -C idxbuild.
Progress Software Technical Support Note # 12528