Profile Tokens › Token Tables › Optional Tokens

Optional Tokens

Most builds do not require modifications to optional tokens. Standard defaults are overridden when tokens in this category are changed. Avoid modifying optional tokens unless necessary to prevent unexpected side effects. The following optional tokens are available:

• OPT.CMD_FORM
• OPT.INSTALL_TRANCODES
• OPT.CBDLIST
• OPT.VSVERSION
• OPT.BITS
• OPT.LIBTYPE
• OPT.DEBUG
• OPT.HAS_SQL
• OPT.IEFC
• OPT.IEFLINK
• OPT.COMPRESS_STATICCONTENT
• OPT.COMPRESS_DYNAMICCONTENT

The following information applies to optional tokens:

• OPT.CMD_FORM

  This token specifies the type of application to build, and where to place the executables.

  For Windows systems

  Setting this token to YES will cause the Blockmode application to be built as a console application, leaving all executables and the trigger dll in the model's \c directory. Setting this token to NO for Server or BlockMode Transactional applications, will move all built executables and the trigger dll into the model's \c\inqload directory.

  For UNIX and Linux systems

  Setting this token to YES will cause the Blockmode application to be built as a console application, moving all executables and the trigger shared library into the model's /bin directory. Setting this token to NO for Server or BlockMode Transactional applications will move all built executables and the trigger shared library into the model's /inqload directory.

  This token is not applicable for GUI applications.

• OPT.CBDLIST

  This token is used to identify the name of a text file that lists component libraries to use at link time for other components or load modules.

  For Windows systems

  When working with pathnames which contain spaces, you need to quote each file name.

• OPT.HAS_SQL

  This token is used to force the use of the selected DBMS, chosen during generation, to be linked into the BlockMode or Server load module, regardless of whether or not the generated code contains any embedded SQL statements.

• OPT.BITS

  With the introduction of Visual Studio 2010 compiler support, the customer can create both 32-bit and 64-bit BlockMode and Server applications. This token controls the bit setting of the compiler and which CA Gen libraries (bitwise) will be linked into the application being built.