Kbase 12693: Release Notes for Altos 386 6.2N
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Release Notes for Altos 386 6.2N
ADDITIONAL NOTES FOR THIS RELEASE
PLATFORM: altos386
MEDIA TYPE: Cartridge Tape
SOFTWARE RELEASE: 6.2N
EXTRACT COMMAND: cpio -iuvcdBm </dev/rct
INSTALL COMMAND: ./proinstall
MACHINE NOTES:
OPERATING SYSTEM NOTES:
TERMINAL NOTES:
SOFTWARE NOTES:
o Fast Track (convft)
---------------------
If you use the convft utility to convert your database
to a Fast Track database, you must set the PROEXE enviornment
variable first:
PROEXE=/usr/dlc/_progres;export PROEXE convft database-name
o REMOTE RMS GATEWAY
------------------
Transactions are not rolled back from the RMS database
when a ctrl-\ is pressed from a remote rms client.
C-ISAM GATEWAY
--------------
o PROBUILD
1. Before you build a C-ISAM Gateway executable, you
must set the CISAMLIB environment variable by entering
the following command at your operating system prompt:
CISAMLIB=-lisam; export CISAMLIB
2. The NetISAM gateway can only be built on Sun-4/SPARC
machines.
o NFS Mounting
The C-ISAM Gateway cannot access NFS mounted files.
Therefore, to access C-ISAM files with the C-ISAM Gateway,
you must store the files on a disk volume local to the
machine running the gateway executable.
o Record Locking
The Documentation states that all record reads are read
EXCLUSIVE-LOCK by default. This is not the case. All
reads are NO-LOCK by default. In order to avoid any record
contention when running your application,we recommend that
whenever you are reading a record for update, you should
explicitly specify EXCLUSIVE-LOCK, as in:
FIND FIRST CUSTOMER EXCLUSIVE-LOCK.
UPDATE customer.
However, if you do not specify NO-WAIT NO-ERROR when
accessing the record, as in the above example, and another
user already has the record locked, you will receive the
following message, and PROGRESS will perform default error
processing (undo, retry of the closest block with error
property):
C-ISAM record locked. (2177)
In this case, you will be returned to the PROGRESS editor.
The following example will avoid this error:
FIND FIRST CUSTOMER EXCLUSIVE-LOCK NO-WAIT NO-ERROR.
IF AVAILABLE customer THEN
UPDATE customer.
ELSE IF LOCKED customer THEN ...
Whenever you are reading a record for display purposes
only, you should explicitly specify NO-LOCK, as in:
FOR EACH customer NO-LOCK:
DISPLAY customer.
END.
o Data Type Comparisons
If you try to store a larger value into a field than
it can handle, you will receive the following error message:
PROGRESS to ISAM integer data overflow.
The same error will occur if you are joining from more
than one file and trying to compare a larger to a smaller
data type, as in the following example:
FOR EACH bignum, EACH smallnum WHERE bignum.field
= smallnum.field:
DISPLAY bignum.field smallnum.field.
END.
A workaround would be to put a conditional statement
within the FOR EACH block, as in:
FOR EACH bignum, EACH smallnum:
IF smallnum.field = bignum.field THEN DO:
DISPLAY bignum.field smallnum.field.
END.
END.
REMOTE CISAM GATEWAY
--------------------
While using the remote CISAM Gateway, if you press CTRL-\
during a transaction, you are disconnected from the server.
Additionally, your records will not be backed out.
When creating a REMOTE C-ISAM Server with PROBUILD, you
must select C-ISAM-GATEWAY, otherwise the load script fails
to create the_cissrv executable.
DISCONNECTING REMOTE USERS WITH KILL
------------------------------------
If a kill -9 is used to kill a remote PROGRESS process
and/or the MPROSRV process, that user session will hang.
Additionally, other clients waiting for the record to be
release will continue to wait for the record. The workaround
it to use PROMON to disconnect the user in question and
thereby release the record for another client process.
PROBUILD WITH X11 R5 ENVIRONMENT
--------------------------------
If you run PROBUILD, or have a PROGRESS executable that
was linked dynamically, in an environment using X11 R5
you will receive errors reflecting unresolved symbols during
runtime. Please call PROGRESS Technical Support for a patch.
RESULTS - QUERY PERMISSIONS
---------------------------
If you create a database from demo or empty and add your
own file (with or without adding records), then run RESULTS
and build a .qc file (with the AUTO option), and then run
the query form for ANY file, the "add", "update", and "query"
options will not display on the menu bar. The workaround
is to go into the ADMIN module and change the query permissions
for those options to "*" to make them available to everyone.
Progress Software Technical Support Note # 12693