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

    Circ: "Unable to find available slot"

    • Article Type: General
    • Product: Aleph
    • Product Version: 18 and up

    Description


    In the Audiovidéothéque sub-library (AV) an item was in the 'Reserve' collection and had a item status 03 (Reserve).
    The item information was then changed, the item was removed from the 'Reserve' collection with no new collection attributed, and the item status was changed to 01 - Regular loan.

    When one tries to lend out this item remote service error (c0441 53): "Unable to find available slot" is displayed.
     



    Resolution



    A Z321 record is created for each item (Z30) that is an "advance booking" copy, indicating the date until which it is a reserved copy. “Advance booking” item statuses are defined in xxx50/tab/tab43.

    The pc_cir_c0441 loan program checks to see if there's a z321 record for the item. If so, it calls the pc_cir_short_loan program.

    pc_cir_short_loan checks to see if the z320_end_date of the z320 record pointed to by the z321_item_number (the advance booking item number) is greater than today's date. If not, it issues error 53 ("Unable to find available slot").

    The z321.pdq document says:

    " Both tables, Z320 and Z321, are generated by running
    the “Open Advance Booking Schedule” (p_cir_60) batch procedure. This service is
    available from the Advance Booking option of the Services menu in the Circulation
    module. It is recommended to run the “Open Advance Booking Schedule” function
    once a week, in order to open up a new schedule for the next week that will be
    displayed for patron requests.
    Z320 and Z321 are deleted by running the “Delete Advance Booking Schedule”
    (p_cir_61) batch procedure. This service is available from the Advance Booking
    option of the Services menu in the Circulation module.
    It is recommended to run this function once a week, in order to delete the previous
    week's schedule. "

    Running "Delete Advance Booking Schedule (cir-61)" followed by "Open Advance Booking Schedule (cir-60)" corrected this problem.

     

    • Article last edited: 15-Aug-2016