Kbase 10756: VMS RELEASE 6.2G50 and above (WHAT IT FIXES)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
05/04/2000 |
|
VMS RELEASE 6.2G50 and above (WHAT IT FIXES)
With VMS releases starting at 6.2G50 PROGRESS requires that virtual
terminals be set on the system (See entry on how to set).
Fixes in this release are as follows:
1) Abonormal terminations of processes:
When a process is abnormally disconnected from PROGRESS, it will
first be logically disconnected. PROGRESS will clean up all the lock
s, undo transactions, etc. The process will then be physically discon
nected. The server should STAY UP, the database should continue, and
other users should NOT be affected. VIRTUAL TERMINALS IS A MUST TO
HELP PROGRESS MAKE THIS HAPPEN.
2) Traversing RM Chain causing hangs:
When massive updates (thousands) have been completed, and an add
is executed, delays will no longer result. The add will take place in
a timely manner.
3) Attempting to establish a logical link results in "error reading
socket" (778)
A new startup parameter, /COMTIMEOUT=N has been established that
will allow the user to define the number of times PROGRESS will try to
establish a logical link when using /SERVICE and /HOST startup paramet
ers. The default value in prior versions was 6. It has been changed
to 20. The user value should be entered as n.
4) "Unexpected wake up from wait code..." (1007) error should no lon
ger occur.
5) "A server or self-server died during db service." (1028) should n
o longer occur as a result of ABNORMAL TERMINATIONS.
6) "tThe DB semaphore was found unlocked while in db service."
(1030) should no longer occur.
7) "ucwait is xx not xx..."(1070) should no longer occur.
Progress Software Technical Support Note # 10756