connect

Transforms the Replication Server into a gateway to its RSSD, ID server, to a remote Replication Server, or to a remote data server.

Syntax

connect [to] [rssd | idserver | srv_name | ds_name.db_name]

rssd – Turns Replication Server into a gateway to its RSSD. Allows the gateway to use RSSD_primary_user and RSSD_primary_pw entries in its configuration file. rssd is the default connect to option.
idserver – Turns Replication Server into a gateway to its ID server, providing that the Replication Server itself is not the ID server. Allows the gateway to use ID_user and ID_pw entries in the configuration file.
srv_name – The name of the remote Replication Server you want the gateway to connect to. Gateway uses RSI to log into the remote server, and requires a direct route to the remote server.
ds_name.db_name – The name of the remote data server and database that you want the gateway to connect to. The Replication Server gateway uses the maintenance user to log into the remote data server. This allows you to perform tasks that maintenance users of the designated database are permitted to do. However, you cannot access the other databases defined in the data server you connected to.
Replication Server gateway can directly connect to Adaptive Server, and to Sybase® IQ data servers that do not require Enterprise Connect Data Access (ECDA). For other data servers, Replication Server gateway has to connect to use the ECDA to connect the Replication Server and the remote data server.

Example 1 – Creates a gateway connection to the RSSD ost_replinuxvm_01.emb from the Replication Server ost_replinuxvm_02 by logging into ost_replinuxvm_02 and issuing the connection to command:
```
isql -Usa -P -S ost_replinuxvm_02
1> connect to
2> go
```
```
Gateway connection to 'ost_replinuxvm_01.emb' is created.
```
The show server command verifies the connection:
```
1> show server
2> go
```
```
ost_replinuxvm_01.emb
```
Example 2 – Connects to Replication Server ost_replinuxvm_03 from the Replication Server ost_replinuxvm_02:
```
isql -Usa -P -S ost_replinuxvm_02
1> connect to ost_replinuxvm_03
2> go
```
The show server command verifies the connection:
```
1> show server
2> go
```
```
ost_replinuxvm_03
```

Example 3 – Creates a gateway connection to the Adaptive Server ost_replinuxvm_01.pdb:

isql -Usa -P -S ost_replinuxvm_02
1> connect to ost_replinuxvm_01.pdb1
2> go

Gateway connection to 'ost_replinuxvm_01.pdb1' is
created.

1> select db_name()
2> go

------------------------------ 
pdb1
(1 row affected)

Issuing the connect command requires an sa role for the first log in to Replication Server.
Issuing the connect command without specifying an option creates a gateway connection to the RSSD.
When acting as a gateway, Replication Server uses your RSSD primary user name and password to log in to RSSD, your ID server user name and password to log in to ID Server, and your Remote Server Identification (RSI) to log in to a remote Replication Server. You do not need to supply this information more than once, when you access Replication Server itself.
Cascaded connections created in the gateway are kept in a connection stack, with the Replication Server that issued the first connect command placed at the bottom of the stack.
Replication Server cannot directly connect to itself. However, you can work around this by using a cascading connection.
When using Replication Server Gateway, the client and the server must use the same locale set because Replication Server cannot perform character set conversion.

Transforming the Replication Server into a gateway requires “sa” permission.