Kbase 15093: 7.2E01 VAX README.PRO, Release Notes for commercial release
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
7.2E01 VAX README.PRO, Release Notes for commercial release
RELEASE NOTES
-------------
PLATFORM: VAX OpenVMS 5.5-2
SOFTWARE RELEASE: 7.2E01
INSTALL COMMAND: @PROINSTALL
-------------------------------------------------------------------------------
SOFTWARE CORRECTION NOTES
-------------------------
The following pages outline a series of product corrections
and enhancements Progress Software has incorporated into the
PROGRESS VAX/VMS Full-Commercial ship of 7.2E01
If you have questions regarding the contents of this
document, please feel free to contact Progress Technical
Support at (781)280-4999.
UNRESOLVED ISSUES
-----------------
Progress Software has identified the following issues:
Description: APPLICATION COMPILER ERROR
When compiling one or more files in the application
compiler the following error occurs:
adecom/_compile.p not found (293)
bfblst-too many block levels,increase -nb parameter
Currently, the best way to compile .p code is in the
procedure editor using a command such as:
COMPILE new.p SAVE.
Description: PROTERMCAP - VT200, VT300 SERIES USE F11 AS
ESC KEY
When defining the PROTERM logical as VT200 or VT300 series
terminals, the PROGRESS Edit Screen Menu indicates accessing
functions via the ESC key. To access these functions use the
F11 key as the ESC key. Also, note that CTRL X acts as a
BACKTAB key when in the editor. Use the MENU-Compile option
to run a procedure or use the PF1 key as the GO key.
Description: CLIENT LOGIN FAILS ON LONG DATABASE PATH
A remote login will fail if the database path name is too
long. For remote dataservers, this includes username and
password. The server log will post the following message:
SRV 0: Login refused; client has version 17 and server
has version 40.
Do not use database paths greater than 50 characters. A
database path is defined as:
<device>:[directory]<database name>.DB
Description: DEFINE LOGICALS PROEXE, PROCFG, PROSRV, PROLOAD
In addition to the logicals listed in the Installation
Notes, make sure the following logicals are also defined:
$ DEFINE PROEXE <device>:[DLC.BIN]PROGRES.EXE
$ DEFINE PROCFG DLC:PROGRESS.CFG
$ DEFINE PROSRV <device>:[DLC.BIN]_MPROSRV.EXE
$ DEFINE PROLOAD <device>:[DLC.PROBUILD.]
Description: PROAIW, PROBIW, PROAPW PROCEDURES LOCATED IN
DLCBIN NOT DLC
Documentation incorrectly states the location of these
utility procedures as being in the DLC directory. They are
located in the DLCBIN directory. A logical for DLCBIN can
be defined as follows:
$ DEFINE DLCBIN <device>:[DLC.BIN]
Then the procedures can be run like so:
$ @DLCBIN:PROBIW
Description: BULKLOAD MUST BE RUN WHERE DATA IS LOCATED
Bulkload must be done from the directory where the data is
located or the following errors will be seen:
Data input file "<filename>.d" could not be opened. (1505)
Bulk load aborted near "<filename>" because of errors. (1507)
Description: CONV67 FAILS WITH PROG/LANGUAGE_USER
CONV67 will fail if the database being converted is using
user defined collation table.
Do not convert the database with a user defined collation
table.
Description: PROBUILD LINK WARNINGS
Running LDPRO.COM results in the following link warnings when
PROBUILDing the Oracle Remote Dataserver.
%LINK-W-WRNERS, Compilation warning in modul PROFM file
%LINK-W-WRNERS, Compilation warnings in module SFTRAP file
These errors will not effect the executable.
Progress Software Technical Support Note # 15093