- Article Type: General
- Product: Aleph
- Product Version: 16.02
The p_manage_01 job which we ran for our Course Reserve library left the library locked. Why is that?
Also, when unlocking the ABC30 library (with util c/6) after this was observed, the following messages were displayed. Can you explain what these messages mean and whether / how they should be addressed?
*** util_c_06 - unlock ABC30 ***
Library ABC30 unlocked
environment variable 'bl_pid' not defined
lib_batch is already running for ABC30
ABC30 is not in ACC_AUT_STARTUP_LIBS
ABC30 is not in MESSAGE_STARTUP_LIBS
ABC30 is not in REQUEST_STARTUP_LIBS
When a job leaves the library locked, that means that there was a problem with the job. In this case, the last two lines in the log are these:
Exiting due to job suspension.
As described in KB 5728, you need to look at the $data_scratch/p_manage_01.err file to see exactly what the error is.
(In this case, the subsequent run of the job has deleted the p_manage_01.err file, and we are not able to see the error.)
The messages you see when you unlock the library are discussed in KB 8192-472. As described there, these messages are normal for the unlocking of a Course Reserve library.
- Article last edited: 10/8/2013