Kbase 13836: 7.2E Release Notes for VAX/VMS
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
7.2E Release Notes for VAX/VMS
RELEASE NOTES
-------------
PLATFORM: VAX Open-VMS 5.5-2
SOFTWARE RELEASE: 7.2E
INSTALL COMMAND: @PROINSTALL
----------------------------------------------------------------------------
Please note that the Install Utility has changed significantly.
Please refer to the Progress VMS Installation Documentation for
a complete description.
Many new features and functions have been added to the Progress
VMS Version 7.2E release. Refer to the Progress Version 7
System Administration Reference and the System Administration
Guide Documentation for complete details.
If you have questions regarding the contents of this document,
please feel free to contact Progress Technical Support at
617-280-4999.
SOFTWARE NOTES:
The following notes are added here to assist with resolving
potential questions which might arise while using Progress
Version 7 under VMS. If you have any questions or problems,
contact Progress Technical Support at 617-280-4999.
DESC: INSTALL FAILS TO ERASE EXISTING DIRECTORY
If you try to install Progress into an existing directory,
a dialog box will appear that offers the option to erase the
directory. This option will not actually erase the directory.
Erase the directory with the DCL DELETE command first before
installing Progress or specify a directory which does not
already exist.
DESC: VIEWING RELEASE NOTES AFTER INSTALLATION
If you select this option from the Progress Install Utility,
you are put into your default system editor to view the release
notes. Please refer to the Digital Equipment Corporations VMS
Text Processing Documentation for complete details on the use
of VMS EDT or EVE Text Editors.
DESC: ARCHIVE FILES NEED TO BE DELETED AFTER INSTALLATION
The following archive files in your DLC directory need to be
deleted after your installation is complete:
ADECMSRC.;1 AR1.;1 AR10.;1 AR16.;1
AR17.;1 AR18.;1 AR19.;1 AR20.;1
AR21.;1 AR22.;1 AR23.;1 AR24.;1
AR26.;1 AR27.;1 AR8.;1 AR9.;1
BASEADE.;1 DBUTILS.;1 FTRT.;1 ORACLNT.;1
ORADS.;1 PMBASE.;1 PMCZE.;1 PMDAN.;1
PMDUT.;1 PMENG.;1 PMFIN.;1 PMFRE.;1
PMGER.;1 PMHBR.;1 PMHUN.;1 PMITA.;1
PMMEX.;1 PMNOR.;1 PMPOL.;1 PMPOR.;1
PMSPA.;1 PMSWE.;1 PMTAI.;1 PROARC.LST;1
RMSCLNT.;1 RMSDS.;1
DESC: PROBUILD NEEDS EUCAPP DIRECTORY IN PROPATH
In order for PROBUILD to create files, you need to add your
EUCAPP directory to your PROPATH. For example, if you installed
in sys$sysdevice:[dlc], you must add sys$sysdevice:[dlc.eucapp]
to your PROPATH.
DESC: BUILDENV.COM IS NOT SUPPORTED
This release no longer supports BUILDENV.COM. As a result, you
will need to define your PROLOAD rooted logical to point to
your PROBUILD area. For example: "$define/trans=concealed
PROLOAD sys$sysdevice:[dlc.probuild.]".
DESC: PROBUILD FILE DIRECTORY PROBLEM
When using the PROBUILD Utility and specifying a directory name
which does exist, you will receive a message that the directory
does not exist, do you want to create it? Answer yes.
PROBUILD will not actually create the directory (since it
already exists). The link script gets created properly in the
directory which you indicated.
DESC: 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 that you
access 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 your procedure or use the PF1 key as the GO key.
DESC: FILE OPEN <FILES...> DOES NOT WORK
From the editor, ESC-M=MENUS or PF3=MENUS FILE->OPEN to browse
will not work. Enter the actual filename at the 'File Name:'
prompt.
DESC: PROG/CREATE CAN'T FIND BUSY DB
If you try to copy a database that is in use, either in single
user mode or has a database server process running for
multi-user mode, you will receive an error
PROGRESS database 'dbname' was not found.
%PROGRESS-F-BADEXIT, Abnormal termination has occured
The message should indicate that the database is in use or is
busy.
DESC: COMPILE ERROR CHANGES EDIT BUFFER
When you compile some p-code that has an error in it from the
progress editor and then create a new edit buffer, using the
Menu-File-New and again compile code which has an error, the
compile will place you back into your first procedure edit
buffer.
DESC: XCODE DOESN'T FIND *.P'S
The Progress command PROGRESS/XCODE/DIRECTORY=[dirname] *.P,
does not work as indicated. You cannot do 'mass' compiles in
this fashion. You must specify each p-code file that you wish
to compile. To do 'mass' compiles, create a .com file which
has a separate line such as shown below.
$PROG/XCODE/DIR=[.DEPLOY] FIRST.P
$PROG/XCODE/DIR=[.DEPLOY] SECOND.P
.
.
$PROG/XCODE/DIR=[.DEPLOY] LAST.P
DESC: ESQL_LOG STARTUP PARAMETER INVALID
The /ESQL_LOG command as referenced in the Progress Version 7
System Administration Reference Documentation does not work
from the VMS DCL command line. To use this startup option, you
must use a parameter file and specify this command in its Unix
format. (i.e. use -esqllog in the parameter file.)
DESC: ESQL_NO_PAD STARTUP PARAMETER INVALID
The /ESQL_NO_PAD command as referenced in the Progress Version
7 System Administration Reference Documentation does not work
from the VMS DCL command line. To use this startup option, you
must use a parameter file and specify this command in its Unix
format. (i.e. use -esqlnopad in the parameter file.)
DESC: PARM FILE ON CONNECT NEEDS FULL PATH
You have to provide the full path along with the parameter
filename and not simply the parameter filename when specifying a
.pf file when connecting through ESC-M=MENUS or PF3=MENUS,
TOOLS->DATABASE->SELECT->WORKING DATABASE.
If you specify just the parameter filename you will get an
error
** Could not recognize argument: filename (301)
Unable to execute CONNECT statement. (325)
DESC: TOOLS-> APPLICATION COMPILER NEEDS FILENAME
The application compiler gives the option of ">.".
This will not compile successfully for VMS and the
user will get the following error:
"utDirOpendll is not yet implemented on this operating
system <ok>".
Workaround: From the editor, type "COMPILE NAME.P SAVE."
or in the tools application compiler, Select DELETE,
ADD and enter your NAME.P file.
DESC: MS-WINDOWS CLIENT DISCONNECT NOT WRITTEN IN SERVER LOG
If a remote windows client disconnects from the database,
the server log will not show that the client logged out
until the client reconnects to the database. At that time,
you will see the logout and the login posted. If the
client does not reconnect, the logout should be posted 25
minutes after the logout occurred.
DESC: PROBUILD LINK ERRORS
When running the command procedure generated by probuild,
you will see LINK warning messages. These may refer to
undefined symbols, compilation warnings etc. The executable
will be built correctly and it should run fine.
DESC: PERFORMANCE FOR REMOTE DECNET CLIENTS
You will see a significant reduction in performance if you
have the following situations in a procedure. A transaction
open that contains a FIND FIRST using a UNIQUE index, along
with a DELETE statement.
Workaround: Access the records specifying a non-unique
index.
DESC: PROCESS FAILURE DURING A DATABASE RESTORE
If the process running a database restore is abnormally
stopped, and then the restore is restarted, the restore will
complete, but there will be database corruption. As with
all PROGRESS utilities, please do not use any type of force
exit or stop/id to abnormally terminate a process that is
using PROGRESS.
DESC: PROGRESS/COPY of a MULTI-VOLUME DATABASE
If you try to copy an existing multi-volume database, with a
large bi file, into a new void multi-volume database, you
may encounter the following error.
SYSTEM ERROR: rlrdprv: note len 31764 too big (3831)
Workaround: Truncate the before-image file (.bi) prior to
doing the copy.
DESC: CONV67
CONV67 will fail if you try to convert the database using a
user defined collation table.
Workaround: Do not convert the database with a user defined
collation table.
DESC: LANGUAGE : PUT
Running the followng piece of code will fail at compile time
with the error ** unmatched quote found in procedure (133).
PUT UNFORMATTED ' fieldbegin:"\\"\;' SKIP.
DESC: PERFORMANCE FOR ORACLE DATASERVER
You will see a significant reduction in performance when you
use the UPDATE/ADD Oracle Table Definitions from the Tools
Menu.
Tools -> Data Adminstration -> DataServers -> Oracle
Utilites -> Update/Add Oracle Table Definitions.
DESC: READ-ONLY CLIENTS
If you have clients connected to the database in read-only
mode, it is possible that the shutdown of the server will
hang. If this happens, you will need to stop/id the process
for each user.
DESC: ERROR SHUTTING DOWN DATASERVER
If you shut down a server while clients are accessing data
the server will not shut down. This is true for a KILL or
EMERGENCY shutdown. When the clients finish accessing the
data, they will get the following error:
** Incomplete write when writing to the server. (735)
Error writing socket, ret=1, errno=8420. (778)
Workaround: Disconnect all users before shutting down
the server.
DESC: DATASERVER PROMON DISCONNECTS NOT WORKING
Promon disconnects for individual users does not work.
Users who have been disconnected will recieve the following
error when they finish accessing data:
** Incomplete write when writing to the server. (735)
Error writing socket, ret=1, errno=8420. (778)
Workaround: Users will have to disconnect themselves instead
of using Promon.
DESC: ESQL/C LARGE CLIENT PROBUILD EXECUTABLE NEEDS TCP
The ESQL/C Large Client ACCVIO'S when demo executable links
without networking.
Workaround: Link demo executable with TCP.
DESC: ORACLE DATASERVER PROBUILD EXECUTABLE NEEDS TCP
The Oracle dataserver ACCVIO'S when linked without networking.
Workaround: Link Oracle Dataserver with TCP.
DESC: RMS DATASERVER PROBUILD EXECUTABLE NEEDS TCP
The RMS dataserver ACCVIO'S when linked without networking.
Workaround: Link RMS Dataserver with TCP.
Progress Software Technical Support Note # 13836