LDicomNet::OnReceiveNActionResponse

Summary

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

Syntax

virtual L_VOID LDicomNet::OnReceiveNActionResponse(nPresentationID, nMessageID, pszClass, pszInstance, nStatus, nAction, 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 nStatus

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

L_UINT16 nAction

An application specific action to be performed on the specified data set.

LDicomDS* pDS

The data set on which the specified action is to be performed.

Returns

None.

Comments

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

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

The action specified may be the addition of a new patient, the deletion of a patient, the addition of a new study, a print job, etc. The nAction value, which designates the action to perform is determined by the server. To find out the values used, you must contact the organization that created the server. When creating a server, the values and their corresponding meanings are determined by those creating the server.

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::SendNActionRequest
• LDicomNet::SendNActionResponse
• LDicomNet::OnReceiveNActionRequest

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::OnReceiveNActionResponse(L_UCHAR nPresentationID, L_UINT16 nMessageID, L_TCHAR *pszClass, L_TCHAR *pszInstance, L_UINT16 nStatus, L_UINT16 nAction, LDicomDS *pDS) 
   { 
      CString strMsg; 
      L_UINT lPeerPort; 
      L_TCHAR  szPeerAddress[100]; 
       
      GetPeerInfo(szPeerAddress, 100, &lPeerPort); 
      strMsg.Format(TEXT("*** OnReceiveNActionR\ 
   esponse ***\nPeer[%s]\nnPresentationID[%d]\nnMessageID[%d]\npszClass[%s]\npszInstance[%s]\nnStatus[%d]\nnAction[%d]\npDS[%x]\n"),  
         szPeerAddress, 
         nPresentationID,  
         nMessageID,  
         pszClass, 
         pszInstance,  
         nStatus, 
         nAction, 
         pDS); 
    
      AfxMessageBox(strMsg); 
   }