## Server List File

The Configuration Expert has the following server list files:

- `gervers.lst`

- `iservers.lst`

The Configuration Expert imports the `gservers.lst` file generated by the C++ and Rose Experts (as part of the Framework Classes generation phase) as its source of server executable configuration information.

Similarly, the available servers file, `iservers.lst` contains a list of external server executables that can be added to the application. This file is updated when a new server is created using the Create button. However, the file may also be shared by multiple developers and thus be marked as read-only.

### Syntax example of Server List Files

The syntax of the `gservers.lst` and the `iservers.lst` file is:

`<module_name>,<server_name>,<rmname>,<Y|N>, <default_clopt>`

where

- `<module_name>` is the module name. This name is not used by the Configuration Expert.

- `<server_name>` is the server executable.

- `<rmname>` is the Resource Manager name for the associated server you have added. If a - is shown, no resource manager is required. The Resource Manager name should match a resource manager in the `$TUXDIR/udataobj/RM` file.

- `<Y|N>` indicates whether the server is conversational or non conversational. If `N` is selected, this indicates that there is a non conversational property of the server. Conversely if `Y` is entered, the server is a conversational server.

- `<default_clopt>` is the default command line option for that server. This option is entered on the General New Server Properties dialog window.

#### Example of a gservers.lst file

An example of the `gservers.lst` file looks like the following
(your file may look different):

> Listing 4-1 `gservers.lst` File

>     Account, ACCT, TUXEDO/SQL, N, -A

>     Balance, BAL, TUXEDO/SQL, N, -A

>     Teller, TLR, TUXEDO/SQL,N,-A -- -T 100

>     Transfer, XFER, TUXEDO/SQL,N,-A

#### Example of iservers.lst

An example of the `iservers.lst` file looks basically the same as the `gservers.lst` file. The only difference is that the Module name will always appear exactly the same as the server name. The following is an example of a `iservers.lst` file

> Listing 4-2 `iservers.lst` File

>     ACCT,ACCT,TUXEDO/SQL, N, -A

>     BAL,BAL,TUXEDO/SQL, N, -A

>     TLR,TLR, TUXEDO/SQL,N,-A -- -T 100

>     XFER,XFER,TUXEDO/SQL,N,-A