The functions for managing jobs are only available if the interface was started with RF_DFE_PORTS::jobPort enabled.
The rf_send_job_status_request() function may be used to query job status. It is only available if the interface was started with RF_DFE_PORTS::statusPort enabled.
◆ rf_send_job_cancel()
Send a Job Cancel message.
An immediate reply of an RF_JOB_CANCELLING message is expected. If no errors were reported, an RF_JOB_COMPLETED message should be received when each job specified has been completed.
- Parameters
-
[in] | iface_ctxt | The context handle from rf_iface_start(). |
| id | The job ID to cancel. If this is zero, cancel all jobs. |
- Returns
TRUE
if the message was successfully queued. Otherwise FALSE
. A TRUE
value doesn't necessarily mean the RIP farm received the message.
◆ rf_send_job_pause()
Send a Job Pause message.
An immediate reply of an RF_JOB_PAUSING message is expected. If no errors were reported, a notification message will be received for each job affected when the state of the job is changed. The notification will normally be RF_JOB_PAUSED, however it may also be RF_JOB_COMPLETED (if the job already had all page chunks scheduled, or was cancelled before it could be paused), it may also be RF_JOB_RESUMED and then RF_JOB_PAUSED if the job was already resuming from a previous pause. The final notification state observed should be used by the client to determine its view of the job's state.
- Parameters
-
[in] | iface_ctxt | The context handle from rf_iface_start(). |
| id | The job ID to pause. If this is zero, pause all jobs. |
- Returns
TRUE
if the message was successfully queued. Otherwise FALSE
. A TRUE
value doesn't necessarily mean the RIP farm received the message.
◆ rf_send_job_resume()
Send a Job Resume message.
An immediate reply of an RF_JOB_RESUMING message is expected. If no errors were reported, a notification message will be received for each job affected when the state of the job is changed. The notification will normally be RF_JOB_RESUMED, however it may also be RF_JOB_STARTED (if the job was paused before any pages were scheduled), RF_JOB_COMPLETED (if the job was cancelled before it could be resumed), it may also be RF_JOB_PAUSED and then RF_JOB_RESUMED if the job was in the process of pausing. The final notification state observed should be used by the client to determine its view of the job's state.
- Parameters
-
[in] | iface_ctxt | The context handle from rf_iface_start(). |
| id | The job ID to resume. If this is zero, resume all paused jobs. |
- Returns
TRUE
if the message was successfully queued. Otherwise FALSE
. A TRUE
value doesn't necessarily mean the RIP farm received the message.
◆ rf_send_job_start()
Send a Job Start message.
An immediate reply of an RF_JOB_STARTING message is expected. If there is no error reported in RF_REPLY_JOB_STARTING, an RF_JOB_STARTED message should be received when the job is scheduled and an RF_JOB_COMPLETED message should be received when the job has finished. If there is an error configuring the job, the RF_JOB_STARTED message may be omitted, and the RF_JOB_COMPLETED message will indicate the error.
- Parameters
-
[in] | iface_ctxt | The context handle from rf_iface_start(). |
[in] | params | The job information. |
- Returns
TRUE
if the message was successfully queued. Otherwise FALSE
. A TRUE
value doesn't necessarily mean the RIP farm received the message.