Sets Adaptive Server query processing options for the duration of the user’s work session. The subset of options listed below affects behavior unique to Component Integration Services. For a complete list of options, see the Adaptive Server Reference Manual.
set cis_rpc_handling {on | off}
set strict_dtm_enforcement {on | off}
set transaction_isolation_level {on | off}
set transactional_rpc {on | off}
set textptr_parameters {on | off}
set textsize value
Usage
Normally, all outbound RPCs are routed through Adaptive Server’s site handler. These RPCs cannot participate in any transactions, and the performance characteristics of routing many RPCs through the site handler may necessitate the use of an alternate method for RPC handling.
Component Integration Services provides an alternate means of handling outbound RPCs. If cis_rpc_handling is on, outbound RPCs are routed through a Client-Library connection that is persistent through the life of the client’s connection to the Adaptive Server. This means that any number of RPCs can be routed through the same connection, without a connect and disconnect between each RPC. This connection is the same connection used by Component Integration Services to handle all interaction with the remote server, including processing of select, insert, delete and update commands.
The client application issues set cis_rpc_handling on or off to control whether an outbound RPC is to be routed through the Adaptive Server’s site handler or through a Component Integration Services connection. If cis_rpc_handling is on, Component Integration Services processes the RPC request; if cis_rpc_handling is off, the site handler processes the RPC.
When a client application makes a new connection to Adaptive Server, the connection inherits the setting for the configuration parameter cis rpc handling (default is off). This determines the default handling for outbound RPCs.
If this property is ON, then transactions that involve participants that are not DTM-enabled servers (i.e. non-ASE 12.0 servers) are aborted.
The default is OFF, in which case the behavior of transaction management for remote servers is “best-effort”, which is compatible with prior release behavior.
The isolation level state between the local thread and the thread created by the connection to the remote server is maintained. If the isolation level changes, then the state is synchronized between the local and remote servers by sending the appropriate set transaction_isolation_level command.
This state synchronization is only performed for connections to servers in class ASEnterprise.
Setting transactional_rpc on results in the same behavior as setting cis_rpc_handling on, except that RPCs that are issued outside of a transaction will continue to be routed through the site handler if cis_rpc_handling is off.
This command will affect the behavior of parameters to RPCs that are managed by CIS.
Any RPC parameter that is of type binary(16) or varbinary(16) is assumed to be a textptr if the setting for textptr_parametrs is on - only if the binary parameter is preceded by a char or varchar parameter that contains a string reference to a table that was the source of the textptr (Please refer to the discussion of textptr_parameter handling in Chapter 3 of this book).
The textptr is expanded into as many 32k chunks of text as are needed to contain the full text value, and sent to the remote server as CS_LONGCHAR parameters if the remote server supports the TDS LONGCHAR data type. If this type is not supported, then the expansion is disabled, and the setting of textptr_parameters is assumed to be off.
See Also
set in the Adaptive Server Reference Manual.
