RECEIVECMOVEREQUESTCALLBACK

#include "ltdic.h"

L_VOID pEXT_CALLBACK Your Function(hNet, nPresentationID, nMessageID, pszClass, nPriority, pszMoveAE, hDS, pUserData)

HDICOMNET hNet;	/* a DICOM Network handle */
L_UCHAR nPresentationID;	/* presentation ID */
L_UINT16 nMessageID;	/* message ID */
L_CHAR * pszClass;	/* class type */
L_UINT16 nPriority;	/* priority of the message */
L_CHAR * pszMoveAE;	/* name of the application entity */
HDICOMDS hDS;	/* data set to be moved */
L_VOID * pUserData;	/* pointer to additional data */

Notifies a connection that a C-MOVE-REQ command was received. This function is available in the Medical Suite Toolkit.

Parameter	Description
hNet	A DICOM Network handle.
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.
nPriority	The priority level of the message. The Service Class Provider may or may not support priority. Therefore, setting this parameter may or may not have any effect. Possible values are:
	Value	Meaning
	COMMAND_PRIORITY_LOW	[0x0002] Low priority message.
	COMMAND_PRIORITY_MEDIUM	[0x0000] Medium priority message.
	COMMAND_PRIORTY_HIGH	[0x0001] High priority message.
pszMoveAE	Character string that contains the name of the application entity that originally requested the move. For a simple storage request from a client to a server, this should be "". When the request is a sub-operation of a C-MOVE, this will contain the name of the AE that requested the move.
hDS	Pointer to the data set to be moved.
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 an SCP when L_DicomSendCMoveRequest is called by the SCU.

To use this callback function, RECEIVECMOVEREQUESTCALLBACK 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

Functions:	L_DicomSendCMoveRequest, L_DicomSendCMoveResponse, L_DicomSendCStoreRequest, L_DicomSendCStoreResponse, RECEIVECMOVERESPONSECALLBACK, RECEIVECSTOREREQUESTCALLBACK, RECEIVECSTORERESPONSECALLBACK
Topics:	Receiving Messages