4 \page dcmpsrcv Network receive for presentation state viewer
6 \page dcmpsrcv dcmpsrcv: Network receive for presentation state viewer
9 \section synopsis SYNOPSIS
12 dcmpsrcv [options] config-file
15 \section description DESCRIPTION
17 The \b dcmpsrcv application is invoked by the Grayscale Softcopy Presentation
18 State Viewer and is not intended to be invoked manually. The application
19 reads the common configuration file which is shared between the different
20 components of the viewer and opens a TCP/IP socket on which incoming
21 association requests are accepted. The application sparks a separate
22 process for each DICOM connection. It supports the same storage SOP classes
23 as the \b storescp utility as SCP, but does not support encapsulated transfer
24 syntaxes. Incoming images are stored in the common viewer database. See the
25 full conformance statement for further details.
27 \section parameters PARAMETERS
30 config-file configuration file to be read
33 \section options OPTIONS
35 \subsection general_options general options
38 print this help text and exit
41 print version information and exit
44 print expanded command line arguments
47 quiet mode, print no warnings and errors
50 verbose mode, print processing details
53 debug mode, print debug information
55 -ll --log-level [l]evel: string constant
56 (fatal, error, warn, info, debug, trace)
57 use level l for the logger
59 -lc --log-config [f]ilename: string
60 use config file f for the logger
63 terminate all running receivers
66 \section logging LOGGING
68 The level of logging output of the various command line tools and underlying
69 libraries can be specified by the user. By default, only errors and warnings
70 are written to the standard error stream. Using option \e --verbose also
71 informational messages like processing details are reported. Option
72 \e --debug can be used to get more details on the internal activity, e.g. for
73 debugging purposes. Other logging levels can be selected using option
74 \e --log-level. In \e --quiet mode only fatal errors are reported. In such
75 very severe error events, the application will usually terminate. For more
76 details on the different logging levels, see documentation of module "oflog".
78 In case the logging output should be written to file (optionally with logfile
79 rotation), to syslog (Unix) or the event log (Windows) option \e --log-config
80 can be used. This configuration file also allows for directing only certain
81 messages to a particular output stream and for filtering certain messages
82 based on the module or application where they are generated. An example
83 configuration file is provided in <em><etcdir>/logger.cfg</em>).
85 \section command_line COMMAND LINE
87 All command line tools use the following notation for parameters: square
88 brackets enclose optional values (0-1), three trailing dots indicate that
89 multiple values are allowed (1-n), a combination of both means 0 to n values.
91 Command line options are distinguished from parameters by a leading '+' or '-'
92 sign, respectively. Usually, order and position of command line options are
93 arbitrary (i.e. they can appear anywhere). However, if options are mutually
94 exclusive the rightmost appearance is used. This behaviour conforms to the
95 standard evaluation rules of common Unix shells.
97 In addition, one or more command files can be specified using an '@' sign as a
98 prefix to the filename (e.g. <em>\@command.txt</em>). Such a command argument
99 is replaced by the content of the corresponding text file (multiple
100 whitespaces are treated as a single separator unless they appear between two
101 quotation marks) prior to any further evaluation. Please note that a command
102 file cannot contain another command file. This simple but effective approach
103 allows to summarize common combinations of options/parameters and avoids
104 longish and confusing command lines (an example is provided in file
105 <em><datadir>/dumppat.txt</em>).
107 \section environment ENVIRONMENT
109 The \b dcmpsrcv utility will attempt to load DICOM data dictionaries specified
110 in the \e DCMDICTPATH environment variable. By default, i.e. if the
111 \e DCMDICTPATH environment variable is not set, the file
112 <em><datadir>/dicom.dic</em> will be loaded unless the dictionary is built
113 into the application (default for Windows).
115 The default behaviour should be preferred and the \e DCMDICTPATH environment
116 variable only used when alternative data dictionaries are required. The
117 \e DCMDICTPATH environment variable has the same format as the Unix shell
118 \e PATH variable in that a colon (":") separates entries. On Windows systems,
119 a semicolon (";") is used as a separator. The data dictionary code will
120 attempt to load each file specified in the \e DCMDICTPATH environment variable.
121 It is an error if no data dictionary can be loaded.
125 <em><etcdir>/dcmpstat.cfg</em> - sample configuration file
127 \section see_also SEE ALSO
129 <b>dcmpssnd</b>(1), <b>storescp</b>(1)
131 \section copyright COPYRIGHT
133 Copyright (C) 1998-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg, Germany.