job-state-reasons (Job Only)
Identifies the reasons that a job is in the held, terminating, or retained state. If this attribute value is blank, the job is not in one of these states.
You can use the synonym state-reasons or reasons.
InfoPrint sets this value to any of these fixed values:
|aborted-by-system||The server aborted the job.|
|cancelled-by-operator||An operator or system administrator cancelled the job.|
|cancelled-by-user||The person who submitted the job cancelled the job.|
|completed||The job completed without any errors or warnings that InfoPrint could detect. This does not guarantee that there were no errors of any kind.|
|completed-successfully||The job completed without any errors or warnings.|
|completed-with-errors||The job completed with errors. Based on the dss-job-message-disposition actual destination attribute, the messages associated with the errors either print at the end of the job or in a message log. See dss-job-message-disposition.|
|deadline-in-jeopardy||The value of the estimated-completion-time attribute for the job is later than the time specified by the job-deadline-time attribute; or the time specified by the job-deadline-time attribute is past.|
|job-hold-set||The job is in a queue and the job-hold job attribute of the job has a true value.|
|job-print-after-specified||The job is in a queue and the time specified by the job-print-after job attribute has not yet occurred.|
|pull-print||The job is in a queue destined for an actual destination with pull-print-printer set to true or in an AnyPlace queue and the time period specified by the pull-print-job-timeout server attribute has not yet past.|
|required-resource-not-ready||The job is in a queue but InfoPrint cannot schedule it because one or more of the resources required by the job (such as media, fonts, and so on) are not ready on any of the actual destinations that can accept the job. The job's required-resource-not-ready attribute identifies the resources that need to be made ready.|
|required-resource-not-supported||The job is in a queue but InfoPrint cannot schedule it because none of the actual destinations that can accept the job support one or more of the resources required by the job (such as media, fonts, and so on). The job's required-resource-not-supported attribute identifies the resources that are not supported.|
|retained-immediately||The job is not put on a queue or scheduled when it is received by the InfoPrint server. The job is immediately processed according to the values of its retention period attributes.|
|rip-and-hold-completed||The RIP has successfully converted the job. The job has not been scheduled because the value of the job-rip-action attribute is rip-and-hold or is rip-and-hold-ignore-ready.|
|rip-completed||A job with job-rip-action=rip-and-print-ignore-ready has been RIPped, but InfoPrint cannot schedule it because one or more of the resources required by the job are not ready on any of the actual destinations that can accept the job. Jobs held for this reason are released automatically when the required resources become ready.|
|rip-failed||The RIP failed to convert the job.
Note: You will see this reason only if the job is retained or if the value of the requeue-failed-jobs queue attribute is true. When neither of these conditions is true, jobs that fail to rip are discarded.
No default value