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. Missing switches in distributed tab100

    Missing switches in distributed tab100

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

    Description:
    Why don't the USMnn tab100 tables include settings for all of the parameters shown in the tab100 header?

    Resolution:
    As can be seen in the tab100 header, there are a total of 166 tab100 parameters. I find that the usm50 tab100 includes only 80 of these as actual settings with a value specified (in the form "XXXXX=N") in the body of the table. And that your abc50 tab100 has these same 80 actual settings. The value of each of the other 86 parameters is defaulting to the "Default" value shown in the header.

    I believe that these 80 settings have been chosen because they are the ones which customers most commonly want to change, and that the other 86 are not included because customers only rarely want to change them. In addition, some parameters may apply to a particular library type (such as ILL) and are not relevant for the ADM library, for instance.

    If a parameter appears in the tab100 header but does not have an actual XXXXXX=N setting in the body of the table, an XXXXXX= setting can be freely added to the body. The only exceptions are the following, which indicate "tab100 of library: No" in their header entries (-- these parameters must be specified in the $alephe_tab/tab100 only):

    FRENCH-AUT
    USER-HOME-PERMISSION
    PLAIN-ONLY
    ALPHA-NUMERIC-PASSWORD
    FIRST-LOGIN-PASS-CHANGE
    MINIMUM-PASSWORD-LENGTH
    PASSWORD-CHANGE-PERIOD
    PASSWORD-FAIL-BLOCK
    PASSWORD-NO-USE-PERIOD
    PW-EXPIRY-WARNING
    SUPPRESS-DECIMAL-DISP
    PDS-AWARE
    PDS-KEY-TYPE
    XSS-VALIDATION
    CONSORTIAL-HOLD-REQUEST

    Thus, there are 71 rarely-changed parameters which can be included in the body of the xxx50 tab100 body but are not. I, personally, feel that including these would make it harder to locate a particular, *more*-commonly-changed parameter.

    A customer can see all the possible parameters in the header and, if a particular parmeter is not included below, can add it. I think that leaving this as is is preferable.


    • Article last edited: 12/4/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Missing subfield data from p_print_03 marc xml format output
      • Missing Z324s; "io_z105 - table doesn't exist in database or tab_io_remote ... "
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 20
      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