• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
Rush recall letters are not being generated by p_cir_13 and I cannot figure out why.
Here is an example, this title had a rush recall placed on it yesterday:

02 z36_rec_key \
03 doc_number ................006173569
03 item_sequence .............000010
02 z36_id ......................344344425
...
02 z36_loan_date ...............20100427
...
02 z36_due_date ................20100507
...
02 z36_letter_number ...........00
02 z36_letter_date .............00000000
...
02 z36_recall_date .............20100427
02 z36_recall_due_date .........20100507
...
02 z36_recall_type .............02

cir_13 is a nightly batch job, the output for this library, pt_hold_bb.pt_hold_bb, contains no letter to this patron.
Checking the knowledge base I saw a reference to tab100/ONLINE-RECALL, we have it set to Y.

There's a z37 record, with a status of A:

02 z37_rec_key \
03 doc_number ..................006173569
03 item_sequence ...............000010
03 sequence ....................0001
02 z37_id ........................110680329
02 z37_status ....................A

Resolution:
Possible ue_06 interference with p_cir_13 is described in KB 8192-9271. Since the z37_status is "A" (rather than "W") ue_06 is not involved in this case.

As described in KB 8192-919, when you are using the ONLINE-RECALL button, "Recall button is ONLY to generate a Recall letter and update the Z36 Recall fields".

Thus, the recall letter is produced immediately. Since the z36_recall_date was already updated, p_cir_13 does *not* produce a recall letter for this loan.

[From site:] I think this SI can be closed. It turns out there is a problem generally with emailing circ notices at Baruch, so it is a local IT issue. When the rush recall was placed the system attempted to generate the notice immediately, but the email server didn't respond (which I think is an issue w/my gui setup.)

• Article last edited: 10/8/2013