- Article Type: General
- Product: Aleph
- Product Version: 16.02
I find that after running p_manage_02 the UTIL-G-2 last-acc-number counter is lower than it was before running the job. Why would that be?
When a heading is updated, the system does *not* update the existing Z01 record but instead deletes its Z02 records (the numbers of the BIB records which contain the heading) and creates a new Z01 with the Z02's attached to *it*.
Each update will result in 2 Z01's where there was previously 1. (In building an index display Z01s which have no Z02s attached are ignored -- unless they have been created from authority records.)
The p_manage_15 job physically deletes Z01s which have no Z02s and are not connected to an authority record, but these "holes" are ignored by the counter, which always continues upward and never reuses any old numbers.
When run with the "rebuild entire" option, p_manage_02 drops/recreates the Z01 from scratch. Not only are the non-authority Z01s which have no Z02s removed, but any Z01s which have come from authority records and have been replaced are also deleted and not replaced. Thus, the post-p_manage_02 count is usually lower.
[KEYWORDS: p-manage-15 manage-15 manage_15 p-manage-02 manage-02 manage_02]
p_manage_02, UTIL G/2, last-acc-number
- Article last edited: 10/8/2013