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

Description:
It's my understanding that the new ue_01 calls the program to sort long headings. We have recently rebuilt the browse index using parallel indexing. When we switched the browse indexes to the indexing library, we also updated the last-acc-number and the last-long-acc-number counters of the actual library. I see that the last-acc-number has since been updated but not the last-long-acc-number. It is still at 36770366 while last-acc-number is at 36878901.

When are the long headings going to be sorted?

Resolution:
The last-long-acc-number is updated by p_manage_17 only.

In v16-up, p_manage_17 needs to run only after p_manage_02 is run. After that, ue_01 takes over the updating of long headings. ue_01 calls update_acc which calls update_long_heading, which updates the long headings but does not update the last-long-acc-number.

Thus, when you run p_manage_17 after running p_manage_02, you should check the last-long-acc-number to confirm that p_manage_17 has run correctly.

But when ue_01 starts doing the updating, the last-long-acc-number is no longer valid and you should ignore it.

KEYWORDS: UTIL-G-2 p-manage-17 manage-17 manage_17 p-manage-02 manage-02 manage_02

• Article last edited: 10/8/2013