z36-recall-date, cir-13 and the UPDATE-RECALL-DATE switch

Question

Is it true that z36-recall-date and z36-recall-due-date can only be set by a staff-placed recall or by Recall Items on Loan (cir-13)?
Although very few staff-placed recalls have been entered and, the only time cir-13 was run, update_file = N was set, a SQL query reveals that there are 400 z36 (Loans) records with non-zero z36-recall-dates and about 1500 z37 (Requests) records.

Answer

It is true if xxx50/tab/tab100 UPDATE-RECALL-DATE parameter = N.
When an item is loaned and there is a matching, open hold request:
N = recall of a loaned item is triggered only by cir-13 (updating z36-recall-date and z36-recall-due-date)
Y = item loan can trigger recall (z36-recall-date and z36-recall-due-date are automatically set at time of loan if there is a matching "O" request)

Additional Information

* The only other way z36-recall...date fields can be updated is via util f/2/20 (Update Loan Record).
* Please note: cir-13 does nothing if z36_recall_date is non-zero. In that case (loaned with existing recall), there be no need for a recall because the user got the recall-adjusted Due Date at the time of the loan.

Category: Circulation (500)

Subject: Hold requests (500)

• Article last edited: 10/8/2013