You are here: SwitchKit® Development Environment - TCAP Interface User’s Guide > C Appendix - SKTAL Data Types and Codes > SKTAL Data Types

SKTAL Data Types

Purpose

This section provides information on SKTAL data types and error codes.

Table C-1 SKTAL Data Types

Data Types | Description
--- | ---
SKTAL_BOOLEAN | unsigned int.
SKTAL_OCTET | unsigned char.
SKTAL_USHORT | unsigned short.
SKTAL_UINT | unsigned int.
SKTAL_ULONG | unsigned long.
SKTAL_CHAR | char
SKTAL_SHORT | short
SKTAL_INT | int
SKTAL_LONG | long
SKTAL_HANDLE | void
SKTAL_POINTER | char
SKTAL_ByteArray | vector <SKTAL_OCTET>

SKTAL Event

typedef struct

{

SKTAL_USHORT len; /* length of event data */

SKTAL_USHORT src; /* not Used */

ITS_OCTET* data; /* Event data containing TCAP Dialogue or Component

* Information */

}

To distinguish between TCAP Dialogue events and TCAP Component Events use the following macros:

• #define TCAP_MSG_TYPE(ev) ((ev)->data[0])

• #define SKTAL_TCAP_DLG 1

• #define SKTAL_TCAP_CPT 2

Table C-2 SKTAL Return Codes

Code | Value
--- | ---
SKTAL_SUCCESS | 0
SKTAL_FALSE | 0
SKTAL_TRUE | 0x1
SKTAL_BITS_PER_BYTE | 8
SKTAL_ENOMEM | -1
SKTAL_ERCVFAIL | -6
SKTAL_ENOMSG | -8
SKTAL_ESENDFAIL | -9
SKTAL_ETCAPMSGSENDFAIL | -13
SKTAL_BADTCAPMESSAGE | -16
SKTAL_ETOOMANYDIALOGS | -18
SKTAL_ENOINVID | -20
SKTAL_ENOMUTEX | -24
SKTAL_EBADMUTEX | -25
SKTAL_EINVALIDARGS | -39
SKTAL_ENOLICENSE | -45
SKTAL_EPROTERR | -46
SKTAL_EOVERFLOW | -49
SKTAL_EINITFAIL | -52
SKTAL_EINUSE | -55
SKTAL_EDESTPROHIBIT | -56
SKTAL_EINVPTYPE | -57
SKTAL_EINVOPFAM | -58
SKTAL_EINVOPSPEC | -59
SKTAL_EINVLEN | -60
SKTAL_ENULLPTR | -61
SKTAL_EBADSTATE | -64
SKTAL_ENOTFOUND | -65
SKTAL_EASNENCODE | -66
SKTAL_EASNDECODE | -67
SKTAL_EINVOPC | -72
SKTAL_EINVDPC | -73
SKTAL_EINVINITSTATE | -86
SKTAL_ALREADY_REGISTERED | -121
SKTAL_STACK_IN_USE | -122
SKTAL_NO_MORE_STACKS | -123
SKTAL_NO_MORE_DIDS | -124
SKTAL_INVALID_ARG | -125
SKTAL_BAD_MUTEX | -126

A sequence of eight bits.
In PPL, a condition that, when met, drives a state machine (PPL Component) from one state to another, by invoking an associated Primitive. In PPL files, an Event is marked by an arrow and text.
See Transaction Capability Application Part.