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