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 ValuesThis topic describes how to change the cursor configuration parameter values. You can change the cursor configuration parameter for Siebel clients in the following locations:
For information on overriding the MaxCursorSize parameter value from within a Siebel script, see 478276.1 (Doc ID) on OracleMetaLink 3. This document was formerly published as Siebel Technical Note 592. For information on Siebel clients, see Siebel Installation Guide for the operating system you are using. For more information on Siebel Tools, see Using Siebel Tools. Setting the Cursor Configuration Parameter for the Siebel Web Client and Siebel ServersFor the Siebel Web Client, the MaxCursorSize parameter value is set from the command line at the Siebel Enterprise Server level. As a result, you cannot set this parameter separately for each class of users. You must set it to the same value for all users, typically 128. For additional information on modifying enterprise server parameters and using the Siebel Server Manager command-line interface (srvrmgr) program, see Siebel System Administration Guide. To set the cursor configuration parameter value for the Siebel Web Client
Setting the Cursor Configuration Parameter for Siebel Developer and Mobile Web ClientsFor the Siebel Developer Web Client and the Siebel Mobile Web Client, you can set the MaxCursorSize cursor configuration parameter for different classes of users in application configuration files. Table 13 lists the user classes and the recommended MaxCursorSize parameter value for each class. NOTE: You do not need to set a cursor configuration parameter value for Siebel Mobile Web Client users who connect exclusively to the local database and update by synchronizing with the corporate Siebel Database. These users do not have a cursor configuration parameter in the Take special care with the training of Siebel Mobile Web Client users who access both their local database and the Siebel Database. 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 Siebel Database, and showing how to formulate queries for common cursor close alert scenarios. For information on application configuration files, see Siebel System Administration Guide. To set the cursor configuration parameter for the Siebel Developer and Siebel Mobile Web Clients
Using Siebel Tools to Bypass the Number of Rows ReturnedThere might 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 value for MaxCursorSize 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 MaxCursorSize parameter for these business components to -1. |
![]() |
![]() ![]() |
Implementing Siebel Business Applications on DB2 UDB for z/OS | Copyright © 2008, Oracle. All rights reserved. | |