The queue is blocked, i.e. you cannot submit a JDF ticket, when:
Access to the control panel requires login
PRISMAsync Print Server is in Transaction Printing mode
If the queue is blocked and the state of a queue entry is submitted/hold/resumed/aborted/removed, the return code is 112. The reason for the blocked queue is also added to /Response/Notification/Comment.
Use a JMF message to submit the JDF ticket over HTTP in one of the following methods:
HTTP reference to JDF in JMF message SubmitQueueEntry
Meaning: JMF + JDF in URL + PDF in URL.
MIME package with JMF message SubmitQueueEntry combined with JDF ticket
Meaning: MIME package (containing JMF + JDF) + PDF in URL.
MIME package with JMF message SubmitQueueEntry, JDF ticket and PDL (PDF) data all combined.
Meaning: MIME package containing (JMF + JDF + PDF). This way to submit is known as MJM.
The JDF ticket MUST contain an HTTP URL reference to the PDL (PDF) data.
The reference to the JDF ticket in JMF message SubmitQueueEntry.
The QueueSubmissionParams must contain one URL reference to a JDF ticket. The URL must be either:
HTTP
cid: (in case of MIME submission)
The JDF ticket must be available for download during submission. If the JDF ticket cannot be retrieved via HTTP, error 120 (URL not accessible) will be sent in response to the message SubmitQueueEntry.
The PRISMAsync Print Server no longer needs the files after sending the JMF message ReturnQueueEntry.
Syntax
XPath: /JMF/Command[@Type=”SubmitQueueEntry”]/QueueSubmissionParams@URL
Example - Reference to PDL data in the JDF ticket
<JMF>
<Command ID="123456" Type="SubmitQueEntry">
<QueueSubmissionParams URL="http://somewhere/JobTicket.jdf"/>
</Command>
</JMF>