Bookshelf Home | Contents | Index | PDF |
Implementing Siebel Business Applications on DB2 UDB for z/OS > Maintenance Considerations for z/OS > About Cursor Close > Changing Cursor Configuration Parameter ValuesYou can change cursor configuration parameters for Siebel clients in the following locations:
For information on Siebel clients, see the Siebel Installation Guide for the operating system you are using. For more information on Siebel Tools, see the Using Siebel Tools guide. Setting Cursor Configuration Parameter Values for the Siebel Web Client and Siebel ServersFor the Siebel Web Client, cursor close parameter values are set from the command line at the Siebel Enterprise Server level. As a result, you cannot set them separately for each class of users. You must set them to the same value for all users, typically 128. For more information on modifying enterprise server parameters, see the Siebel System Administration Guide. To set cursor configuration parameter values for the Siebel Web Client
Setting Cursor Configuration Parameter Values for the Siebel Developer Web ClientFor the Siebel Developer Web Client, you can set cursor configuration parameter values for different classes of users in application configuration files. Table 15 lists the user classes and the recommended cursor configuration parameter values for each class. For information on application configuration files, see the Siebel Installation Guide for the operating system you are using. To set cursor configuration parameter values for the Siebel Developer Web Client
Setting Cursor Configuration Parameter Values for the Siebel Mobile Web ClientFor the Siebel Mobile Web Client, cursor configuration parameter values are set in application configuration files. Determine the cursor configuration parameter values based on the usage and network access of the Siebel Mobile Web Client user:
Take special care with the training of Siebel Mobile Web Client users who access both their local database and the Siebel Database Server. This training must include explaining the difference in operation between the two platforms, setting appropriate expectations for receiving cursor close alerts when connected to the Database Server, and showing how to formulate requeries for common cursor close alert scenarios. For information on application configuration files, see the Siebel Installation Guide for the operating system you are using. To set cursor configuration parameter values for the Siebel Mobile Web Client
Using Siebel Tools to Bypass the Number of Rows ReturnedThere may be cases where you do not want to change the general limitation concerning the number of rows returned (default 128), but do want to have an unlimited number of rows available for certain operations. To do this, leave the parameter values for MaxCursorSize and PreFetchSize in the .cfg file set to the default number (or any number you choose), but use Siebel Tools to set values for the specific Business Components for which you want unrestricted operation. To ignore the Cursor Close limitation, change the properties for the parameters MaxCursorSize and PreFetchSize for these Business Components to -1. |
Implementing Siebel Business Applications on DB2 UDB for z/OS |