ExcelliPrint Jobs and Log
The ExcelliPrint® window has the queues on the left and two tabs on the right: Jobs and Log. Closing the window doesn’t stop the service or any queue.
Jobs
The Jobs tab lists every job received, newest first. Click a column heading to sort by it; drag headings to rearrange the columns, and right-click them to show or hide columns.
| ID | ExcelliPrint’s number for the job, also available to file names |
|---|---|
| Arrived, Completed | When the job started arriving and when its output was delivered |
| Port, Client IP | The queue’s port, and the host’s address |
| Job Name, Job Key, User ID, Spool ID, File Name, Form, Lib Name, Output Queue | The spooled file’s details, as the host sent them. IBM i fills all eight; z/OS fills job name, job key and form |
| Format, Output Path | The output’s type, and where it went: the file, the printer or the email address |
| Pages | The pages in the output |
| Status | processing, completed, failed or interrupted |
With a job selected, Job > Open Output opens its file, Job > Show in Folder opens the folder with the file selected, and Job > Properties shows everything about the job in one window, including the details the host sent under their IBM names.
A job that can’t be finished is marked failed, and a partial file is never delivered.
Log
The Log tab shows the service’s events: jobs received, completed and failed, warnings, connections refused, service start and stop, and license changes. A failed job’s entry says why it failed, for example a folder that couldn’t be reached, a password that was refused, or a mail server’s reply. Right-click to copy entries or export the log.
Job history
ExcelliPrint keeps the Jobs list and the Log for a few days, then removes old entries so its database stays small: by default 7 days of jobs and 3 days of log messages, adjustable from 1 to 30 days in Settings > Job History. Output files are never deleted; only the list entries go.
Diagnostic logging
When support asks for more detail, Settings > Diagnostics switches on diagnostic logging for the service or the queues, without restarting anything.