I am curious about this also. GSEMNUM is 97 here also with a 117 UV
user license on Redhat Linux UV 10.1.12.
-Original Message-
From: IT-Laure Hansen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 01, 2008 5:43 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] locking question
Hi Brenda,
Is the rule of thumb about the value of GSEMNUM valid for
other systems?
In my personal opinion (which may be wrong!), the rule of thumb is not
right.
UV locking is a very complex topic. It is another good reason to recommend
the UniVerse Internals course.
To explain the
we have a 473 user license of universe and GSEMNUM was 87 so I think
we are woefully undersized as far as that parameter goes.
Hopefully this will fix our issue and I'll owe you guys (and gals) a
HUGE thank you!
one question though what exactly is this parameter used for? I am
trying to
:[EMAIL PROTECTED]
Sent: Wednesday, July 02, 2008 9:05 AM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] locking question
Hi Brenda,
Is the rule of thumb about the value of GSEMNUM valid for
other systems?
In my personal opinion (which may be wrong!), the rule of thumb is not
right.
UV locking
02, 2008 9:08 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] locking question
Like the original poster we don't have any locking issues and since it
has been 2-3 years since I took the UV Internals course and about 2
years since the last time I had to change UV settings, I just didn't
Hi Doug,
has anybody run across/seen an issue where a process sets a lock via READU
and then when it tries to write back the record cannot
because the record is locked but somehow lost the fact that the
process trying to write the record is the process that created the lock?
My money (but
I notice you're on nix ...
Is the piece of code that writes invoked via an EXECUTE or PERFORM from the
code that did the original READU?
I wouldn't expect it to on doze, but on Unix that *might* change the execution
environment enough to cause a problem... (grasping at straws to see if it
Thats for the responses Wol and Martin!
Wol - the lock and the write are in the same program so there is no
execute involved.
Martin - I need to look up the archives that previously talked about
the query processor holding a group lock but that is exactly the lock
we are seeing (a group
If you are sure that this is a Group lock (of what type ?), you may adjust
the UniVerse parameter PAKTIME, which stands for the duration of a Group
lock corresponding to the record displayed just before the Press any key
to continue... prompt.
Reason being for that parameter that when a LIST
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] locking question
If you are sure that this is a Group lock (of what type ?), you may
adjust
the UniVerse parameter PAKTIME, which stands for the duration of a
Group
lock corresponding to the record displayed just before the Press any
key
to continue
10 matches
Mail list logo
