1termscu(1) OFFIS DCMTK termscu(1)
2
3
4
6 termscu - DICOM termination SCU
7
9 termscu [options] peer port
10
12 The termscu application implements a Service Class User (SCU) for
13 DCMTK's private Shutdown SOP Class. It tries to negotiate this private
14 Shutdown SOP Class with a Service Class Provider (SCP) which (if this
15 feature is implemented) will immediately shutdown after refusing the
16 association. The application can be used to shutdown some of DCMTK's
17 server applications.
18
20 peer hostname of DICOM peer
21
22 port tcp/ip port number of peer
23
25 general options
26 -h --help
27 print this help text and exit
28
29 --version
30 print version information and exit
31
32 --arguments
33 print expanded command line arguments
34
35 -q --quiet
36 quiet mode, print no warnings and errors
37
38 -v --verbose
39 verbose mode, print processing details
40
41 -d --debug
42 debug mode, print debug information
43
44 -ll --log-level [l]evel: string constant
45 (fatal, error, warn, info, debug, trace)
46 use level l for the logger
47
48 -lc --log-config [f]ilename: string
49 use config file f for the logger
50
51 network options
52 application entity titles:
53
54 -aet --aetitle [a]etitle: string
55 set my calling AE title (default: ECHOSCU)
56
57 -aec --call [a]etitle: string
58 set called AE title of peer (default: ANY-SCP)
59
60 other network options:
61
62 -pdu --max-pdu [n]umber of bytes: integer (4096..131072)
63 set max receive pdu to n bytes (default: 16384)
64
66 DICOM Conformance
67 The termscu application supports the following SOP Classes as an SCU:
68
69 PrivateShutdownSOPClass 1.2.276.0.7230010.3.4.1915765545.18030.917282194.0
70
72 The level of logging output of the various command line tools and
73 underlying libraries can be specified by the user. By default, only
74 errors and warnings are written to the standard error stream. Using
75 option --verbose also informational messages like processing details
76 are reported. Option --debug can be used to get more details on the
77 internal activity, e.g. for debugging purposes. Other logging levels
78 can be selected using option --log-level. In --quiet mode only fatal
79 errors are reported. In such very severe error events, the application
80 will usually terminate. For more details on the different logging
81 levels, see documentation of module 'oflog'.
82
83 In case the logging output should be written to file (optionally with
84 logfile rotation), to syslog (Unix) or the event log (Windows) option
85 --log-config can be used. This configuration file also allows for
86 directing only certain messages to a particular output stream and for
87 filtering certain messages based on the module or application where
88 they are generated. An example configuration file is provided in
89 <etcdir>/logger.cfg).
90
92 All command line tools use the following notation for parameters:
93 square brackets enclose optional values (0-1), three trailing dots
94 indicate that multiple values are allowed (1-n), a combination of both
95 means 0 to n values.
96
97 Command line options are distinguished from parameters by a leading '+'
98 or '-' sign, respectively. Usually, order and position of command line
99 options are arbitrary (i.e. they can appear anywhere). However, if
100 options are mutually exclusive the rightmost appearance is used. This
101 behaviour conforms to the standard evaluation rules of common Unix
102 shells.
103
104 In addition, one or more command files can be specified using an '@'
105 sign as a prefix to the filename (e.g. @command.txt). Such a command
106 argument is replaced by the content of the corresponding text file
107 (multiple whitespaces are treated as a single separator unless they
108 appear between two quotation marks) prior to any further evaluation.
109 Please note that a command file cannot contain another command file.
110 This simple but effective approach allows to summarize common
111 combinations of options/parameters and avoids longish and confusing
112 command lines (an example is provided in file <datadir>/dumppat.txt).
113
115 The termscu utility will attempt to load DICOM data dictionaries
116 specified in the DCMDICTPATH environment variable. By default, i.e. if
117 the DCMDICTPATH environment variable is not set, the file
118 <datadir>/dicom.dic will be loaded unless the dictionary is built into
119 the application (default for Windows).
120
121 The default behaviour should be preferred and the DCMDICTPATH
122 environment variable only used when alternative data dictionaries are
123 required. The DCMDICTPATH environment variable has the same format as
124 the Unix shell PATH variable in that a colon (':') separates entries.
125 On Windows systems, a semicolon (';') is used as a separator. The data
126 dictionary code will attempt to load each file specified in the
127 DCMDICTPATH environment variable. It is an error if no data dictionary
128 can be loaded.
129
131 Copyright (C) 2005-2010 by OFFIS e.V., Escherweg 2, 26121 Oldenburg,
132 Germany.
133
134
135
136Version 3.6.0 6 Jan 2011 termscu(1)