APPX Software Library

Chapter 2: System Administration

FMS Controls Overlay for Sybase

If you select the FMS Group Attributes option in File System Groups File Maintenance for a file system group with FMS type 4, the FMS Controls overlay for Sybase appears as shown in Figure 2-19 below.

FMS Controls Overlay for Sybase (Type 4)
Figure 2-19. FMS Controls Overlay for Sybase (Type 4)

The Sybase overlay contains the fields discussed below. Consult your Sybase database administrator for help in completing these fields.

Server Name

Indicates the name of the server on which the file system resides.

Database Name

Indicates the external name of the database being accessed.

Table Naming Scheme

Assists APPX in translating its 8-character file names to Sybase’s external table names. If users will be accessing Sybase at the File System Group level, then a “Table Naming Scheme” is entered here. Select the Hints option for help on constructing a table-naming scheme. See the Table Naming Scheme Hints section for an example of the Hints overlay. If you intend to override these parameters at the file level in Database Management, then you can leave this field blank and enter an explicit table name there.

Proxy Database ID

Defines the APPX Database ID.

Table Segment Name

Identifies the area within the database to store data for the table.

Index Segment Name

Identifies the area within the database to store index information for the table.

Locking Scheme

Indicates the level of locking for the table:

  • datarows locks the current record only (the most similar to APPXIO behavior)
  • datapages locks the entire page or block containing the current record (not recommended)
  • allpages locks the entire table
Max. Rows Per Page

Defines the blocking factor.

Expected Row Size

Estimates the average size of a row (or record).

Reserve Page Gap

Determines how much space to reserve between pages. This is used to allow room for growth.

Suppress Null Numerics?

Determines whether or not to disable the null numeric feature inherent in the database; answer "yes" checked box if you want to be consistent with APPXIO behavior which does not have this capability (a zero entry cannot be distinguished from a null value in APPXIO).