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 set properly.
Verify that the SQLCPI registry variable has been set properly from within Zim by outputting the $SQLPath system variable, as shown below:
> output $SQLPath
c:Zim
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 where you installed the Zim SAM.
If you are running the C-shell, enter the following command:
setenv SQLCPI /usr/zim
Before you run Zim, ensure that the location of the Zim software is included in the UNIX PATH environment variable. If you are running the SQLDif utility, ensure that the location of the SQLCPI import and export utilities are included in the UNIX PATH environment variable as well.
Note:This topic assumes that your current PATH includes the directories /bin and /usr/bin.
To add /usr/zim to your PATH in the Bourne or Korn shells, enter
PATH=/bin:/usr/bin:/usr/zim
In the C-shell, enter
set path = ( /bin /usr/bin /usr/zim)
You can also add these commands to your login script so that they are automatically executed each time you log in to your system.
All SQL servers require that some type of connection be established between a client program and the server before any database operations can be attempted. In Zim, a connection between a Zim application and an SQL server is established by the “CONNECT” command and removed by the “DISCONNECT” command.
During the execution of any Zim application, a CONNECT command must have been executed prior to the execution of any Zim command requiring database operations to be performed by the SQL server. Connections can be multiple or single as explained below.
When SQL database servers are accessed one at a time, a connection is always followed by a disconnection. Example:
connect to “JDBCSAM” using (“SalesDB”, “sqlserver”, “admin”, “”, “1422”, “172.16.20.33”)
…
disconnect from “JDBCSAM”
…
connect to “JDBCSAM” using (“Marketing”, “oracle”, “scott”, “tiger”, “1501”, “www.mycompany.com”)
…
disconnect from “JDBCSAM”
…
Notice that each CONNECT statement is followed by a DISCONNECT statement. In the above example, the first connection is different from the second one but it can be the same as well.
In this scenario, more than one connection is established and maintained at the same time without an intervening disconnection:
connect to “JDBCSAM” using (“SalesDB”, “sqlserver”, “admin”, “”, “1422”, “172.16.20.33”)
connect to “MYJDBC” using (“Marketing”, “oracle”, “scott”, “tiger”, “1501”, “www.mycompany.com”)
…
disconnect from “MYJDBC”
disconnect from “JDBCSAM”
Now, the second connection is performed not to JDBCSAM anymore but an alias to it called MYJDBC. The reasoning behind this difference is that all ZIM objects need to reference a specific type of object (for Entity Sets, it is the EntType; for Relationships, it is the RelType and so on) and Zim needs to know which object belongs to each type.
The aliases are defined in the “zimalias.zim” configuration file as described in the Servers Alias Configuration File.
Obviously, an alias could have been used in the example for single connections as well.
English 
Portuguese