Library Technical Services

Scope: This procedure provides instructions for running automated import, export, cleanup, reporting and various related jobs using shell scripts and other tools created by the Library Systems Office. The list of jobs includes the frequency of the work, the list of people responsible for performing this work, as well as the function of each job. In addition, this procedure includes guidelines for scheduling batch routines.

Contact: Jena Bakula

Unit: Database Management Services

Date last reviewed: 04/02/07

Date of next review: July 2008

• Host Name: library22-a.library.cornell.edu
• Userid: ctsbulk
• Password: ******

2.  At the "/export/home/ctsbulk $" prompt, issue the command for the job you wish to run. Jobs are listed in the the Bulk Loads List.

• Let this process run until finished. At that time the UNIX command prompt will be displayed and mail will have been sent to the appropriate people, including Library Systems staff. If the subject line of the SUMMARY mail file contains RC=0, then all is well. Any other RC means a potential problem.
• Bulk loading tips:
  • Vendors aren't always case-consistent with their file names. If the FTP fails, try using lower- instead of upper-case in the file name, or vice versa.
  • To view the basic CTSBULK command line(s) associated with a given command entry, type <command> <enter>.
    • Example: To view the command lines associated with the general command "vendor_load", type: vendor_load <enter>.
• To stop a process before it has run to completion (for instance, if you discover you've misnamed an extract file), type: <control> c.
• Logout of the UNIX session, by typing: exit
• If you have any problems or questions, please contact Library Systems via CTSBULK-L.