In This Topic ▼

LDicomNet::OnReceiveNReportResponse

#include "ltdic.h"

virtual L_VOID LDicomNet::OnReceiveNReportResponse(nPresentationID, nMessageID, pszClass, pszInstance, nStatus, nEvent, pDS)

Notifies a connection that an N-EVENT-REPORT-RSP command was received. This function is available in the PACS Imaging Toolkit.

Parameters

L_UCHAR nPresentationID

Presentation ID. The presentation ID provides information about both the class type of the data and the transfer syntax to use when transferring the data.

L_UINT16 nMessageID

Message ID. Each message sent by a member of a connection should have a unique ID. Since a member of a connection may send several messages, this ID allows that member to identify when a specific request has been completed.

L_TCHAR * pszClass

Class affected by the request. This will be an SOP Class or an SOP MetaClass.

L_TCHAR * pszInstance

The instance of the class. A server may, for example, have three instances of the Nuclear Medicine Class. This value identifies the data with a specific instance.

L_UINT16 nStatus

The status of the original request. For a list of possible values, refer to Status Constants.

L_UINT16 nEvent

An application specific event for which a report is to be generated.

LDicomDS *pDS

Application specific data set which contains information related to the operation.

Returns

None.

Comments

A call to this function is generated on a peer member of a connection when LDicomNet::SendNReportResponse is called locally.

To customize this function, you must derive a class from LDicomNet and override this function.

Required DLLs and Libraries

LTDIC
For a listing of the exact DLLs and Libraries needed, based on the toolkit version, refer to Files To Be Included With Your Application

Platforms

Win32, x64

Functions

Topics

Receiving Messages

Example

In this example:

LMyDicomNet is a class derived from LDicomNet
LMyDicomNet has the following member variables:
m_nClientOrServer: can be (STATUS_NONE, STATUS_SERVER, STATUS_CLIENT)
identifies the LMyDicomNet object as a server or a client
m_nDataCommand: can be (COMMAND_C_MOVE,COMMAND_C_GET)
set so the server knows how a C-Store Response was generated
m_pDicomNet points to a valid LMyDicomNet object
LMyDicomNet *m_pDicomNet
A connection exists between client and server

An association exists between the client and server

L_VOID LMyDicomNet::OnReceiveNReportResponse(L_UCHAR nPresentationID, L_UINT16 nMessageID, L_TCHAR *pszClass, L_TCHAR *pszInstance, L_UINT16 nStatus, L_UINT16 nEvent, LDicomDS *pDS) 
{ 
   CString strMsg; 
   L_UINT lPeerPort; 
   L_TCHAR  szPeerAddress[100]; 
 
   GetPeerInfo(szPeerAddress,100, &lPeerPort); 
 
   strMsg.Format(TEXT("*** OnReceiveNReportResponse ***\nPeer[%s]\nnPresentationID[%d]\nnMessageID[%d]\npszClass[%s]\npszInstance[%s]\nnStatus[%d]\nnEvent[%d]\npDS[%x]\n"),  
      szPeerAddress, 
      nPresentationID,  
      nMessageID,  
      pszClass, 
      pszInstance,  
      nStatus,  
      nEvent,  
      pDS); 
   AfxMessageBox(strMsg); 
}

Download our FREE evaluation

Help Version 21.0.2021.7.2

LEADTOOLS DICOM C++ Class Library Help

Introduction

Version History

Getting Started

LEADTOOLS DICOM Features

Redistributables/Files To Be Included With Your Application

Quick Reference

Classes and Member Functions

Appendix