Kbase 11134: Release notes for 6.2L
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Release notes for 6.2L
ADDITIONAL NOTES FOR THIS RELEASE
PLATFORM: VAX/VMS
MEDIA TYPE: 9 Track Tape
SOFTWARE RELEASE: 6.2L05
EXTRACT COMMAND: backup/log
oassist msa0:/rewind []
INSTALL COMMAND: @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 environment
variable first:
DEFINE PROEXE usr:[dlc]_progres
convft database-name
o ORACLE GATEWAY
--------------
The Oracle Gateway, remote and local, does not currently use an
index when selecting on a date field. Use an ORDER BY statement
to avoid this problem.
o REMOTE RDB GATEWAY
------------------
- If you try to create a schema holder database from a remote machine,
you will receive errors, such as:
** FIND FIRST/LAST Failed for file _Field (565)
and after loading the data, if you try to access the data, you will
see errors such as:
SYSTEM ERROR: fmx -- bad data type (52)
- When loading in records, data in fields may be truncated.
For example, if you load in the value 180 into the cust-num
field, it may be truncated to 18.
The workaround is to create and maintain your schema holder
database on the VMS machine.
o REMOTE RMS GATEWAY
------------------
Transactions are not rolled back from the RMS database when
a ctrl-\ is pressed from a remote rms client.
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.
o Changes to Batch Functionality
-------------------------------
The previous functionality was as follows:
If the /BATCH option was used non-interactively, the Progress
session would not be submitted as a batch job. Instead,
it would be executed in the current process stream.
In addition, using /BATCH=xxx$batch where xxx$batch is a
different queue, the same behavior would result. i.e,
everything would still be executed in the same process
stream, and no batch job would be submitted to the specified
queue.
The new functionality is as follows:
The use of the /BATCH option will result in the creation
of a new batch process to the specified queue (or the default
batch queue, if none is specified).
As a result, users should review DCL command procedures
containing use of the PROGRESS/BATCH option, to verify that
the command files will be compatible with the new functionality.
In addition, temporary submit files used for batch submissions
are removed before the batch job invokes Progress, which will
prevent these files from being left in the directories, due
to process aborts and abnormal terminations.
The Naming Convention of Log files has been modified to:
PROBATCH + the decimal value of the process id of the
submitting process.
o Backup Functionality
--------------------
Backup of databases to multiple tapes is now supported.
Progress requires that new tapes be initialized, prior to
executing the backup procedure. Tapes that have been
initialized and used previously do not need to be
re-initialized. Progress will simply overwrite it.
Users are no longer required to issue the mount command
prior to loading the tapes for backup. Users are not required
to issue the dismount and mount commands between tape volumes.
o PROLIB Functionality
--------------------
VMS PROLIB now allows case-insensitive execution of .r
code, as well as declaration of libraries on the PROPATH,
UNIX and VMS style. While PROLIB will accept any ASCII
file, only .r files can be executed.
If you specify myfile.p, it will search for myfile.r
and execute it. If it is not found, it will search for
for myfile.p in the PROPATH, but will not search the
library for myfile. The purpose of PROLIB is to increase
performance by decreasing search time for .r code.
Running .p code defeats this purpose.
o Running RESULTS on VMS
----------------------
In order to invoke results as described in the RESULTS
documentation, the user must copy the results.com from
the installation area to their local directory.
Then @results can be used to execute results. Be sure to set
DLCRES to where you installed PROGRESS RESULTS.
o RESULTS with ORACLE and RDB Gateways
------------------------------------
To run RESULTS for Version 6 with an ORACLE or Rdb gateway, the gateway
must be Version 6.2G or later.
o Fast Track
----------
When anything (QBF, report, etc...) is generated with Fast Track
and DIRECTORY is prompted for, you must specify a sub-directory
with no brackets.
Example: DIRECTORY fm
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 mua0:
proshut demo -C online mua0: incremental -o 2
After restoring the full backup, if you skip any of the incrementals,
you recieve 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.
Progress Software Technical Support Note # 11134