Consultor Eletrônico

Release notes Tower 650 (tow650-2)á

900618-SAL01Release Notes for Tower 650: Progress Version 6.2A

ADDITIONAL NOTES FOR THIS RELEASE


PLATFORM: Tower 32-650
MEDIA TYPE: 600' hi-density tape
SOFTWARE RELEASE: 6.2A
EXTRACT COMMAND: cpio -iudcvBm < /dev/rstp/34yy
INSTALL COMMAND: ./proinstall


MACHINE NOTES:


OPERATING SYSTEM NOTES:


TERMINAL NOTES:


SOFTWARE NOTES:

o This release does not support Oracle Gateway
o This release does not support X-Windows
o This release supports Embedded SQL (HLI) for C.

o Online Backups:
--------------
The use of the -o (overlap factor) is not supported in this
release; you must restore the incremental backups exactly the
same way as you did when you backed them up or you will have
problems. For example,
proshut demo -C online /dev/rst8
proshut demo -C online /dev/rst8 incremental -o 2
After restoring the full backup, if you skip any of the
incrementals, you receive an error message indicating that
the tapes are out of sequence and the restore fails.

Workaround: Make sure all backups are restored in exact order.

o HLI (Embedded SQL for C)
------------------------
A C program that has a combination of CREATE TABLE
and INSERT INTO TABLE statements may fail when
executing in multi-user mode. For
example, when you run the following code in multi-user, it
produces the errors:

SYSTEM ERROR: lkpurge: record not locked (430)
** Please save file named core for analysis (439)

EXEC SQL CREATE TABLE players (custnum int)
EXEC SQL INSERT INTO players (custnum) SELECT cust\-num FROM
order;

Workaround: Use two different C programs for your CREATE TABLE
and INSERT INTO TABLE statements.

o Toolkit
-------
In order to use the mkdump and procomp utilities, set
the environment variable DLCTK. Modify the procomp script to
execute $DLCTK/_procomp. For example, to set the environment
variable, you would enter:

DLCTK=/usr/dlctk;export DLCTK

and to execute _procomp, the line should read:

exec $DLCTK/_procomp -1 "$@"

o Fast Track
----------
If you use the convft utility to convert your database to a Fast
Track database, you must set the PROEXE environment variable
first. Enter the following:

PROEXE=/usr/dlc/_progres;export PROEXE
convft database-name


o Index Deactivation
------------------
If you are deactivating indexes, you should do it through the
Index Editor in the Modify-Schema menu. Deactivating indexes
through the Admin menu in the Dictionary will deactivate the
first index.

For example:

In the customer file there are three indexes, Cust-num,
State and Zip. If you choose to deactivate zip, it
deactivates cust-num.

o File-Level Timestamp
--------------------
In the Dictionary's Field Editor, if you make
any modifications to a field (including format, label,
help, etc.) defined as character that is not a component
in an index, the timestamp on your file
will change.

This will invalidate any precompiled procedures you
currently have that reference the file. For example,
with the following procedure:


FOR EACH customer:
DISPLAY customer.
END.

if you compile and save this procedure to produce a .r:

COMPILE stamp.p save

then go back into the dictionary and change the label on the
Address field in the customer file, and then try to run stamp.p,
you will receive a message indicating that the dictionary
has been modified since stamp.p was compiled. You must
recompile the procedure.


o PROBUILD
--------
The second option on PROBUILD's product list (RUN-TIME PROGRESS)
does not include a compiler.

If you choose this option, you cannot build an executable that
includes the ORACLE Gateway. When you run the load script, it
fails with the following messages:

Undefined:
_smtrop
_smtrhs
_smegen
_smprhsc
script-name: Failed to load rt.

where script-name is the name of the script you tried to run.
To include the ORACLE Gateway in your executable, use the first
option on PROBUILD's product list (PROGRESS 4GL).

Progress Software Technical Support Note # 9165