This section contains the rules for writing IFD files.
Comments are started with an exclamation point. Any characters after a ! are ignored. Comments may start in any column and appear after an IFD command.
Each IFD command (with it's parameters and qualifiers) must be on a single line. Lines may be continued by placing a hyphen as the last non-blank character of the line. Total line length must not exceed 255 characters.
Each IFD command consists of a keyword, parameters and qualifiers. The syntax follows standard DCL parsing rules. For example, lists of values on a qualifier must be enclosed in () and separated by commas. If a single value is specified then the () may be omitted. If strings contains spaces, commas, or lowercase characters, then the string must be enclosed in quotes.
As an IFD file is being processed, DYNFORM maintains a "current line" pointer for each screen. By default, each TEXT and QUESTION item is placed on the next available screen line and the current line pointer is advanced by one. You may affect the current line pointer using either the SET LINE command or the /SKIP or /KEEP qualifiers. Once the current line pointer is changed in this manner it will again be advanced by one for each item until another SET LINE or /SKIP is encountered.
IFPRC and DYNFORM will attempt to process a form regardless of errors in the IFD file. Syntax errors that occur in the form will be displayed on the terminal when the form is processed by either IFPRC or DYNFORM. Other errors will be written to a log file in OECN$OUT with the same name as the IFD file and an extension of .LOG.
LSE Language Definition
The LSEPlus editor (a customized LSE editor used by the SSDT) contains a language definition for IFD files. Any command or qualifier can be expanded using LSE when editing a file with a .IFD extension. If you would like copy of the LSE IFD language, contact the SSDT.