LDicomNet::OnReceiveNReportRequest

Summary

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

Syntax

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

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 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::SendNReportRequest 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

See Also

Functions

• LDicomNet::SendNReportRequest
• LDicomNet::SendNReportResponse
• LDicomNet::OnReceiveNReportResponse

Topics

• Receiving Messages

Example

In this example:

1. LMyDicomNet is a class derived from LDicomNet
2. 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

3. m_pDicomNet points to a valid LMyDicomNet object
   LMyDicomNet *m_pDicomNet

4. A connection exists between client and server

5. An association exists between the client and server
   

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