Job_List: the Basics System Librarian, Make your Job easier with job_list Presented at NAAUG 2002 by Susan Marshall

Job_List: the Basics 2 What’s the point? The Job Daemon and Job List are used to schedule jobs to run automatically at predetermined times. –Weekly –Daily This scheduling is maintained through ALEPH rather than by using ‘chron jobs’ outside of ALEPH.

Job_List: the Basics 3 Be more specific… Examples of jobs to include: –Checking for disk space –Removing result set tables (z05/z110) –Removing session tables (z63/z64/z65) –Removing lock table (z60/z50) –Removing statistics table (z34) –Removing web basket table (z109) –Hold shelf reports (cir_06) –Overdue notices (cir_50, cir_51 or cir_52) –Send list of Orders (acq_14)

Job_List: the Basics 4 What is needed? Edit two tables from $alephe_tab –Job_list –Job_list.conf Start (or re-start) the Job Daemon

Job_List: the Basics 5 Managing the Job Daemon - 1 The job daemon must be running in order to process the jobs. This is managed via the Utilities menu. Use UTIL E/14 (from any library/directory) –There is only one job daemon per alephe

Job_List: the Basics 6 Managing the Job Daemon - 2 Run UTIL E/14/3 to check if the Job Daemon is running : –If the system returns a blank line, the job daemon is not running. –A line similar to the following shows when the job daemon is running: ? S 0:00 /aleph/15_2/a55_5/aleph/exe/jobd 555

Job_List: the Basics 7 Managing the Job Daemon - 3 Run UTIL E/14/1 to start the Job Daemon. Run UTIL E/14/2 to stop (kill) the Job Daemon. –No scheduled jobs will be processed until the daemon is restarted. Run UTIL E/14/4 or look in $alephe_scratch to view the jobd.log

Job_List: the Basics 8 How do I edit the tables? - 1 Use E/15 on UTIL menu in telnet session or Use ALEPHADM GUI module to edit tables in the ALEPH section or CD to $alephe_tab at the UNIX prompt and VI the tables

Job_List: the Basics 9 How do I edit the tables? - 2 Using UTIL menu, choose UTIL E/15/1 to edit job_list or E/15/5 to edit job_list.conf or Using ALEPHADM GUI module, select ALEPH/tab from the Tables Navigator menu or Use cd $alephe_tab command at the UNIX prompt & then vi the table. See example below: support.exlibris-usa.com-M555=EXU50-SUSAN>>cd $alephe_tab support.exlibris-usa.com-M555=EXU50-SUSAN>>pwd /aleph/15_2/u55_5/alephe/tab support.exlibris-usa.com-M555=EXU50-SUSAN>>ls -l job* -rw-rw-r-- 1 aleph aleph 6833 Jul 26 16:53 job_list -rw-rw-r-- 1 aleph aleph 1058 Jul 26 14:57 job_list.conf support.exlibris-usa.com-M555=EXU50-SUSAN>>vi job_list.conf

Job_List: the Basics 10 What is the Purpose of job_list.conf? - 1 Defines daily and/or weekly time definitions to be used in job_list. –Instead of specifying single days and times when scheduling jobs in job_list, it is possible to specify a definition from job_list.conf instead. There are two types of definitions –Weekly (W) –Daily (D)

Job_List: the Basics 11 Structure of the table: job_list.conf - 1 Weekly procedure slots: Col. 1Code Col. 2 W(eekly) Col. 3Flags (Sun - Sat) Y/N !1 2 3 !!----!-!!!!!!! W1 W NYYYYYN (In the example above, the jobs in job_list using W1 will run Monday – Friday).

Job_List: the Basics 12 Structure of the table: job_list.conf - 2 Define daily procedure slot: Col. 1Code Col. 2D(aily) Col. 3Start time Col. 4End time Col. 5Interval ! !!----!-!!!!!-!!!!!-!!!!! D1 D 09:00 17:00 01:00 (In the example above, the jobs in job_list using D1 will run every hour between 9:00 AM & 5:00 PM).

Job_List: the Basics 13 What is the Purpose of job_list? - 1 The job_list table contains the list of programs and procedures that should be run on a regular basis by the job daemon. Jobs can be defined to run for a cycle of a week. The table has two types of lines: – a line defined for a job (procedure) that is sent to the ALEPH batch queue ! !!-!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!! –a line for the running of any program. ! !!-!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!> The file is located in the $alephe_tab directory.

Job_List: the Basics 14 Structure of the table: job_list - 1 Col. 1 : day –00 = Sun., 01 = Mon., 02 = Tues., etc. –Instead of entering a value for a specific day of the week, you may enter a day definition like W1 (W2, W3 etc), which refers back to job_list.conf. This allows you to run the job multiple days with just one entry.

Job_List: the Basics 15 Structure of the table: job_list - 2 Col. 2 : hour –The time the job should be run, in the following format: ‘HH:MM:SS’ –Instead of entering a time, you may enter a time definition of D1 or D2, which refers back to the job_list.conf 00 23:00:00 Y EXU50 util_a_12_b EXU50 (In the example above, the job will run on Sunday at 11:00 PM) W4 D1 N EXU50 p_cir_12 EXU50,XLAW,call_slip_%D_%H_%M,ENG,00,1,04,01,,N,,,1,Y,,A,00,00, (In the example above, the job will run every hour, everyday between 9:00 AM and 5:00 PM, according to job_list.conf)

