Related Topics

HOWTO: Backing Up the ILLiad Database
HOWTO: Breaking the User Link in the ILLiad Database
PROBLEM: Cancellations or OCLC Reasons for No are all updating as Other
HOWTO: Changing the Port for Microsoft SQL Server 2000
HOWTO: Changing the size of a field in the ILLData database
See more

Other Support Options

Contact Atlas Systems
Phone Numbers, Support Options, Online Help, and more.
Listserv
Pose a question to other users.

Page Tools

Print this page Print this page
E-mail this page E-mail this page

Feedback

How helpful was this article?
Suggestions:

Revised:January 6, 2006 (mc)
Version:All DLL Versions
Revision:1
INFO: User Request Limits
January 6, 2006

SUMMARY

All customers statuses in ILLiad are limited in the number of active requests allowed in the ILLiad system at any given time. By default all statuses have the same limit and that number is set by the RequestLimit key in the Customization Manager (under Web Interface .. Limits). All other limits keys are then ignored.

There is an option to give separate request limits to each status. In this case, the key for UserRequestLimit is set to Yes and a key must exist for each customer status in the database. The defaults are already provided, but if additional statuses have been added, RequestLimit keys need to be created for those as well (i.e. RequestLimitDoctoral, RequestLimitAdministrative, etc.). Each key can then have its own number value for the number of active requests allowed for that status. If the UserRequestLimit is changed to Yes, but all limit keys do not exist, the dll may return an error when attempted to request an item of "Key Value Not Found for RequestLimitDoctoral" etc. To add a key for these statuses, type in the appropriate values into the Customization table under System .. General in the Customization Manager. All fields must be filled out in the Customization table.

There is currently no way to turn off the request limit in the web interface. A request limit can be as high as you like, however (i.e. 2000 or 9999).

More Related Topics

PROBLEM: Class Not Registered error when trying to initiate Z39.50 Searching
PROBLEM: Incorrect Queues and E-mail Routing Entries in the ILLiad Client for a Shared Server Site
HOWTO: Enabling Logging on the ILLiad Gateway
HOWTO: Enabling Logging on the ILLiad Web DLL
HOWTO: Increasing the Username field in the ILLiad database
INFO: ILLiad and McAfee VirusScan 8
OCLC ILLiad and Windows Server 2003
INFO: ILLiad and the NVTGC Field
HOWTO: Implementing SSL with ILLiad
HOWTO: Importing a Customized List of Addresses to ILLiad
HOWTO: Importing Pre-ILLiad Copyright Information into your ILLiad Database
PROBLEM: Z39.50 Searching Form gives File Not Found error for Yaz.dll
INFO: Z39.50 Profiles in ILLiad
INFO: Z39.50 Compatibility in ILLiad
INFO: What Ports are Required to be Open for General ILLiad Use?
HOWTO: Updating Across a Multiple Server ILLiad Installation
PROBLEM: I/O Error 32 or Path not Found when opening the Borrowing Request Form
HOWTO: Migrating an ILLiad Database to a New ILLiad Server
PROBLEM: Error Message "Login failed. Reason: Not associated with a Trusted SQL Server connection"
PROBLEM: SQL Server Agent fails when executing job to run ILLiad Connector
ERROR: SQL ERROR: Unmatched '' near TransactionNumber
PROBLEM: EDBEngine Error: Vendor Initialization Failed
Microsoft SQL Server 2005 Compatibility
HOWTO: Changing the Default Request Type for Manually Entered Transactions
INFO: Required ILLiad Server Permissions
HOWTO: Routing Rules Across Modules
BUG: Routing Rules for Borrowing and Doc Del do not work using the ILLiad Connector