We do not provide storage commitment examples as they are too application
specific. I can give you a walk through of how you would implement it though.
The server who has the dataset that you wish to have committed shall be called
the SCP. The client who will issue the commitment request shall be called the
SCU.
First, the SCU will connect with the SCP and negotiate an association. Next
the SCU will send an N-ACTION request (using SendNActionRequest) with
MessageID = 1 and information describing what to commit. The SCU then waits
for the SCP to respond using the NetReceiveNActionResponse event. This is the
SCP confirming it has received the request and will be processing. At this
point the SCU disconnects from the SCP. The SCU then listens for incomming
connections. It is waiting for the SCP to connect to it, which will occur
when the SCP has finished processing the commitment request. Once the SCP
finishes, it connects to the SCU. Once connected the SCU waits for the
NetReceiveNReportRequest event to be called. This is where the SCU receives a
report from the SCP of what was successfully commited and what was not. The
SCU should then respond with an acknowledgement that it received the report
(use SendNReportResponse). Once the SCP receives the acknowledgment it will
close the connection.
For more information about Storage Commitment please consult the DICOM
specification part 4 Annex J
Travis Montgomery
Senior Sales Engineer
