Kbase 9153: Release Notes for Motorola m8000 Version 6.2F01
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
SUMMARY:
This solution provides additional reference material for the Motorola m8000 Version 6.2F01 release.
EXPLANATION:
Platform: Motorola m8000
Media type: Cartridge Tape
Extract command: cpio -iudcvBm </dev/r41t
Install command: ./proinstall
Software notes:
- This release was ported with Oracle Version 6.
- This release supports Embedded SQL (HLI) for C.
- 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 you restore the full backup, you receive an error
message that indicates the tapes are out of sequence and the
restore fails if you skip any of the incrementals.
Solution:
Make sure all backups are restored in exact order.
- 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
- Fast Track:
Unlike earlier versions, Fast Track Version 6.2F enables you
to choose from more than 500 files when you create QBF's,
reports, or forms. 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 that
were generated with earlier versions of Fast Track in order
to run them under Version 6.2F.
- Index Deactivation:
If you deactivate indexes, do it through the Index Editor.
Going through the Admin menu in the Dictionary deactivates
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.
- Oracle ldemo:
The ldemo script that resides in subdirectory ora in the
directory where you install Progress (for example,
/usr/dlc/ora/ldemo) will not work with the Query/Runtime or
Runtime product. It makes schema modifications which these
products do not support.
- Remote gateways:
In Version 6.2F, you can remotely access an Oracle or RMS
database. To do this, you must install a Version 6.2F (or
later) core Progress product (for example, PADS, 4GL&RDBMS,
Query Report, or Runtime) on the machine where you run your
Progress application and on the machine that hosts your
non-Progress database.
- Version 6.2F does not trap the CTRL-C if you use it with Remote
Oracle Gateway.
If you use CTRL-C within a transaction, you are disconnected
from the Remote Oracle server with the following message on
your client:
** Disconnected by the server, code 7 (706).
Also, the Remote Oracle server's log has the following error
messages:
SERVER: SYSTEM ERROR: oratmstrt: transaction already
started (1473)
SERVER: ** Please save file name core for analysis by
PSC. (439)
SERVER: logout usernum 0, userid, on (739).
- PROBUILD:
When you run PROBUILD, the $PROLOAD/eucapp/euc.pl file must
have at least read and write permissions (rw-rw-rw-),
otherwise you 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.
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, select your
networking protocols and REMOTE ORACLE GATEWAY at the
CONFIGURABLE ELEMENTS screen.
If you need to access your non-Progress database locally,
you need to purchase the Progress 4GL&RDBMS software and the
Database Gateway software. If you do not have this
combination of products, you cannot load the standard
gateway in your executable. (Refer to Chapter 1 in the
Progress 3GL Interface Guide for more information.)
- 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.
- 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.
Solution:
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.
Reference to Written Documentation:
Progress 3GL Interface Guide, Chapter 1.