LRETBL and (deprecated) LRECLTBL parameters: Difference between revisions
m (Dme moved page LRETBL parameter to LRETBL (and deprecated LRECLTBL) parameters) |
No edit summary |
||
| Line 1: | Line 1: | ||
The <var>LRECLTBL</var> parameter is an alias for <var>LRETBL</var>. | |||
<var>LRECLTBL</var> is deprecated — use <var>LRETBL</var> instead. | |||
==Summary== | ==Summary== | ||
<dl> | <dl> | ||
Revision as of 16:20, 21 March 2013
The LRECLTBL parameter is an alias for LRETBL. LRECLTBL is deprecated — use LRETBL instead.
Summary
- Default value
- 200
- Parameter type
- System
- Where set
- On User 0's parameter line
- Related products
- All
- Introduced
- Model 204 V6.1 or earlier
Description
The length in bytes of each user's part of the record enqueuing table
LRETBL is multiplied by the value of the NUSERS parameter to get the size of the record enqueuing table. The resolution of this formula-(NUSERS * LRETBL) + ((NFILES +2) * 32) + 88-is forced to be at least 600, and its maximum is 231 - 1.
Space in the record enqueuing table is flexibly shared by the users: an individual user is not restricted to LRETBL bytes of the record enqueuing table (except in batch mode, when NUSERS=1).
The record enqueuing table contains control information necessary to detect conflicts between users who are trying to update records simultaneously. The amount of space in this table needed by a request is roughly proportional to the number of lists and FIND statements in the request. Each FIND or list requires about 46 bytes per file for files less than or equal to 300,000 records. The space required increases at the rate of 2.25 bytes per segment.