How to run p_cir_25 at a multi-ADM site

• Article Type: General
• Product: Aleph
• Product Version: 20, 21, 22, 23

Description:
Because of problems with the z353, we need to run p_cir_25. We have 55 xxx50 libraries. How do we do this? Can the jobs run at the same time?

Also, does p_cir_25 need to be done on a regular basis?

Resolution:
p_cir_25 needs to be run in each xxx50 ADM library. The run for the first ADM would specify "Y" for "Delete All"; the runs for each of the other ADMs would specify "N".

These jobs can *not* run at the same time; they need to be run in sequence.

You may want to create a "super_p_cir_25" file like this:

csh -f $aleph_proc/p_cir_25 ABC50,Y, > & $alephe_scratch/abc50_p_cir_25.xxxx
csh -f $aleph_proc/p_cir_25 DEF50,N, > & $alephe_scratch/def50_p_cir_25.xxxx
csh -f $aleph_proc/p_cir_25 GHI50,N, > & $alephe_scratch/ghi50_p_cir_25.xxxx
<etc.>
csh -f $aleph_proc/p_cir_25 XYZ50,N, > & $alephe_scratch/xyz50_p_cir_25.xxxx &


which you would submit as follows:

csh -f super_p_cir_25 > $alephe_scratch/super_p_cir_25 &

Note that only the csh for the last xxx50 line in the super_p_cir_25 file has the "&" at the end. (This makes it so the jobs run in sequence rather than simultaneously.)

The preceding will make it unnecessary to submit the jobs individually.

p_cir_25 does *not* normally need to be run on a regular basis. If you find that you have recurring problems with the z353 which require its running, let Ex Libris know what those problems are and we will try to prevent them.


If you have many ADMs and need to rebuild the z353 for just one of them (xxx50), you could run the following SQL to delete the z353's for this particular ADM:

SQL> delete from z353 where z353_rec_key like 'xxx50%' or z353_rec_key like ' xxx50%';

and p_cir_25 could then be run for the xxx50 ADM (with "Delete All" *not* checked).

You should back up the z353 using p_file_03 before doing this.