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