.TH "getscu" 1 "Tue Dec 19 2023" "Version 3.6.8" "OFFIS DCMTK" \" -*- nroff -*- .nh .SH NAME getscu \- DICOM retrieve (C-GET) SCU .SH "SYNOPSIS" .PP .PP .nf getscu [options] peer port [dcmfile-in\&.\&.\&.] .fi .PP .SH "DESCRIPTION" .PP The \fBgetscu\fP application implements an SCU for the Query/Retrieve Service Class\&. \fBgetscu\fP supports retrieve functionality using the C-GET message\&. It sends query keys to an SCP and waits for responses with images or other DICOM objects sent via C-STORE\&. As the DICOM service demands, C-GET and the accompanying C-STORE messages are handled on the same association\&. Therefore, objects can only be received by \fBgetscu\fP itself and cannot be sent to a third party (\fBmovescu\fP would be the right tool for this task)\&. .SH "PARAMETERS" .PP .PP .nf peer hostname of DICOM peer port tcp/ip port number of peer dcmfile-in DICOM query file(s) .fi .PP .SH "OPTIONS" .PP .SS "general options" .PP .nf -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 +v --verbose-pc show presentation contexts in verbose mode .fi .PP .SS "network options" .PP .nf override matching keys: -k --key [k]ey: gggg,eeee='str', path or dictionary name='str' override matching key query information model: -P --patient use patient root information model (default) -S --study use study root information model -O --psonly use patient/study only information model application entity titles: -aet --aetitle [a]etitle: string set my calling AE title (default: GETSCU) -aec --call [a]etitle: string set called AE title of peer (default: ANY-SCP) preferred storage transfer syntaxes (incoming associations): +x= --prefer-uncompr prefer explicit VR local byte order (default) +xe --prefer-little prefer explicit VR little endian TS +xb --prefer-big prefer explicit VR big endian TS +xs --prefer-lossless prefer default JPEG lossless TS +xy --prefer-jpeg8 prefer default JPEG lossy TS for 8 bit data +xx --prefer-jpeg12 prefer default JPEG lossy TS for 12 bit data +xv --prefer-j2k-lossless prefer JPEG 2000 lossless TS +xw --prefer-j2k-lossy prefer JPEG 2000 lossy TS +xt --prefer-jls-lossless prefer JPEG-LS lossless TS +xu --prefer-jls-lossy prefer JPEG-LS lossy TS +xm --prefer-mpeg2 prefer MPEG2 Main Profile @ Main Level TS +xh --prefer-mpeg2-high prefer MPEG2 Main Profile @ High Level TS +xn --prefer-mpeg4 prefer MPEG4 AVC/H\&.264 HP / Level 4\&.1 TS +xl --prefer-mpeg4-bd prefer MPEG4 AVC/H\&.264 BD-compatible HP / Level 4\&.1 TS +x2 --prefer-mpeg4-2-2d prefer MPEG4 AVC/H\&.264 HP / Level 4\&.2 TS for 2D Videos +x3 --prefer-mpeg4-2-3d prefer MPEG4 AVC/H\&.264 HP / Level 4\&.2 TS for 3D Videos +xo --prefer-mpeg4-2-st prefer MPEG4 AVC/H\&.264 Stereo HP / Level 4\&.2 TS +x4 --prefer-hevc prefer HEVC H\&.265 Main Profile / Level 5\&.1 TS +x5 --prefer-hevc10 prefer HEVC H\&.265 Main 10 Profile / Level 5\&.1 TS +xr --prefer-rle prefer RLE lossless TS +xd --prefer-deflated prefer deflated explicit VR little endian TS +xi --implicit accept implicit VR little endian TS only proposed retrieve transfer syntaxes (outgoing associations): -x= --propose-uncompr propose all uncompressed TS, explicit VR with local byte ordering first (default) -xe --propose-little propose all uncompressed TS, explicit VR little endian first -xb --propose-big propose all uncompressed TS, explicit VR big endian first -xd --propose-deflated propose deflated explicit VR little endian TS and all uncompressed transfer syntaxes -xi --propose-implicit propose implicit VR little endian TS only other network options: -to --timeout [s]econds: integer (default: unlimited) timeout for connection requests -ta --acse-timeout [s]econds: integer (default: 30) timeout for ACSE messages -td --dimse-timeout [s]econds: integer (default: unlimited) timeout for DIMSE messages -pdu --max-pdu [n]umber of bytes: integer (4096\&.\&.131072) set max receive pdu to n bytes (default: 16384) --repeat [n]umber: integer repeat n times --abort abort association instead of releasing it .fi .PP .SS "output options" .PP .nf general: -od --output-directory [d]irectory: string (default: '\&.') write received objects to existing directory d storage mode: -B --normal receive in memory, then write to disk (default) +B --bit-preserving receive directly to disk --ignore ignore store data, receive but do not store .fi .PP .SH "NOTES" .PP Each file supplied on the command line will be sent to the SCP as part of a C-GET request\&. The query file must be a valid DICOM data set containing the dataset part of a C-GET-RQ message\&. The query file could, for instance, be created with the \fBdump2dcm\fP utility from a script like the following example: .PP .PP .nf # request all images for the patient with ID=PAT001 (0008,0052) CS [PATIENT] # QueryRetrieveLevel (0010,0020) LO [PAT001] # PatientID .fi .PP .PP Another possibility is to use the \fBdcmodify\fP tool to create a file from scratch using the option \fI--create-file\fP with successive calls to the \fI--insert\fP option\&. Individual attributes can be modified or supplemented using the \fI-k\fP (or \fI--key\fP) option\&. For example the command: .PP .PP .nf getscu -k '0010,0020=PAT002' caesar 5678 patqry\&.dcm .fi .PP .PP will, when sent to the SCP caesar at TCP/IP port 5678, cause any PatientID attribute in patqry\&.dcm to have the value 'PAT002'\&. If such an attribute is present it will be replaced, if absent it will be inserted\&. The \fI-k\fP option can be present more than once\&. The value part (after the '=') may be absent causing the attribute to be sent with zero length\&. It is also possible to specify sequences, items and nested attributes using the \fI-k\fP option\&. In these cases, a special 'path' notation has to be used\&. Details can be found in the \fBdcmodify\fP documentation\&. .PP If no file is specified on the command line, the query must be specified completely with one or more \fI-k\fP options\&. If multiple query files are provided, \fBgetscu\fP will send multiple C-GET requests to the SCP\&. .SS "Known Problems" \fBgetscu\fP is intended to be used as a testing tool for DICOM software developers\&. The query keys file must be created by hand based upon the contents of the SCP\&. .PP C-GET is not supported by all Query/Retrieve SCPs\&. The C-MOVE protocol which is implemented by the \fBmovescu\fP tool is more commonly found in practice\&. .PP The \fBgetscu\fP application makes no attempt to prevent incorrect queries\&. In particular, the query keys of a C-MOVE request should only contain the QueryRetrieveLevel attribute and one or more of the so-called 'unique key attributes' (PatientID, StudyInstanceUID, SeriesInstanceUID and SOPInstanceUID)\&. .SS "DICOM Conformance" .SS "SCU Conformance" The \fBgetscu\fP application supports the following SOP Classes as an SCU: .PP .PP .nf GETPatientRootQueryRetrieveInformationModel 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.2\&.1\&.3 GETStudyRootQueryRetrieveInformationModel 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.2\&.2\&.3 GETPatientStudyOnlyQueryRetrieveInformationModel 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.2\&.3\&.3 .fi .PP .PP The \fBgetscu\fP application will propose presentation contexts for one of the abovementioned supported SOP Classes depending on command line options (\fI-P\fP, \fI-S\fP, or \fI-O\fP)\&. For outgoing associations, the following transfer syntaxes are supported: .PP .PP .nf LittleEndianImplicitTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2 LittleEndianExplicitTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.1 DeflatedExplicitVRLittleEndianTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.1\&.99 (*) BigEndianExplicitTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.2 .fi .PP .PP (*) if compiled with zlib support enabled (see \fI--version\fP output) .PP Which transfer syntaxes are actually proposed in what order, can be specified with the \fI--propose\fP options\&. .SS "Storage Conformance" The \fBgetscu\fP application supports the following SOP Classes as an SCP: .PP .PP .nf VerificationSOPClass 1\&.2\&.840\&.10008\&.1\&.1 RETIRED_StoredPrintStorage 1\&.2\&.840\&.10008\&.5\&.1\&.1\&.27 RETIRED_HardcopyGrayscaleImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.1\&.29 RETIRED_HardcopyColorImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.1\&.30 ComputedRadiographyImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.1 DigitalXRayImageStorageForPresentation 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.1\&.1 DigitalXRayImageStorageForProcessing 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.1\&.1\&.1 DigitalMammographyXRayImageStorageForPresentation 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.1\&.2 DigitalMammographyXRayImageStorageForProcessing 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.1\&.2\&.1 DigitalIntraOralXRayImageStorageForPresentation 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.1\&.3 DigitalIntraOralXRayImageStorageForProcessing 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.1\&.3\&.1 CTImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.2 EnhancedCTImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.2\&.1 LegacyConvertedEnhancedCTImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.2\&.2 RETIRED_UltrasoundMultiframeImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.3 UltrasoundMultiframeImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.3\&.1 MRImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.4 EnhancedMRImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.4\&.1 MRSpectroscopyStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.4\&.2 EnhancedMRColorImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.4\&.3 LegacyConvertedEnhancedMRImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.4\&.4 RETIRED_NuclearMedicineImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.5 RETIRED_UltrasoundImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.6 UltrasoundImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.6\&.1 EnhancedUSVolumeStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.6\&.2 SecondaryCaptureImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.7 MultiframeSingleBitSecondaryCaptureImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.7\&.1 MultiframeGrayscaleByteSecondaryCaptureImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.7\&.2 MultiframeGrayscaleWordSecondaryCaptureImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.7\&.3 MultiframeTrueColorSecondaryCaptureImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.7\&.4 RETIRED_StandaloneOverlayStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.8 RETIRED_StandaloneCurveStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.9 TwelveLeadECGWaveformStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.9\&.1\&.1 GeneralECGWaveformStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.9\&.1\&.2 AmbulatoryECGWaveformStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.9\&.1\&.3 HemodynamicWaveformStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.9\&.2\&.1 CardiacElectrophysiologyWaveformStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.9\&.3\&.1 BasicVoiceAudioWaveformStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.9\&.4\&.1 GeneralAudioWaveformStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.9\&.4\&.2 ArterialPulseWaveformStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.9\&.5\&.1 RespiratoryWaveformStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.9\&.6\&.1 RETIRED_StandaloneModalityLUTStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.10 RETIRED_StandaloneVOILUTStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.11 GrayscaleSoftcopyPresentationStateStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.11\&.1 ColorSoftcopyPresentationStateStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.11\&.2 PseudoColorSoftcopyPresentationStateStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.11\&.3 BlendingSoftcopyPresentationStateStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.11\&.4 XAXRFGrayscaleSoftcopyPresentationStateStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.11\&.5 XRayAngiographicImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.12\&.1 EnhancedXAImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.12\&.1\&.1 XRayRadiofluoroscopicImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.12\&.2 EnhancedXRFImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.12\&.2\&.1 RETIRED_XRayAngiographicBiPlaneImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.12\&.3 XRay3DAngiographicImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.13\&.1\&.1 XRay3DCraniofacialImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.13\&.1\&.2 BreastTomosynthesisImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.13\&.1\&.3 IntravascularOpt\&.Coh\&.Tom\&.ImageStorageForPresentation 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.14\&.1 IntravascularOpt\&.Coh\&.Tom\&.ImageStorageForProcessing 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.14\&.2 NuclearMedicineImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.20 RawDataStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.66 SpatialRegistrationStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.66\&.1 SpatialFiducialsStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.66\&.2 DeformableSpatialRegistrationStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.66\&.3 SegmentationStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.66\&.4 SurfaceSegmentationStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.66\&.5 RealWorldValueMappingStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.67 SurfaceScanMeshStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.68\&.1 SurfaceScanPointCloudStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.68\&.2 RETIRED_VLImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1 VLEndoscopicImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.1 VideoEndoscopicImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.1\&.1 VLMicroscopicImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.2 VideoMicroscopicImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.2\&.1 VLSlideCoordinatesMicroscopicImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.3 VLPhotographicImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.4 VideoPhotographicImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.4\&.1 OphthalmicPhotography8BitImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.5\&.1 OphthalmicPhotography16BitImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.5\&.2 StereometricRelationshipStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.5\&.3 OphthalmicTomographyImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.5\&.4 VLWholeSlideMicroscopyImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.1\&.6 RETIRED_VLMultiframeImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.77\&.2 LensometryMeasurementsStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.78\&.1 AutorefractionMeasurementsStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.78\&.2 KeratometryMeasurementsStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.78\&.3 SubjectiveRefractionMeasurementsStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.78\&.4 VisualAcuityMeasurementsStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.78\&.5 SpectaclePrescriptionReportStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.78\&.6 OphthalmicAxialMeasurementsStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.78\&.7 IntraocularLensCalculationsStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.78\&.8 MacularGridThicknessAndVolumeReportStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.79\&.1 OphthalmicVisualFieldStaticPerimetryMeasurementsSt\&. 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.80\&.1 OphthalmicThicknessMapStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.81\&.1 BasicTextSRStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.88\&.11 EnhancedSRStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.88\&.22 ComprehensiveSRStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.88\&.33 Comprehensive3DSRStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.88\&.34 ProcedureLogStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.88\&.40 MammographyCADSRStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.88\&.50 KeyObjectSelectionDocumentStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.88\&.59 ChestCADSRStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.88\&.65 XRayRadiationDoseSRStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.88\&.67 ColonCADSRStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.88\&.69 ImplantationPlanSRStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.88\&.70 EncapsulatedPDFStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.104\&.1 EncapsulatedCDAStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.104\&.2 PositronEmissionTomographyImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.128 LegacyConvertedEnhancedPETImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.128\&.1 RETIRED_StandalonePETCurveStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.129 EnhancedPETImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.130 BasicStructuredDisplayStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.131 RTImageStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.481\&.1 RTDoseStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.481\&.2 RTStructureSetStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.481\&.3 RTBeamsTreatmentRecordStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.481\&.4 RTPlanStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.481\&.5 RTBrachyTreatmentRecordStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.481\&.6 RTTreatmentSummaryRecordStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.481\&.7 RTIonPlanStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.481\&.8 RTIonBeamsTreatmentRecordStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.1\&.1\&.481\&.9 RTBeamsDeliveryInstructionStorage 1\&.2\&.840\&.10008\&.5\&.1\&.4\&.34\&.7 .fi .PP .PP The \fBgetscu\fP application will usually accept presentation contexts for all of the abovementioned supported SOP Classes using any of the following transfer syntaxes: .PP .PP .nf LittleEndianImplicitTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2 LittleEndianExplicitTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.1 BigEndianExplicitTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.2 .fi .PP .PP When acting as a storage SCP, the \fBgetscu\fP application will prefer transfer syntaxes having an explicit encoding over the default implicit transfer syntax\&. If \fBgetscu\fP is running on big-endian hardware it will prefer BigEndianExplicit to LittleEndianExplicit transfer syntax (and vice versa)\&. This behavior can be changed with the \fI--prefer\fP options (see above)\&. Depending on the \fI--prefer\fP option actually used, a combination of the following transfer syntaxes is supported: .PP .PP .nf LittleEndianImplicitTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2 LittleEndianExplicitTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.1 DeflatedExplicitVRLittleEndianTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.1\&.99 (*) BigEndianExplicitTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.2 JPEGProcess1TransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.50 JPEGProcess2_4TransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.51 JPEGProcess14SV1TransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.70 JPEGLSLosslessTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.80 JPEGLSLossyTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.81 JPEG2000LosslessOnlyTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.90 JPEG2000TransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.91 MPEG2MainProfileAtMainLevelTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.100 MPEG2MainProfileAtHighLevelTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.101 MPEG4HighProfileLevel4_1TransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.102 MPEG4BDcompatibleHighProfileLevel4_1TransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.103 MPEG4HighProfileLevel4_2_For2DVideoTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.104 MPEG4HighProfileLevel4_2_For3DVideoTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.105 MPEG4StereoHighProfileLevel4_2TransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.106 HEVCMainProfileLevel5_1TransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.107 HEVCMain10ProfileLevel5_1TransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.4\&.108 RLELosslessTransferSyntax 1\&.2\&.840\&.10008\&.1\&.2\&.5 .fi .PP .PP (*) if compiled with zlib support enabled (see \fI--version\fP output) .PP The \fBgetscu\fP application does not support extended negotiation\&. .SH "EXAMPLES" .PP .PP .nf getscu --patient --call ARCHIVE caesar 104 q\&.dcm .fi .PP .PP sends the attributes contained in the DICOM file 'q\&.dcm' as part of a C-GET request to application entity ARCHIVE on the host caesar at port 104 using the Patient Root query model\&. \fBgetscu\fP itself uses the default AE title GETSCU\&. .PP In contrast to C-MOVE-based Query/Retrieve SOP Classes, the C-GET-based SOP Classes utilized by \fBgetscu\fP only permit retrieving the desired objects on the same connection, i\&.e\&. \fBgetscu\fP will receive the objects itself\&. Thus, it is not possible to tell the SCP to transmit the objects to a third party\&. This is a limitation of the DICOM protocol and not of the \fBgetscu\fP tool\&. .SH "LOGGING" .PP 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 \fI--verbose\fP also informational messages like processing details are reported\&. Option \fI--debug\fP can be used to get more details on the internal activity, e\&.g\&. for debugging purposes\&. Other logging levels can be selected using option \fI--log-level\fP\&. In \fI--quiet\fP 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'\&. .PP In case the logging output should be written to file (optionally with logfile rotation), to syslog (Unix) or the event log (Windows) option \fI--log-config\fP 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 \fI/logger\&.cfg\fP\&. .SH "COMMAND LINE" .PP 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\&. .PP 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\&. .PP In addition, one or more command files can be specified using an '@' sign as a prefix to the filename (e\&.g\&. \fI@command\&.txt\fP)\&. 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 one to summarize common combinations of options/parameters and avoids longish and confusing command lines (an example is provided in file \fI/dumppat\&.txt\fP)\&. .SH "ENVIRONMENT" .PP The \fBgetscu\fP utility will attempt to load DICOM data dictionaries specified in the \fIDCMDICTPATH\fP environment variable\&. By default, i\&.e\&. if the \fIDCMDICTPATH\fP environment variable is not set, the file \fI/dicom\&.dic\fP will be loaded unless the dictionary is built into the application (default for Windows)\&. .PP The default behavior should be preferred and the \fIDCMDICTPATH\fP environment variable only used when alternative data dictionaries are required\&. The \fIDCMDICTPATH\fP environment variable has the same format as the Unix shell \fIPATH\fP 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 \fIDCMDICTPATH\fP environment variable\&. It is an error if no data dictionary can be loaded\&. .SH "SEE ALSO" .PP \fBfindscu\fP(1), \fBmovescu\fP(1), \fBdump2dcm\fP(1), \fBdcmodify\fP(1) .SH "COPYRIGHT" .PP Copyright (C) 2011-2023 by OFFIS e\&.V\&., Escherweg 2, 26121 Oldenburg, Germany\&.