- Article Type: General
- Product: Aleph
- Product Version: 19.01
Do you know why QUE_STARTUP_LIBS and other variables are not defined in a second column of aleph_start:
setenv QUE_STARTUP_LIBS "usm01 usm50 vir01"
but in aleph_start.private =>
setenv QUE_STARTUP_LIBS "$QUE_STARTUP_LIBS ABC01 ABC10 ABC30 ABC50 ABC60"
We found that missing variable in a second column of aleph_start.private does affect Library Batch Queue start up.
When "$QUE_STARTUP_LIBS" is included in the aleph_start.private QUE_STARTUP_LIBS line, it means that the proc will do this:
1. Take the current value of QUE_STARTUP_LIBS -- which is what you have in aleph_start -- and
2. Append the values in the aleph_start.private line to it.
If you omit the "$QUE_STARTUP_LIBS" from the aleph_start.private QUE_STARTUP_LIBS line, then the only libraries which will have the batch queue started are those in the aleph_start.private QUE_STARTUP_LIBS.
Not starting up the USMnn libraries does not matter so much, but the VIR01 batch queue *must* be started (in order to let clear_vir01 run). You need to either add VIR01 to the aleph_start.private or include the "$QUE_STARTUP_LIBS" in the aleph_start.private QUE_STARTUP_LIBS.
- Article last edited: 10/8/2013