Kbase 16654: 7.3C12 VMS PATCH Release Notes
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  10/05/1998 |
|
7.3C12 VMS PATCH Release Notes
PROGRESS Version 7.3C12
-----------------------
This Patch for PROGRESS 7.3C12 includes the following files and
resolves the attached problems. Outlined below are detailed
instructions for implementation. If you need further assistance,
please contact Progress Technical Support.
NOTE: Use of ".D" and ".DF" file extensions
-------------------------------------------
The .D and .DF extensions are "reserved" to Progress Software
Corporation in order to signify database data and definitions files.
When the Progress image discovers it is reading a .D or .DF file it
believes that it is loading the database and thus ensures the format
of the file to be in "STREAM_LF" format. Thus if you use .D or .DF
for your own personal data files and then read them into Progress,
Progress will convert your file format if it is not STREAM_LF. This
caused some confusion in the 7.3C release which first introduced this
issue and caused some problems.
Patch Contents
--------------
As a departure from previous patch kits which listed all the files
without regard to which bug they fixed or where they should go, this
patch kit will expand to the same directories as you should have in
your currently installed version of Progress.
You may then more easily copy files from one directory to another with
more assurance that you've copied the file to the correct place.
Bug Fixes
---------
This patch includes solutions to the following issues:
1. Foreign national characters did not show up in Results.
Bug # 95-12-15-008
TSR # Not found.
This patch kit recompiled the source modules for results to use the
undefined character set as opposed to the commercial release that
used a defined character set of ISO8859-1.
This patch only resolves the problem for the French character sets.
If you need this for your languages character set, please contact
Progress Technical Support and request a special patch kit.
Files required:
[.DLC.TTY.PRORES.RESLANG]*.*
2. DBI files were not created in temporary directory.
Bug # 96-12-11-013
TSR # 961108-48035
This patch kit resolves a problem where if you specified a
temporary directory (/TEMPORARY_FILES and /SAVE_TEMP_FILES) and a
DBI file is created for temporary tables, the file was never placed
where you expected it, rather it was created "hidden" in your
current working directory.
Files required:
[.DLC.PROBUILD.4GL]DRDBSET.OBJ
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
3. Cannot execute PROGRESS/STRUCTURE/REPAIR=file.st mvdb
Bug # 96-10-23-028
TSR # 961018-AS455
This patch kit resolves a problem where you couldn't use the
REPAIR syntax to the PROSTRCT image.
Files required:
[.DLC]PROGRESS.CLD
[.DLC.BIN]_DBUTIL.EXE
4. RMS DataServer problems with Signed Integer and OPUNCH datatypes.
Bug # 96-10-15-025
TSR # 961010-52280
This patch kit resolves a problem with the RMS DataServer where
storing an unsigned value into a 2 byte signed integer would
result in the wrong value being displayed. Thus a -1 stored to a
two byte signed field would result in 65535 being displayed to the
screen.
Bug # 96-12-13-021
TSR # 961025-54744
This patch kit resolves a problem with the RMS DataServer where a
comparison of 0 to 0 (zero to zero) of an OPUNCH field would
resolve incorrectly. A 0 to 0 comparison returned greater than
value rather than equal to value.
Files required:
[.DLC.PROBUILD.RMS]RCSYS.OBJ
[.DLC.RMS]PROGRES.EXE
5. Print to NULL device kills client with HANGUP signal.
Bug # 96-11-15-021
TSR # 960904-57094
This patch kit resolves a problem where the server would send a
hangup signal to the client after an attempt to print to the NULL
device as follows:
$ define sys$print "nul"
$ progress sports
output to printer.
display "Ignore - just testing"
output close.
<PF1>
Database SPORTS was disconnected. (1015)
%PROGRESS-F-BADEXIT, Abnormal termination has occurred
$
Files required:
[.DLC.PROBUILD.4GL]DRCLIENT.OBJ
[.DLC.PROBUILD.4GL]RNTMPIO.OBJ
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
6. Cannot TYPE/TAIL a Database .LG file.
Cannot TYPE/TAIL a file which was output by 4GL "OUTPUT TO"
statement.
Bug # 96-10-07-011
TSR # 960924-36439
This patch kit resolves problems where file creation done by
Progress would not allow for the TYPE/TAIL command to work
properly in VMS, unless a "SET FILE/ATTRIBUTES" was performed on
the file, because the "Longest Record Length" of the file was too
large (32767).
Files required:
[.DLC.PROBUILD.4GL]DBLG.OBJ
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
[.DLC.BIN]PRODB.EXE
7. Unable to open .PF file with specific version number.
Bug # 96-07-19-025
TSR # 960719-29124
This patch kit resolves a problem where an attempt to open a
specific .PF version file would fail or open the wrong file.
Files required:
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
8. DataServer Login/Logoff missing user name output for RMS.
Bug # 96-10-15-029
TSR # 961011-39324
This patch kit resolves a problem where the DATASERV.LG file did
not receive the user name when listing which users logged in and
out of the RMS database via DECnet.
Files required:
[.DLC.PROBUILD.4GL]NSCRSVP.OBJ
[.DLC.BIN]_PROBRKR.EXE
[.DLC.BIN]_PROOIBRK.EXE
9. Database file kept open after "Disconnect" statement.
Bug # 96-11-19-001
TSR # 961118-UK953
This patch kit resolves a problem where the database file (.db)
was opened twice on VMS during the CONNECT process, but only
closed once during the DISCONNECT process. The following code
exhibits the problem (in the procedure editor, assuming you have
sports database in local directory):
CONNECT SPORTS -1.
DISCONNECT SPORTS.
VMS.
$$ SHOW DEVICE/FILES/NOSYS
Process name PID File name
SYSTEM 0000022F [PRO73C10.DLC.BIN]PROGRES.EXE;1
SYSTEM 0000022F [PRO73C10.DLC]PROMSGS.DAT;1
SYSTEM 0000022F [PRO73C10.DLC]CONVMAP.CP;1
SYSTEM 0000022F []LBI000559.;
SYSTEM 0000022F [PRO73C12.TEST]SPORTS.DB;1 <======= ***
SYSTEM 0000022F []SRT000559.;
....
$$ LOGOUT
Files required:
[.DLC.PROBUILD.4GL]BKSET.OBJ
[.DLC.BIN]PROGRES.EXE
[.DLC.BIN]_MPROSRV.EXE
[.DLC.BIN]_RFUTL.EXE
10. OS-COPY command not working correctly for RMS Indexed files
Bug # 96-11-25-011
TSR # 961121-42912
This patch kit fixes a problem where using the OS-COPY command in
Progress incorrectly copied a RMS "index" formatted file to a
sequential file.
Files required:
[.DLC.PROBUILD.4GL]N2FULHLI.OBJ
[.DLC.PROBUILD.4GL]N2PSHUT.OBJ
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
11. OS-COMMAND command scrolling screen extra line
This patch kit removes a bug fix where the last line of output was
not scrolled and had the "Press space bar to continue" overwriting
the line. The bug fix caused more problems with the usage of the
OS-COMMAND now skipping a line when it was not expected to.
Files required:
[.DLC.PROBUILD.4GL]IOLYR.OBJ
[.DLC.BIN]PROGRES.EXE
12. Usage of OpenVMS System Service "SYS$FORCEX" on client process
caused broker to crash.
Bug # 97-01-29-045
TSR # 970124-31514
This patch kit resolves a problem where the usage of the OpenVMS
System Service "sys$forcex" to attempt to normally terminate a
client caused the broker to crash.
Files required:
[.DLC.PROBUILD.4GL]FD.OBJ
[.DLC.BIN]PROGRES.EXE
[.DLC.RMS]PROGRES.EXE
13. Cannot connect to more than 33 databases concurrently from client.
Bug # 96-12-20-005
TSR # 961217-SW004
A hardcoded restriction within Progress disallowed you from having
any one client connect to more than 33 databases concurrently.
This "restriction" has been removed and a client can now connect
up to 240 databases concur- rently (240 is the maximum of
/MAXDATABASES or -h).
Files required:
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.PROBUILD.4GL]DBMGR.OBJ
[.DLC.BIN]PROGRES.EXE
14. PROPATH path element does not find files in [000000] directory
when path element is a ROOTED logical.
Bug # xx-xx-xx-xxx
TSR # xxxxxx-xxxxx
A problem existed when Progress searched your PROPATH for files
which were located in the master file directory ([000000]) of a
rooted logical and you used your PROPATH element to include both
files and subdirectories as you can do easily using UNIX
environment variables.
For example, if your directory structure was as follows:
disk:
|
[dir1]
[dir2] foo.p
bar.p
And you defined your PROPATH to use a rooted logical as follows:
define /translation=concealed path1 disk:[dir1.]
define propath ",path1,..." (where ... is the rest of your
PROPATH)
Within the procedure editor, Progress would not find "foo.p"
unless you included it specifically, such as "dir1:[000000]foo.p".
This has been resolved and you now may just "include foo.p", and
the file will be found.
The only restriction to the fix is that you must define your path
element logical "/TRANSLATION=CONCEALED" in order for Progress to
understand you are attempting to include both files and
subdirectories from the path element location.
The prior work-around to the problem was to add ":[000000]" to
your PROPATH element. This work-around will still work.
Files required:
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
15. Memory violation when database is in the state of disconnecting a
dead user.
Bug # 96-05-28-042
TSR # n/a
A problem existed where if a PROGRESS/KILL_USERS was attempted on
a database which was in the state of disconnecting a dead user,
the database broker would cause the following error:
"SYSTEM ERROR: lkrend called with active transaction (5142)".
This has been fixed.
Files required:
[.DLC.PROBUILD.4GL]MUSYS.OBJ
[.DLC.PROBUILD.4GL]DBSYS.OBJ
[.DLC.PROBUILD.4GL]DBLKSCH.OBJ
[.DLC.BIN]_MPRSHUT.EXE
16. Inability to access record locking table in PROMON.
Bug # 96-09-25-004
TSR # n/a
A problem existed where PROMON would not allow access to the
record locking table when trying to determine what user was
locking the database. This problem has been fixed.
Files required:
[.DLC.PROBUILD.4GL]DBSYS.OBJ
[.DLC.BIN]_MPRSHUT.EXE
17. Codepages and the use "OUTPUT TO TERMINAL PAGED"
Bug # 96-09-06-013
TSR # 960904-DE202
A problem has been fixed with the usage of the Progress statement
"OUTPUT TO TERMINAL PAGED" when the codepage for a report does not
match the code-page used to store the data.
Files required:
[.DLC.PROBUILD.4GL]IOLYR.OBJ
[.DLC.BIN]PROGRES.EXE
18. Failure to automatically extend .TL file
Bug # 96-10-08-053
TSR # n/a
A problem has been resolved where if too many transactions were
logged to the .AI file, then during a roll forward an attempt to
extend the .TL file would fail.
Files required:
[.DLC.PROBUILD.4GL]UP2PHASE.OBJ
[.DLC.BIN]_RFUTIL.EXE
[.DLC.BIN]_PROUTIL.EXE
19. Behaviour of the "NEXT-PROMPT" command
Bug # 96-02-08-025
TSR # 960206-61103
A regression occurred in V7 of Progress when using the
"NEXT-PROMPT" keyword when running a procedure as the result of
input to a field. This regression has been fixed.
Files required:
[.DLC.PROBUILD.4GL]IOLYR.OBJ
[.DLC.BIN]PROGRES.EXE
20. Database server crashes with "MUXFREE 9 NOT OWNER" errors.
Bug # 96-09-23-014
TSR # 960826-55301
A problem has been resolved where on a multiple CPU system a
condition existed where an internal lock of the database was freed
incorrectly leading to database server shutdown.
Files required:
[.DLC.PROBUILD.4GL]MTSYS.OBJ
[.DLC.BIN]PROGRES.EXE
[.DLC.BIN]_MPRSHUT.EXE
[.DLC.BIN]_MPROSRV.EXE
21. Procedure Editor switches buffer on a Progress Compile error.
Bug # 96-11-11-029
TSR # 961007-49201
This patch kit resolves a problem where if you were in the
Procedure Editor compiling a named file which had an error in the
code, then the Procedure Editor changed your buffer to a buffer
name "P#####.PED". If you then fixed the errors and attempted to
save the file to the same name as you had opened, Progress would
not allow you to. This problem has been fixed and the Procedure
Editor does not switch to the ".PED" buffer, rather you
are kept in the buffer with your original file name.
Files required:
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
Instructions
------------
1. Create a directory call tmp
$ create/directory [.V73C12]
2. Unpack files from the tape
$ backup/log <tapedev>:V73C12.sav/save [.V73C12...]*.*
!<tapedev> is site
!specific tape name.
3. Set working directory to [.V73C12]
$ set default [.V73C12]
4. Copy the files to their appropriate directories. The
subdirectories here mirror the [dlc...] directories where you have
Progress installed. Simply copy the files from here to where
Progress is installed. For example, if you have installed Progress
at the default location of sys$sysdevice:[dlc] the following will
work:
$ copy/log [...]*.* sys$sysdevice:[dlc...]*.*
5. If you install the PROGRESS verb into your system DCLTABLES, then
you will need to update the system DLCTABLES.
$SET COMMAND/REPLACE/TABLE=SYS$LIBRARY:DCLTABLES.EXE DLC:PROGRESS.CLD
$MCR INSTALL/REPLACE SYS$LIBRARY:DCLTABLES.EXE
If your node is a member of a cluster each node in the cluster in
which you run Progress from must run the "MC INSTALL" command, use
SYSMAN to perform this task across cluster members.
6. If necessary, don't forget to replace images in shared memory using
the INSTALL utility:
$ MCR INSTALL/REPLACE ...
where ... are the Progress images you may have installed.
7. Relink new executables to include new objects if your environment
requires the use of PROBUILD.COM.
8. Print a hardcopy of the readme.pro before file deletion.
$ print readme.pro
9. Once you are sure that appropriate files are copied and installed,
delete the files located in [.V73C12...]
$ delete
oconfirm [...]*.*;*
You will need to repeat the delete command a couple of times until
there are no more files in the current directory, then:
$ set default [-]
$ delete
oconfirm V73C12.DIR;
Progress Software Technical Support Note # 16654