• Product: Aleph
• Product Version: 20, 21, 22, 23
• Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

Description:
We have a separate $usr_library, ABC00, (separate from our ADM libraries). When I submit the p_manage_111 job to build words for the z303/z304 in the xxx50 ADM library, the p_manage_111 log has the messages: 
Table Z303 is not managed by this library, skipping...
Table Z304 is not managed by this library, skipping... 

And we are unable to run the job in the usr_library, because that library is not set up in the GUI.

Running p_manage_64 for the z303 is a similar case, except it doesn't even let us submit the job: we get an error popup "Table does not exist" for the z303 or z308.

Resolution:
The z111 for the z70, z72, and the z76 tables (budget/vendor keywords) is in the ADM library; the z111 for the z303 and z304 (patron keywords) is in the $usr_library. At single-ADM sites, the $usr_library and the ADM library will usually be the same, but at multi-ADM sites they are different.

There are two choices for running p_manage_111 in the $usr_library:
1. Include your $usr_library in your .\Alephcom\tab\library.ini and in your .\Circ\tab\per_lib.ini. When you start the Circ client and connect to the usr_library, you will be able to click on Services and submit p_manage_111 for z303/z304 and p_manage_64 for z303 and z308.
2. Run these jobs from the command line with your $usr_library (in this case, “ABC00”) specified as the library parameter, like this:
> csh -f $aleph_proc/p_manage_111 ABC000,,Y,0,00, > & abc00_p_manage_111.mmdd.log & 
(This will rebuild both the z303 and the z304.)

• Article last edited: 12-Mar-2016