If stopping & starting SIP2 it uses active library instead of specified one

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

Description:
If we have to stop and start the SIP2 server, using the util w menu, it uses the active library instead of the library we have specified:

setenv SIP2_STARTUP_LIBS "umn50"

If the active library at the time the sip2 server is started is not umn50, the shelf-check machine can not connect.
We see the following error:
Error: Active library 'UMN01' is not a ADM library - exiting.

What is the solution to this?

Resolution:
The STARTUP_LIBS setenv's in aleph_start are used to start the process for certain libraries when aleph is restarted.
They play no role after that.

The system does not prevent the start-up of a sip2_server in a non-ADM library (that would be an enhancement request), but it does issue this clear message in the log.

You need to make sure that you are dlib-ed to the correct library when you start the server.