RECLOCKO parameter: Difference between revisions
Jump to navigation
Jump to search
m (→Description) |
mNo edit summary |
||
| Line 30: | Line 30: | ||
<tr> | <tr> | ||
<td>X'04'</td> | <td>X'04'</td> | ||
<td>Maintain extra information in the record locking table. This information is provided in message MSIR.1056 or MSIR.1057, following MSIR.1055, which is issued after a record locking conflict (depending on the X'01' and X'02' bits of <var>RECLOCKO</var>) and can be useful in determining the cause of a record locking conflict. The extra information collected by setting this bit is also available in <var>[[RecordLockingConflict_class|RecordLockingConflict]]</var> objects. | <td><p class="note"><b>Note:</b> This setting is ignored as of version 7.5 of <var class="product">Model 204</var>. The information that follows here and the comments in the "Usage notes," below, is relevant only to Sirius customers who have not upgraded to <var class="product">Model 204</var> V7.5. </p> | ||
<p>Maintain extra information in the record locking table. This information is provided in message MSIR.1056 or MSIR.1057, following MSIR.1055, which is issued after a record locking conflict (depending on the X'01' and X'02' bits of <var>RECLOCKO</var>) and can be useful in determining the cause of a record locking conflict. The extra information collected by setting this bit is also available in <var>[[RecordLockingConflict_class|RecordLockingConflict]]</var> objects. </p> | |||
<p> | <p> | ||
Setting this bit increases the record locking table space requirements. See the usage notes below for more information.</p></td> | Setting this bit increases the record locking table space requirements. See the usage notes below for more information.</p></td> | ||
| Line 40: | Line 42: | ||
<li>The default value for <var>RECLOCKO</var> is X'03', which means that all record locking conflicts will result in <code>MSIR.1055</code> messages being issued to provide information about any record locking conflict. Since record locking conflicts should be relatively rare, there would seem to be little cost to always issuing these messages. | <li>The default value for <var>RECLOCKO</var> is X'03', which means that all record locking conflicts will result in <code>MSIR.1055</code> messages being issued to provide information about any record locking conflict. Since record locking conflicts should be relatively rare, there would seem to be little cost to always issuing these messages. | ||
<li>Setting <var>RECLOCKO</var> to X'04' increases recording locking table space requirements, so it should probably be accompanied by an increase in <var>LRETBL</var>. While a 33% increase in table usage is theoretically possible, the actual increase would probably be significantly less than that, more on the order of 5% to 10%. Since the record locking table is in 64-bit storage, the cost of an increase in <var>LRETBL</var> is an increase in 64-bit storage usage, which should not affect the availability of 31-bit storage. | <li><p class="note"><b>Note:</b> The X'04' setting of RECLOCKO is ignored as of version 7.5 of <var class="product">Model 204</var>. The information in the comments below is relevant only to Sirius customers who have not upgraded to <var class="product">Model 204</var> V7.5: </p> | ||
<ul> | |||
<li>Setting <var>RECLOCKO</var> to X'04' increases recording locking table space requirements, so it should probably be accompanied by an increase in <var>[[LRETBL parameter|LRETBL]]</var>. While a 33% increase in table usage is theoretically possible, the actual increase would probably be significantly less than that, more on the order of 5% to 10%. Since the record locking table is in 64-bit storage, the cost of an increase in <var>LRETBL</var> is an increase in 64-bit storage usage, which should not affect the availability of 31-bit storage. | |||
<li>If <code>RECLOCKO X'04'</code> is set and the conflict is with a single record or recordset lock, message MSIR.1056 is issued after an <code>MSIR.1055</code>. MSIR.1056 indicates whether the lock being conflicted with is a record or a recordset, whether it is locked share or exclusive, the time the lock was originally obtained, and the user number of the user that originally obtained the lock. The latter could be different from the current user that holds the lock in the case of session objects. The time the lock was obtained can be used to determine what request was running when the record was locked. | <li>If <code>RECLOCKO X'04'</code> is set and the conflict is with a single record or recordset lock, message MSIR.1056 is issued after an <code>MSIR.1055</code>. MSIR.1056 indicates whether the lock being conflicted with is a record or a recordset, whether it is locked share or exclusive, the time the lock was originally obtained, and the user number of the user that originally obtained the lock. The latter could be different from the current user that holds the lock in the case of session objects. The time the lock was obtained can be used to determine what request was running when the record was locked. | ||
| Line 46: | Line 51: | ||
<li>If <code>RECLOCKO X'04'</code> is set and the conflict is with a pending update lock, message MSIR.1056 is issued after an MSIR.1055, and it indicates that the conflict is with an exclusive pending update lock (pending update locks are always exclusive). A pending update lock is held by <var class="product">Model 204</var> for all updated records in TBO files so that users cannot see the partially updated record and so that no other user can update the record until the transaction is committed or backed out. | <li>If <code>RECLOCKO X'04'</code> is set and the conflict is with a pending update lock, message MSIR.1056 is issued after an MSIR.1055, and it indicates that the conflict is with an exclusive pending update lock (pending update locks are always exclusive). A pending update lock is held by <var class="product">Model 204</var> for all updated records in TBO files so that users cannot see the partially updated record and so that no other user can update the record until the transaction is committed or backed out. | ||
<li>If the <code>X'04'</code> bit is off, then neither MSIR.1056 nor MSIR.1057 is issued, whether <code>X'01'</code> or <code>X'02'</code> is on or not. | <li>If the <code>X'04'</code> bit is off, then neither MSIR.1056 nor MSIR.1057 is issued, whether <code>X'01'</code> or <code>X'02'</code> is on or not. | ||
</ul> | </ul> | ||
<li>If both the <code>X'01'</code> and <code>X'02'</code> bits are off, neither message MSIR.1055, MSIR.1056, nor MSIR.1057 is issued. | |||
</ul> | </ul> | ||
[[Category:System parameters]] | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Revision as of 21:10, 18 December 2013
Record locking options
Summary
- Default value
- X'03'
- Parameter type
- System
- Where set
- User 0 CCAIN parameters
- Related products
- All
- Introduced
- Sirius Mods 8.1
Description
This parameter enhances Model 204 record lock conflict handling. The meaning of the bits are:
| X'01' | Issue message MSIR.1055 for any untrapped record locking conflicts. MSIR.1055 provides information about the user that holds the lock and the file and record number for which there's a conflict. In addition, if the X'04' bit of RECLOCKO is set, MSIR.1055 would be followed by an MSIR.1056 or MSIR.1057 message that provides further information about the lock conflict.
A record locking conflict is considered untrapped if it is not inside a Try block with a |
| X'02' | Issue message MSIR.1055 for any trapped record locking conflicts. MSIR.1055 provides information about the user that holds the lock and the file and record number for which there's a conflict. In addition, if the X'04' bit of RECLOCKO is set, MSIR.1055 would be followed by an MSIR.1056 or MSIR.1057 message that provides further information about the lock conflict.
A record locking conflict is considered trapped if it is inside a Try block with a |
| X'04' | Note: This setting is ignored as of version 7.5 of Model 204. The information that follows here and the comments in the "Usage notes," below, is relevant only to Sirius customers who have not upgraded to Model 204 V7.5. Maintain extra information in the record locking table. This information is provided in message MSIR.1056 or MSIR.1057, following MSIR.1055, which is issued after a record locking conflict (depending on the X'01' and X'02' bits of RECLOCKO) and can be useful in determining the cause of a record locking conflict. The extra information collected by setting this bit is also available in RecordLockingConflict objects. Setting this bit increases the record locking table space requirements. See the usage notes below for more information. |
Usage notes
- The default value for RECLOCKO is X'03', which means that all record locking conflicts will result in
MSIR.1055messages being issued to provide information about any record locking conflict. Since record locking conflicts should be relatively rare, there would seem to be little cost to always issuing these messages. Note: The X'04' setting of RECLOCKO is ignored as of version 7.5 of Model 204. The information in the comments below is relevant only to Sirius customers who have not upgraded to Model 204 V7.5:
- Setting RECLOCKO to X'04' increases recording locking table space requirements, so it should probably be accompanied by an increase in LRETBL. While a 33% increase in table usage is theoretically possible, the actual increase would probably be significantly less than that, more on the order of 5% to 10%. Since the record locking table is in 64-bit storage, the cost of an increase in LRETBL is an increase in 64-bit storage usage, which should not affect the availability of 31-bit storage.
- If
RECLOCKO X'04'is set and the conflict is with a single record or recordset lock, message MSIR.1056 is issued after anMSIR.1055. MSIR.1056 indicates whether the lock being conflicted with is a record or a recordset, whether it is locked share or exclusive, the time the lock was originally obtained, and the user number of the user that originally obtained the lock. The latter could be different from the current user that holds the lock in the case of session objects. The time the lock was obtained can be used to determine what request was running when the record was locked. - If
RECLOCKO X'04'is set and the conflict is with a pending update lock, message MSIR.1056 is issued after an MSIR.1055, and it indicates that the conflict is with an exclusive pending update lock (pending update locks are always exclusive). A pending update lock is held by Model 204 for all updated records in TBO files so that users cannot see the partially updated record and so that no other user can update the record until the transaction is committed or backed out. - If the
X'04'bit is off, then neither MSIR.1056 nor MSIR.1057 is issued, whetherX'01'orX'02'is on or not.
- If both the
X'01'andX'02'bits are off, neither message MSIR.1055, MSIR.1056, nor MSIR.1057 is issued.