LDicomNet::OnReceiveCMoveResponse
#include "ltdic.h"
virtual L_VOID LDicomNet::OnReceiveCMoveResponse(nPresentationID, nMessageID, pszClass, nStatus, nRemaining, nCompleted, nFailed, nWarning, pDS)
L_UCHAR nPresentationID; |
/* presentation ID */ |
L_UINT16 nMessageID; |
/* message ID */ |
L_TCHAR * pszClass; |
/* class type */ |
L_UINT16 nStatus; |
/* status */ |
L_UINT16 nRemaining; |
/* number of remaining instances */ |
L_UINT16 nCompleted; |
/* number of instances completed */ |
L_UINT16 nFailed; |
/* number of instances that failed */ |
L_UINT16 nWarning; |
/* number of warnings */ |
LDicomDS *pDS; |
/* data set */ |
Notifies a connection that a C-MOVE-RSP command was received. This function is available in the Medical Suite Toolkit.
Parameter |
Description |
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. |
nStatus |
The status of the original request. For a list of possible values, refer to Status Constants. |
nRemaining |
Number of remaining instances to search. |
nCompleted |
Number of instances searched. |
nFailed |
Number of instances that failed the search. |
nWarning |
Number of instances in which warnings occurred. |
pDS |
Pointer to the dataset that holds additional information about a non-successful C-MOVE sub-operation. |
Returns
None.
Comments
A call to this function is generated on an SCU when LDicomNet::SendCMoveResponse is called by the SCP.
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 |
See Also
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)
// identifieds 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::OnReceiveCMoveResponse(L_UCHAR nPresentationID, L_UINT16 nMessageID, L_TCHAR *pszClass, L_UINT16 nStatus, L_UINT16 nRemaining, L_UINT16 nCompleted, L_UINT16 nFailed, L_UINT16 nWarning, LDicomDS *pDS) { CString strMsg; L_UINT lPeerPort; L_TCHAR szPeerAddress[100]; GetPeerInfo( szPeerAddress, 100, &lPeerPort); strMsg.Format(TEXT("*** OnReceiveCMoveResponse ***\nPeer[%s]\nnPresentationID[%d]\nnMessageID[%d]\npszClass[%s]\nnStatus[%d]\nnRemaining[%d],nCompleted[%d]\nnFailed[%d]\nnWarning[%d]\npDS[%x]"), szPeerAddress, nPresentationID, nMessageID, pszClass, nStatus, nRemaining, nCompleted, nFailed, nWarning, pDS ); AfxMessageBox(strMsg); }