Consultor Eletrônico

Release Notes for Arix 6.2N

ADDITIONAL NOTES FOR THIS RELEASE

PLATFORM: arix825
MEDIA TYPE: Cartridge Tape
SOFTWARE RELEASE: 6.2N01
EXTRACT COMMAND: cpio -iuvcdBm < /dev/rmt1
INSTALL COMMAND: /mnt/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.

o REMOTE RDB GATEWAY ------------------
A load script built from RUNTIME with remote RDB will
not build an executable. The following error will appear:

./ldprort: Loading _progres undefined
first referenced symbol in file
smtrhs /usr1/rdl62/dlcload/4gl/vcsys.o
smegen /usr1/rdl62/dlcload/4gl/vcsys.o
smprhsc /usr1/rdl62/dlcload/4gl/vcsys.o
smtrop /usr1/rdl62/dlcload/4gl/vcsys.o
ld fatal: Symbol referencing errors.
No output writeen to _progres
./ldprort: FAILED to load _progres

To get around this error, you will need to modify the
link script before running it. After the first reference
to "n1" insert the following line: $PROLOAD/4gl
1prort.o
Upon running the modified link script, the executable
shall be complete.

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.

NETWORKING
----------
When using TCP (sockets) and two networked servers
on the same machine, the system will allow the bind to
succeed. However, this will cause the two servers to listen
to the same port and lead to every other request to connect
to fail for the new database.

The work around is to use TLI (the default) as the networking
protocol.

DISPLAY WITH SPACE TAKING TERMINALS
-----------------------------------

If you run a procedure using a DISPLAY statement on a space
taking terminal and then try to "compile program.p attr-space
save" it you will receive a system error: bus error (48).

The work around is to go into the editor and type "run
program.p", then type "compile program.p" and then hit
F1.

Progress Software Technical Support Note # 12695