Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. p_file_20 doesn't update Pincode / Barcode Verification

    p_file_20 doesn't update Pincode / Barcode Verification

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    We are trying to load patrons for out academic libraries for the Summer and Fall semesters. The Pincode and Barcode Verification are not loading correctly. They should be set to the student's last name.

    When we look at the input file with the "Display PLIF Records from Sequential File" (Util F 2 5 1), the "Verification" record shows the correct Last Name, but when the file is loaded, the students end up with somethign completely different.

    Resolution:
    The ABC50 PLIF input file contains one ID segment for the first patron (Ridman). Note that the "TYPE" is 03:

    USER-KEY-REC # 01
    ACTION............. A
    KEY................
    TYPE............. 03
    LOGIN............ ABU1000169
    VERIFICATION....... RIDMAN
    VERIFICATION-TYPE.. 00
    STATUS............. AC
    ENCRYPTION......... Y

    ABU1000169 matches on ABU504373.

    The following SQL shows the current state of the ABU504373 z308's:


    sys00@ALEPH1> select * from z308 where z308_id = 'ABU504373';
    **** Hit return to continue ****

    Z308_REC_KEY Z308_VERIFICATION Z3 Z308_ID Z3 Z
    --------------------------- ---------------------------------------- -- ------------ -- -
    00ABU504373 P5496 00 ABU504373 AC N
    03ABU1000169 RIDMAN 00 ABU504373 AC N
    01ABUB12036 P14811 00 ABU504373 AC N

    As you can see the z308_verification for the type 03 record *has* been set to "RIDMAN".

    The verification for the type 00 (system #) and the type 01 (barcode) were *not* updated.

    You could update the type 01 by including a USER-KEY-REC type 01 in the PLIF load with the desired VERIFICATION.

    You can not update the type 00 via the PLIF, but I wouldn't think it would be necessary since I wouldn't think that this system # would be used as login....

    Another possibility, if the type 03's have been updated with the desired verification, would be to use SQL to update the type 01 z308_verification (and type 00?) with the type 03 z308_verification.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • p_file_20 creates duplicate patron records; barcode as match-point
      • p_file_20 error: z305_expiry_date is wrong
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 18.01
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved