dcmpsrcv(1)

📦
version 3.7.1 · 10 versions
, in arch rolling

💅 dcmpsrcv — like, the manual page, bestie 🎀

okay so this is the dcmpsrcv(1) page from the OFFIS DCMTK fam — yes, the whole thing, don't worry, I'm not skipping a single crumb ✨

🌸 NAME 🌸

dcmpsrcv — network receive for the presentation state viewer, aka the quiet little icon that does the receiving 🫶

⭐ SYNOPSIS ⭐

dcmpsrcv [options] config-file

🦋 DESCRIPTION 🦋

okay so here's the tea ☕ — dcmpsrcv is not a "hey bestie let me just run this myself" kind of app. It gets invoked by the Grayscale Softcopy Presentation State Viewer, and it is literally not intended to be invoked manually. Like, it's giving backstage crew, not main character — but the show does not go on without it 💅

What it does, fr fr: it reads the common configuration file that all the different viewer components share (one config file to rule them all, iykyk), and then it opens a TCP/IP socket where incoming association requests get accepted. Then — and this is the cute part — it sparks a separate process for each DICOM connection 🔥

It supports the same storage SOP classes as the storescp utility, as SCP. But — and this is the important caveat, no skipping — it does not support encapsulated transfer syntaxes. Incoming images get stored in the common viewer database.

For the full detailed lore, see the full conformance statement. 📜

🍓 PARAMETERS 🍓

  • config-file — the configuration file to be read 📖 (that's the one, bestie)

✨ OPTIONS ✨

💜 general options

  • -h, --help — print this help text and exit. the classic "help me help you" move 🙈
  • --version — print version information and exit 👑
  • --arguments — print expanded command line arguments. like a little receipt for your command line 🧾
  • -q, --quiet — quiet mode, print no warnings and errors. shhh 🤫
  • -v, --verbose — verbose mode, print processing details. now we're talking 🗣️
  • -d, --debug — debug mode, print debug information. for when you need the nitty gritty 🔍
  • -ll, --log-level [l]evel: string constant — the valid values are 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 📝
  • -t, --terminate — terminate all running receivers 💀 periodt, they're done

🌈 LOGGING 🌈

okay so 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. Basic, but valid 💅

Using option --verbose and suddenly informational messages like processing details get reported too — she's chatty now 🗣️✨ 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. And like — in such very severe error events, the application will usually terminate 😭 so, y'know. heads up.

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), and a combination of both means 0 to n values. slay, consistent notation 💅

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 behavior conforms to the standard evaluation rules of common Unix shells. yes bestie, rightmost wins, that's the rule 👑

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. no inception, no nesting, we don't do that here 🙅‍♀️

This simple but effective approach allows one to summarize common combinations of options/parameters and avoids longish and confusing command lines (an example is provided in file <datadir>/dumppat.txt). it's giving organized ✨

💖 ENVIRONMENT 💖

The dcmpsrcv 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 behavior 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. like, actual error. not a vibe.

🎀 FILES 🎀

  • <etcdir>/dcmpstat.cfg — sample configuration file. a little starter pack, we love her 💖

🦋 SEE ALSO 🦋

go read those too, bestie, cross-referencing is self care 🌸

Copyright (C) 1998-2026 by OFFIS e.V., Escherweg 2, 26121 Oldenburg, Germany. 🫡 protecting the brand, we respect it.

okay that's the whole page, no crumbs left 🍓 — this was dcmpsrcv(1), from OFFIS DCMTK Version 3.7.1, dated Sat Oct 17 2026 09:34:01. mwah, go receive some networks 💋💅✨

📦 where this page comes from