Kbase 9166: Release notes for NCR Tower 32/650 V6.2G
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Release notes for NCR Tower 32/650 V6.2G
910617-gfs01
ADDITIONAL NOTES FOR THIS RELEASE
PLATFORM: Tower 650
MEDIA TYPE: Cartridge Tape
SOFTWARE RELEASE: 6.2G
EXTRACT COMMAND: cpio -iuvcdBm < /dev/rtp
INSTALL COMMAND: ./proinstall
MACHINE NOTES:
OPERATING SYSTEM NOTES:
TERMINAL NOTES:
SOFTWARE NOTES:
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 Fast Track (convft)
-------------------
If you use the convft utility to convert your database to a
Fast Track database, you must set the PROEXE environment
variable first:
PROEXE=/usr/dlc/_progres;export PROEXE
convft database-name
o Fast Track (500 file limit)
---------------------------
Unlike earlier versions, Fast Track Version 6.2F01 or higher
enables you to choose from more than 500 files when creating
QBF's, reports or forms. Now there is no limit to the number
of files you can select. However, because of internal changes
to the Fast Track code, you must recompile any QBF's or menus
generated with earlier versions of Fast Track to run them
under Version 6.2F01.
o Index Deactivation
------------------
If you are deactivating indexes, do it through the Index
Editor. Deactivating indexes through the Admin menu in
the Dictionary will deactivate the top 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 as well as Zip.
o REMOTE GATEWAYS
---------------
In PROGRESS Version 6.2F01 or higher, you can remotely access
an Oracle or RMS database. You must install a Version 6.2F01
(or higher) core PROGRESS product (for example, PADS,
4GL&RDBMS, Query Report, or Runtime) on the machine where you
are running your PROGRESS application and on the machine
hosting your non-PROGRESS database.
o REMOTE ORACLE GATEWAY
---------------------
While using the remote ORACLE gateway, if you press
CTRL-C during a transaction, you are disconnected from
the remote ORACLE server.
o REMOTE RDB GATEWAY
------------------
A selection for 'Remote RDB Gateway' incorrectly appears
in the PROBUILD menu. Remote RDB is not supported in
PROGRESS Version V6.2F01.
o PROBUILD
--------
o When running PROBUILD, the $PROLOAD/eucapp/euc.pl file must
have at least read and write permissions (rw-rw-rw-),
otherwise you will get the error:
** Cannot find or open euc.pl errno 13
To avoid this error, change the permissions on the euc.pl
file as follows:
chmod 666 $PROLOAD/eucapp/euc.pl
where $PROLOAD is an environment variable set to where
you have the dlcload directory installed - /usr/dlcload
by default.
o You can now use PROBUILD to build an executable with a
remote gateway configurable element. For example, if you
need to access a remote Oracle database, just select your
networking protocols and REMOTE ORACLE GATEWAY at the
CONFIGURABLE ELEMENTS screen.
o PROBUILD
--------
The load script generated by the PROBUILD utility does a
cd $PROLOAD. (changes the directory)
The load script cannot find your local .o's unless you put
the absolute path in the script - example:
cd $PROLOAD
$CC $CCNPOT $LDOPT -o $IMAGE
** /usr1/ps/fjh/prog1.o \ ---- (add absolute path value)
4gl/bklk.o etc....
Workaround:
The workaround to this bug is to put your absolute of
your local .o's into the load script.
o Connecting Databases
--------------------
You must use the -Nv 12 startup option to connect a 6.2F01
client to a Version 5 or 6.2A-6.2F PROGRESS server.
o Multi-Volume Databases - prostrct add
-------------------------------------
If you define a variable-length extent and then use the
"prostrct add" command to add another variable length
extent, the command does not work correctly. It should
convert the previous variable-length to a fixed-length
extent, but it does not.
To workaround this problem, do not use the "prostrct add"
command. Instead, create a new structure file (.st).
Define all of the extents you want to use, including any
new extents. Create a new void multi-volume database and
use the "procopy" command (or the "probkup" and "prorest"
commands) to copy the old database to the new one.
o Prorest Utility
---------------
Restoring an incremental backup out of sequence will
cause you to lose data. For example, if you restore
incremental 2, then restore incremental 1, you will lose
the data restored from incremental 2. You receive a
message telling you that the tapes are out of sequence,
but you are not warned about the data loss.
Progress Software Technical Support Note # 9166