Alternating valid/invalid due dates (1 hr. vs. 1 month) for certain hourly items
- Article Type: General
- Product: Aleph
- Product Version: 18.01
Description:
One of the colleges, ABC50 is getting bogus due dates for at least one of their items on checkout. The items are their laptops which should go out for one day (current day) only. Every other time we check out a test item it will check out incorrectly, i.e., one check out and it will be do today; check it in and check it out again it will be checked out as if it were a 3 week loan (incorrectly anyway).
The item status type is 21. The patron type is 02 (staff). Below is a copy of the z36H table for a set of the tests we did this morning. As you can see, every other due date is for January. It should always be for today.
I reviewed the closed day table -- it looks good, rebuilt due dates, and had them restart their clients. The "Active due date" table in the client has the correct due date for this item type. We have seen some other problems with the due date, but this one is the only one we have been able to replicate.
This is on our R18 current production.
The sql statement used to get this list is:
select Z36H_LOAN_DATE, Z36H_DUE_DATE, Z36H_ITEM_STATUS, Z36H_BOR_STATUs from z36h where Z36H_REC_KEY like '%1588394%' and Z36H_LOAN_DATE = '20101207';
date
20101207 20101207 21 02
20101207 20110103 21 02
20101207 20101207 21 02
20101207 20110103 21 02
20101207 20101207 21 02
20101207 20110103 21 02
20101207 20101207 21 02
Resolution:
Restarting the pc_server corrected the problem.
- Article last edited: 10/8/2013