Description

Though most of our xxx01 bib records have z00r entries, some records, as shown by the following SQL, do not. 

  SQL> select z00_doc_number from z00 minus select z00r_doc_number from z00r;

Why might this be?

Resolution

One cause can be that the bib record is logically deleted (that is, it has a "DEL Y" field).  *Usually* what happens in the case of logical deletion is that the z00r has the same fields as the bib stub record (that is, LDR, 008, CAT, etc.), but it seems that in some cases the z00r's are not written.  (Since the record is deleted, this shouldn't be an issue.)

But we have found that there are other cases where the the z00r's are missing even though the bib record has no "DEL Y" field.  The following SQL can be used to locate such cases:
 
SQL> select z00_doc_number from z00 minus select z00r_doc_number from z00r minus select z13_rec_key from z13 where z13_title is not null;

In a previous case we found that resending the (non-deleted) records to the server resulted in the expected z00r entries being generated.  They created a file like this:

   000123456ABC01
   000234567ABC01
   <etc.>

which they used as input to the manage-40 Service, which generated z07's which were processed by ue_01, generating proper index entries, including the z00r.
 

• Article last edited: 1-Nov-2017