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

    Service pack reports successful, but logs have error: "Command not found"

     

    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

     

    Description:
    We ran the service_pack 3136-3723. It says it was successful. Now we are running the util_sp > 

    5. Run SP Utility > 
    7. Run Automatic Implementation Notes > 
    2. Run ALL Implementation Notes 

    and each of the logs in the /exlibris/aleph/a20_1/service_pack/3136-3723/ain/logs/log.20120531.091338/ directory show “xxx01: Command not found” :

    ...logs/log.20120531.091338>grep 'not found' *
    3137.log:xxx01: Command not found.
    3175.log:xxx01: Command not found.
    <etc.>

     (“xxx01” appears here because it is, alphabetically, the first library in the list of libraries.)

    But why is the AIN utility looking at a library list when it is expecting a command?

     

    Resolution:
    The source of the problem was incorrect configuration, in $alephe_root/sp.ain.config, "setenv uk_libraries" .

    The following note have been added to section 8.5 "Updating Configuration (Util SP 5/8)": 
    Note: When updating the Libraries to be handled parameter with option E – edit the list using VI – use the following format: 
    setenv uk_libraries "loc10 tst01 tst10 tst40 tst50 tst60" 
    Do not remove the text, "setenv uk_libraries". 
    Enter the space delimited list of libraries within the quotation marks.

     

     


    • Article last edited: 12-Mar-2016
    • Was this article helpful?