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

NAME

6       dcmprscp - DICOM basic grayscale print management SCP
7
8

SYNOPSIS

10       dcmprscp [options]
11

DESCRIPTION

13       The  dcmprscp  utility  implements  the  DICOM  Basic  Grayscale  Print
14       Management  Service  Class  as  SCP.  It  also  supports  the  optional
15       Presentation  LUT SOP Class. The utility is intended for use within the
16       DICOMscope viewer.
17
18       The dcmprscp utility accepts print jobs from a  remote  Print  SCU.  It
19       does  not  create  real  hardcopies  but stores print jobs in the local
20       DICOMscope database as a set of Stored Print objects (one per page) and
21       Hardcopy  Grayscale  images  (one  per  film box N-SET). The DICOMscope
22       application allows one  to  load  a  Stored  Print  object  created  by
23       dcmprscp  and  to render a screen preview of the hardcopy. The dcmprscp
24       utility reads the characteristics of the printer to  be  emulated  from
25       the configuration file.
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         -l   --logfile
55                write a log file (not with --log-config)
56
57                # this option is available for reasons of backward
58                # compatibility only
59
60   processing options
61         -c  --config  [f]ilename: string
62               process using settings from configuration file
63
64         -p  --printer  [n]ame: string (default: 1st printer in config file)
65               select printer with identifier n from config file
66
67         +d  --dump
68               dump all DIMSE messages
69

LOGGING

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

COMMAND LINE

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

ENVIRONMENT

114       The dcmprscp utility will  attempt  to  load  DICOM  data  dictionaries
115       specified  in the DCMDICTPATH environment variable. By default, i.e. if
116       the  DCMDICTPATH  environment   variable   is   not   set,   the   file
117       <datadir>/dicom.dic  will be loaded unless the dictionary is built into
118       the application (default for Windows).
119
120       The  default  behavior  should  be  preferred   and   the   DCMDICTPATH
121       environment  variable  only used when alternative data dictionaries are
122       required. The DCMDICTPATH environment variable has the same  format  as
123       the  Unix  shell PATH variable in that a colon (':') separates entries.
124       On Windows systems, a semicolon (';') is used as a separator. The  data
125       dictionary  code  will  attempt  to  load  each  file  specified in the
126       DCMDICTPATH environment variable. It is an error if no data  dictionary
127       can be loaded.
128

FILES

130       <etcdir>/dcmpstat.cfg,  <etcdir>/printers.cfg  -  sample  configuration
131       files
132

SEE ALSO

134       dcmprscu(1)
135
137       Copyright (C) 1999-2022 by OFFIS e.V., Escherweg  2,  26121  Oldenburg,
138       Germany.
139
140
141
142Version 3.6.7                   Fri Apr 22 2022                    dcmprscp(1)
Impressum