Standard Files Supplied In the CTO

When a new application is created (either through the OpenInsight graphical Presentation Manager, or through an account- or file-restore in the CTO), a table named MD (for Master Dictionary) is created. The MD table may contain the following types of items:

- "Q-pointers": these items (designated by a "Q" in field 1) allow users to create "synonyms" for their tables. The name of the item is the "synonym" name (the name by which you wish to refer to the table); field 1 contains a "Q", and field 3 contains the real table name. Field 2 contains either nothing (indicating that this q-pointer defines a table in the current application, or the name of the application where this table is defined.

- "V"erb definitions: these items (designated by a "V" in field 1) define certain "verbs" in the CTO environment.

- Control items: these items (usually designated by an "X" in field 1) are used to control the behavior of the CTO environment. Some of the control items you may wish to modify include:

a) PROCPATH: This item contains a list of the files the CTO environment should search when looking for a PROC or PAragraph to invoke (note that MD need not be listed here; the MD is always searched first). Field one should be “X”, and fields 2 through <n> contain the names of the files to process;

b) CASE.MODE: This item contains an “X” in field 1, and a "1" in field 2 to indicate "case sensitive" operations, or a "0" in field 2 to indicate "case insensitive" operations. (Note that this only applies to the command name itself; additional parameters may still behave in a case-sensitive fashion);

c) TODO: This item (created after an account- or file-restore) indicates files and items that require user attention;

d) Translation items (named <yourname>*TRANSLATE): this is used during account- or file-restore to specify the locations for newly-created files, and how such files should be created;

e) FORMATVARS: This optional item contains an “X” in field 1, and fields 2 through <n> contain the names of “formatting” variables used in basic+ programs. Specifying a variable name in this list allows the CTO precompiler to properly identify the variable and convert it to an OpenInsight-appropriate format;

f) CATALOG.ITEMS: This item contains a list of the cataloged pointers found during the account-restore operation. Field 1 contains an “X”, field 2 contains the list of tables, and field 3 contains an associated submultivalued list of the items that were cataloged (on the original system) for each table.

- "Catalog" pointers: these items (designated by a "P" in field 1) indicate that the associated BASIC+ routine has been compiled and 'cataloged' (that is, it may be invoked just by the name of the BASIC+ program - non-cataloged programs must be invoked with RUN). Field 5 contains the name of the table the BASIC+ routine has been cataloged from; field 4 contains the date and time of the cataloging; field 3 contains a "G" if this is a "GLOBAL" catalog entry.

Additionally, the MD table may contain PROCs, PAragraphs, or Sentences. These are "batch files" that are often used as simple "job control language" routines. They may reside either in the MD, or in any other table. If the PROCPATH control item has been set appropriately, typing in the name of the PROC, PAragraph, or Sentence at TCL will invoke the routine regardless of its actual location; if these routines reside in a table that is _not_ specified in PROCPATH, then an entry in the MD (or in another table that is listed in PROCPATH) must be created to transfer control to the routine.

g) RESTORED.DPOINTERS: This item contains a list of the “d-pointer” (file definition information) items found during the account-restore operation. Field 1 contains an “X”, field 2 contains a multivalued list of the dictionary name of the d-pointer, field 3 contains a multivalued (associated) list of the data name of the d-pointer, and fields 4 throught 14 (or beyond) contain a multivalued (associated) list of the d-pointer data.

h) SAVE.CONVERTED: This optional item contains an “X” in field 1, and a “0” in field 2 to instruct the CTO compiler to NOT write a copy of the converted BASIC source code in the SYSLISTS table. If this item is not present, or a “1” is in field 2, then the CTO compiler will write a copy of the converted BASIC source code into the SYSLISTS table, with the item id<tablename>_<programname> (e.g. “BP_SAMPLE”)

i) FLAVOR: This item identifies the emulation type desired in this CTO account. Field 1 contains an “X”, and field 2 contains the ‘flavor type’ (R83 by default). Valid values are currently R83, D3, and OI.