Skip to main content
Skip table of contents

(v13) The exitserver and startjob operators

This page applies to Harlequin v13.1r0 and later; and to Harlequin Core but not Harlequin MultiRIP.

Using exitserver enables you to make changes to the interpreter environment that persist between jobs, until you next quit the RIP. For example, if you include a call to exitserver in a page feature (for the GUI version of the RIP), the page feature operates until the call to exitserver, and anything following it is ignored. Then the job to which you have attached the page feature operates outside the server loop.

A similar function is performed by startjob , except that it runs in a Level 2 context.

When using these operators, the page device context in which the job runs is not one seen by jobs run inside the server loop. For example, you may find that the device resolution is 72 dpi. Also, read the warnings about effects on VM in [RB2].

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.