When processing a job, Prinergy generates detailed history entries to allow you track actions performed on the job. The software considers non-essential history entries to be less important.
You can configure Prinergy to delete non-essential history entries on a regular basis—for example, every 30 days. In general, you should keep other history entries indefinitely.
The Prinergy system considers the following history entries to be non-essential:
- Element "a" submitted for processing: Indicates that a job or job element has been submitted to the JTP for processing, but is not yet queued at a particular JTP. For example, Page1 submitted at service Normalize.
- Element "a" queued at service "b": Indicates that a job or job element is queued for processing by a JTP. For example, Page1 queued at service Normalize.
- Element "a" active at JTP "b": Indicates that a job or job element is being processed. For example, Page1 active at service Normalize.
- Element "a" ended at JTP "b": Indicates that a job or job element is no longer being processed, including when a task has been cancelled. For example, Page1 stopped at service Normalize.
- Element "a" finished all processing: Indicates that a job or job element has completed processing. For example, Page1 finished at service Normalize.
- Assigned page "n" to page set "d"
- Trapping page "n" from file "x"
- Color-matching done on page "n" from file "x"
- Color-matching finished successfully
- Trapping finished successfully
- "n" traps created in "m" minutes
- No color-matching required, time in "m" minutes
- Page geometry assigned from the QuarkXPress software registration marks from file "x"
- Output device is beginning to plot the "n" separation
- No trapping required, time "m" minutes
- Output device has completed plotting the "n" separation
- An unassigned page position has been selected for output. Assigning a blank page as a substitute.
- Color-matching done on "n" objects in "m" minutes
- Warning and error messages from the RIP
See also
Controlling how long history logs are kept
Compressing the database