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 - plif import failing - "Unsupported action"

    p_file_20 - plif import failing - "Unsupported action"

    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 testing p_file_20/plif:

    The job is failing with the following errors in the log:

    Error (b_file_20_chk_edit_record) : Errors in Z304. Record No 000001
    Unsupported action
    Error (b_file_20_chk_edit_record) : Errors in Z305. Record No 000001
    Unsupported action

    Resolution:
    The first byte in each PLIF input record segment (USER, ID, ADDR, and BOR) is the xxxx-REC-ACTION. The legitimate values for ACTION are "I" (Insert), "A" (Add), and "D" (Delete). When the program finds that the xxx-REC-ACTION is not one of these values, it issues this error.

    This could be because you didn't understand the correct values for this byte, but, more commonly, it indicates that the input format has gotten off and there is, for instance, a blank where the program expects to find the ACTION.

    In such cases, you can use the util f/2/5/1 utility to check the structure/validity of the PLIF input file.

    Using util f/2/5/1 to look at the Address and BOR segments of this record 633 from the banner02.plif file, we see that both "ADDR-REC # 02" and "BOR-REC # 01" have a blank ACTION:

    ADDR-REC # 01
    ACTION...... A
    SEQUENCE.... 01
    TYPE........ 01
    ADDR-1...... CLEMATIS,ST. LOUIS
    ADDR-2...... #1 PRIVATE ROAD
    ADDR-3...... BEHARRY TRACE
    ADDR-4...... D?BADIE
    ADDR-5...... TRINIDAD AND TOBAGO
    ZIP......... 1868
    PHONE....... 868 7669999
    PHONE-2.....
    PHONE-3.....
    PHONE-4.....
    E-MAIL...... 810000224@mysta.abc.edu
    START-DATE.. 0000000
    STOP-DATE... 00000000
    SMS-NUMBER.. 0

    ADDR-REC # 02
    ACTION...... <---------------- blank
    SEQUENCE.... A0
    TYPE........ 20
    ADDR-1...... 2CLEMATIS,ST. LOUIS
    ADDR-2...... #1PRIVATE ROAD
    ADDR-3...... BEHARRY TRACE
    ADDR-4...... D?BADIE
    ADDR-5...... TRINIDAD AND TOBAGO
    ZIP.........
    PHONE....... 868 7669999
    PHONE-2.....
    PHONE-3.....
    PHONE-4.....
    E-MAIL...... 810000224@mysta.abc.edu
    START-DATE.. 000000
    STOP-DATE... 00000000
    SMS-NUMBER.. 00

    Display Bor (CR cont, Q quit, S skip) :

    BOR-REC # 01
    ACTION...... <------------------- blank
    SUB-LIBRARY. ASTA
    TYPE........ 50
    STATUS...... 01
    EXPIRY-DATE. 60201105
    REG-DATE.... 31201009

    My intuition is that this problem has to do with the "D?BADIE" in the first Address. I believe that the incorrect processing of this diacritic has caused the following bytes to be shifted one byte to the right.

    Fix the input file and try again.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • p_file_20 - Patron Loader does not update Address records
      • p_file_20 (for LDAP): Z308-VERIFICATION can not be empty when TAB-BOR-ID-VER ...
    • 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