System information

APPENDIX DPSLab
APPENDIX DPSLab 6
If you do not wish to changes the image size (in local area network connections, where file
size may be very high, without reducing the efficiency of sending), and you wish the target
machine to do this, OPTSIZEDISK will be increased to a sufficiently high value to prevent
processing. For example, 100000 (in bytes, 100Mbyte).
Another way of working is to adapt the image to the exact dimensions of the print size of the
target machine. It may be a requirement of this machine, and it saves processing time on it,
but it obliges the machine running the DPSLab module to perform more calculations and will
therefore reduce its performance. It is recommended only in local area network (not Internet-
based) connections where large file sizes are permitted, although it is also possible for jobs
sent to remote laboratories with reasonable print sizes and forcing a JPG format
compression.
In this case there are two options available, "Cut" and "Fit Sides", explained in greater detail
at a later point in this annex.
The PAUSE button in Dispatcher is effective in the process phase.
1.1.2 Sending jobs
Jobs are sent chronologically as they arrive, regardless of the service they are associated.
The orders accepted by the DPSLab module go from the "PENDING" to “EXECUTING” or
"BATCH EXECUTING" status as long as the image processing and sending lasts. Only when
the DPSLab module reports that these jobs have been completed successfully will these
orders pass to the "DONE" status.
If during the sending of a job there is any communication error with the remote mechanism or
laboratory, or any abnormal situation arises interrupting the process, the order will be left in
the internal status "FAILED_TO_SEND" (in DPSLab environments) and the pre-established
time will be allowed to elapse before a retry. During this waiting time DPSLab will process the
following order, if there is one. In some cases, depending on the protocol being used, the
system will be able to try to send another order of the same service even when others are in
the „FAILED TO SEND‟ status. Other protocols won‟t do that.
Once the waiting time is up, since work orders are processed cyclically, in the next round the
job will be attempted again beginning with the first file that was left pending from the previous
attempt. This is true for the LAN and FTP transfer methods. In the SELF method depends on
the protocol being used.
Throughout this process, the order is reflected in DISPATCHER in the “EXECUTING” or
"BATCH EXECUTING" status.
If this error persists, a series of attempts will be made (according to configuration) until the
job is abandoned as "FAILED", and the following pending job will be processed. DPSLab jobs
in the "FAILED" status become services with the "error" status in DISPATCHER.