If an account
statement is set to flag back to the account record – to update last statement
date, statement page number or Credit Control flag – then the system requires
exclusive access to the sales accounts file when doing a statement run.
This new option allows the ability to use record locking rather than file locking for statement production. This allows the system to process a statement for all required accounts but skipping any that are exclusively locked by another operator and reports at the end of the procedure if any accounts not processed. Missed accounts can be reprocessed later by running the statement on a selective basis (perhaps using the statement date not equal to ‘today’).
A new parameter has been added to the statement design
to omit file locks for the statement print.To update the Document Design select Installation from the main menu followed by the Application Manager option and then Document Design Manager. Select the Sales Ledger application and the Statements document type.Select the document to be updated and then, once the document mask is
displayed, select the Parameters option
on the main toolbar – the new option is available on the first parameter
screen.
Omit File
Locks – set
to omit exclusive file locks when the statement definition is run but to apply
record locks to the accounts.
File / Record Locking
In processing a statement the system applies U-usage locks to the accounts and transaction files. As each account is processed the system applies a U lock on the account record and, for the update, places a W-wait lock on the transaction file whilst updating the account record before releasing the W lock and then releasing the U lock on the account record. The system then repeats this process for each account to be processed. Only accounts which are exclusively locked by another process will be omitted.
Article ID: 1905
Created On: Fri, Oct 26, 2012 at 11:28 AM
Last Updated On: Mon, Jun 19, 2023 at 3:23 PM
Online URL: https://kb.datafile.co.uk/article/improvements-to-statement-print-locking-1905.html