Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    p_file_20 not creating a 01 barcode entry in z308

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

    Description:
    When we ran a patron load (PLIF) which does not have the entry for a patron barcode at version 18, file-20 would create a z308 entry for the 01 key-type which filled in the barcode with the patron_id (z308_id). At a later time, we would run a second load which had the patron's barcode which would then overlay the z308 entry.

    Currently at version 20 when we run the patron load without the barcode, the z308 01 key-type row is not getting created, which is causing problems when the second load tries to add the barcode to the record, because it doesn't want to overlay an entry which doesn't exist and creates a new z308 row for the barcode which does not have a z308_id entry:

    Error (b_file_20_chk_edit_record) : failed to find z308-key-type 01 for cur-id XXXXX

    What has changed with the file-20 at version 20 that is preventing the creation of the z308 row?

    Resolution:
    My analysis showed that the b_file_20_chk_edit_record program checks existing records for a Z308-KEY-DATA value matching the incoming record. In the case where the incoming record has null or blank Z308-KEY-DATA -- as the system-produced z308 type 01 *always* does -- and where there are defective Z308 records which actual null or blank Z308-KEY-DATA, the program matches on these and fails to create a z308 type '01'.

    The following defective records were found in the site's $usr_library:

    abc50@APROD20> select z303_name from z303 where z303_rec_key = ' ';
    **** Hit return to continue ****

    Z303_NAME
    ------------
    Law ILL Unit


    abc50@APROD20> select z308_rec_key from z308 where z308_id = ' ';
    **** Hit return to continue ****

    Z308_REC_KEY
    ---------------------------
    00
    01

    abc50@APROD20> select z308_rec_key from z308 where z308_id is null;
    **** Hit return to continue ****

    Z308_REC_KEY
    ---------------------------
    LEPH

    Similarly, the following defective z308's were found in usm50 on il-aleph07 203:

    usr00@ALEPH201> select z308_rec_key from z308 where z308_id is null;
    **** Hit return to continue ****

    Z308_REC_KEY
    ---------------------------
    00
    00 UNI50
    01
    01 UNI50

    4 rows selected.

    usr00@ALEPH201> select z303_rec_key from z303 where z303_rec_key is null;
    no rows selected


    The site found they were unable to bring the "Law ILL Unit" patron -- with blank as the z303_rec_key! -- up in the GUI (and, in fact, a replacement z303 had already been created for this patron). Therefore, I had them delete the three defective z308 records and the one defective z303.

    And on il-aleph07 usr00 I deleted the two z308 records with null Z308-KEY-DATA (and Z308-USER-LIBRARY), leaving the two z308's with "UNI50" as the Z308-USER-LIBRARY.

    ***At both the site and on il-aleph07, after deleting these defective records: p_file_20 then created a z308 type '01' record when the input file lacked one.***

    KB 16384-37074 describes v20 rep_change 3520 which prevents z308s with blank z308_id's from being created.


    • Article last edited: 10/8/2013