| Michael
This problem was caused when two processes on the same node
tried to access the database at the same time. We are using
the time as a unique transaction ID. Well two process could
just happen to get in there between when the clock is updated
in OpenVMS.
All that happens here is the Scheduler stops and you have to
restart it. This problem has been fixed in the latest kit
V2.2.
If you do not have it on CD or tape yet, you can copy it from:
cookie::aim$public:[defrag.v22.kits]dfg*.%
thanks
jim amend
|