COMPILING AND PRINTING FORMS
Online
If your LPS is
Remote communications The LPS can also receive forms data from a remote device on the Ethernet network.
Compiling a form
Once the file has been created, the next step is to enter the command that compiles the .FSL to an .FRM.
Multiple .FSLs contained in one file are paginated so that each new .FSL starts on the front side of a new page.
FDL compilation time
The time it takes to compile a form file depends on the position of the font file in its directory and the size and number of disks on the system. If your LPS has a large number of font files located on several disks, you may notice an increase in compilation time for forms that perform text handling. To ensure that your form files compile as quickly as possible, remove any unnecessary font files and use the COMPRESS utility to reorganize your files on the disk. This will shorten the font lookup time and use the disk space efficiently.
Invoking the forms compiler
To invoke the forms compiler, enter the following command at the LPS keyboard. The entire command must fit on one line.
FDL filename NOPRINT TRAY DEBUG XPAN NOSOURCE PROOF SIMPLEX RES=spi
| The FDL compilation command includes any combination of the |
| following options. |
Parameter options | filename |
| Specifies the name of the .FSL to be compiled. The file |
| extension, .FSL, may be included. No other extension is |
| allowed. The file name cannot be a keyword option such as |
| TRAY, DEBUG, XPAN, and so on. These are reserved names |
| that could cause problems when you use a task outside of |
| the forms compiler. |
| NOPRINT |
| Specifies that the .FSL source statements listing, form |
| summary, and sample form will not be printed. However, if |
| an error occurs during form processing, the listing and the |
| summary are printed. |
XEROX 4050/4090/4450/4650 LPS FORMS CREATION GUIDE |