JMF error messages
This documents describes how error messages (after submitting the JDF of a job) which are received
from a JDF partner via a JMF message are logged and visible as from version 7.15 R0.
Searching an error message
If problems occur for a given job, look-up the job via the JDF Job management module and for the
selected job, the related JMF messages are shown in individual records in the lower grid. This grid
has a column ‘Errors’. If a red error indicator is present in this column for a given message, this
indicates that there were error messages logged when sending/receiving that message.
When you double-click this grid, the ‘JMF controllers status’ screenopens, which contains the same
grid, and some tabs showing the content of the (selected) JMF message and its answer. If there was
an error message logged by Cerm, it also shows an ‘Error message’ tab where you can read the
message.
You can also open the same screen from the Job Explorer or Jobs Main screen via the button ‘JMF
status’:
How error messages are logged
There are two ways how error messages are logged.
The first one is used to log error messages from Esko. After sending a JMF with the JDF to Esko (type
SubmitQueueEntry), Esko always sends a JMF back, of the type ReturnQueueEntry. If something
went wrong, the <ReturnQueueEntryParams> tag in this returned message will have the attribute
‘Aborted=xxx’, with ‘xxx’ the ID’s of the JDF Node(s) which have the Status=”Aborted”. Cerm will then
look in the JDF file for all the Auditpool/Notification[@Class=’Error’]/Comment nodes and save the
texts in a separate file. In the example in the screenshots, the JDF returned by Esko will have
contained something like:
A second way of logging error messages is by looking at the answer of the SubmitQueueEntry
Message. If the Response[@ReturnCode] is not equal to 0, something went wrong. Cerm will then
look for Notifications in the JMF answer and save the texts in the Notification/Comment nodes along
with the return code. The next screenshots show an example of this.
Free status action tag
Besides looking for error messages, Cerm will also change any free status (of the job) that has a
status value with action tag ‘JobSubmissionError’ (see the Cerm Help for more info about free
statusses and action tags). In other words: you can configure a free status for jobs, so that if
something went wrong with the submission of the JDF, the free status is set to a certain value.