Why don't records sent thru p_manage_40 end up in the Z07P table

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Article Type: General
Product: Aleph
Product Version: 20, 21, 22, 23

Description:
I re-indexed a number of records yesterday by sending the records numbers to the Z07 table using p_manage_40. I expected that this would also send the record numbers to the Z07P table.

When I checked everything today, the records were re-indexed in Aleph, but the record numbers were never sent to the Z07P table.

Is this a bug? The way things are supposed to work? Or was this just something that was missed when the publishing platform was developed?

If I use UTIL-F-1-13 to do an immediate update of a record, it ends up in the Z07P, this is one reason I expected the same behavior using p_manage_40.

Resolution:
The ue_01_a program which processes the z07 indexing requests writes a z07p only if the compare_docx program finds that the record is different after a test execution of fix_doc using the lines with the label "UE_01" in tab_fix.

The ue_01_z0102_index program writes a z07p when the bib record belongs to a base specified in tab_base.eng with a "Y" in column 8 ("Use Z0102 for the logical base"). KB 25908 describes a case where starting ue_01_z0102 caused the desired generation of z07p records to occur.

The write_z07 program, which is called by the online programs, does an unconditional call of the update_z07p routine.

(Though at some sites it has been found that the z07p is written by the ue_01_z0102 process even when tab_publish, column 2, is empty), the site found that adding the bib library ("SYS01") as the base in column 2 and restarting ue_01, caused ue_01_z0102 to write z07p records.

Article last edited: 10/8/2013