Xerox 4650 ユーザーズマニュアル
COMPILING AND PRINTING FORMS
File storage
A large number of forms may be stored in the forms source
directory (uncompiled) and form directory (compiled) on the
system disks. Two files with the same name cannot be stored in
the same directory. The number of forms that can be stored
depends on the amount of data required to describe each form
and the total amount of disk space allocated to the libraries.
directory (uncompiled) and form directory (compiled) on the
system disks. Two files with the same name cannot be stored in
the same directory. The number of forms that can be stored
depends on the amount of data required to describe each form
and the total amount of disk space allocated to the libraries.
The forms are filed in the system under their identifying names.
The information stored in the file includes the identifier, the
encoded form, and the list of specified fonts and logos. The
original source statements that created the forms description are
stored separately under the same identifier.
The information stored in the file includes the identifier, the
encoded form, and the list of specified fonts and logos. The
original source statements that created the forms description are
stored separately under the same identifier.
A list of all of the forms stored in the directory, a sample of each,
and the source statement lists can all be obtained using operator
commands.
and the source statement lists can all be obtained using operator
commands.
PROOF
The forms compiler makes it possible to compile a form and
delete the .FRM file after it has been printed. If you use this
option, less disk space is consumed by resident form files. The
PROOF option has the following format:
delete the .FRM file after it has been printed. If you use this
option, less disk space is consumed by resident form files. The
PROOF option has the following format:
FDL
filename
PROOF
If the form is compiled without errors, the .FRM file and the
source statement and/or summary sheet is printed. Since the
PROOF option deletes it, there is no form file on the disk.
source statement and/or summary sheet is printed. Since the
PROOF option deletes it, there is no form file on the disk.
When you use the PROOF option, the form file that is created is
given a pseudonym that differs from the one specified in the
.FSL. Therefore, when TRYIT.FSL is compiled, for example, the
form that is created is not automatically named TRYIT.FRM. The
newly created .FRM file is given a different name, and it is this
renamed form that is eventually deleted. Due to this safeguard,
if a file named TRYIT.FRM already exists on the system disk, that
form still exists after the new .FRM file is compiled and deleted.
given a pseudonym that differs from the one specified in the
.FSL. Therefore, when TRYIT.FSL is compiled, for example, the
form that is created is not automatically named TRYIT.FRM. The
newly created .FRM file is given a different name, and it is this
renamed form that is eventually deleted. Due to this safeguard,
if a file named TRYIT.FRM already exists on the system disk, that
form still exists after the new .FRM file is compiled and deleted.
Secured files
•
If you attempt to overwrite a secured file while compiling a
form, a security violation message displays, and the
compilation process is aborted.
form, a security violation message displays, and the
compilation process is aborted.
•
If you attempt to overwrite a secured file having the same
name on both the task invocation line and in the .FSL, a
security violation message is displayed and the form is
aborted.
name on both the task invocation line and in the .FSL, a
security violation message is displayed and the form is
aborted.
For example, TRYIT1.FSL is a secured file.
You enter:
FDL
TRYIT1
TRAY
The .FSL contains:
FORM TRYIT1;
GRID IS 1 INCH;
END;END;
GRID IS 1 INCH;
END;END;
In this case, a security violation message displays and
compilation aborts.
compilation aborts.
XEROX 4050/4090/4450/4650 LPS FORMS CREATION GUIDE
3-5