1dcmpsrcv(1)                       OFFIS DCMTK                      dcmpsrcv(1)
2
3
4

NAME

6       dcmpsrcv - Network receive for presentation state viewer
7
8

SYNOPSIS

10       dcmpsrcv [options] config-file
11

DESCRIPTION

13       The   dcmpsrcv   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  and  opens  a  TCP/IP
17       socket  on  which  incoming  association  requests  are  accepted.  The
18       application sparks a separate process for  each  DICOM  connection.  It
19       supports  the  same storage SOP classes as the storescp utility as SCP,
20       but does not support encapsulated transfer  syntaxes.  Incoming  images
21       are  stored  in  the  common  viewer database. See the full conformance
22       statement for further details.
23

PARAMETERS

25       config-file  configuration file to be read
26

OPTIONS

28   general options
29         -h   --help
30                print this help text and exit
31
32              --version
33                print version information and exit
34
35              --arguments
36                print expanded command line arguments
37
38         -q   --quiet
39                quiet mode, print no warnings and errors
40
41         -v   --verbose
42                verbose mode, print processing details
43
44         -d   --debug
45                debug mode, print debug information
46
47         -ll  --log-level  [l]evel: string constant
48                (fatal, error, warn, info, debug, trace)
49                use level l for the logger
50
51         -lc  --log-config  [f]ilename: string
52                use config file f for the logger
53
54         -t   --terminate
55                terminate all running receivers
56

LOGGING

58       The level of logging output of  the  various  command  line  tools  and
59       underlying  libraries  can  be  specified by the user. By default, only
60       errors and warnings are written to the  standard  error  stream.  Using
61       option  --verbose  also  informational messages like processing details
62       are reported. Option --debug can be used to get  more  details  on  the
63       internal  activity,  e.g.  for debugging purposes. Other logging levels
64       can be selected using option --log-level. In --quiet  mode  only  fatal
65       errors  are reported. In such very severe error events, the application
66       will usually terminate. For  more  details  on  the  different  logging
67       levels, see documentation of module 'oflog'.
68
69       In  case  the logging output should be written to file (optionally with
70       logfile rotation), to syslog (Unix) or the event log  (Windows)  option
71       --log-config  can  be  used.  This  configuration  file also allows for
72       directing only certain messages to a particular output stream  and  for
73       filtering  certain  messages  based  on the module or application where
74       they are generated.  An  example  configuration  file  is  provided  in
75       <etcdir>/logger.cfg.
76

COMMAND LINE

78       All  command  line  tools  use  the  following notation for parameters:
79       square brackets enclose optional  values  (0-1),  three  trailing  dots
80       indicate  that multiple values are allowed (1-n), a combination of both
81       means 0 to n values.
82
83       Command line options are distinguished from parameters by a leading '+'
84       or  '-' sign, respectively. Usually, order and position of command line
85       options are arbitrary (i.e. they  can  appear  anywhere).  However,  if
86       options  are  mutually exclusive the rightmost appearance is used. This
87       behavior conforms to the  standard  evaluation  rules  of  common  Unix
88       shells.
89
90       In  addition,  one  or more command files can be specified using an '@'
91       sign as a prefix to the filename (e.g. @command.txt).  Such  a  command
92       argument  is  replaced  by  the  content of the corresponding text file
93       (multiple whitespaces are treated as a  single  separator  unless  they
94       appear  between  two  quotation marks) prior to any further evaluation.
95       Please note that a command file cannot contain  another  command  file.
96       This  simple  but  effective  approach  allows  one to summarize common
97       combinations of options/parameters and  avoids  longish  and  confusing
98       command lines (an example is provided in file <datadir>/dumppat.txt).
99

ENVIRONMENT

101       The  dcmpsrcv  utility  will  attempt  to  load DICOM data dictionaries
102       specified in the DCMDICTPATH environment variable. By default, i.e.  if
103       the   DCMDICTPATH   environment   variable   is   not   set,  the  file
104       <datadir>/dicom.dic will be loaded unless the dictionary is built  into
105       the application (default for Windows).
106
107       The   default   behavior   should  be  preferred  and  the  DCMDICTPATH
108       environment variable only used when alternative data  dictionaries  are
109       required.  The  DCMDICTPATH environment variable has the same format as
110       the Unix shell PATH variable in that a colon (':')  separates  entries.
111       On  Windows systems, a semicolon (';') is used as a separator. The data
112       dictionary code will  attempt  to  load  each  file  specified  in  the
113       DCMDICTPATH  environment variable. It is an error if no data dictionary
114       can be loaded.
115

FILES

117       <etcdir>/dcmpstat.cfg - sample configuration file
118

SEE ALSO

120       dcmpssnd(1), storescp(1)
121
123       Copyright (C) 1998-2014 by OFFIS e.V., Escherweg  2,  26121  Oldenburg,
124       Germany.
125
126
127
128Version 3.6.4                   Thu Nov 29 2018                    dcmpsrcv(1)
Impressum