Job_List: the Basics 16 Structure of the table: job_list - 3 Col. 3 : queue (y/n) –Sent to ALEPH queue (Y/N) –If set to Y, the job will take its turn in the queue at the specified time and in the order listed in job_list (if the start times are identical). –If set to N, the job will be processed at the time specified and may be running simultaneously with other jobs. –Be careful that jobs which are related are running in the correct order by setting this value to Y.

Job_List: the Basics 17 Structure of the table: job_list - 4 Column 4 (for PROGRAMS): log name OR target name –this column is used to specify the name of the log file that will be produced after running the program ! !!-!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!> 05 13:20:00 N disk_size_0 df –k support.exlibris-usa.com-M555=EXU50-SUSAN>>ls –l -rw-rw-r-- 1 aleph aleph 450 Jul 26 13:20 disk_size_0_13729 Column 4 (for PRCEDURES): target name –If you are running a procedure, this column can be used to specify a Print ID for the report output ! !!-!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!! W2 23:01:00 Y circ_print EXU50 p_cir_51 EXU50,ci rc_51_educ_%D_%H_%M,Y,,Y,,XEDUC,00,00,00,Y,Y,N,O,4,

Job_List: the Basics 18 Structure of the table: job_list - 5 Column 5 (for PROGRAMS): name of the program to run – In the example below, the program, “df –k,” will be run and the results can be seen in $alephe_scratch ! !!-!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!!!!!!!!!!> 05 13:20:00 N disk_size_0 df –k Column 5 (for PRCEDURES): the library in which the procedure should be run (EXU50, EXU01, etc.) –In the example below, the library, EXU50, is where the procedure will run. ! !!-!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!! W2 23:01:00 Y circ_print EXU50 p_cir_51 EXU50,ci rc_51_educ_%D_%H_%M,Y,,Y,,XEDUC,00,00,00,Y,Y,N,O,4,

Job_List: the Basics 19 Structure of the table: job_list - 6 Column 6 (for PRCEDURES): name of the procedure to run –This column is only used if you are running a procedure, and specifies the name of the procedure. ! !!-!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!!!!!! W2 23:01:00 Y circ_print EXU50 p_cir_51 EXU50,ci rc_51_educ_%D_%H_%M,Y,,Y,,XEDUC,00,00,00,Y,Y,N,O,4,

Job_List: the Basics 20 Structure of the table: job_list - 7 Column 7 (for PRCEDURES): parameters to be passed to the procedure –This column is only used if you are running a procedure, and specifies the parameters to be passed to the procedure –Adding the wild card values of _%D_%H_%M to the end of the output filename keeps the new files from replacing the old ones. ! !!-!!!!!!!!-!-!!!!!!!!!!!!!!!!!!!!-!!!!!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!- !!!!!! W2 23:01:00 Y circ_print EXU50 p_cir_51 EXU50,ci rc_51_educ_%D_%H_%M,Y,,Y,,XEDUC,00,00,00,Y,Y,N,O,4,

Job_List: the Basics 21 Getting the parameters for procedures - 1 Run job from Services menu using desired parameters View results in the GUI module of Task (Job) Manager to determine if this is what you want Copy parameters from the lib_batch_log and/or the batch_log in the xxxnn/files directory (For example, EXU50/files for p_cir_12) Carefully paste parameters in column 7 of job_list.

Job_List: the Basics 22 Getting the parameters for procedures - 2 Looking at lib_batch_log in EXU50/files directory for cir_12, we see: Sat Jul 27 11:37:37 chrish *** executing /aleph/15_2/a55_5/aleph/proc/p_cir_12 w ith parameters EXU50,XLAW,call_slip,ENG,00,1,04,01,,N,,,1,Y,,A,00,00, Sat Jul 27 11:37:37 chrish *** log file is: /aleph/15_2/u55_5/alephe/scratch/exu 50_p_cir_ We can create the following job in alephe/tab/job_list: W3 D1 N EXU50 p_cir_12 EXU50, XLAW,call_slip_%D_%H_%M,ENG,00,1,04,01,,N,,,1,Y,,A,00,00,

Job_List: the Basics 23 Finding the Results - 1 The Job Daemon log file is can be found in the $alephe_scratch directory -rw-rw-r-- 1 aleph aleph 1823 Jul 28 03:35 jobd.log -rw-rw-r-- 1 aleph aleph 181 Jul 26 12:54 jobd.log The results for programs can be found in the $alephe_scratch directory -rw-rw-r-- 1 aleph aleph 450 Jul 26 13:20 disk_size_0_13729

Job_List: the Basics 24 Finding the Results - 2 The results for procedures can be found in the $data_print directory -rw-rw-r-- 1 aleph aleph Jul 27 11:37 call_slip -rw-rw-r-- 1 aleph aleph 0 Jul 27 11:37 call_slip_wait The results for procedures that are sent to a printer can be found in the $data_print directory -rw-rw-r-- 1 aleph aleph Jul 26 15:13 circ_51_educ

Job_List: the Basics 25 Documentation The headers for job_list and job_list.conf Training Document for System Librarian called “Task Manager SysLib14.2_ ” Data Base Management Guide (DMG) – part 1 –Section E.14 and E.15

Job_List: the Basics 26 Documentation Online Sources Ex Libris DocPortal – –Contact for username and Web Guide at – –Use your staff username and password