y_vts.c File Reference

VTS functions for LR 11.5 and above. More...

Go to the source code of this file.

Functions
void	y_vts_report_error (char *message)
int	y_vts_process_returncode (int returncode)
	Error translation and reporting facility for VTS return codes. This will emit VTS errors using lr_error_message() in human readable form, if the code represents a VTS error. More...

Detailed Description

VTS functions for LR 11.5 and above.

Library wrapperrs for talking to a VTS-server. This is part of LR 11.5 and needs to be installed seperately. For LR versions older than 11.5, see the old y_vts.c.

Warning

This y_vts.c is NOT compatible with the vts version that was shipped before LR 11.5, and the older y_vts.c is NOT compatible with the version in LR 11.5 either.

Definition in file y_vts.c.

Function Documentation

int y_vts_process_returncode

(

int

returncode

)

Error translation and reporting facility for VTS return codes. This will emit VTS errors using lr_error_message() in human readable form, if the code represents a VTS error.

Parameters

returncode

An error code as returned by VTS

Returns

the returncode

This is what the header file vts2.h tells us about error codes:

//VTS Error Codes
#define  VTCERR_OK                            0
#define  VTCERR_INVALID_CONNECTION_INFO  -10000
#define  VTCERR_FAILED_TO_RESOLVE_ADDR   -10001
#define  VTCERR_FAILED_TO_CREATE_SOCKET  -10002
#define  VTCERR_FAILED_TO_CONNECT        -10003

#define  VTCERR_INCOMPLETE_REQUEST       -10100
#define  VTCERR_FAILED_TO_RECV_RESPONSE  -10101
#define  VTCERR_INCOMPLETE_RESPONSE      -10102
#define  VTCERR_RESPONSE_ARGS_UNMATCH    -10103

// --- Operation Error Base
#define  VTCERR_OPERATION_ERROR_BASE     -11000
#define  VTCERR_SERVER_IS_BUSY           (VTCERR_OPERATION_ERROR_BASE - 0xFF)
#define  VTCERR_CLIENT_REQUEST_ERROR     (VTCERR_OPERATION_ERROR_BASE - 0xFE)

Loadrunner 11.52 expanded that a little, to the following definition in the help files:

VTCERR_OK 0 Success 
VTCERR_INVALID_CONNECTION_INFO -10000 The corresponding handle does not exist or the connection information is corrupted. Disconnect and reconnect. 
VTCERR_FAILED_TO_RESOLVE_ADDR -10001 Failed to find server. 
VTCERR_FAILED_TO_CREATE_SOCKET -10002 Failed to create socket. 
VTCERR_FAILED_TO_CONNECT -10003 Failed to connect. Check the server name, port number, network connectivity, and whether server is on line. 
VTCERR_INVALID_API_CALL -10004 Failed to get the API entry.  <-- NEW

VTCERR_INCOMPLETE_REQUEST -10100 Communications packet from client is invalid. 
VTCERR_FAILED_TO_RECV_RESPONSE -10101 No response received from server. 
VTCERR_INCOMPLETE_RESPONSE -10102 Communications packet from server is invalid. 
VTCERR_RESPONSE_ARGS_UNMATCH -10103 Unexpected count of arguments in server response. 
VTCERR_INVALID_ARGUMENT -10104 Invalid argument.  <-- NEW
VTCERR_HANDLE_NOT_EXIST -10105 Connection handle does not exist. <-- NEW
VTCERR_INNER_JSON_CONVERT -10106 Cannot parse server response. <-- NEW
VTCERR_INNER_UTF8_CONVERT -10107 Cannot convert between UTF8 and Locale.  <-- NEW
VTCERR_COL_FORMAT_ERROR -10108 Invalid or empty column name.  <-- NEW
VTCERR_COL_VALUE_NO_MATCH -10109 Column names list and messages list do not have the same number of values. Check delimiters.  <-- NEW
VTCERR_EVAL_STRING -10110 Error evaluating parameter value.  <-- NEW
VTCERR_DATA_NOT_EXIST -10111 There is no data at the specified column and row.  <-- NEW

.. note however that the "Operation Error Base" codes are gone.

Author

Floris Kraak

Definition at line 103 of file y_vts.c.

void y_vts_report_error

(

char *

message

)

Definition at line 42 of file y_vts.c.