- The precompiler opens the database session under a user name which can be specified as a parameter of the call. This user name does not need to be identical to the ADABAS user name used during the execution of the program. If the username is not specified as a parameter, then the CONNECT that is statically placed in the module as the first statement is taken. If the first statement is not a CONNECT, a database session is opened with predefined user specifications.
- The precompiler checks the compatibility of the corresponding host variables and ADABAS column types. In doing so, the rules specified for the conversion possibilities apply.
- The precompiler actually executes administrative statements (CREATE TABLE, etc.) and resets their effects at the end of the precompiler run.
- The precompiler analyzes the syntax of table statements (INSERT, SELECT etc.) and checks them with regard to the privileges. When accessing existing tables, it is important that they are already available for the ADABAS user whose name is used by the precompiler.
- The precompiler enters the names of the tables the program processes into system tables. Afterwards, the relations of the programs and used tables can be shown via select statements performed on the tables DOMAIN.MOD_USES_TAB or DOMAIN.MOD_USES_COL. These tables are described in the Reference manual.
- The precompiler generates the compiler input transforming the embedded SQL statements into calls of procedures of the ADABAS precompiler runtime system.
See also:
Translation of an ADABAS Application Program
User Specifications for a Precompiler Run