This section describes what happens at the mainframe and at the server in the Client Option processing.
A Client Option application calls a pre-written procedure, such as a stored procedure or an Open Server application. All calls from the Client Option to remote nodes are processed using TCP/IP. For requests to an Open Server, the client can access any data available to the Open Server application.
For TCP/IP, the Client Option includes a Server-Host Mapping Table that allows you to define servers for two-tier environments. For more information, see Appendix A, “Customization Options.”
The called procedure or transaction executes and returns results to the calling Client Option application, which can use the results for local processing. If the client has permission, the client transaction can update data at remote sites by inserting, modifying, and deleting entries in database tables or other data storage systems.
The Client Option includes isql, a utility that allows users to send SQL language commands using TSO. You specify the server, user ID, password, and the input file containing the SQL statements. For more information about using isql with the Client Option, see Chapter 4, “Using isql.”
Typically, a server accepts requests from a client and returns results. The server can be an ASE, an Open Server, or a Server Option on the mainframe.
From the server standpoint, a request from an IBM host is no different than a request from a Sybase client. The Client Option performs ASCII-EBCDIC translations and datatype conversions.
