In version 20, jobs don't run for libraries in tab_library_group groupings

• Article Type: General
• Product: Aleph
• Product Version: 20

Description:
We just went to version 20. We are multi-ADM. Some of our libraries are *not* receiving their lost and overdue notices in the Task Manager.

I checked the job_list and p_cir_51 is configured to run daily but nothing showed up. I ran them manually from the Services menu which said the job was submitted but it never showed up in the batch queue, batch log or file list.
Next I attempted to run them manually from the command line which did end up running and producing a file of size 0 in task manager.

Resolution:
As we can see from the following commands in $alephe_scratch:

> ls -lrt lmn50*
> ls -lrt pqr50*

the last time that any batch jobs ran for these ADMs was June 9.

I see that the p_cir_51 for lmn50 and pqr50 *are* in the job_list and the $alephe_scratch/jobd.log shows them being released, but I do not find any logs in $alephe_scratch in July for either of these ADM's.

I observe that these libraries are members of $alephe_tab/tab_library_group groupings. And that *none* of the ADM's in these groupings have any job logs in $alephe_scratch since June 9 (except xyz50, for which you did a manual run).

In looking at the xxx50 jobs in $alephe_scratch, I have observed that as long as a library belongs to a group -- whether a member library or the hosting library --, it does not have any automatically-submitted job logs for July.

Though this grouping function can reduce the number of processes required, I think it's more important to get the jobs to run. I suggest that you eliminate the groups for now and, if you have problems with too many processes, we can revisit this later.

Note 1: Libraries which have been part of groups in tab_library_group have probably been omitted from the QUE_STARTUP_LIBS, WORD_STARTUP_LIBS, etc., lists in aleph_start.private. If you remove a library from a group in tab_library_group, you will probably need to add it to the appropriate xxxx_STARTUP_LIBS.

Note 2: If you find that your site has this problem, please report that fact to jerry.specht@exlibrisgroup.com .

• Article last edited: 10/8/2013