p_manage_18 [/p_manage_31] doesn't trigger update of bib headings

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

Description:
p_manage_18 doesn't trigger any update of the bib headings. We find that it isn't writing any z105s and the ue_01, in processing the z07 produced by p_manage_18, is not either.

(We ran p_manage_40 for *all* the MGU12 authority records to try and get them to generate z105s which would trigger ue_08 processing for them in the MGU01 library. This didn't work. No z105s were produced.)

Resolution:
Corrected by 15.2 rep_change 1256, by 15.5 rep_change 2172, and by rep_ver in version 16-up.

*But* in order for this to work you need to have ue_11 stopped when p_manage_18 is running. (The reason for this is that ue_11 can run faster in processing the z105s than the authority ue_01 runs in processing the z07s. Thus, when the bib ue_08 goes to link the new heading to the authority library, it may fail because the authority z01 may not yet be written.) (For a complete description of the aut-bib update sequence, see SKB 4100.).

Thus, the correct sequence is the following:

1. Make sure the xxx10 ue_01 is running and the $z105 library ue_11 is stopped..

2. Run p_manage_18 in the xxx10, specifying Indexing = FULL..

3. Use this SQL to make sure that the z07s have been processed: select count(*) from xxx10.z07.

4. Start the $z105_library ue_11. (And make sure that the ue_08 in the xxx01 bib library is also running.).

Note: the p_manage_31 job, which also updates authority records, does write z105 records, but it's possible that it could have the problem of the bib Z01 being updated before the authority Z01. If so, you will want to follow the above procedures for it as well.....

Thanks to Christine Moulen at MIT and Pat Riva and Jane Aitkens at McGill for their work in solving this problem.