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