| LEADTOOLS DICOM C DLL Help > Callback Functions > RECEIVENREPORTRESPONSECALLBACK | 
| 
 | Available in LEADTOOLS Medical Imaging toolkits. | 
#include "ltdic.h"
L_VOID pEXT_CALLBACK Your Function(hNet, nPresentationID, nMessageID, pszClass, pszInstance, nStatus, nEvent, hDS, pUserData)
| HDICOMNET hNet; | /* a DICOM Network handle */ | 
| L_UCHAR nPresentationID; | /* presentation ID */ | 
| L_UINT16 nMessageID; | /* message ID */ | 
| L_TCHAR * pszClass; | /* class type */ | 
| L_TCHAR * pszInstance; | /* instance */ | 
| L_UINT16 nStatus; | /* status */ | 
| L_UINT16 nEvent; | /* event */ | 
| HDICOMDS hDS; | /* data set */ | 
| L_VOID * pUserData; | /* pointer to additional data */ | 
Notifies a connection that an N-EVENT-REPORT-RSP command was received. This function is available in the Medical Imaging Suite.
| Parameter | Description | 
| hNet | A DICOM Network handle to the peer member of the connection. | 
| 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. | 
| 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. | 
| pszClass | Class affected by the request. This will be an SOP Class or an SOP MetaClass. | 
| 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. | 
| nStatus | The status of the original request. For a list of possible values, refer to Status Constants. | 
| nEvent | An application specific event for which a report is to be generated. | 
| hDS | Application specific data set which contains information related to the operation. | 
| pUserData | Void pointer that you can use to access a variable or structure containing data that your callback function needs. This gives you a way to receive data indirectly from the function that uses this callback function. | 
| 
 | Keep in mind that this is a void pointer, which must be cast to the appropriate data type within your callback function. | 
Returns
None.
Comments
A call to this function is generated on a peer member of a connection when L_DicomSendNReportResponse is called locally.
To use this callback function, RECEIVENREPORTRESPONSECALLBACK must be set using L_DicomSetCallback.
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 | 
Win32, x64
See Also
| Functions: | L_DicomSendNReportRequest, L_DicomSendNReportResponse, RECEIVENREPORTREQUESTCALLBACK | 
| Topics: | 
Example
static HWND hList;      /* handle to list box */
L_VOID EXT_CALLBACK OnReceiveNReportResponse(HDICOMNET hNet, L_UCHAR nPresentationID, L_UINT16 nMessageID, L_TCHAR *pszClass, L_TCHAR *pszInstance, L_UINT16 nStatus, L_UINT16 nEvent, HDICOMDS hDS, L_VOID *pUserData)
{
   UNREFERENCED_PARAMETER(pszInstance);
   UNREFERENCED_PARAMETER(pUserData);
   UNREFERENCED_PARAMETER(hDS);
   UNREFERENCED_PARAMETER(hNet);
   L_TCHAR szMsg[800];
   ListBox_AddString(hList, TEXT("Command Set - N-REPORT-RESPONSE"));
   wsprintf(szMsg, TEXT("     Presentation ID: %d"), nPresentationID);
   ListBox_AddString(hList, szMsg);
   wsprintf(szMsg, TEXT("     Message ID: %d"), nMessageID);
   ListBox_AddString(hList, szMsg);
   wsprintf(szMsg, TEXT("     Affected SOP Class: %s"), pszClass);
   ListBox_AddString(hList, szMsg);
   wsprintf(szMsg, TEXT("     Status: %d"), nStatus);
   ListBox_AddString(hList, szMsg);
   wsprintf(szMsg, TEXT("     Event: %d"), nEvent);
   ListBox_AddString(hList, szMsg);
}