Alex: Create MSIR.1083 page: description and response

2026-10-06T13:06:46Z

Create MSIR.1083 page: description and response

New page

{{Template:MSIR.1083 skeleton}}
<p>
The record locking table has been compacted (garbage collected), and this message reports the result. <var class="product">[[Model 204]]</var> compacts the table when it cannot satisfy a request for a record locking entry from the free space already available. Because compaction moves entries, it is performed with the subtasks stopped, so it briefly serializes the <var class="product">Model 204</var> run.
</p>
<p>
The substituted values are:
</p>
<table class="thJustBold">
<tr><th>freed bytes</th><td>The number of bytes recovered by the compaction.</td></tr>
<tr><th>RSXD</th><td>The number of bytes of the record set extension (RSXD) area that are in use after the compaction.</td></tr>
<tr><th>RETD</th><td>The number of bytes occupied by the record enqueue entry headers (RETD). This part of the table is not compactable.</td></tr>
</table>
<p>
<b>Response:</b> None required for an isolated occurrence; the message is informational and is written only to the audit trail. Frequent occurrences indicate that the record locking table is under pressure, and that the run is paying a recurring cost to reclaim space from it. In that case, consider increasing the <var>[[LRETBL parameter|LRETBL]]</var> parameter, which sets the length of the record locking table, and review applications that lock very large record sets. The <var>[[MSRES parameter|MSRES]]</var> parameter, which limits the number of set record entries per file, may also be relevant.
</p>
{{Template:MSIR.1083 footer}}

MSIR.1083 - Revision history

Alex: Create MSIR.1083 page: description and response