1dcmprscp(1) OFFIS DCMTK dcmprscp(1)
2
6 dcmprscp - DICOM basic grayscale print management SCP
7
9 dcmprscp [options]
10
12 The dcmprscp utility implements the DICOM Basic Grayscale Print
13 Management Service Class as SCP. It also supports the optional
14 Presentation LUT SOP Class. The utility is intended for use within the
15 DICOMscope viewer.
16 The dcmprscp utility accepts print jobs from a remote Print SCU. It
18 does not create real hardcopies but stores print jobs in the local
19 DICOMscope database as a set of Stored Print objects (one per page) and
20 Hardcopy Grayscale images (one per film box N-SET). The DICOMscope
21 application allows to load a Stored Print object created by dcmprscp
22 and to render a screen preview of the hardcopy. The dcmprscp utility
23 reads the characteristics of the printer to be emulated from the
24 configuration file.
25
27 general options
28 -h --help
29 print this help text and exit
30 --version
32 print version information and exit
33 --arguments
35 print expanded command line arguments
36 -q --quiet
38 quiet mode, print no warnings and errors
39 -v --verbose
41 verbose mode, print processing details
42 -d --debug
44 debug mode, print debug information
45 -ll --log-level [l]evel: string constant
47 (fatal, error, warn, info, debug, trace)
48 use level l for the logger
49 -lc --log-config [f]ilename: string
51 use config file f for the logger
52 -l --logfile
54 write a log file (not with --log-config)
55 # this option is available for reasons of backward
57 # compatibility only
58 processing options
60 -c --config [f]ilename: string
61 process using settings from configuration file
62 -p --printer [n]ame: string (default: 1st printer in config file)
64 select printer with identifier n from config file
65 +d --dump
67 dump all DIMSE messages
68
70 The level of logging output of the various command line tools and
71 underlying libraries can be specified by the user. By default, only
72 errors and warnings are written to the standard error stream. Using
73 option --verbose also informational messages like processing details
74 are reported. Option --debug can be used to get more details on the
75 internal activity, e.g. for debugging purposes. Other logging levels
76 can be selected using option --log-level. In --quiet mode only fatal
77 errors are reported. In such very severe error events, the application
78 will usually terminate. For more details on the different logging
79 levels, see documentation of module 'oflog'.
80 In case the logging output should be written to file (optionally with
82 logfile rotation), to syslog (Unix) or the event log (Windows) option
83 --log-config can be used. This configuration file also allows for
84 directing only certain messages to a particular output stream and for
85 filtering certain messages based on the module or application where
86 they are generated. An example configuration file is provided in
87 <etcdir>/logger.cfg).
88
90 All command line tools use the following notation for parameters:
91 square brackets enclose optional values (0-1), three trailing dots
92 indicate that multiple values are allowed (1-n), a combination of both
93 means 0 to n values.
94 Command line options are distinguished from parameters by a leading '+'
96 or '-' sign, respectively. Usually, order and position of command line
97 options are arbitrary (i.e. they can appear anywhere). However, if
98 options are mutually exclusive the rightmost appearance is used. This
99 behaviour conforms to the standard evaluation rules of common Unix
100 shells.
101 In addition, one or more command files can be specified using an '@'
103 sign as a prefix to the filename (e.g. @command.txt). Such a command
104 argument is replaced by the content of the corresponding text file
105 (multiple whitespaces are treated as a single separator unless they
106 appear between two quotation marks) prior to any further evaluation.
107 Please note that a command file cannot contain another command file.
108 This simple but effective approach allows to summarize common
109 combinations of options/parameters and avoids longish and confusing
110 command lines (an example is provided in file <datadir>/dumppat.txt).
111
113 The dcmprscp utility will attempt to load DICOM data dictionaries
114 specified in the DCMDICTPATH environment variable. By default, i.e. if
115 the DCMDICTPATH environment variable is not set, the file
116 <datadir>/dicom.dic will be loaded unless the dictionary is built into
117 the application (default for Windows).
118 The default behaviour should be preferred and the DCMDICTPATH
120 environment variable only used when alternative data dictionaries are
121 required. The DCMDICTPATH environment variable has the same format as
122 the Unix shell PATH variable in that a colon (':') separates entries.
123 On Windows systems, a semicolon (';') is used as a separator. The data
124 dictionary code will attempt to load each file specified in the
125 DCMDICTPATH environment variable. It is an error if no data dictionary
126 can be loaded.
127
129 <etcdir>/dcmpstat.cfg, <etcdir>/printers.cfg - sample configuration
130 files
131
133 dcmprscu(1)
134
136 Copyright (C) 1999-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
137 Germany.
138Version 3.6.0 6 Jan 2011 dcmprscp(1)