COMPILING AND PRINTING FORMS4-6 XEROX DOCUPRINT 96/DOCUPRINT 96MX LPS FORMS CREATION GUIDE• If the form names on the invocation line and in the FSL aredifferent, the compilation is aborted and a single sheet isprinted. It contains the heading for the page and the portion ofthe FSL that was processed before the security violation wasdetected.In this case, a security violation message would still appear and thecompilation would abort, but a single page would be printedcontaining the page heading and the FSL line “FORM TRYIT1;”Example 1 FDL TRYIT,TRAYThis command causes the system to compile the FSL named“TRYIT” (provided it does not contain errors), generate the sourcestatement, print a copy of the statement and the form, and deliverboth to the SAMPLE tray.If you do not include the word TRAY in your command, the printout isdelivered to the currently active bin.Example 2 If you want to compile the form but you do not want a printout of theform just yet, enter the following:FDL TRYIT,NOPRINTThe FSL compiles, but the form and the source statement does notprint.Debugging and modifying the fileWhenever you first create a file, it rarely produces the form exactly asyou imagined it to look.• You may have syntax errors which prevent the form fromprinting.• You may have successfully followed all the FDL rules andproduced a form, but you inadvertently placed some text orgraphic on the form in the wrong place or misspelled a word.• Everything comes out the way you planned it, but the printedform just doesn’t look right (that is, it would look better if thatbox were a little larger).It is easy to identify the specific cause of the problem (debugging)and correct it (modifying). YourDocuPrint 96/DocuPrint 96MXOperations Reference provides a complete explanation on how tomodify your FSL file.Example: TRYIT1.FSL is a secured file:You enter: FDL TRYIT,TRAYFSL contains: FORM TRYIT1;GRID IS 1 INCH;END;END;