README.PRO 7.3C15 Release Notes for VAX and ALPHA OpenVMS
PROGRESS Version 7.3C15
-----------------------
This Patch for PROGRESS 7.3C15 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 regar d 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 assuranc e 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.
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
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" statment.
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
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
[.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 []LBI000559.;
SYSTEM 0000022F
[PRO73C15.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]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
environement 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
[.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:
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
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. (V7.3C13)
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
22. Error message of "utqio deaccess error" display when
using
ointegrity (V7.3C13)
Bug # N/A
This patch kit resolves a problem where if you
connected to a database using the "/NOINTEGRITY"
qualifier, then grew the size of the database an
informational message would show up on the screen and the
in the log file as follows:
"utqio deaccess, RMS status 0x013C"
Files required:
[.DLC.PROBUILD.4GL]DBMGR.OBJ
[.DLC.BIN]PROGRES.EXE
23. New Default Setting for Century (-yy) Parameter
---------------------------------------------------
(V7.3C13)
(V7.3C13)
Bug # 97-01-20-024
For PROGRESS Versions 8.2A, 7.3E and 8.1A01, the default
setting for the Century (-yy) parameter is
now 1950. Prior to these versions of PROGRESS, the -yy
default was 1900. The -yy parameter controls how a 2-digit
year gets expanded into a 4-digit year. It does not define
a "default" century. Instead, it defines a 100-year
period in which it is safe and legal to use 1 or 2-digit
year designations. The new default is in preparation for the
year 2000.
Changing -yy to 1950 will cause PROGRESS to look at any
2-digit year "nn" and make it be 19nn if nn is >= 50, and
20nn if nn is < 50. This means that:
01/01/99 will be 01/01/1999 and
01/01/00 will be 01/01/2000
With this new default, the following line (if run on
December 31, 1999):
DISPLAY TODAY TODAY + 1.
gives the following output:
12/31/99 01/01/00
Similarly, the following line (if run on Jan 1, 2000):
DISPLAY TODAY - 1 TODAY.
gives the same output as above.
If you do not want to use the new default, you can set -yy
to 1900 and PROGRESS will behave exactly as before.
If you want to change the setting of the -yy parameter, you
should choose a 100-year span like 1920 to 2020, or perhaps
1910 to 2010. The setting you choose should best cover the
dates you have to accommodate, such as birthdays and future
mortgages (30 yr future dates, etc.). Once you have set -yy
to a suitable setting, you can use a 2-year date format
("99/99/99") for dates inside the range you define. You
should use a 4-year date format ("99/99/9999") for dates
falling outside of the range you define.
Files required:
[.DLC.PROBUILD.4GL]RUNTIME.OBJ
[.DLC.PROBUILD.4GL]HLILIB.OBJ
[.DLC.PROBUILD.4GL]IOLYR.OBJ
[.DLC.PROBUILD.4GL]DRSETUP.OBJ
24. Remove Progress Core dump when use VMS system service
-----------------------------------------------------------
-------- (V7.3C13)
Bug # 97-01-29-045
TSR # 970124-31514
This patch kit resolves a problem where if you used
your own crafted routine to perform a sys$forcex on a
client connection, the database server would crash.
While this patch kit does resolve the database server
crashing problem, Progress Software reminds you that
performing a forced exit on a client which is in the
middle of a transaction or micro-transaction will cause
the database server to be shut down. This is due to the
desire to protect your data at all costs. Progress
Software strongly recommends the usage of the forced
exit through the Progress defined interfaces. To do this,
a "PROGRESS/MULTI_USER=SHUTDOWN/DISCONNECT=<pid>",
where <pid> is the Extented PID listed in a "SHOW
SYSTEM" command or the "pid" listed in the Progress
MONitor display.
Files required:
[.PROBUILD.4GL]DRSETUP.OBJ
[.DLC.BIN]_MPROSRV.EXE
25. Fix problem with overwritten value used in
-----------------------------------------------------------
---------------- (V7.3C13)
Bug # 96-12-10-005
TSR # 961031-UK505
This patch kit resolves a problem where if upon startup
the server specified the "/message_buffer_size" it was
being ignored.
Files required:
[.PROBUILD.4GL]DRARGS.OBJ
[.DLC.BIN]_MPROSRV.EXE
[.DLC.BIN]PROGRESS.EXE
26. OS-DELETE does not allow for deletion of specific
version of a file. (V7.3C13)
Bug # 97-03-03-002
TSR # 970226-UK951
This patch kit resolves a problem where the Progress
4GL command OS-DELETE would only delete the most
current version of a file. Thus if you had 3 files
such as :
foo.bar;3
foo.bar;2
foo.bar;1
and you attempted to do an OS-DELETE("foo.bar;2"), the
foo.bar;3 would be erroneously deleted.
Files required:
[.PROBUILD.4GL]UT.OLB
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
27. Partial removal of bug fix 96-10-07-011 (item #6 above).
(V7.3C13)
Bug # 97-05-02-028
TSR # 960924-36439
This bug fix removes a portion of the fix for
96-10-07-011. It was determined that the fix caused
other problems for the customer with file usage and
VMS messages displayed when the file formats differed.
In order to work around the original bug for TYPE/TAIL
of a file created by the 4GL "OUTPUT TO" statement, add
the following line to your 4GL code immediately after
the "OUTPUT CLOSE" statement:
VMS SILENT "SET FILE/ATTRIBUTES=(MRS=256,LRL=256)
<filename>"
where <filename> is the file you have created. You
must have at least OpenVMS V6.1 or greater to issue
this command. You may also issue the command directly
from DCL.
Files required:
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
28. PROPATH issues
(V7.3C13)
Bug # 97-05-21-045
TSR # 970115-37698
This patch kit fixes a problem with PROPATH where
Progress did not find the correct version of a file
that existed in multiple areas within the PROPATH.
This problem was seen when the PROPATH consisted entirely
of ROOTED logicals (define/translation=concealed) and
the PROPATH was defined to not look in the current
working directory (just a "," as a PROPATH element).
An attempt was run to run a procedure which ran another
procedure off of the PROPATH. In the case seen, the
second procedure run was not run from the correct
directory. A case example:
topfoo
foo1 foo2 foo3
progs progs progs
bar.p foo.p foo.p
foo.p bar.p bar.p
Where each foo.p uses the 4GL syntax: "display running
foo#/foo.p", where # is the number of the directory.
The bar.p just does a "run progs/foo.p".
Defining the path as follows:
define/trans=conc foo1 disk:[topfoo.foo1.]
define/trans=conc foo2 disk:[topfoo.foo2.]
define/trans=conc foo3 disk:[topfoo.foo3.]
define propath "foo1,foo2,foo3"
define propath "foo1,foo2,foo3"
When running in the procedure editor "run progs/bar.p",
Progress returned "Running foo2/foo.p".
Files required:
[.DLC.PROBUILD.4GL]RUNTIME.OBJ
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
[.DLC.RMS]PROGRES.EXE
29. "REMOVE" option to PROGRESS/STRUCTURE/REMOVE= doesn't
-----------------------------------------------------------
----------------- (V7.3C13)
Bug # 97-05-??-???
This patch kit fixes a problem where the ability to
remove an AI file from a multivolume database through
the command interface was missing.
The command syntax is: PROGRESS/STRUCTURE/REMOVE=AI
<dbname>
Files required:
[.DLC]PROGRESS.CLD
30. Progress client crashes on usage of shared frame and
-----------------------------------------------------------
---------- (V7.3C14)
Bug # 97-06-04-012
TSR # 970527-51684
This patch kit resolves a problem with using shared
frames and queries viewed through a browser. Prior the
fix, the Progress client would exit with the
"PROGRESS-F-BADEXIT" message. No other logging was done.
Files required:
[.DLC.PROBUILD.4GL]IOLYR.OBJ
[.DLC.BIN]PROGRES.EXE
31. SEARCH function fails to find file if it cannot READ it
-----------------------------------------------------------
(V7.3C14)
Bug # 97-04-14-017
TSR # 970414-AS045
This patch kit resolves a problem where Progress would
fail to find a file using the 4GL "SEARCH" command if
the file was either already open (and thus locked by
RMS for shared reads) or if the file didn't have the read
privilege available.
Files required:
[.DLC.PROBUILD.4GL]FMEBASE.OBJ
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
32. OS-COPY command not working correctly for RMS
-----------------------------------------------------------
------ (V7.3C14)
Bug # 97-06-10-025
TSR # 970522-38797
Bug # 97-06-10-025
TSR # 970522-38797
This patch kit fixes a problem where using the OS-COPY
command in Progress incorrectly copied a RMS
"sequential" formatted file to a stream_lf file.
Files required:
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
33. Cannot open network file
----------------------------
(V7.3C14)
Bug # 96-11-29-006
TSR # 960823-34765
This patch kit resolves a problem in using the <ESC>-O
or "File" menu option to open a networked file. Prior
to the fix, the file would not be opened and Progress
would display an error dialog box stating that the
file could not be found and to verify the path is correct.
A networked file uses the following syntax:
nodename::disk:[directory]file.p
Files required:
[.DLC.PROBUILD.4GL]UT.OLB
[.DLC.BIN]PROGRES.EXE
34. Cannot use /KILL when connected to more than one
-----------------------------------------------------------
-- (V7.3C14)
Bug # 96-02-28-022
TSR # 960227-72665
This patch kit resolves a problem when a client is
connected to two or more databases using a parameter
file, an attempt to kill all the clients using the
"PROGRESS/MULTI=SHUT/KILL" command will hang on the second
database shutdown command waiting for the client from
the first shutdown/kill to "Press space bar to
continue".
Files required:
[.DLC.PROBUILD.4GL]WVSYS.OBJ
[.DLC.BIN]PROGRES.EXE
[.DLC.BIN]_MPROSRV.EXE
35. Saving "Untitled" buffer, saves wrong record format for
-----------------------------------------------------------
----- (V7.3C14)
Bug # 96-12-18-003
TSR # 961218-UK953
This patch kit resolves a problem where if one attempts
to save the untitled buffer as a new file, it was saved
using a "variable record format". The file is now
saved as expected in "Stream_LF record format".
Files required:
[.DLC.PROBUILD.4GL]PROVV.OLB
[.DLC.BIN]PROGRES.EXE
36. Unable to PROBKUP with AFTER_IMAGE file.
--------------------------------------------
(V7.3C15)
Bug # 97-09-08-005 ?
This patch kit resolves a problem where if one attempts
to run PROBKUP on a database with after imaging
enabled, they are unable to supply the after image
file name argument. The following sequenced produced the
error:
progress/create sports sports
progress/util=aimage_begin/after_image=sports.ai sports
progress/after_image=sports.ai sports
<do some processing - such a "create customer".
and exit from progress. progress/backup sports sports
<results in error>:
You must supply the -a ai-file-name parameter. (875)
%PROGRESS-F-BADEXIT, Abnormal termination has
occured
This is now resolved.
This is now resolved.
Files required:
[.DLC]PROGRESS.CLD
[.DLC.BIN]_DBUTIL.EXE
37. Progress Roll Forward Utility on VMS does not support
-----------------------------------------------------------
------------------ (V7.3C15)
Bug # 97-09-09-012
TSR # 970730-50894
This patch kit resolves a problem where the Roll
Forward utility on VMS did not support the "endtime"
and "endtrans" qualifiers through the CLI to Progress.
The following are the commands in UNIX format:
rfutil sports -C roll forward -a sports -C endtime
yyyy:mm:dd:hh:mm:ss rfutil sports -C roll forward
-a sports -C endtrans transaction-number
This has been now fixed. In order to utilize the
options on VMS you may use the "/ENDTRANS=" or
"/ENDTIME=" qualifiers to the Roll Forward Utility. The
the following commands will now work:
$ progress/utility=roll_forward/after_image=sports -
/endtime=yyyy:mm:dd:hh:mm:ss sports
$ progress/utility=roll_forward/after_image=sports -
/endtrans=transaction-number sports
Where the "yyyy:mm:dd:hh:mm:ss" is replaced by a valid
year, month, day, hour, minute, and second value and
the "transaction-number" is replaced by a number
representing the transaction number to roll forward to.
See the Progress System Administration Reference for
details.
Files Required:
[.DLC]PROGRESS.CLD
[.DLC.BIN]_RFUTIL.EXE
38. SAVE INTO option for source code compilation
-----------------------------------------------------------
------------ (V7.3C15)
Bug # 97-09-10-013
TSR # 970910-40924
TSR # 970910-40924
The SAVE INTO option of the compile statement does not
append the path of the source program. Page 161 of the
language reference manual A-F states:
If you specify a relative pathname for the source
file, that pathname is appended to the SAVE INTO
path. For example:
PROPATH "/pro1/source".
COMPILE test/proc1.p SAVE INTO /pro1/obj.
In the example, progress should save the source file
"/pro1/source/test/proc1.p" as
"/pro1/obj/test/proc1.r". Instead it saves it to
"/pro1/obj/proc1.r". It is ignoring the pathname of the
source file.
This has now been fixed and the file is saved correctly.
Files Required:
[.DLC.BIN]PROGRES.EXE
Instructions
------------
1. Create a directory call tmp
$ create/directory [.V73C15]
2. Unpack files from the tape
$ backup/log <tapedev>:V73C15.bck/save [.V73C15...]*.*
!<tapedev> is site
!specific tape name.
3. Set working directory to [.V73C15]
$ set default [.V73C15]
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 [.V73C15...]
$ 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 V73C15.DIR;
Progress Software Technical Support Note # 17545