SIP2 server does not process message 63 (Patron Information Request)

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Article Type: General
Product: Aleph
Product Version: 20

Description:
In regards to our SI 16384-278434. We installed the hot fix yesterday and everything works fine for message 23 Patron Status request. The MnLink gateway also uses message 63 Patron Information request. The sip2 server aborts when this request is sent. This stops our patrons from using the MnLink Gateway.

Resolution:
[From site:] We talked to the people at the MnLink Gateway. The reason for the 63 message was for patrons that manage their requests on VDX. Our patrons do not manage their requests on VDX. They reconfigured the gateway to not send the 63 message.

The code for the 63 is not needed {and the rep_change (for v20 fix_request 1284) will be created without it}.

Article last edited: 10/8/2013