Setting Up Your System › Pseudo-Conversational Processing

Pseudo-Conversational Processing

CA IDMS Server uses pseudo-conversational processing to minimize resource use on the CA IDMS system. The ODBC and JDBC drivers support pseudo-conversational processing by automatically issuing an internal SUSPEND command, which causes the current task to end, freeing resources on the CA IDMS CV.

By default, pseudo-conversational processing is optimized for interactive applications, in which a user enters a command and then works with the results for a while before entering another command, similar to the way an on-line application would be used. The drivers suspend the connection and end the task after most SQL commands.

You can customize this behavior can be by selecting a "suspend strategy" that specifies a set of suspend options appropriate for a particular type of application. These suspend strategies are:

• Interactive—Intended for use by applications with a user interface, in which database activity and user input are intermixed. The driver suspends the connection when the transaction is committed. This is the default strategy for ODBC and non-pooled JDBC connections.
• Service—Intended for use by JDBC applications that run in an application server that pools connections and allocates them temporarily to units of work that that access the database one or more times without waiting for user input. The driver suspends only when it determines that the connection is idle. This is the default for pooled JDBC connections. It is of limited use for ODBC applications, since the ODBC driver manager does not notify the driver when a connection is returned to the idle pool.
• Batch—Intended for use by applications access the database many times and terminate without waiting for user input. The driver does not use pseudo-conversational processing at all.
• Custom—Intended for compatibility with previous releases. The driver's behavior is determined by the options specified in the Windows registry, or equivalently, in the USS configuration file or Java properties file. These options are documented in the appendices.

The following table shows the detailed suspend options that correspond to each strategy, 0 = disabled, 1 = enabled, X = either: