Kbase 10356: Quickstart/V7.0d Release Notes
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Quickstart/V7.0d Release Notes
920722-ddc06
QUICKSTART RELEASE NOTES
The Quickstart software is functionally equivalent to a PROGRESS 4GL/RDBMS
License. Runtime and Query/Runtime functionality is not provided in this
release.
The combined Quickstart product components are not meant to imply the
final packaging of the commercial PROGRESS Version 7 product. Components
such as the Translation Manager may well be separately purchased products
at commercial delivery.
1) QUICKSTART ENVIRONMENTS
DOS Windows
-----------
Quickstart supports single-user only and requires Microsoft Windows
release 3.1 or above. Networking with Windows is not currently
supported.
X-Windows
---------
PROGRESS Quickstart on the SUN Sparc platform provides support of
the OSF Motif X-Window Manager based on X-Windows release R11.4
or higher. SUN Microsystems also provides an Open Windows X-Windows
Manager with their operating system. PROGRESS Quickstart will run
with version 2.1 only of the Open Windows manager. All widgets run
under the Open Windows Manager will take on the appearance of Motif
widgets, however, and may produce unexpected results.
If you are using the Virtual Desktop flavor of the OpenLook Windows
Manager, then you must have the file ".olvwmrc" in your home directory.
Also, to maximize performance, set the "OpenWindows.VirtualReRead" to
false in your .Xdefaults file.
Unix Client-Server
------------------
The Quickstart software may be run in single-user or multi-user
mode on a local machine.
Networking Support
Sun Server SCO Server
---------- ----------
Sun client yes ?
SCO client ? ?
The "?" indicates that limited testing has been done in this
client-server combination but it is believed to work.
2) PROGRESS VERSION 6 FUNCTIONALITY IN QUICKSTART
Products:
---------
The following PROGRESS Version 6 products are not supported in this
version:
RESULTS, FAST TRACK, Gateways, HLI, HLC
Help System Functionality:
-------------------------
The Help System is provided as an aid but has not been tested.
The following PROGRESS Version 6 Help Utilities are not available
in this version:
The PROGRESS Procedure Library
PROGRESS Utilities
------------------
These utilities are not provided with Quickstart:
After-imaging (rfutil)
Probkup, Prorest
Multi-volume (prostrct)
promon
prolog
bulkload (proutil)
chanalys (proutil)
dbanalys (proutil)
ixanalys (proutil)
dbipcs (proutil)
dbrpr (proutil)
These utilities are provided with Quickstart:
proutil conv67
truncate bi
language
idxbuild
prodb
prodel
3) PROGRESS QUICKSTART FUNCTIONALITY PROVIDED BUT NOT TESTED
The following features were added late in the release and have been
documented but not tested thoroughly:
Temporary Tables
CLIPBOARD System Handle
PROGRESS On-line Documentation (provided under MS-Windows)
4) CHARACTER MODE SUPPORT
We have tested a PROGRESS Version 6 application recompiled and run under
Quickstart and have found it to work with the exception of the following
command:
PUT SCREEN
This will be corrected in the final commercial version
5) GUI (GRAPHICAL USER INTERFACE) SUPPORT
At present, an application developed under PROGRESS Version 6 for character
terminals and compiled under PROGRESS Quickstart GUI may require changes to
screen (form) layout. The rest of the application should run without
changes, however.
6) PROGRESS DATA DICTIONARY ISSUES
Several different dictionary interfaces are provided with QuickStart.
To access administrative utilities (e.g. dump and load), it is necessary,
at this time, to run the Version 6 Data Dictionary. Schema modifications
can be executed via the Quickstart ADE Dictionary. These Data Dictionaries
can be accessed by defining the PROPATH environment variable accordingly.
They are found in their own subdirectories of the DLC directory which
look like this:
DLC
|
|
------------------------------
| | | |
| | | |
adedict char-r gui-r prodict
Where:
dlc/adedict ==> ADE GUI Data Dictionary location
dlc/char-r & dlc/gui-r ==> UNIX only Data Dictionary locations
dlc/prodict ==> WINDOWS character mode Data Dictionary
location
The directory dlc/adedict contains a compiled version of the PROGRESS
Version 7 Data Dictionary with GUI interface. For purposes of clarity we
refer to this as the ADE Dictionary in this document.
The directory dlc/char-r contains a compiled version of the PROGRESS
Version 6 Data Dictionary for use in a character environment. For purposes
of clarity we refer to this as the CHAR Dictionary in this document.
The directory dlc/gui-r contains a compiled version of the PROGRESS
Version 6 Data Dictionary for use in a GUI environment. For purposes
of clarity we refer to this as the GUI Dictionary in this document.
The directory dlc/prodict contains source code (.p's) for the PROGRESS
Version 6 Data Dictionary. For MS-Windows, compiled code for this
Dictionary is also included in this directory. For UNIX, the compiled
code is stored in the char-r and gui-r directories.
In the Unix environment, to run the CHAR or GUI Dictionary from the
PROGRESS editor, type dict. The runs the PROGRESS Version 6 Dictionary.
Please note that the presence and order of directories in the PROPATH
environment variable dictates whether the GUI or character dictionary is
run. To run the version 7 dictionary from the editor type: run dictg.p.
7) KNOWN PROBLEMS
Some of the known problems in the Quickstart software are listed below.
The list is an attempt to make you aware of the most serious and most
common errors you are likely to encounter. We encourage you to document
other bugs that you discover and submit them to PROGRESS Software
Technical Support via the Problem Reporting Form so that we can address
them in time for the Version 7 commercial release.
Utilities
=========
* PROCOPY
If you use procopy to copy a PROGRESS database, be sure to first truncate
the before-image file with proutil truncate bi or a PROGRESS error 49
(memory violation) will result.
Language
========
* The FIND statement does not work with inequality operators on character
fields. For example:
FIND Customer WHERE name > "U".
DISPLAY Customer.name Customer.Cust-num.
returns the error "**customer record not on file"
* Displaying data in some instances may result in frames being either
not completely painted or represented by a black rectangle when
working in GUI.
DEFINE VARIABLE a as CHARACTER INITIAL "ABCDE".
DEFINE VARIABLE b as CHARACTER INITIAL "BCDEF".
COLOR DISPLAY MESSAGES a b WITH FRAME x.
DISPLAY a WITH FRAME x.
DISPLAY b WITH FRAME x.
/* do some work*/
DO i = 1 to 500:
a = a.
END.
/*pause.*/ /*uncomment the pause and frames appear correctly*/
HIDE FRAME x NO-PAUSE.
* ON Statement
The following program will not compile:
DEF VAR cnt AS INTEGER.
cnt = 0.
IF cnt = 0 THEN
ON F11 ENDKEY.
ELSE
DISPLAY "Hello".
/* if you surround the ON statement with a DO...END
block, it will compile correctly. */
DATA DICTIONARY
==============
* The use of MENUS when an incomplete DIALOG BOX is on the screen
may produce unpredictable results. Nested DIALOG BOXES are not
currently supported.
* When using the GUI Dictionary, some screens are either not completely
painted or are represented as a black rectangle with no text. The
functionality of the menu choice is not affected, only it's display.
These Dictionary options include:
Gateway-> PROGRESS -> I (incremental .df file)
Utilities -> E (editor for parameter files)
Admin -> Dump -> Data Definitions (dump to .df file)
Admin -> Load -> Data Definitions (load from .df file)
When using field validation in the Data Dictionary, be sure that
both the validation message and validation expression fields are
filled in. A blank validation expression but non-blank validation
message can result in PROGRESS "hanging" when the field to be validated
is updated in a PROGRESS program.
* If you modify a text field with VIEW-AS-EDITOR to contain carriage
returns, that file will no longer be loadable into a PROGRESS
database using the Dictionary load utility. Although the file
dumps without error, the load writes the records to the error file.
* The file description field in the ADE Data Dictionary can be no more
than one line long in this release. A file that has a multiple-line
description produces an error when you attempt to dump or load it
using the Data Dictionary.
* The delete database function in the ADE dictionary is not yet
implemented. Use prodel from the operating system level to
delete a database.
* The PROGRESS help functions displayed when pressing <F2> are
not guaranteed to work.
* In the GUI dictionary, changing the format for new field's data type
will result in that field taking on the default format for the
given data type when viewed in the Field Properties windows. To
correct this, simply enter the proper format in the Field Properties
window.
* In the GUI dictionary, the character data type default format is
displayed even when entering a non-character data type. To correct
this, simply overide the format value.
Triggers
========
* A trigger does not apply "STOP" or "F4" in a frame.
DEFINE BUTTON abtn LABEL "QUIT".
FORM abtn WITH FRAME z.
ON SELECTION OF abtn APPLY "STOP" to FRAME z.
UPDATE abtn WITH FRAME z.
* A PROGRESS fatal error and core file occurs if you attempt to use the
FIND statement to locate a record that was created via a trigger in a
previous block.
DO FOR order:
ON FIND OF customer USING order DO:
CREATE order.
order.order-num = 1000.
UPDATE order.
END.
FIND order WHERE order.order-num = 1000.
/*this FIND causes the error 49*/
* A write trigger does not work if a shared buffer is modified in
a subprocedure that is called outside of the block in which it was
first referenced.
DEFINE NEW SHARED BUFFER b FOR customer.
DO FOR b:
ON WRITE OF customer DO:
DISPLAY cust-num city.
END.
RUN subproc.p.
/* subproc.p */
DEF SHARED BUFFER b FOR customer.
FIND FIRST b.
UPDATE city.
WORD QUERY
==========
* Word queries are prohibited in a CAN-FIND.
IF CAN-FIND (FIRST customer WHERE address CONTAINS "st")
THEN DISPLAY "yes".
GUI
===
* When using GUI, if you run a batch job and forget to use an INPUT
FROM statement and the program being run uses a CHOOSE FIELD, you
will receive a core dump. The following demonstrates this problem:
bpro <dbname> -p choose.p | cat
/* choose.p */
def var i as integer extent 5.
display i.
choose field i.
* The VIEW-AS FILL-IN phrase used to display an array AT a specific
frame location causes only the last element of the array to be displayed.
DEFINE VARIABLE array-var AS CHARACTER EXTENT 3
INITIAL ["Coke", "Pepsi","Moxie"]
VIEW-AS FILL-IN.
/*only the last element of the array is displayed*/
DISPLAY array-var AT COLUMN 10 ROW 20 WITH SIDE-LABELS.
* Attempting to set frame attributes without first displaying something
in that frame will result in the error "unable to find UIC in rnwdatr".
DEFINE FRAME x.
VIEW FRAME x. /*Instead of VIEW, DISPLAY something to correct*/
FRAME x:width-columns = 80.
FRAME x:height-rows = 18.
* Setting row/column attributes to less that one is not supported.
DEFINE RECTANGLE r SIZE 10 by 10.
FORM r.
r:row = .2.
r:column = 0.
message r:row r:column.
ADE EDITOR
==========
* If you attempt to run the ADE editor or any other PROGRESS procedure
that contains GUI functionality while you are in character mode,
the results are extremely unpredictable and are likely to result in
a PROGRESS fatal error and core file. If you are using a tty
terminal in a UNIX environment, you must use the pro/mpro scripts
rather than the proade/mproade scripts for the ADE editor.
* The ADE editor does not detect the opening of the same file into
multiple buffers. This can cause damage to the file if it is saved
or edited. To avoid potential problems, be sure that the file is
only opened once. You can check by choosing LIST from the BUFFER
MENU to see which files are currently open.
* The following keys do not perform their normal PROGRESS function in the
ADE editor:
Function Function Key Control Key
-------- ----------- ----------
Append Line <F12> <CTL-A>
Break Line <F11> <CTL-W>
Tab <Tab> <CTL-I>
Backtab <Backtab> <CTL-U>
Delete Line <F10> <CTL-D> *control sequence does work
Block <CTL-U>
* In GUI, you can block off text for deletion and then hit the <DELETE>
or <BACKSPACE> keys to delete the text. Be advised that if you hit
any other key, the text will also be deleted; this is standard
behavior in a windowing environment. In this context, beware that
there is not yet a function that allows you to undo your deletion.
* If your cursor is positioned beyond that last typed character of
a line in the editor, <CTL> <D> will not delete that line. If
you reposition the cursor anywhere on the typed line, however, it
does work. The delete sequnce, <CTL> <D>, also fails if you are
positioned anywhere on the last line of text.
* If you are positioned on a blank line, the delete sequence <CTL> <D>
deletes the blank line and the first character of the line which follows
it.
CHARACTER EDITOR
================
The character editor has been provided for use with tty terminals
in the UNIX environment. Currently, you may see unpredictable
behavior during its use and you may have to use the REPAINT (ESC-P)
key to restore the screen. When using GET (F5) or PUT (F6), the
file names are not remembered from your last request; therefore,
you must type in the full pathname followed by a CARRIAGE-RETURN
each time (the GO (F1) key will not work).
SCO UNIX ONLY
=============
In a menu driven application, the error message "SYSTEM ERROR:
Memory Violation(49)" is generated upon hitting F4 when in the
default window denoted in the procedure. The following procedure
illustrates this issue.
/* test.p */
DEFINE MENU main_menu
MENU-ITEM menu_item3.
DEFINE MENU mbar1 MENUBAR
SUB-MENU main_menu.
DEFAULT-WINDOW:menubar = HANDLE(MENU mbar1).
DISPLAY WITH FRAME x SIDE-LABELS.
UPDATE ab AS char WITH FRAME x SIDE-LABELS.
Progress Software Technical Support Note # 10356