Consultor Eletrônico

SUMMARY:

PROGRESS VERSION 6.3F RELEASE NOTES

CONTENTS:

6.3F is a maintenance release. No new features have been implemented.

Highlights of issues resolved in this release are:

- The issue with workfiles that resulted in a memory violation is
resolved in this release.

- The issue with shared frames that resulting in shared frame errors
is resolved in this release.

- The size of the resultant .r code when compiling procedures with
include files is now more comparable to the size of .r code in
version 6.2.

- A race condition that made it possible for a FIND by RECID to lock
a record that was just created by another user but not yet locked
by that user has been eliminated.

- The NO-LOCK issue with records held with NO-LOCK being left in
memory during transaction backout which resulted in index
corruption errors is resolved in this release.

- The handling of the PROPATH environment variable has been
corrected so that the wrong procedure will not be run if the
PROPATH variable is modified at runtime and two or more procedure
libraries have a procedure with the same name.

- The problem with selecting only certain elements of an array while
creating a RESULTS report causing the following error has been
resolved in this release:
Starting position for SUBSTRING must be 1 or greater (82).


* PROGRESS DATABASE

- The broker now detects abnormal termination of remote clients and
will remove the users from the Progress user list.

- The -c option now correctly sets the number of index cursors at
broker startup.

- When running with a multi-extent bi file, when a new bi cluster is
needed only 1 cluster is formatted instead of 4. This will avoid
a pause that was noticed by users when 4 clusters were formatted
at a time.


- The rpc library is not included in the link script produced by
the Probuild utility when no networking elements are selected.

- The issue that resulted in the database hanging when a hangup
signal was recieved by an on-line PROBKUP process has been
resolved in this release.

- The following errors are no longer displayed when running with a
database on a local filesystem when NFS is not installed on the
system:
File <dbname>.db is on a remote system (2226)
Database integrity CANNOT be guaranteed for this session. (2227)
** This session is running with the non-raw (-r) parameter. (515)


- The maximum socket number configured in Progress has been increase
to resolve the issue that could result in the following error:
Socket number <n> is too large; it cannot be greater than 63. (782)

- The issue with the -bibufs parameter being too low and resulting
in the following errors and an abnormal shutdown is resolved in
this release:
dpend: <num> sdpend: <num> dbkey:: <num>
rlwritten: <num> rldepend: <num>
rlputmod: dpend: <num> already written
Begin abnormal shutdown. (2249)

* AS/400

- The issue resulting in an SNA write error when connecting to AS/400
via SNA is resolved in this release.

* ORACLE GATEWAY

- The FIND WHERE statement works as expected with the unknown value,
"?", in an Oracle DataServer environment.

- The issue with the Oracle gateway not removing an exclusive lock
request from a user who has canceled the request by hitting CTRL-C
after recieving the following message is resolved in this release:
<file> in use by <user> on <tty>. Wait or press CTRL-C to cancel.

- The Oracle gateway now selects an index based on factors other
than just the WHERE clause.


- The _probrkr process now waits for the termination of expired
child processes, such as _orasrv, so that the child process does
not become a zombie process until the _probrkr exits.

- Because Oracle version 7 does not treat year 0 as being between
years -4732 and +4732, the Progress Oracle gateway now uses year
0001 instead of year 0000 for unknown inequality tests.

- With the Oracle gateway, indexes added through the Data Dictionary
will produce a valid ORDER BY clause when the Progress 4GL
USE-INDEX clause is specified.

- With the Oracle gateway, the -znotrim startup parameter can be
used to specify that trailing blanks not be trimmed in WHERE
clause values.

* C-ISAM GATEWAY

- Support has been added for the following C-ISAM datatypes:
ACU COBOL LEADING
ACU COBOL TRAILING

- The C-ISAM gateway no longer drops the last character when
converting a field from the PROGRESS "character" datatype to the
C-ISAM "string" datatype.

SOFTWARE NOTES:

The following is a list of issues at the time of release of 6.3F:

* PROGRESS 4GL

- Printing from within a Progress procedure with the OUTPUT THROUGH
statement may result in a defunct process. This defunct process
will go away when the Progress session is exitted by the user.

* ORACLE GATEWAY

- When doing a semi-auto upgrade using Oracle 6 and Oracle 7,
protoora does not add the additional NUMBER column,
"progress_recid", to the Oracle table. This prevents the use of
the RECID function and the FIND PREV and FIND LAST statements.

- When connecting to an Oracle database, the USERID("dictdb")
function may incorrectly return the Oracle userid and not the
user's login name.

- With Oracle version 6, the following error is returned when an
Oracle gateway schema is created from a database that was created
with the protoora utility:
** This frame uses rows 1 to 23 but maximum row is 21. (108)

- When using the Oracle utilities in the Data Dictionary to update
an entry in the schema holder, all character fields will be set to
case-sensitive even if original value of case-sensitive was "No".