tablesONLINE allows you to build applications that are table-driven. To create or customize an application you will take the seven tables that are used by tablesONLINE to drive an application and customize them to your needs. This chapter describes the seven Application Driving Tables and explains the editing process for each of these tables.

The following is a list of the Application Driving Tables required for an application together with a brief description of the content of each of these tables. These tables are stored in the Application Driving Tables Library.

The table names listed in Table 167 include a four-character application identifier, indicated by XXXX, which is unique for each application. For example, for a payroll application you, may wish to use an identifier of PAYR. In that case, your Application Driving Tables will be called PAYRMENU, PAYRPFKS, PAYRCMDS, and so on.

Table 167. Application Driving Tables

Application Driving Table Name



Contains customized menu entries for the application. This controls the flow of your application.


Contains customized PF Key assignments for the application.


Contains the command translation information for the application. This enables you to define aliases for commands.


Contains screen descriptions for the application. This lets you modify some textual lines on the screens.


Contains customized messages for the application.


Contains customized help for the application.


Contains the DSN to DDNAME translation for the application.

Each application, when started up, will pick up the names of its controlling tables from the Application Control Table. Once started up, the application is guided by those tables.

Special Views are used in the editing process for the Application Driving Tables. These Views ensure that the system knows how each table is set up. Much data validation and error-checking is performed automatically when these tables are edited.