RECLOCKO parameter
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.
Catch RecordLockingConflict clause and if there is no On Record Locking Conflict or On Find Conflict that would be driven by the conflict. |
| 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.
Catch RecordLockingConflict clause or if there is a On Record Locking Conflict or On Find Conflict that would be driven by the conflict. |
| X'04' | 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.1055 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.
- Setting RECLOCKO X'04' increases recording locking table space requirements so should probably be accompanied by an increase in LRETBL. While a 33% increase in table usage is theoretically possibly, the actual increase would probably be significant 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 and shouldn't affect the availability of 31-bit storage.