Kbase 9210: Release Notes for vax/vms 6.2B
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/04/2000 |
|
Release Notes for vax/vms 6.2B
901016-slk01
ADDITIONAL NOTES FOR THIS RELEASE
PLATFORM: VAX/VMS
MEDIA TYPE: TK-50 Cartridge Tape
SOFTWARE RELEASE: 6.2B
EXTRACT COMMAND: backup/log
oassist mua0:/rewind []
INSTALL COMMAND: @proinstall
TERMINAL NOTES
SOFTWARE NOTES:
# Exporting
If you export data while connected to at least two Progress
Databases that have the same filename within the databases, and you
select that filename from one of the databases to export it, you
receive two error messages:
1. Filename is in database DBNAME1 and DBNAME2 (425).
2. Unknown or ambiguous file item (725).
The database name is not prepended to the filename.
# HLI
After you create an HLI load script with PROBUILD, PROBUILD places
the following command at the end of the file:
PURGE 'prog'.exe.
Before running your load script, remove .EXE from this command.
When running PROBUILD, you need to make sure the PROLOAD logical
ends with a '.' . The PROBUILD script appends another subdirectory
to the PROLOAD logical. For example:
define PROLOAD DUB0:[rdl6.rel.dlcload.]
# Version of Oracle
Version 6.2B of Progress supports Oracle Version 6 and Version 5.
# FastTrack(QBF Deployment)
Do not specify a subdirectory when deploying your QBFs
(Query-By-Forms). If you do, the subdirectory you specify is
incorrectly appended to the deployment directory.
# Compile
If you try to do a COMPILE on a .p (procedure file) and you use
the LISTING option, you receive the following error message:
SYSTEM ERROR: Bus error. (48)
NOTE: This release note is here in error. The 10/90
Technical Bulletin has an entry to notify users.
# Generating the Oracle Gateway
To build an executable that includes the ORACLE Gateway, do the
following:
1) Copy the ORATPL.VMS template into your current directory and
rename it EXETPL.VMS.
2) Run PROBUILD to create an options file with a .OPT extension.
3) Edit the options file, removing ",-" in the last line of the
file.
4) Comment out the following line wherever it appears in
ORA_COMMON:loutl.com (ORACLE Version 6) or
ORA_COMMON:COM$:loutl.com (ORACLE Version 5):
PSECT_ADDR = $CHAR_STRING_CONSTANTs, SHR,NOWRT,EXE
5) For ORACLE Version 5, type the following command to build your
executable:
@com$:lcee image-name options-file/opt
where image-name is the name of your final executable and
options-file is the name of the options file that PROBUILD
created.
6) For ORACLE Version 6, type the following command to build your
executable;
@ora_common:lnocic image-name options-file/opt
where image-name is the name of your final executable and
options-file is the name of the options file that PROBUILD
created.
#Startup
The startup option that tells PROGRESS what version of ORACLE to
use is incorrectly documented for VMS.
It states: ORACLE_VERSION=n
It should be: VERSION_ORACLE=n
#Crash Recovery:
If a client process accessing a multi-user database creates a record
and abnormally terminates (is killed or crashes), other client
processes will not be able to access that record. If you run the
PROMON utility against the database, you will see that the original
client is still considered connected and the record lock is intact.
Note: This release note is here in error. The 10/90
Technical Bulletin has an entry to notify users.
Progress Software Technical Support Note # 9210