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

    Making due date changes take effect immediately

    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23

    Desired Outcome Goal:
    Is there a way of making due date changes take effect immediately?
    Changes made in ./xxx50/tabtab16 (to due dates) and ./xxx50/tab/tab17 (calendar) only take effect overnight.


    The current due dates for each loan period, based on ./xxx50/tab/tab16 and ./xxx50/tab/tab17, are stored in the Oracle table z301.
    The system uses this z301 to assign the due dates. The first circulation transaction each day recreates the z301 with the correct values for that day.

    It is possible to make these changes take effect immediately

    A) By dropping/recreating the z301 table:

    1) dlib xxx50 <where xxx50 is your ADM library>
    2) util a / 17 / 1
    Enter library name : xxx50
    You asked to delete from library xxx50
    Enter table name to Drop & Create (all/table-name): z301

    This will update the z301 to contain the new due dates based on the current tab16 and tab17.  (Note:  The z301 will be populated when the first circ transaction is performed in the GUI.)

    When util a/17/1 has been run for the z301 in xxx50, the xxx50 $data_scratch should show a file like this:
    -rw-rw-r-- 1 aleph exlibris 149 Nov 4 22:51 create_ora_tables_z301;


    B) By running service "Rebuild Due Dates (cir-01)" in your ADM library; it will do the same as the above.

    Additional Information

    NOTE 1) when a change is made to tab16 which affects the due-date, that is, changes to:

    col. 2 (item status)
    col. 4 (patron status)
    col. 5 (date operator)
    col. 6 (date parameter)
    col. 8 (hour operator)
    col. 9 (hour parameter)
    col. 15 (date operator - request)
    col. 16 (date parameter - request)
    col. 17 (hour operator - request)
    col. 18 (hour parameter - request)
    col. 27 (Adjust Due Date and Hour)

    the xxx50 z301 table needs to be recreated.

    NOTE 2) As described in KB 16384-32529 ("Fines for Closing Days"), when util a/17/1 has been run for the z301 in xxx50, the xxx50 $data_scratch should show a file like this:

    -rw-rw-r-- 1 aleph exlibris 149 Nov 4 22:51 create_ora_tables_z301

    The presence of this create_ora_tables_z301 file confirms that you did util a/17/1 for the correct file in the correct library.

    NOTE 3): non-due-date changes to tab16 are *not* stored in the z301; they require restart of the pc_server only to take effect.

    As noted in KB 16384-32194 ("Change to tab16 not taking effect"), some columns, such as, column 27 ("Adjust Due Date and Hour") require both that the z301 be recreated and that the pc_server be restarted.

    Category: Circulation (500)

    Subject: Table configuration (500)

    • Article last edited: 7/10/2014