Novell Doc: NDK: SMS Developer Components - NWSMTSScanDataSetContinue

Syntax

  #include <smstsapi.h> 
   
  CCODE NWSMTSScanDataSetContinue (
     UINT32                   connection,
     NWSM_DATA_SET_NAME_LIST  *resourceName,
     NWSM_SCAN_CONTROL        *scanControl,
     NWSM_SELECTION_LIST      *selectionList,
     NWSM_DATA_SET_NAME_LIST  *cursorDataSetName, 
     UINT32                   *sequence, 
     NWSM_SCAN_INFORMATION    **scanInformation, 
     NWSM_DATA_SET_NAME_LIST  **dataSetNames);

Parameters

connection: (IN) Specifies the connection information returned by NWSMTSConnectToTargetService or NWSMTSConnectToTargetServiceEx.
resourceName: (IN) Points to the starting point or path of the resource to scan.
scanControl: (IN) Points to the attributes and characteristics of all data sets to scan or ignore (see Scan Control Options).
selectionList: (IN) Points to the data sets to scan or ignore and contains the name as it appears under every name space supported by resourceName.
cursorDataSetName: (IN) Points to the point or the full path of last successfully backed up data set name, to continue the scan.
sequence: (OUT) Points to the scanning sequence value (does not need to be initialized as it is set by the TSA).
scanInformation: (OUT) Optional. Points to the general attributes and information of the first data set that meets the scanning criteria.
dataSetNames: (OUT) Optional. Points to the name of the first data set that met the scanning criteria.

Return Values

See Section 9.3, Target Service Return Values for more information.

The following table lists the return values associated with the function.

0x00000000	Successful
0xFFFDFFAF	NWSMTS_CLUSTER_TARGET_DOES_NOT_EXIST
0xFFFBFFFB	NWSMUT_OUT_OF_MEMORY
0xFFFBFFFC	NWSMUT_NO_MORE_NAMES
0xFFFBFFFD	NWSMUT_INVALID_PARAMETER
0xFFFBFFFF	NWSMUT_INVALID_HANDLE
0xFFFDFFB9	NWSMTS_UNSUPPORTED_FUNCTION
0xFFFDFFC9	NWSMTS_OUT_OF_MEMORY
0xFFFDFFDA	NWSMTS_INVALID_SEL_LIST_ENTRY
0xFFFDFFDC	NWSMTS_INVALID_PATH
0xFFFDFFDD	NWSMTS_INVALID_PARAMETER
0xFFFDFFE4	NWSMTS_INVALID_DATA_SET_NAME
0xFFFDFFE7	NWSMTS_INVALID_CONNECTION_HANDL
0xFFFDFFF2	NWSMTS_DATA_SET_NOT_FOUND
0xFFFDFFB1	NWSMTS_INTERNAL_ERROR
0xFFFEFFFE	NWSMDR_INVALID_PARAMETER
0xFFFEFFFF	NWSMDR_INVALID_CONNECTION

Recovery Error Codes

This section lists the return values returned by the following TSA and SMDR APIs, during cluster failover/failback.

0xFFFDFFAF	NWSMTS_CLUSTER_TARGET_DOES_NOT_EXIST	Cluster target does not exist
0xFFFEFFCE	NWSMDR_OPEN_FAILURE	Unable to open the configuration file for reading
0xFFFEFFCD	NWSMDR_READ_FAILURE	Unable to read from source
0xFFFEFFCC	NWSMDR_WRITE_FAILURE	Unable to write to the destination
0xFFFEFFFC	NWSMDR_TRANSPORT_FAILURE	The transport mechanism has failed
0xFFFEFFB1	NWSMDR_DISCONNECTED	Resource disconnected

Remarks

This API is cluster specific and is not to be used for normal backup failures
This API doesn’t support restore recovery during cluster failover/failback.
If scanning is in progress, call NWSMTSScanDataSetEnd before reconnection.
After cluster failover/failback, release the current connections of engine to TSA or SMDR by calling NWSMTSReleaseTargetService or NWSMReleaseTSA respectively.
Re-establish the connection using NWSMConnectToTSA and NWSMTSConnectToTargetService or NWSMTSConnectToTargetServiceEx.
The cursor should contain the last successfully backed-up data set information. If there are no such data sets during failover/failback, use NWSMTSScanDataSetBegin.

NOTE:This symbol is not present in the SMS import file, as all versions of SMS do not export this symbol. To use this function, programmatically import the symbol and invoke it.

Example

See the example for NWSMTSScanDataSetBegin.

NWSMTSScanDataSetContinue