Kbase 15025: What does PROGRESS 6.2N11 resolve on Alpha and VAX
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
What does PROGRESS 6.2N11 resolve on Alpha and VAX
VAX/VMS and Alpha OpenVMS PROGRESS Version 6.2N11
-------------------------------------------------
The patch 6.2N11 for Alpha OpenVMS and VAX OpenVMS is
commercially available and should be applied to the
commercial ship for each platform. The patch includes
solutions to the following problems.
Platform Commercial Version Patch Version
------------------------------------------------------
Alpha OpenVMS 6.2N05 6.2N11
VAX OpenVMs 6.2N03 6.2N11
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.
Progress Software Technical Support Note # 15025