A Zim Client-Server application can be developed as a stand-alone standard Zim application on any supported platform. Once developed, the application can be moved easily to another platform and configured to access remote data sources. Because of this capability, Zim enables you to separate your application from the ultimate data source, enabling development to be…
Read more
Zim can manipulate and retrieve data from third-party data sources as well as from a Zim database. Client applications for SQL database servers are designed and developed as complete Zim application systems. The objective of the Zim product is 100 percent source code portability of applications including seamless access to databases being managed by SQL…
Read more
DB2 provides support for three levels of multiple user concurrency control. These isolation levels select the extent to which database operations performed by one user are isolated from concurrent operations performed by other users. “Repeatable Read” isolation level means that locks are held on all rows read or updated by a user for the duration…
Read more
Execution Error Conditions The execution environment of a Zim client-server application involves products from more than one vendor. This can introduce the potential for additional error situations. For example, if the parameters to the connect command are not specified correctly for the particular installation of the SQL server being used, then the connect command fails…
Read more
The benefit of $serverfunction is the ability to code server functions that Zim does not support. Often there are similar functions in Zim and the server, but the mapping is not exact. As a result, the function is not present in the .sql file, forcing Zim to retrieve the entire table and evaluate the where…
Read more
Zim Client-Server uses the SQLCPI variable to find the SAM module and the utilities used to import and export objects. Under Windows, the SQLCPI variable is set in the Windows registry and is set to the directory where the SAM software is installed. When running Zim on Windows, ensure that the registry variable SQLCPI is…
Read more
In addition to installing Zim and modifying your UNIX operating environment to accommodate the Zim software, you must also set the environment variable “SQLCPI” to represent the directory for SAM files. To define SQLCPI, enter the following command if you are running the Bourne or Korn shells: SQLCPI=/usr/zim; export SQLCPI where zim is the directory…
Read more
If the server function requires parameters (called input host variables), these can be supplied by placing parameter markers in the syntax (indicated with a ‘?’) and then specifying the parameters as the second and subsequent arguments to $ServerFunction. Here is an example: change all orders where orderno = 1003 \ let RequiredByDate = $ServerFunc(‘trunc( ?,…
Read more
The Import/Export functions of the Zim Development Center application provides support for the import/export and translation of database object definitions between the Zim and SQL server environments. In particular, Zim EntitySet and data relationship definitions can be exported to the SQL server to create corresponding tables and indexes. Additionally, SQL table definitions can be extracted…
Read more
This option is used to import table definitions from the SQL server and to translate them into equivalent Zim definitions. To import SQL definitions into Zim, select the Tools/Import/Objects/From SQL option from the development center main menu. The SQL Definition Import window appears. On this window, choose the ODBC Server as the server from which…
Read more
English 
Portuguese