I wrote UniVerse Transaction Log Replication, an application that uses
UniVerse Transaction Logging. It runs on Windows and *NIX. By using
UniVerse Transaction Logging, it is not intrusive on an application.
It maintains synchronization between a primary and remote server. As logs
become full,
You might consider issuing a sync call in your scripts before splitting off
a mirror. You do not want to miss any dirty block in the I/O buffer cache
that have not made it to the disk storage. If the mirror split process
already contains a sync, then it will take little additional time as there
So if you defragment a disk, and read a record from two different files,
you could force head motion.
If many files grow the disk blocks can be allocated from the free areas,
which might actually localize time dependent or associated data near each
other on the disk.
Except when I am all by my
But many of the parameters depend upon user count, and more specifically
application activity. I do not think an install script could be that
intelligent.
I don't know why IBM doesn't just make them the default.
Or better still, make the installer a little more intelligent (less
stupid?) so
Another way to create random file corruption is to back up an active
database with a system-level utility that does not honor the lock manager,
and restore the backup. Backing up the database in this manner creates an
inconsitent image.
Mark A. Baldridge
Principal Consultant
North American Lab
Note that Mark is reporting results from D3.
A=
FOR I=1 TO 5
A1,-1=I
NEXT I
Style 2: -1 attribute level then CONVERT to
253...41 seconds
UniVerse caches the last-accessed field position in a dynamic array. On my
1.7 GHz pentium laptop,
0001: A =
To carry Glenn's response a little further, think of the Group lock table
and the READU lock table as comprised of GSEMNUM rows, and GLTABSZ and
RLTABSZ columns respectively.
The group lock associated with the READU lock will be in the same row. It
is determined by taking the group number plus
Also remember that without UV/Net, record and group locks are not respected
between the two systems sharing the mapped drive. You can corrupt internal
file integrity with file updates and insertions.
Date: Fri, 22 Jul 2005 12:14:34 +0100
From: Andy Moore [EMAIL PROTECTED]
Subject: [U2] Using
Could we not just avoid confusing the old(er) timers by just using
assembler and PROC?
Mark A. Baldridge
Principal Consultant
North American Lab Services
DB2 Information Management, IBM Software Group
(607) 351-5666
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please
UniVerse compatibility can be determined by knowing the machine class. If
the machine classification is the same then the object code will be
compatible. Unless the actual run machine has changed, then object code
should remain upwardly compatible.
The object code gets compile-time information
The original request was for a shortest code fragment. This likely meant
as line count, but could have been execution time.
I am using UniVerse 10.1.3 on a 1.7 GHz pentium. Here are some current
timings. Except for test 0001 which is an empty FOR NEXT loop, to the left
of the | is a hint of
11 matches
Mail list logo