Implementing Siebel Business Applications on DB2 for z/OS > Maintaining Siebel Business Applications on DB2 for z/OS > About Cursor Close >

Changing Cursor Configuration Parameter Values


This topic describes how to change the cursor configuration parameter values. You can change the cursor configuration parameter for Siebel clients in the following locations:

  • Application configuration (.cfg) files for the Siebel Developer Web Client and Siebel Mobile Web Client.
  • From the command line for the Siebel Web Client.

    Because the Siebel Web Client does not have an application configuration file, it uses the configuration parameter values specified for the Enterprise Server; these values are applied to all server components and the Web Client.

  • Application configuration (.cfg) file for Siebel Tools.
  • At the business component level in Siebel Tools.

For information on overriding the MaxCursorSize parameter value from within a Siebel script, see 478276.1 (Article ID) on My Oracle Support. 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 Servers

For 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

  1. List the DSMaxCursorSize cursor configuration parameter to check its current value. From the Siebel Server Manager command-line interface, enter the following:

    srvrmgr > list advanced param DSMaxCursorSize for named subsystem ServerDataSrc

  2. Change the value of the DSMaxCursorSize parameter by entering the following from the command line:

    srvrmgr > change parameter DSMaxCursorSize=value for named subsystem ServerDataSrc

    where value is the new value you want to specify for the DSMaxCursorSize parameter.

  3. Stop and restart the Siebel Server for the changes to take effect.

Setting the Cursor Configuration Parameter for the Siebel Developer Web Client and Siebel Mobile Web Client

For 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 11 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 [Local] sections of their application configuration (.cfg) files.

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.

Table 11. User Classes and Recommended MaxCursorSize Parameter Values
User Class
Description
Recommended Value

Siebel administrator

Accesses the database to perform system updates. Might need to access large amounts of data.

-1

Siebel application developer

Performs development and customization of the Siebel application using Siebel Tools.

-1

Special

Sporadically submits queries or executes operations returning a large number of rows. Special users cannot be effective if their queries are limited by the cursor configuration parameter value.

Examples include:

  • No requery formulation is available to access the next set of data.
  • Operation requires the complete result set.
  • Data returned must be internally consistent. When a requery is issued, the returned data set might have changed because of other database activity.

-1

Typical

Majority of users. Examples include call center agents and sales representatives.

128

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

  1. Create a backup copy of the application configuration (.cfg) file.
  2. Open the original .cfg file in a text editor.
  3. Set the MaxCursorSize parameter in the [ServerDataSrc] section of the .cfg file.
  4. Save your changes.

Using Siebel Tools to Bypass the Number of Rows Returned

There 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 for z/OS Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.