Consultor Eletrônico

Release Notes - V7.2A for RS 6000 - 8mm

PROGRESS V7.2A RELEASE NOTES


PLATFORM: IBM System 6000
MEDIA TYPE: 8mm
SOFTWARE RELEASE: 7.2A
EXTRACT COMMAND: cpio -iudvBmc < /dev/rmt0
INSTALL COMMAND: ./proinstall
BLOCK SIZE: 512


** 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) Terminal Support
3) Add-on Products
4) ISO Latin Character Set 8859-1 Support in the Sports Database
5) Known Problems:
A) Networking Related
B) User Interface/Widget Related
C) Language Related
D) Application Compiler Related
E) Procedure Editor Related
F) Procedure Librarian Related
G) Data Dictionary Related
H) Utilities Related
I) Miscellaneous


INSTALLATION ISSUES
-------------------

* PROGRESS V7 does not support space-taking terminals, unless the
terminal has a firmware setup option to change it to non-space
taking mode.

* 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 corrupted.

* Environment Variables

All environment variables setup for prior versions of PROGRESS
should be removed before running PROGRESS V7.2A.

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
appended onto the current PROPATH definition: $DLC, $DLC/tty 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 super-
cession of these directories will result in either the inability to
run ADE tool or in serious performance degradation.

When running Results the PROPATH should include the
$DLC/tty/prores directory.

The PROTERMCAP environment variable must be set in order for the
on-line Help facility to function in V7.2A. PROTERMCAP should be
set to $DLC/protermcap.


TERMINAL SUPPORT
----------------

* The IBM-native console terminal-type "hft" is not supported.

* PROGRESS V7 does not support space-taking terminals, unless the
terminal has a firmware setup option to change it to non-space
taking mode.

* The following is list of terminals supported in V7 protermcap:

vt100
vt220
xterm
sun-xterm
aixterm
sun
wyse 370
wyse 60
wyse 50
ansi
sco386 console
color ansi
unix386
ibm 3151
ibm 3163
ibm 3164
unix pc/att 3b1

In addition, some of the keybindings have been changed from V7 to
V6. The default is set to Version 7. If you want to have V6
keybindings, change the following line in the PROTERMCAP file for
the particular terminal:

tc:=v7kf----> change to ---> tc:v6kf

The changes for the keybindings are as follows:

Keylabel V7 V6
-------- -- --
CTRL-W NEXT-WORD HELP
ESC-? HELP N/A
ESC-C COPY CHOICES
ESC-O GET OPTIONS
CTRL-P PREV-WORD PUT
CTRL-G EDITOR-TAB GET
ESC-S PUT N/A


ADD-ON PRODUCTS
---------------

The following products are not part of this development release
of PROGRESS Version 7:[DC1]

* Embedded SQL for C (HLI)
* DataServers (Gateways)
* Fast Track
* Toolkit


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.


KNOWN PROBLEMS:
---------------

The following items represent both problem reports and functionality
issues. The discussion of an issue does not necessarily imply that its
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.

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.

The use of the -cl client startup parameter when connecting to a
V6 database server may cause the server to hang. Also, the use of
the -m1 parameter to shutdown one of the server processes may cause
the server to hang. Use the -S and -H startup parameters to denote
service and host names, respectively, as an alternative to -cl.

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.

* User Interface/Widget Related

Pressing the page-down key while viewing a browse may result in the
browse advancing two page lengths.

When editing fill-in fields, the cursor may automatically wrap
around the screen leaving the cursor outside of the boundaries of
the screen generating a warning beep. END-ERROR out of the
procedure if this doccurs.

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.

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.

The right-hand border of a browse widget may appear broken in spots
when an xterm terminal type is used.

In character mode, a sorted selection list will display incorrectly
until the selection list is given focus. For example, a selection
list with "c,b,a,d,e,f" as its list-items will be displayed as
"c,d,e,f". As soon as focus is passed to the list it re-draws
itself and shows "a,b,c,d,e,f".

If you enter two or more lines of data into a field using the
EDITOR widget, the data contains new-line characters. This new-line
character causes problems with the display when the data is displayed
with a FORMAT "x(60)" or greater.

The cursor is placed in the middle of a date field in update mode.

Column-labels in a down frame may "bleed" into each other.

Decimal fields are not aligned by the decimal when displayed in a
browse widget.

Alert boxes with multiple lines of text may result in the loss of
the buttons.

* Language Related

Temporary tables defined like a database table will not inherit the
indexes of that table if you define an additional fields for the
temporary table.

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).

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 assigned an ENTRY or CHOOSE trigger.

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).

* Application Compiler Related

The Application Compiler tool's main screen flashes several times
upon choosing File->Exit.

* Procedure Editor Related

When executed in the Procedure Editor, 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
the PROGRAM NAME() to implement runtime security.

There are some known problems in the HELP facility that will be
addressed in a subsequent release.

If you CTRL-C after pressing F2 from the editor, the function keys
will no longer work.

Executing the File->Close menu options in the Procedure Editor will
cause the new screen to paint twice.

* 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.

Adding items with the Librarian by selecting ITEMS->Item List may
produce tty errors such as "/dev
ull already has a conflicting
use".

* Data Dictionary Related

The Data Dictionary process to generate an incremental schema file
(delta.df) will delete data without a warning message if the
delta.df contains DROP and ADD instructions. These DROP and ADD
instructions are ouput to the .df file when data types are modified
or extents changed.

* Utilities Related

Be sure to truncate the before image file prior to running "proutil
demo -C convchar" against a database.

In the IBM system 600 environment, pressing CONTROL-\ after using
the RFUTIL to mark a database as backed up will result in a lock
file (.lk) being left on disk for the database.

"Proutil demo -C convchar" always generates a warning message about
the -stream setting. This erroneous message may be ignored.

To restore a database backed up to a norewind tape device you must
advance past one of the EOF markers. This is due to PROBKUP adding a
EOF marker during the backup process.

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 contents need to
be listed. If this is done, be careful not to overwrite or other-
wise damage the contents of the procedure library.

Pressing Control-\ while the PROUTIL CONV67 utility is converting
indexes may cause a fatal error.

Attempting to list the contents of an empty procedure library
via the "prolib libary.pl -list" command will generate a fatal
error.

Using the -a startup parameter when starting a database server for
a database that has not had after imaging enabled will cause the
PROSERVE process to hang after the "Multi-user session begin. (33)
** You gave the -a parameter, but after-image is not enabled.".

If a Version 6 database has index numbers 1000, 1020, 1021, 1024,
1025, "PROUTIL DBNAME -C Conv67" 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.

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 # than high water mark #(3636)" error message upon attempting
access for the first time after the records have been deleted and
improper termination. The corrupted indexes can be fixed by doing
an index rebuild via the following command:
proutil dbname -C idxbuild

Progress Software Technical Support Note # 12530