User guide

UTILITIES WINDOW
5-10 XEROX DOCUPRINT 180 LPS PC UI REFERENCE
Guidelines for PC Editor You must be careful when managing controller files on the PC UI.
The controller file structure is record-oriented and information about
the file’s structure is maintained within the controller operating
system. The controller file naming convention signifies the type and
structure of the file to the System UI Software. In order to access
these files on the PC UI and to correctly transfer the file back to the
controller with the correct file type and record size, it is necessary for
the user to be aware of certain operational procedures. Please note
that these guidelines do not apply to files residing only on the PC or
intended for non-controller processing.
• Do not mix the types of editors being used.
The LPS line editor (provided by the controller EDI task)
performs the edit of the file on the controller disk. The PC
Editor performs the edit of the file on the PC hard disk or PC
floppy.
If a file is retrieved from the controller and then edited using the
LPS line editor, any changes are made to the file residing on
the controller disk, not to the retrieved file on the PC disk.
• Use the PC Editor options to edit an controller file.
In order to maintain controller file type integrity, you are
cautioned against using the file transfer or file copy/convert
feature and then selecting the PC Editor utility to edit an
controller file. The recommended procedure is to use the PC
Editor window options specifying the controller as the source
device and then selecting the open/edit target. The PC Editor
will automatically initiate the transfer of a file from the controller
transfer. When the changes to the file have been made, using
the editor to SAVE the file will initiate the transfer of the file from
the PC to the controller in the correct format.
• Use the PC file management features for files on the PC floppy.
To copy or save files from the PC hard disk to the PC floppy,
the file management features provided within the PC UI are to
be used. If DOS commands or other non-PC UI utilities are
used, the information needed to maintain file type integrity for
PC UI processing will not be copied to the floppy. This can
result in files that are not correctly formaed or useable by the
PC UI for subsequent processing.
• Adhere to controller file extension naming conventions.
When creating new controller files or copying/saving existing
controller files on the PC UI, you are cautioned to maintain the
controller file extensions and change only the file name.
Incorrect and unexpected results can occur if you change the
file extension or copies a file to one with a different file
extension. The resulting file transferred back to the controller
may no longer have the correct file structure or record type.
When using the file conversion feature, the file extension must
be changed to reflect the new file type.
Predefined file types are used by the PC UI for controller files
with the following extensions: CMD, DAT, FSL, ISL, LIB, JSL,
MSC, PCH, TMP.
• Follow the file naming rules of the DP 180 LPS component.
Controller file names may consist of no more than six
characters.