L_DicomSendNActionResponse

#include "ltdic.h"

L_LTDIC_API L_INT L_DicomSendNActionResponse(hNet, nPresentationID, nMessageID, pszClass, pszInstance, nStatus, nAction, hDS)

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 nAction;	the action performed
HDICOMDS hDS;	data set

Sends an N-ACTION-RSP message to a peer member of a connection. This function is available in the PACS Imaging Toolkit.

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.
nAction	An application specific action that was performed on the specified data set.
hDS	Data set resulting from the specified action.

Returns

DICOM_SUCCESS	The function was successful.
>0	An error occurred. Refer to Return Codes.

Comments

L_DicomSendNActionResponse is sent by the SCP in response to an L_DicomSendNActionRequest call placed by an SCU. This generates a call to RECEIVENACTIONRESPONSECALLBACK on the SCU.

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, Linux.

Example

#include <windowsx.h> 
#include <windowsx.h> 
static HWND hList;      /* handle to list box */ 
L_INT16 PerformACTIONCommand(L_TCHAR * pszClass, L_TCHAR * pszInstance,L_INT nAction,HDICOMDS hDS) 
{ 
   UNREFERENCED_PARAMETER(pszClass); 
   UNREFERENCED_PARAMETER(pszInstance); 
   UNREFERENCED_PARAMETER(nAction); 
   UNREFERENCED_PARAMETER(hDS); 
   // 
   // Add your code here 
   // 
   return DICOM_SUCCESS; 
} 
L_VOID EXT_CALLBACK OnReceiveNActionRequest( 
HDICOMNET hNet, 
L_UCHAR nPresentationID, 
L_UINT16 nMessageID, 
L_TCHAR *pszClass, 
L_TCHAR *pszInstance, 
L_UINT16 nAction, 
HDICOMDS hDS, 
L_VOID *pUserData) 
{ 
   UNREFERENCED_PARAMETER(pUserData); 
   L_INT16 nRet; 
   L_TCHAR szMsg[800]; 
   ListBox_AddString(hList, TEXT("Command Set - N-ACTION-REQUEST")); 
   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("     Requested SOP Class: %s"), pszClass); 
   ListBox_AddString(hList, szMsg); 
   wsprintf(szMsg, TEXT("     Requested SOP Instance: %s"), pszInstance); 
   ListBox_AddString(hList, szMsg); 
   wsprintf(szMsg, TEXT("     Action: %d"), nAction); 
   ListBox_AddString(hList, szMsg); 
   /* this function should perform the action command */ 
   nRet = PerformACTIONCommand(pszClass, pszInstance, nAction, hDS); 
   if(nRet != DICOM_SUCCESS) 
      nRet = COMMAND_STATUS_PROCESSING_FAILURE; 
   /* send a response */ 
   L_DicomSendNActionResponse(hNet, nPresentationID, nMessageID, pszClass, pszInstance, nRet, nAction, 0); 
}

Help Version 19.0.2017.10.27

Products | Support | Contact Us | Copyright Notices
© 1991-2017 Apryse Sofware Corp. All Rights Reserved.

LEADTOOLS DICOM C API Help

Introduction

Version History

Getting Started

Features of LEADTOOLS DICOM

Redistributables/Files To Be Included With Your Application

Functions:	L_DicomSendNActionRequest, RECEIVENACTIONREQUESTCALLBACK, RECEIVENACTIONRESPONSECALLBACK
Topics:	Working with DICOM Network Connections