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

    batch jobs run when incorrect parameters are supplied, ignore other parameters

    • Article Type: General
    • Product: Voyager
    • Product Version: 7.2.3

    Description:
    Bug Report Form for Issue 16384-16945

    Module(s): Batch jobs with optional parameters (patron extract, patron update, bursar transfer, marc export, bulk import, prebulk, GHC)
    Server platform(s) affected: Solaris/all
    PC OS (if applicable): n/a
    Browser & version (if applicable): n/a
    Release(s): reported in 7.2.1, 7.2.3; replicated in 8.1

    Expected results: If you make a mistake in the syntax of the optional parameters when running any of the batch jobs, the run should error out indicating that the command line had an incorrect parameter.

    Actual results: If you enter invalid data in the command line to run any of the batch jobs, the system runs using only the parameters supplied before the error and nothing after.

    Workflow implications: Depending on where the error is, you can affect quite a lot of data unintentionally.

    Replication steps:
    Take bursar transfer, for example:
    Find one patron with fines > $5, incurred before today’s date
    Find one patron with fines < $5, incurred before today’s date
    Find one patron with fines > $5, incurred today
    Run this command line: Pbursar -c/m1/voyager/ubgwccdb/sbin/bursar.cfg -p m5 -i2

    If run with the dash in front of the m parameter, this would transfer the first patron’s fines, but not the second or third (based on the –m, the second patron doesn’t have enough fines; based on the –i, the third patron hasn’t passed the interval for transfer). Run without the dash, it transfers fines for all three patrons.

    Other information: The above example is for bursar transfer, but the same thing appears to happen with all of the batch jobs that have optional parameters – if there’s a parameter the job can’t understand, it runs anyway, ignoring any parameters that follow.

    Workaround: Proofread command line carefully

    Resolution:


    • Article last edited: 3/4/2015