Using the script commands

Script commands always begin with a period (.). Commands are not case sensitive and can be abbreviated to uniqueness. For example, “.C” is valid for .COLUMN, but “.ENT” is required to distinguish .ENTRY from .END.

Window building commands

Window building commands are script commands that define overall window characteristics, including name, size, screen position, border renditions, and title.

Window definitions within a script file begin with one of the following commands (depending on what kind of window you are building): .WINDOW, .COLUMN, .INPUT, .SELECT, .LISTCLASS. The .END command ends a window definition. You can have more than one window definition (window script) in a single script file.

Arguments

Script commands may have one or more arguments. The first argument must be separated from the command by at least one blank space or tab, and any additional arguments must be separated by commas. There may be one or more blanks or tabs before or after the commas. If you omit optional trailing arguments, you do not need to specify separating commas.

Like commands, arguments can be abbreviated to uniqueness.

Continuation lines

Each script command is a single logical line in the script file. The maximum length of a physical line is 255 characters. You can continue many script commands, such as .BORDER, .FIELD, and .LISTCLASS, on more than one physical line by placing a dash continuation mark (–) at the end of each line that will be continued. The dash can either precede or follow the comma.

Comments and blank lines

A comment line is any line whose first non‑blank, non‑tab character is a semicolon (;). Comment lines can be placed outside or within a window definition. See Special characters for more information about comment lines within the text of a window.

You may include blank lines in your script files to aid in readability. They are ignored when the script is compiled.