1dcmpssnd(1) OFFIS DCMTK dcmpssnd(1)
2
6 dcmpssnd - Network send for presentation state viewer
7
9 dcmpssnd [options] config-file target study [series] [instance]
10
12 The dcmpssnd 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, attempts to establish a
16 DICOM association with the selected target and, if successful, selects
17 the required DICOM instances from the viewer's database and transmits
18 them using the DICOM storage service class, which is supported as SCU.
19 When transmission is finished (successfully or unsuccessfully), the
20 application terminates. This application supports the same storage SOP
21 classes as the storescu utility, but does not support encapsulated
22 transfer syntaxes. See the full conformance statement for further
23 details.
24
26 config-file configuration file to be read
27 target symbolic identifier of send target in config file
29 study study instance UID of study in database to be sent
31 series series instance UID (default: send complete study)
33 instance SOP instance UID (default: send complete series)
35
37 general options
38 -h --help
39 print this help text and exit
40 --version
42 print version information and exit
43 --arguments
45 print expanded command line arguments
46 -q --quiet
48 quiet mode, print no warnings and errors
49 -v --verbose
51 verbose mode, print processing details
52 -d --debug
54 debug mode, print debug information
55 -ll --log-level [l]evel: string constant
57 (fatal, error, warn, info, debug, trace)
58 use level l for the logger
59 -lc --log-config [f]ilename: string
61 use config file f for the logger
62
64 The level of logging output of the various command line tools and
65 underlying libraries can be specified by the user. By default, only
66 errors and warnings are written to the standard error stream. Using
67 option --verbose also informational messages like processing details
68 are reported. Option --debug can be used to get more details on the
69 internal activity, e.g. for debugging purposes. Other logging levels
70 can be selected using option --log-level. In --quiet mode only fatal
71 errors are reported. In such very severe error events, the application
72 will usually terminate. For more details on the different logging
73 levels, see documentation of module 'oflog'.
74 In case the logging output should be written to file (optionally with
76 logfile rotation), to syslog (Unix) or the event log (Windows) option
77 --log-config can be used. This configuration file also allows for
78 directing only certain messages to a particular output stream and for
79 filtering certain messages based on the module or application where
80 they are generated. An example configuration file is provided in
81 <etcdir>/logger.cfg).
82
84 All command line tools use the following notation for parameters:
85 square brackets enclose optional values (0-1), three trailing dots
86 indicate that multiple values are allowed (1-n), a combination of both
87 means 0 to n values.
88 Command line options are distinguished from parameters by a leading '+'
90 or '-' sign, respectively. Usually, order and position of command line
91 options are arbitrary (i.e. they can appear anywhere). However, if
92 options are mutually exclusive the rightmost appearance is used. This
93 behaviour conforms to the standard evaluation rules of common Unix
94 shells.
95 In addition, one or more command files can be specified using an '@'
97 sign as a prefix to the filename (e.g. @command.txt). Such a command
98 argument is replaced by the content of the corresponding text file
99 (multiple whitespaces are treated as a single separator unless they
100 appear between two quotation marks) prior to any further evaluation.
101 Please note that a command file cannot contain another command file.
102 This simple but effective approach allows to summarize common
103 combinations of options/parameters and avoids longish and confusing
104 command lines (an example is provided in file <datadir>/dumppat.txt).
105
107 The dcmpssnd utility will attempt to load DICOM data dictionaries
108 specified in the DCMDICTPATH environment variable. By default, i.e. if
109 the DCMDICTPATH environment variable is not set, the file
110 <datadir>/dicom.dic will be loaded unless the dictionary is built into
111 the application (default for Windows).
112 The default behaviour should be preferred and the DCMDICTPATH
114 environment variable only used when alternative data dictionaries are
115 required. The DCMDICTPATH environment variable has the same format as
116 the Unix shell PATH variable in that a colon (':') separates entries.
117 On Windows systems, a semicolon (';') is used as a separator. The data
118 dictionary code will attempt to load each file specified in the
119 DCMDICTPATH environment variable. It is an error if no data dictionary
120 can be loaded.
121
123 <etcdir>/dcmpstat.cfg - sample configuration file
124
126 dcmpsrcv(1), storescu(1)
127
129 Copyright (C) 1998-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
130 Germany.
131Version 3.6.0 6 Jan 2011 dcmpssnd(1)