![]() |
||||||||
![]() |
||||||||
![]() |
![]() |
![]() |
![]() |
![]() |
||||
![]() |
||||||||
Products | Support | Download | Contact | |||||
![]() |
Contents | Index | About the Icons
ScriptServer® for Open VMS allows a high degree of customization through the use of setup modules. (The new ScriptServer® PAN Printing System provides equivalent functionality with resources.) These modules are downloaded from the device control library at various points in the output stream according to the particular setup module usage.
The order that setup modules are downloaded is:
MODULE TYPE | INVOCATION METHOD |
emulation setup | PRINT/PARAM=DATA_TYPE=emulation |
job setup | SSV$queue_JOB_SETUP_MODULES logical |
file setup* | PRINT/SETUP=modules |
ASCII/PS/HPGL prolog* | PRINT/PARAM=DATA_TYPE=data_type |
form setup* | DEFINE/FORM/SETUP=modules |
page setup *^ | DEFINE/FORM/PAGE_SETUP=modules |
emulation reset | PRINT/PARAM=DATA_TYPE=emulation |
* Sent once for each file in the job | |
*^ Page setup modules are downloaded once per page and are triggered by form feed characters in ASCII files. |
It is important to note that images and graphics placed on the page can become
erased by PostScript commands later in the data stream. These erasures can be
done explicitly with the erasepage and fill operators, or implicitly by operators
such as: initgraphics, showpage or the tray selection commands (e.g. lettertray).
NOTE: Although it is GrayMatter's policy to provide the highest
level of technical support, we cannot assume responsibility for debugging PostScript
code not written by GrayMatter Software.
© 2020 GrayMatter Software Corporation | ![]() |
Privacy policy | ![]() |
Terms of use |