SYNOPSIS

tcpprt [options] [dcmfile-in...]

DESCRIPTION

The tcpprt application implements a Service Class User (SCU) for the DICOM Basic Grayscale and/or Basic Color Print Management Service Class, depending on the configuration. Two modes of operation are supported. In interactive mode, the user can type in commands to load images, select the film layout, film size etc. and request the print server to create a hardcopy. In non-interactive mode, all layout parameters are read from the configuration file and all image files passed on the command line are sent to the Print SCP and printed.

PARAMETERS

dcmfile-in  DICOM image file(s) to be printed

OPTIONS

general options

  -h    --help
          print this help text and exit

        --version
          print version information and exit

        --arguments
          print expanded command line arguments

  -q    --quiet
          quiet mode, print no warnings and errors

  -v    --verbose
          verbose mode, print processing details

  -d    --debug
          debug mode, print debug information

  -ll   --log-level  [l]evel: string constant
          (fatal, error, warn, info, debug, trace)
          use level l for the logger

  -lc   --log-config  [f]ilename: string
          use config file f for the logger

  -i    --info
          display available --auto modes and exit

processing options

  -c    --config  [f]ilename: string (default: tcpprt.cfg)
          process using settings from configuration file

  -a    --auto  [m]ode: string
          use given noninteractive mode

  +s    --save
          save all DIMSE messages to file

network options

  -t    --target  [s]erver address and port number: string
          use given address (e.g. localhost:104)

  -aet  --aetitle  [a]etitle: string
          set my AE title (default: PS Print Server)

  -aec  --call  [a]etitle: string
          set called AE title of peer (default: PS Print Client)

  -to   --timeout  [s]econds: integer (default: unlimited)
          timeout for connection requests

subsection dcmprint_protocol_options IP protocol version

  -i4   --ipv4
          use IPv4 only (default)

  -i6   --ipv6
          use IPv6 only

  -i0   --ip-auto
          use DNS lookup to determine IP protocol

transport layer security (TLS) options

  -tls  --disable-tls
          use normal TCP/IP connection

  +tls  --enable-tls
          use secure TLS connection

DICOM Conformance

Depending on the configuration, the tcpprt application supports the following SOP Classes as an SCU:

BasicGrayscalePrintManagementMetaSOPClass  1.2.840.10008.5.1.1.9
BasicColorPrintManagementMetaSOPClass      1.2.840.10008.5.1.1.18
PrintJobSOPClass                           1.2.840.10008.5.1.1.14
BasicAnnotationBoxSOPClass                 1.2.840.10008.5.1.1.15
PresentationLUTSOPClass                    1.2.840.10008.5.1.1.23

The default behaviour of tcpprt is to propose one presentation context for each supported SOP class (abstract syntax) with the following three uncompressed transfer syntaxes. The first proposed transfer syntax is the explicit VR transfer syntax with local byte order, followed by the explicit VR transfer syntax with opposite byte order, followed by the default implicit VR transfer syntax. This behaviour can be changed in the configuration file.

LittleEndianImplicitTransferSyntax         1.2.840.10008.1.2
LittleEndianExplicitTransferSyntax         1.2.840.10008.1.2.1
BigEndianExplicitTransferSyntax            1.2.840.10008.1.2.2

The tcpprt application does not support extended negotiation.

LOGGING

The level of logging output of the various command line tools and underlying libraries can be specified by the user. By default, only errors and warnings are written to the standard error stream. Using option –verbose also informational messages like processing details are reported. Option –debug can be used to get more details on the internal activity, e.g. for debugging purposes. Other logging levels can be selected using option –log-level. In –quiet mode only fatal errors are reported. In such very severe error events, the application will usually terminate. For more details on the different logging levels, see documentation of module "oflog".

In case the logging output should be written to file (optionally with logfile rotation), to syslog (Unix) or the event log (Windows) option –log-config can be used. This configuration file also allows for directing only certain messages to a particular output stream and for filtering certain messages based on the module or application where they are generated. An example configuration file is provided in <etcdir>/logger.cfg).

COMMAND LINE

All command line tools use the following notation for parameters: square brackets enclose optional values (0-1), three trailing dots indicate that multiple values are allowed (1-n), a combination of both means 0 to n values.

Command line options are distinguished from parameters by a leading '+' or '-' sign, respectively. Usually, order and position of command line options are arbitrary (i.e. they can appear anywhere). However, if options are mutually exclusive the rightmost appearance is used. This behaviour conforms to the standard evaluation rules of common Unix shells.

In addition, one or more command files can be specified using an '@' sign as a prefix to the filename (e.g. @command.txt). Such a command argument is replaced by the content of the corresponding text file (multiple whitespaces are treated as a single separator unless they appear between two quotation marks) prior to any further evaluation. Please note that a command file cannot contain another command file. This simple but effective approach allows to summarize common combinations of options/parameters and avoids longish and confusing command lines (an example is provided in file <datadir>/dumppat.txt).

ENVIRONMENT

The tcpprt utility will attempt to load DICOM data dictionaries specified in the DCMDICTPATH environment variable. By default, i.e. if the DCMDICTPATH environment variable is not set, the file <datadir>/dicom.dic will be loaded unless the dictionary is built into the application (default for Windows).

The default behaviour should be preferred and the DCMDICTPATH environment variable only used when alternative data dictionaries are required. The DCMDICTPATH environment variable has the same format as the Unix shell PATH variable in that a colon (":") separates entries. On Windows systems, a semicolon (";") is used as a separator. The data dictionary code will attempt to load each file specified in the DCMDICTPATH environment variable. It is an error if no data dictionary can be loaded.

FILES

<etcdir>/tcpprt.cfg - example configuration file