1dcmpsrcv(1) OFFIS DCMTK dcmpsrcv(1)
2
6 dcmpsrcv - Network receive for presentation state viewer
7
9 dcmpsrcv [options] config-file
10
12 The dcmpsrcv application is invoked by the Grayscale Softcopy
13 Presentation State Viewer and is not intended to be invoked manually.
14 The application reads the common configuration file which is shared
15 between the different components of the viewer and opens a TCP/IP
16 socket on which incoming association requests are accepted. The
17 application sparks a separate process for each DICOM connection. It
18 supports the same storage SOP classes as the storescp utility as SCP,
19 but does not support encapsulated transfer syntaxes. Incoming images
20 are stored in the common viewer database. See the full conformance
21 statement for further details.
22
24 config-file configuration file to be read
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 -t --terminate
54 terminate all running receivers
55
57 The level of logging output of the various command line tools and
58 underlying libraries can be specified by the user. By default, only
59 errors and warnings are written to the standard error stream. Using
60 option --verbose also informational messages like processing details
61 are reported. Option --debug can be used to get more details on the
62 internal activity, e.g. for debugging purposes. Other logging levels
63 can be selected using option --log-level. In --quiet mode only fatal
64 errors are reported. In such very severe error events, the application
65 will usually terminate. For more details on the different logging
66 levels, see documentation of module 'oflog'.
67 In case the logging output should be written to file (optionally with
69 logfile rotation), to syslog (Unix) or the event log (Windows) option
70 --log-config can be used. This configuration file also allows for
71 directing only certain messages to a particular output stream and for
72 filtering certain messages based on the module or application where
73 they are generated. An example configuration file is provided in
74 <etcdir>/logger.cfg).
75
77 All command line tools use the following notation for parameters:
78 square brackets enclose optional values (0-1), three trailing dots
79 indicate that multiple values are allowed (1-n), a combination of both
80 means 0 to n values.
81 Command line options are distinguished from parameters by a leading '+'
83 or '-' sign, respectively. Usually, order and position of command line
84 options are arbitrary (i.e. they can appear anywhere). However, if
85 options are mutually exclusive the rightmost appearance is used. This
86 behaviour conforms to the standard evaluation rules of common Unix
87 shells.
88 In addition, one or more command files can be specified using an '@'
90 sign as a prefix to the filename (e.g. @command.txt). Such a command
91 argument is replaced by the content of the corresponding text file
92 (multiple whitespaces are treated as a single separator unless they
93 appear between two quotation marks) prior to any further evaluation.
94 Please note that a command file cannot contain another command file.
95 This simple but effective approach allows to summarize common
96 combinations of options/parameters and avoids longish and confusing
97 command lines (an example is provided in file <datadir>/dumppat.txt).
98
100 The dcmpsrcv utility will attempt to load DICOM data dictionaries
101 specified in the DCMDICTPATH environment variable. By default, i.e. if
102 the DCMDICTPATH environment variable is not set, the file
103 <datadir>/dicom.dic will be loaded unless the dictionary is built into
104 the application (default for Windows).
105 The default behaviour should be preferred and the DCMDICTPATH
107 environment variable only used when alternative data dictionaries are
108 required. The DCMDICTPATH environment variable has the same format as
109 the Unix shell PATH variable in that a colon (':') separates entries.
110 On Windows systems, a semicolon (';') is used as a separator. The data
111 dictionary code will attempt to load each file specified in the
112 DCMDICTPATH environment variable. It is an error if no data dictionary
113 can be loaded.
114
116 <etcdir>/dcmpstat.cfg - sample configuration file
117
119 dcmpssnd(1), storescp(1)
120
122 Copyright (C) 1998-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
123 Germany.
124Version 3.6.0 6 Jan 2011 dcmpsrcv(1)