GUI Acq times out updating order with more than 800 arrival records

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

Description:
A user reported a problem where the GUI timed out ("Server failed to execute request after 200 seconds") when she was trying to attach an order to an invoice. As I was experimenting, I found that you can't even update the order record (such as adding a note) because the client times out.

The order is a closed order that had been used for publishing fees for theses and dissertations and has 964 arrival records linked to it, and lots of previous invoices.

The current invoice is a credit, which is why it's being applied to a closed order. The invoice they're trying to attach it to is PPROQUEST/XX12345678. In the database, I can see that it created a z75 line item record, but not a z601 INV record.

Resolution:
There are at least three different programs involved in the order update which read the z78 (arrival records):

./com/correct_z68_status.cbl
./pc_acq_c0506.cbl
./pc_acq_c0520.cbl

Using the following SQL to locate orders with large numbers of arrival records:

SQL> select substr (z78_rec_key,1,14) from z78 group by substr (z78_rec_key,1,14) having count(*) > 800 order by count(*) desc;

and testing the update of these orders, the site found that three orders with 884, 963, and 964 arrival records timed out.

An order with 737 arrival records could be updated successfully.

There is no hard and fast number. (Timeout is due not only to Aleph but also to PC and server constraints.)

We suggested to this site that as the order nears 800 arrivals a new order be created.

• Article last edited: 10/8/2013