By enabling the option "Non-JMF job management", non-JMF submitted jobs can be monitored and managed by JMF. This option can be enabled via the settings editor:
NOTE
The information below is only valid if this option is enabled.
QueueEntryIDs will have a prefix depending on the protocol used to send the jobs.
For jobs sent via LPR and IPP, e.g. LPD-ff74e542-32a0-4d90-bad9-ba65a0bed0c
For jobs sent via HotFolder, e.g. SMB-ff74e542-32a0-4d90-bad9-ba65a0bed0c
For jobs sent via Socket, e.g. RAW-ff74e542-32a0-4d90-bad9-ba65a0bed0c
To monitor non-JMF submitted jobs each JMF query that invokes the status of the queue will report the non-JMF QueueEntryIDs.
Examples of JMF queries:
QueryQueueStatus
QueryStatus (QueueInfo="true")
To manage non-JMF jobs, the following JMF commands can be used:
AbortQueueEntry
ResumeQueueEntry
HoldQueueEntry
RemoveQueueEntry
Regardless of in which order the jobs arrive in the system, within the JMF interface the jobs submitted via JMF will be reported first in a JMF QueryStatus or QueryQueStatus response, and then those who are sent through the other 4 submission channels.
A JMF AbortQueueEntry of a Non-JMF QueueEntryID is equivalent to a RemoveQueueEntry. This means both the job and the QueueEntryID will be deleted from the printer.
No AuditPool data will be reported through the JMF channel for non-JMF Jobs.
The QueueEntryID of a non-JMF job exists as long as the job exists on the printer.
Job completion for a non-JMF job will only be reported in the JMF channel when “Store printed jobs” is enabled.
No AuditPool or JobPhase data will be reported through the JMF channel (JDF ticket, counters, number of sheets used, ink usage, etc.) for non-JMF jobs.
For the aborted Non-JMF jobs, the user will not be able to retrieve a JMF message with the abort reason.
Using a QueryQueueStatus subscription:
When a Non-JMF job is "Aborted": PRISMAsync does not send a JMF signal.