Valid on z/OS.
Use the TIMELOCK control option to control the interval at which CA Top Secret will attempt to obtain the Security File lock or an acid enqueue.
All entry methods are accepted.
This control option has the following format:
TIMELOCK(nnn1,nnn2,nnn3,nnn4)
The operand values are specified as whole numbers with up to four digits in each.
The number of .01 second units between tries for the lock.
The number of retries for the lock.
The number of retries for an acid enqueue.
The number of retries for the lock after it is determined that a BACKUP is in progress.
Default: (25,64,128,1200). The default value specifies a retry for the lock every 25 hundredths of a second (every quarter second), and that the TSS9123A message is issued after 64 tries. Thus, it takes 16 seconds of trying for the lock before the TSS9123A message is issued. When trying to obtain an acid enqueue, the third parameter (128) is used. The TSS9122I message is issued after the first 128 tries (32 seconds), and the ENQ variation of the TSS9123A message after another 128 tries (32 seconds). If a backup is in progress on another system, the TSS9125I message is issued when the first 16 seconds (from the second parameter) expires, and the TSS9123A message is issued after an additional 1200 tries, or 300 seconds, based on the fourth parameter.
It is not recommended that changes be made to any of the default values. However, the following illustrate some circumstances under which you may wish to change them.
If the backup consistently takes longer than 300 seconds (5 minutes), and the TSS9123A message is always seen, the fourth parameter can be increased. A value of 1800 would allow 450 seconds (7.5 minutes) (after the first 16 seconds) for the backup:
TIMELOCK(25,64,128,1800)
If the Security File is shared among several systems, but the total amount of I/O from all of the systems is well under the capacity of the device, significant time may be lost to lock contention due to the quarter second delay any time the attempt to get the lock fails. In this case, reducing the first parameter will have little effect on the average response time for a security request but may reduce the peak response time considerably. If the first parameter is reduced, the second, third, and fourth should be increased so that the time intervals before issuing the messages remains constant. For example:
TIMELOCK(10,160,320,3000)
The two previous examples can be combined as follows:
TIMELOCK(10,160,320,4500)
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|