This chapter contains a survey of all functions of the ADABAS precompiler which may be controlled by options. The syntax of these options is described separately in the platform-specific user manuals.
CACHELIMIT(<cachelimit>)
CACHELIMIT defines the size of a cache buffer for result tables. If the option CHECK or SYNTAX is set, this value overrides the value for the database session with the number 1 either specified in a CONNECT statement or predefined. A description of the CACHELIMIT is included in the Reference manual.
CHECK/NOCHECK
The precompiler checks the syntax of all SQL statements, the existence of the table and column names as well as their type compatibility with the host variables in use. The precompiler opens a database session either under the user name specified in the option or in the CONNECT statement or under the predefined user name, and executes all SQL statements according to the order of their occurrence in the program. Possible error messages of the database system are output as warnings into the precompiler listing. SQL statements which cannot be executed at precompilation time (e.g., dynamic statements) are only checked with regard to syntax errors; they generate warnings. The system tables DOMAIN.MOD_USES_TAB or DOMAIN.MOD_USES_COL, which contain the program-data relationships, are maintained. When starting the precompiler run, all entries stored in the corresponding tables relating to the CONNECT user name and program name or module name are deleted. At the regular end of the precompiler run (no errors), new entries are made in the corresponding tables. The option NOCHECK does not establish a connection to the database. It is therefore possible to precompile without a started database.
CHECK/SYNTAX
The syntax of all SQL statements is checked and possible ADABAS error messages are written into the precompiler listing.
COMMENT
All SQL statements are written as comments into the compiler listing or into the source file saved for the compiler.
COMPATIBLE
With Version 6.1, new language elements are integrated into the embedded SQL (see Section EXEC SQL [<n>] <array statement>). These elements may change the interpretation of programs written for former versions. The option COMPATIBLE enforces the old interpretation and therefore guarantees upward compatibility. This option need only be specified if an error message occurs during re-precompilation of an existing program. In any case, new programs should be written in such a way that they may be precompiled without this option.
DATE-TIME/EUR
This option can be used to set the date and time representation to EUROPE. It is passed to the application program.
DATE-TIME/ISO
This option can be used to set the DATE and TIME representation to ISO. It is passed to the application program.
DATE-TIME/JIS
This option can be used to set the date and time representation to JIS. It is passed to the application program.
DATE-TIME/USA
This option can be used to set the date and time representation to USA. It is passed to the application program.
Representation:
DECPOINT (POINT | COMMA)
For every program, you can choose between point and comma for the decimal representation of real numbers.
EXTERN
A module precompiled with the option EXTERN can be linked to modules of other language precompilers. The module itself must not be a main program. The SQLCA and SQLDA, if needed, must be transferred to the subroutines as parameters.
HELP
This option displays all the precompiler and precompiler runtime options (application programs) on the terminal.
ISOLATION LEVEL(<level number>)
If the option CHECK or SYNTAX is set, the level number 10 (default value) is always specified for the CONNECT. Under this number, the locks have to be set to a database during precompilation. This option is only passed to the application program and has only an effect on the session with the number 1. It overrides the level specification for all CONNECT statements with the session number 1 made in an application program. It may be overridden by the same runtime option when starting the application program.
LIST
A precompiler listing is generated. If this option is not specified, the precompiler listing only consists of warnings and error messages.
MARGINS (<leftmargin>, <rightmargin>)
This option can be used to determine the range of lines in which the precompiler has to work. This option only makes sense with a free format (SOURCEFORMAT option).
NOWARN
The warnings -733, -735, -853, -884, and -885 are not output.
PRECOM
The compiler will not be started after precompilation. The source file is saved for the compiler.
PROFILE
The precompiler generates code for profiling the SQL statements. Profiling is started with a runtime option.
PROGRAM (<program name>)
When using the option CHECK, a program name can be specified here related to which the names of the tables and columns used in the program are stored in the system tables. These entries can be looked up via a SELECT on DOMAIN.MOD_USES_TAB or DOMAIN.MOD_USES_COL. The default value of <program name> is the filename of the source program.
QUOTE (SINGLE | DOUBLE)
The delimiters for character string literals are represented within the program either by the character ' (SINGLE) or by the character '' (DOUBLE).
SERVERDB (<serverdb>)
If the option CHECK or SYNTAX is set, a SERVERDB name can be specified here under which the database will be accessed at precompilation time. This option has an effect on all sessions with the number 1. When precompiling, this option overrides either the specifications made in the CONNECT statement or the predefined user specifications. It is not passed to the application program.
SERVERNODE (<servernode>)
If the option CHECK or SYNTAX is set, a node name can be specified here under which the database will be accessed at precompilation time. This option has an effect on all sessions with the number 1. When precompiling, this option overrides either the specifications made in the CONNECT statement or the predefined user specifications. It is not passed to the application program.
SILENT
No output is made on to the screen.
SOURCEFORMAT
If this option is set, the COBOL program has a free format. The lines are not numbered (columns 1 to 6). Comments are denoted in the first column. Continuation characters, if permitted by the COBOL compiler, have to be specified in the first column. The line length can be determined with the option MARGINS. For more detailed information about the free format, see the COBOL user manuals.
SQLMODE/ADABAS
This is the 'native mode' of an SQL application and the default value of the SQLMODE option.
SQLMODE/ANSI
This mode ensures ANSI compatibility of all SQL statements. Variables and statements must be defined in the program according to the ANSI standard. When this option is enabled, some positive error situations are transformed into negative error messages (see Section ANSI Compatibility).
SQLMODE/ORACLE
This mode ensures ORACLE compatibility of all SQL statements. The precompiler generates the definition of the 'ORACLE SQLCA and SQLDA'. Variables and statements must be defined in the program according to the ORACLE standard.
TIMEOUT (<timeout>)
This option can be used to specify the SESSION TIMEOUT for the session with the number 1. When precompiling, this option overrides either the specifications made in the CONNECT statement or the predefined user specifications. It is not passed to the application program.
TRACE FILE (<trace filename>)
This option can be used to specify a name other than the default name for the trace file. If no other trace option was specified, the option TRACE SHORT is simultaneously enabled by default. The filename is standardized according to the operating system conventions in the platform-specific User Manuals. The name may also be specified (optionally) as a character string constant. This option is only passed to the application program. It may be overridden in the application program by the same runtime option.
TRACE LONG
Each SQL statement is written into a file, together with the values of all host variables, the SQLCODE not equal to zero, the warnings (if warnings exist) and the SQLERRD (INDEX_3) value. This option is only passed to the application program. It may be overridden in the application program by the same runtime option.
TRACE SHORT
Each executed SQL statement is written into a file, together with the SQLCODE not equal to zero, the warnings (if warnings exist), and the SQLERRD (INDEX_3) value. This option is only passed to the application program. It may be overridden in the application program by the same runtime option.
USER (<userid> <password>)
If the option CHECK or SYNTAX is set, a user name can be specified here under which the database will be accessed. This option only has an effect on the session with the number 1. When precompiling, this option overrides either the specifications made in the CONNECT statement or the predefined user specifications. It is not passed to the application program.
USERKEY(<userkey>)
If the option CHECK or SYNTAX is set, a USERKEY can be specified here. The pertinent user, the database, TIMEOUT, CACHELIMIT, and SQLMODE are fetched from the XUSER file. The corresponding database can then be accessed by means of this user id. This option only has an effect on the session with the session number 1.
VERSION
This option can be used to see information about the version used.