Kbase 15317: 6.2N12 patch README.PRO for VAX
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
6.2N12 patch README.PRO for VAX
PROGRESS Version 6.2N12
-----------------------
This Patch for PROGRESS 6.2N12 includes the following files and
resolves the attached problem. Outlined below are detailed
instructions for implementation. If you need further assistance,
please contact Progress Technical Support.
Patch Contents
--------------
BFREC.OBJ;1 COMPILER.OBJ;1 DBMGR.OBJ;1 DBUSR.OBJ;1
DRARGS.OBJ;1 DRSETUP.OBJ;1 DRSIG.OBJ;1 IOLYR.OBJ;1
IOSYS.OBJ;1 MTSYS.OBJ;1 MUSYS.OBJ;1 N1NODNT.OBJ;1
N2FULHLI.OBJ;1 NCSDNET.OBJ;1 NSAPRO.OBJ;1 NSBRKILL.OBJ;1
NSCRSVP.OBJ;1 NSSBSD.OBJ;1 NSSDNET.OBJ;1 PROGRES.EXE;1
PROGRES.MAP;1 README.PRO;1 RNTMPIO.OBJ;1 RUNTIME.OBJ;1
SISYS.OBJ;1 SITOP.OBJ;1 SQLPPSYS.OBJ;1 UPPRODB.OBJ;1
UT.OLB;1 UTSYS.OBJ;1 VCSYS.OBJ;1 VERSION.;1
VMSTOPRO.OBJ;1 _DBUTIL.EXE;1 _DBUTIL.MAP;1 _MPROSRV.EXE;1
_MPROSRV.MAP;1 _MPRSHUT.EXE;1 _MPRSHUT.MAP;1 _PROUTIL.EXE;1
_PROUTIL.MAP;1 _RFUTIL.EXE;1 _RFUTIL.MAP;1
Bug Fixes
---------
This patch includes solutions to the following issues.
1. RDB DataServer
Description: This solution was installed to remedy the improper
assignments of the NULL Value and the Unknown
Value (?) when the datatype DOUBLE PRECISION is
used within an RDB Field. PROGRESS now will
properly insert the correct number when using this
floating datatype.
2. MT Queue
Description: This solution was installed to remedy the problem
regarding the Micro Transaction Queuing. In
particular, PROGRESS was incorrectly flushing
PROGRESS notes prior to cancelling record locks
during abrupt terminal or process disconnects.
3. Ctrl-C
Description: This solution was installed to remedy the improper
CTRL-C handler under client/server environments.
PROGRESS was NOT properly handling the KEYBOARD
event CTRL-C under client/server. PROGRESS was
allocating a buffer and NOT verifying that there
was data in the buffer under some circumstances. A
FLAG is NOW set if the buffer contains data.
4. RMS Block I/O
Description: This solution was installed to remedy the problem
associated to multiple connects and disconnects
to databases. PROGRESS now verifies a file open
array to a file closed array.
5. Disconnect Terminal
Description: This solution was installed to remdy the problem
associated to terminals that abruptly terminated
and PROGRESS was not adequately checking the
disconnect FLAG.
6. DBKEY retry
Description: This solution was installed to verify that when the
PROGRESS error message (1124) exists, that it is
indicative of database corruption. If the PROGRESS
Server receives this message, PROGRESS will perform
a $QIO to device 10 times for record verification.
If the block of data can still NOT get read from
disk, PROGRESS will HEX dump the contents of that
block to the PROGRESS log file.
7. Sort File
Description: Modifications were made to the Sort file routine to
provide a more robust mean of disconnecting users
that run out of disk space during Sort File
Operations.
8. Removing remote TCP/IP Users via PROSHUT/PROMON
Description: When disconnecting REMOTE tcp/ip users via PROSHUT
or PROMON, the REMOTE Servers would ACCESS VIOLATE.
This was a result of improper message handling
between the client and the SERVER.
9. Wait code 0 with PROSHUT, wait=n and REMOTE Servers Hanging
Description: Shutting down the SERVER and REMOTE Servers Hanging
have been resolved by modifications to the PROGRESS
Source specfically around qiow's and Local Event
Flags. This solution also removes a known problem
with management of the Micro Transaction, wait=5.
10. Database Manager Lock Modifications
Description: The DB lock algorithm has been reviewed and
modifications were made to make the function more
robust.
11. Start MANUAL TCP Broker sometime fails
Description: This solution was installed to remedy the problem
associated with starting MANUAL TCP Brokers when
running multiple protocols against one database.
When the MANUAL TCP Broker fails to start the
log file will post messages, and the database
hangs.
BROKER detects death of server -10. (1153)
Disconnecting dead server x
12. KEEPALIVE functionality
Description: KEEPALIVE functionality has been added to remedy
the problem associated with the Server not being
notified when a TCP/IP PC Client disappears, but
their process remains in PROGRESS.
13. PROMON displaying wrong Usr ID
Description: This solution was installed to remedy the problem
associated with PROMON displaying the wrong Usr
ID in option 1 (Usr Control) and option 8 (Shut
Down Database). The Usr ID does not match the
corresponding PID in those options.
14. Shared Memory Violation with multiprocessor systems.
Description: This solution was installed to remedy server crashes
when access to shared memory was performed without
taking out a lock.
The following message is likely to appear:
C-F-LONGJMP. longjump requested
Instructions
------------
1. Create a directory call tmp
$ create/directory [.tmp]
2. Set working directory to [.tmp]
$ set default [.tmp]
3. Unpack files from the tape
$ backup/log <diskdev>:62n12.sav/save *.*
4. Copy the files to their appropriate directories.
$ copy/log *.obj <diskdev>:[dlcload.4gl]* !<diskdev> is site
!specific devname.
$ copy/log ut.olb <diskdev>:[dlcload.4gl]*
$ copy/log version.; dlc:*
$ copy/log *.exe; dlc:*
$ copy/log *.map; dlc:*
5. Replace necessary images in shared memory.
6. Relink new executables to include new objects if your
environment requires the use of PROBUILD.COM.
7. Print a hardcopy of the readme.pro before file deletion.
$ print readme.pro
8. Once you are sure that appropriate files are copied and
installed delete the files located in [.tmp]
$ set default [.tmp] !set def to appropriate tmp directory
$ delete/confirm *.olb;,*.obj;,*.exe;,version.;,readme.pro;
Progress Software Technical Support Note # 15317