In article <37njq6$
...@raffles.technet.sg> pnay
...@solomon.technet.sg writes:
>I am posting this article in regards to a message that appeared on the
>Novell console. We've tried seeking help from Novell vendor and its
>The message is "Waiting on a lock" under the connection information at the
>Novell console. What we have done and observed in the following is ;
> (1) Under the Console monitor in Novell, select Connection Information
> (2) Highlight on one of the user, we will able to see the File Open activities
> (3) Under normal condition, the status of the user is always: Normal
> (4) When the user try to save a file, the status changes to "Waiting on a> lock"
> (5) When this "Waiting on a lock" appeared, the saving process was delayed
> for about 2 - 3 mins, sometime up to 5 mins depending on the amount
> of data. The performance in saving any file is expected to take a few
> seconds or even less than a minute.
> (6) Its affected the rest of the users who are accessing to the same
> application and database files.
First of all, your programmers should try to RTFM first ;-)
Well here is what the a search on the Novell Folio help files using the
keyword "LOCKS" turned up:
----cut----
Parameters SET categories have parameters that can be
viewed or set. The bolded value given with
each parameter is the default setting.
Some categories have two types of parameters:
normal and advanced. Advanced parameters are
marked (adv).
File caching
Directory caching
File system
Communications
Memory
Locks
Transaction tracking
Disk
Miscellaneous
Locks Control how many open files each station can
have and how many total open files the OS can
handle.
They also control how many record locks each
connection can have and how many total record
locks the OS can handle.
These parameters control all three types of
locks: file, physical, and logical.
Maximum Record Locks Per Connection = 500
Limits: 10 to 10000
Maximum File Locks Per Connection = 250
Limits: 10 to 1000
Maximum Record Locks = 20000
Limits: 100 to 200000
Maximum File Locks = 10000
Limits: 100 to 100000
File locks A file lock secures the entire file and
prevents other stations from accessing the
file.
Physical locks A physical record lock controls data access
by multiple users. It prevents other users
from accessing or changing a range of bytes
(a record) in a file.
A physical record lock is enforced by the OS.
If another user tries to access a range of
bytes that is physically locked, the user is
denied access.
Logical locks A logical record lock also controls data access
by multiple users.
The application assigns a name to each section
of data to be locked. The application then
locks this name when it accesses the data.
A logical lock is not enforced by the OS;
it is enforced only to the extent that the
application checks the name each time it
needs access to data.
Maximum Record Locks Per Connection
Controls how many record locks a station can
use at one time.
Increase this parameter if an application
fails because it can't lock enough records.
Decrease this parameter if stations use too
many server resources.
Supported values: 10 to 10000
Default: 500
Maximum File Locks Per Connection
Controls how many opened or locked files a
station can use at one time.
Increase this parameter if an application
can't run because it can't open enough files.
An OS/2 workstation may need a higher
default than 250. You might need to increase
the number of file handles in the station's
SHELL.CFG file.
Decrease this parameter if stations use too
many server resources.
Supported values: 10 to 1000
Default: 250
Maximum Record Locks
Controls how many record locks the OS
can handle.
Increase this parameter if users have
problems running applications and receive
messages that not enough record locks are
available.
Decrease this parameter if users use too
many server resources.
Supported values: 100 to 200000
Default: 20000
Maximum File Locks
Controls how many opened or locked files
the OS can handle.
Use MONITOR to view the current number of
open files during peak usage.
Increase this parameter if the current
number of open files is near the default.
Decrease it to restrict the number of
available server resources.
Supported values: 100 to 100000
Default: 10000
Example 1. Type SET <Enter>
Screen display:
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Setable configuration parameter categories ³
³ 1. Communications ³
³ 2. Memory ³
³ 3. File caching ³
³ 4. Directory caching ³
³ 5. File system ³
³ 6. Locks ³
³ 7. Transaction tracking ³
³ 8. Disk ³
³ 9. Miscellaneous ³
³ Which category do you want to view: ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
2. To select a category, type the number of the
category and press <Enter>.
3. Complete one of the following.
¯ To view the normal and advanced parameters,
type Y. Do not press <Enter>.
¯ To view only the normal parameters, press
<Enter>.
[logical level] The number (0 to 254) of logical record
locks TTS ignores before beginning to track
a transaction.
[physical level] The number (0 to 254) of physical record
locks TTS ignores before beginning to track
a transaction.
Notes A. You must set a logical level before setting
a physical level.
B. Leave a space between logical level and
physical level.
Example 1 To set TTS to ignore two logical and two
physical record locks before tracking
a transaction, type
SETTTS 2 2 <Enter>
Screen display:
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Transaction Tracking Record Lock Thresholds ³
³ Logical level: 2 ³
³ Physical level: 2 ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
Example 2 To view your current setting, type SETTTS <Enter>
LOCK DELAY=number
Default: 1
This parameter determines the amount of
time (in ticks) the shell waits before
trying to get a lock.
When many users access a file at the same
time, the shell may be unable to gain
access before its allotted wait time. If a
workstation frequently receives error
messages when a file is requested, increase
the value of this parameter.
Note This number is used for lock types that
have no wait ability. For locks with a
wait ability, the wait time is calculated
by multiplying this parameter number by
the LOCK RETRIES number and then multiplying
by two. The resulting number is the time, in
ticks, the workstations will wait for a lock.
Parameters ¯ Directory cache buffers
¯ Maximum number of open files
¯
...
read more »
