1dcmprscu(1) OFFIS DCMTK dcmprscu(1)
2
6 dcmprscu - Print spooler for presentation state viewer
7
10 dcmprscu [options] [dcmfile-in...]
11
13 The dcmprscu utility implements the DICOM Basic Grayscale Print
14 Management Service Class as SCU. It also supports the optional Basic
15 Annotation Box and Presentation LUT SOP Classes. The utility is
16 intended for use within the DICOMscope viewer.
17 The dcmprscu utility takes complete print jobs consisting of a Stored
19 Print object and one or more Hardcopy Grayscale objects and spools them
20 to the printer. No attempt is made to check whether the attributes
21 defined in the Stored Print object are supported by the Print SCP.
22 However, the print spooler will not attempt to use the optional
23 Annotation or Presentation LUT services if they are not successfully
24 negotiated with the Print SCP.
25 The dcmprscu utility reads the characteristics of the printer to
27 communicate with from the configuration file. Depending on the
28 printer's support for Presentation LUT, any Presentation LUT present in
29 the print job will be rendered into the hardcopy images before they are
30 spooled to the printer if necessary. If the printer does not support
31 image transmission with 12 bits/pixel (as per the configuration file),
32 the grayscale hardcopy images are down-sampled to 8 bits/pixel before
33 transmission to the printer.
34 The dcmprscu utility can be run either in 'printer mode', in which case
36 the file name of a Stored Print object must be passed, or in 'spool
37 mode', in which case commands are read periodically from a spool
38 directory.
39
41 dcmfile-in stored print file(s) to be spooled
42
44 general options
45 -h --help
46 print this help text and exit
47 --version
49 print version information and exit
50 --arguments
52 print expanded command line arguments
53 -q --quiet
55 quiet mode, print no warnings and errors
56 -v --verbose
58 verbose mode, print processing details
59 -d --debug
61 debug mode, print debug information
62 -ll --log-level [l]evel: string constant
64 (fatal, error, warn, info, debug, trace)
65 use level l for the logger
66 -lc --log-config [f]ilename: string
68 use config file f for the logger
69 print options
71 --noprint
72 do not create print-out (no n-action-rq)
73 --session-print
75 send film session n-action-rq (instead of film box)
76 --monochrome1
78 transmit basic grayscale images in MONOCHROME1
79 mode options
81 +p --print
82 printer mode, print file(s) and terminate (default)
83 +s --spool [n]ame: string
85 spooler mode, use job prefix n
86 processing options
88 -c --config [f]ilename: string
89 process using settings from configuration file
90 -p --printer [n]ame: string (default: 1st printer in cfg file)
92 select printer with identifier n from cfg file
93 +d --dump
95 dump all DIMSE messages
96 spooler options (only with –spool)
98 --sleep [d]elay: integer (default: 1)
99 sleep d seconds between spooler checks
100 basic film session options (not with –spool):
102 --copies [v]alue: integer (1..100, default: 1)
103 set number of copies to v
104 --medium-type [v]alue: string
106 set medium type to v
107 --destination [v]alue: string
109 set film destination to v
110 --label [v]alue: string
112 set film session label to v
113 --priority [v]alue: string
115 set print priority to v
116 --owner [v]alue: string
118 set film session owner ID to v
119
121 The level of logging output of the various command line tools and
122 underlying libraries can be specified by the user. By default, only
123 errors and warnings are written to the standard error stream. Using
124 option --verbose also informational messages like processing details
125 are reported. Option --debug can be used to get more details on the
126 internal activity, e.g. for debugging purposes. Other logging levels
127 can be selected using option --log-level. In --quiet mode only fatal
128 errors are reported. In such very severe error events, the application
129 will usually terminate. For more details on the different logging
130 levels, see documentation of module 'oflog'.
131 In case the logging output should be written to file (optionally with
133 logfile rotation), to syslog (Unix) or the event log (Windows) option
134 --log-config can be used. This configuration file also allows for
135 directing only certain messages to a particular output stream and for
136 filtering certain messages based on the module or application where
137 they are generated. An example configuration file is provided in
138 <etcdir>/logger.cfg.
139
141 All command line tools use the following notation for parameters:
142 square brackets enclose optional values (0-1), three trailing dots
143 indicate that multiple values are allowed (1-n), a combination of both
144 means 0 to n values.
145 Command line options are distinguished from parameters by a leading '+'
147 or '-' sign, respectively. Usually, order and position of command line
148 options are arbitrary (i.e. they can appear anywhere). However, if
149 options are mutually exclusive the rightmost appearance is used. This
150 behavior conforms to the standard evaluation rules of common Unix
151 shells.
152 In addition, one or more command files can be specified using an '@'
154 sign as a prefix to the filename (e.g. @command.txt). Such a command
155 argument is replaced by the content of the corresponding text file
156 (multiple whitespaces are treated as a single separator unless they
157 appear between two quotation marks) prior to any further evaluation.
158 Please note that a command file cannot contain another command file.
159 This simple but effective approach allows one to summarize common
160 combinations of options/parameters and avoids longish and confusing
161 command lines (an example is provided in file <datadir>/dumppat.txt).
162
164 The dcmprscu utility will attempt to load DICOM data dictionaries
165 specified in the DCMDICTPATH environment variable. By default, i.e. if
166 the DCMDICTPATH environment variable is not set, the file
167 <datadir>/dicom.dic will be loaded unless the dictionary is built into
168 the application (default for Windows).
169 The default behavior should be preferred and the DCMDICTPATH
171 environment variable only used when alternative data dictionaries are
172 required. The DCMDICTPATH environment variable has the same format as
173 the Unix shell PATH variable in that a colon (':') separates entries.
174 On Windows systems, a semicolon (';') is used as a separator. The data
175 dictionary code will attempt to load each file specified in the
176 DCMDICTPATH environment variable. It is an error if no data dictionary
177 can be loaded.
178
180 <etcdir>/dcmpstat.cfg, <etcdir>/printers.cfg - sample configuration
181 files
182
184 dcmprscp(1)
185
187 Copyright (C) 1999-2014 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
188 Germany.
189Version 3.6.4 Thu Nov 29 2018 dcmprscu(1)