SIST ES 202 915-2 V1.2.1:2005

• Abstract:

  Maintenance update of ES 202 915-2 V1.1.1 to produce ES 202 915-2 V1.2.1 Updated document will also be known as PARLAY 4.1. Only those parts requiring modification will be updated ( most parts require maintenance fixes )

• Status: Published
• Publication Date: 31-Dec-2004
• ICS: 33.040.01 - Telecommunication systems in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Jan-2005
• Due Date: 01-Jan-2005
• Completion Date: 01-Jan-2005
• Ref Project: ETSI ES 202 915-2 V1.2.1 (2003-08) - Open Service Access (OSA); Application Programming Interface (API); Part 2: Common Data Definitions (Parlay 4)

SIST ES 202 915-2 V1.2.1:2005 is the Slovenian standard published by SIST, identical to ETSI ES 202 915-2 V1.2.1, for Open Service Access (OSA) Application Programming Interface (API) Part 2: Common Data Definitions (Parlay 4). It specifies the shared data types, structures, exceptions and machine-readable bindings used across the OSA API, so application developers and implementers can exchange the same common data model. The updated document is also known as PARLAY 4.1.

What does SIST ES 202 915-2 V1.2.1:2005 specify?

SIST ES 202 915-2 V1.2.1:2005 is part 2 of the OSA Stage 3 API specification. Its scope is the common data definitions used throughout the rest of the OSA API, and clause 5 treats several base types as assumptions for the client operating system.

Clause 4 explains the document structure: the data definitions are presented first, followed by the IDL, WSDL and Java representations. Clause 2 points back to ES 202 915-1 for the provisions it uses, and the foreword places this part in the wider ES 202 915 series from the overview to the service-specific parts.

Annex	What it covers
Annex A	OMG IDL description of the common data definitions
Annex B	W3C WSDL description of the common data definitions
Annex C	Java API description of the common data definitions
Annex D	Exception hierarchy for OSA
Annex E	Record of changes

What are the key requirements of SIST ES 202 915-2 V1.2.1:2005?

The core requirement of SIST ES 202 915-2 V1.2.1:2005 is that all OSA parts use the same common data model. That matters in practice because applications, gateways and service interfaces must agree on the meaning of IDs, addresses, timestamps, charging data and exceptions.

• Clause 5.1 defines the standard data types. It includes primitive types such as Boolean, integers, floating point, strings and octets, plus common OSA types such as TpAssignmentID, TpSessionID, TpAttribute, TpVersion, TpStringSet and TpStringList. TpAssignmentID identifies an object-level assignment, TpSessionID identifies sessions within an SCF instance, and TpAttribute carries a name, type and value. In practice, these types prevent each service part from inventing its own way to encode common values.

• Clause 5.2 defines how complex data is built. The document uses sequences, tagged choices, numbered sets, numbered lists and references. Sets are unordered and do not allow duplicates, while lists are ordered and can repeat values. In practice, this tells implementers whether they must preserve order or uniqueness when mapping the data into a programming language.

• Clause 5.4 defines the common exception model. It covers implicit underlying-technology errors, the TpCommonExceptions structure and a shared set of exceptions that all methods on all interfaces can raise. Annex D extends this into an exception hierarchy with abstract and detailed exceptions. In practice, this gives API designers and developers a consistent way to handle invalid parameters, unsupported methods, unavailable resources and invalid state.

• Clause 5.5 defines date and time types.TpDate, TpTime and TpDateAndTime use ISO 8601 forms, while TpDuration represents a millisecond interval and uses special negative values for infinite and default duration. TpTimeInterval combines a start time and stop time. In practice, this gives a fixed format for scheduling, logging and validity windows.

• Clause 5.6 defines address-related data.TpAddress and TpAddressRange support several address plans, including IP, E.164, URL, SMTP, X400 and SIP. TpAddressRange allows wildcards for matching, and TpURL is separate from TpAddress because it always represents a URL for user interaction content. In practice, this is the part to check when an implementation must route, compare or validate user addresses.

• Clause 5.7 defines price and charging data. It includes TpPrice, Advice Of Charge structures, TpChargePerTime, TpLanguage and the related charging advice elements. In practice, these types support call charging presentation and tariff change handling without free-text interpretation.

• Clause 5.8 defines the shared QoS class type.TpDataSessionQosClass carries the conversational, streaming, interactive and background classes referenced from 3G TS 23.107. In practice, this lets call control and data session control use the same QoS vocabulary.

What terms does SIST ES 202 915-2 V1.2.1:2005 define?

• OSA is Open Service Access, the architecture that lets application developers use network functionality through an open standardised interface.
• API is the Application Programming Interface used by OSA to expose that network functionality.
• IDL is the OMG Interface Definition Language view of the common data definitions, provided in Annex A.
• WSDL is the W3C Web Services Description Language view of the same common data definitions, provided in Annex B.
• TpAddressRange is the address-range form that can match addresses with wildcards and plan-based rules.
• TpCommonExceptions is the shared exception structure used by methods on all interfaces.
• TpDataSessionQosClass is the common QoS class type used for data sessions and multimedia call sessions.

Who uses SIST ES 202 915-2 V1.2.1:2005?

SIST ES 202 915-2 V1.2.1:2005 is used by telecom application developers, API designers and platform implementers working with OSA and Parlay interfaces. It is also used by software developers who need the IDL, WSDL or Java mapping of the common data model, and by testers or integrators who must check that addresses, dates, charging data and exceptions are handled consistently across services.

The document is especially relevant when building OSA applications that call into network functions, or when implementing gateways and service capability interfaces that must interoperate across multiple OSA parts.

What changed in SIST ES 202 915-2 V1.2.1:2005 from the previous edition?

SIST ES 202 915-2 V1.2.1:2005 is a maintenance update of V1.1.1, and the updated document is also known as PARLAY 4.1. The scope says that only the parts requiring modification were updated.

Annex E records these V1.2.1 changes:

• TpDataSessionQosClass was added to the common data definitions and moved from Part 8.
• TpAssignmentID was updated.
• P_ADDRESS_PLAN_NATIONAL was added.
• P_INVALID_STATE was changed to match the IDL.

Which standards are used with SIST ES 202 915-2 V1.2.1:2005?

Standard	What it contributes
ETSI ES 202 915-1	Overview of OSA API and the terms and abbreviations used here
ES 202 915 parts 3-14	The framework and service-specific OSA API parts that use these common data definitions
ISO 8601	Date, time and date-time formats
ISO 639	Language strings for TpLanguage
ISO 4217:1995	Currency unit identification for charging data
IETF RFC 1738, RFC 822, RFC 3261	URL, SMTP and SIP address forms used in address planning
3G TS 23.107	QoS class definitions used by TpDataSessionQosClass
TS 122 024	Charging Advice Information elements used by the charging types

The foreword also states that this ETSI standard is equivalent to 3GPP TS 29.198-2 V5.2.0 (Release 5).

What does the SIST ES 202 915-2 V1.2.1:2005 document contain?

SIST ES 202 915-2 V1.2.1:2005 contains the common OSA data definitions, the rules for combining them, and the shared exception model. It also includes detailed tables for address plans, presentation and screening states, date and time encodings, charging data, and QoS classes.

The annexes add machine-readable descriptions for implementation: Annex A provides OMG IDL, Annex B provides W3C WSDL, and Annex C points to the Java API description. Annex D lays out the exception hierarchy, and Annex E records the changed, added, deprecated and removed items across releases.

SLOVENSKI STANDARD
01-januar-2005
2GSUWLGRVWRSGRVWRULWYH26$±9PHVQLN]DDSOLNDFLMVNRSURJUDPLUDQMH$3,±
GHO'RORþLWHYVNXSQLKSRGDWNRY
Open Service Access (OSA); Application Programming Interface (API); Part 2: Common
Data Definitions (Parlay 4)
Ta slovenski standard je istoveten z: ES 202 915-2 Version 1.2.1
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Open Service Access (OSA);
Application Programming Interface (API);
Part 2: Common Data Definitions
(Parlay 4)
�
2 ETSI ES 202 915-2 V1.2.1 (2003-08)

Reference
RES/SPAN-120096-2
Keywords
API, IDL, OSA, UML
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, send your comment to:
[e-mail]
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2003.
© The Parlay Group 2003.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 202 915-2 V1.2.1 (2003-08)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.6
2 References.6
3 Definitions and abbreviations.6
3.1 Definitions.6
3.2 Abbreviations.6
4 Common Data Definitions.6
5 Common System Data Definitions.7
5.1 Standard Data Types .7
5.1.1 TpBoolean.7
5.1.2 TpInt32.7
5.1.3 TpFloat.7
5.1.4 TpLongString.7
5.1.5 TpOctet.7
5.1.6 TpOctetSet.7
5.1.7 TpString.7
5.1.8 TpAssignmentID.7
5.1.9 TpSessionID.7
5.1.10 TpSessionIDSet.8
5.1.11 TpAny.8
5.1.12 TpAttribute.8
5.1.13 TpAttributeType.8
5.1.14 TpAttributeList.8
5.1.15 TpAttributeSet.8
5.1.16 TpInt64.8
5.1.17 TpVersion.9
5.1.18 TpStringSet.9
5.1.19 TpStringList.9
5.2 Other Data Sorts .9
5.2.1 Sequence of Data Elements .9
5.2.2 Tagged Choice of Data Elements .10
5.2.3 Numbered Set of Data Elements.10
5.2.4 Reference.10
5.2.5 Numbered List of Data Elements.10
5.3 Interface Related Data Definitions .10
5.3.1 IpInterface.10
5.3.2 IpInterfaceRef.10
5.4 Exception Classes.11
5.4.1 Underlying Technology Exceptions .11
5.4.2 TpCommonExceptions.11
5.4.3 Constants associated with TpCommonExceptions .11
5.4.4 Exceptions available to all methods on all interfaces .12
5.5 Date and Time Related Data Definitions.13
5.5.1 TpDate.13
5.5.2 TpTime.13
5.5.3 TpDateAndTime.14
5.5.4 TpDuration.14
5.5.5 TpTimeInterval.14
5.6 Address Related Data Definitions .15
5.6.1 TpAddress.15
5.6.2 TpAddressSet.16
5.6.3 TpAddressPresentation.16
ETSI
4 ETSI ES 202 915-2 V1.2.1 (2003-08)
5.6.4 TpAddressScreening.16
5.6.5 TpAddressPlan.16
5.6.6 TpAddressError.17
5.6.7 TpAddressRange.17
5.6.8 TpURL.18
5.7 Price-related Data Definitions .18
5.7.1 TpPrice.18
5.7.2 TpAoCInfo.18
5.7.3 TpAoCOrder.18
5.7.4 TpCallAoCOrderCategory.19
5.7.5 TpChargeAdviceInfo.19
5.7.6 TpCAIElements.19
5.7.7 TpChargePerTime.19
5.7.8 TpLanguage.19
5.8 Data Types Common Across Call Control and Data Session Control.20
5.8.1 TpDataSessionQosClass.20
Annex A (normative): OMG IDL Description of the Common Data definitions .21
Annex B (informative): W3C WSDL Description of the Common Data definitions.22
Annex C (informative): Java API Description of the Common Data definitions .23
Annex D (normative): Exception Hierarchy.24
Annex E (informative): Record of changes .32
E.1 Data Definitions.32
E.1.1 New.32
E.1.2 Modified.32
E.1.3 Removed.32
E.2 Exceptions.33
E.2.1 New.33
E.2.2 Modified.33
E.2.3 Removed.33
E.3 Others.33
History .34

ETSI
5 ETSI ES 202 915-2 V1.2.1 (2003-08)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This ETSI Standard (ES) has been produced by ETSI Technical Committee Services and Protocols for Advanced
Networks (SPAN).
The present document is part 2 of a multi-part deliverable covering Open Service Access (OSA); Application
Programming Interface (API), as identified below. The API specification (ES 202 915) is structured in the following
parts:
Part 1: "Overview";
Part 2: "Common Data Definitions";
Part 3: "Framework";
Part 4: "Call Control";
Part 5: "User Interaction SCF";
Part 6: "Mobility SCF";
Part 7: "Terminal Capabilities SCF";
Part 8: "Data Session Control SCF";
Part 9: "Generic Messaging SCF";
Part 10: "Connectivity Manager SCF";
Part 11: "Account Management SCF";
Part 12: "Charging SCF";
Part 13: "Policy management SCF";
Part 14: "Presence and Availability Management SCF".
The present document has been defined jointly between ETSI, The Parlay Group (http://www.parlay.org) and the 3GPP,
in co-operation with a number of JAIN™ Community (http://www.java.sun.com/products/jain) member companies.
The present document forms part of the Parlay 4.1 set of specifications.
The present document is equivalent to 3GPP TS 29.198-2 V5.2.0 (Release 5).
ETSI
6 ETSI ES 202 915-2 V1.2.1 (2003-08)
1 Scope
The present document is part 2 of the Stage 3 specification for an Application Programming Interface (API) for Open
Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardised interface, i.e. the OSA APIs.
The present document specifies the Common Data Definitions of the OSA. The Common Data Definitions contain
data-types that are common across the rest of the OSA API. All aspects of the Common Data are defined here, these
being:
• Data Definitions
• IDL Description of the data types
• WSDL Description of the data types
• Reference to the Java API description of the data types
2 References
The references listed in clause 2 of ES 202 915-1 contain provisions which, through reference in this text, constitute
provisions of the present document.
ETSI ES 202 915-1: "Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview
(Parlay 4)".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ES 202 915-1 apply.
3.2 Abbreviations
For the purposes of the present document, the abbreviations defined in ES 202 915-1 apply.
4 Common Data Definitions
The following clauses describe each aspect of the Common data definitions.
The order is as follows:
• The Data Definitions clause shows a detailed expansion of each of the data types associated with the methods
within the classes;
• IDL description of the data types (normative annex);
• WSDL description of the data types (informative annex);
• Reference to the Java API description of the data types (informative annex).
ETSI
7 ETSI ES 202 915-2 V1.2.1 (2003-08)
5 Common System Data Definitions
These data definitions are assumed to be provided by the client operating system.
5.1 Standard Data Types
The APIs assume that the following data types can be supported.
5.1.1 TpBoolean
Defines a Boolean data type.
5.1.2 TpInt32
Defines a signed 32-bit integer.
5.1.3 TpFloat
Defines a single precision real number.
5.1.4 TpLongString
Defines a Byte string, comprising length and data. The length must be at least a 32-bit integer.
5.1.5 TpOctet
Defines an 8-bit quantity that is not translated during transmission.
5.1.6 TpOctetSet
Defines a Numbered Set of Data elements of TpOctet.
5.1.7 TpString
Defines a Byte string, comprising length and data. The length must be at least a 16-bit integer.
5.1.8 TpAssignmentID
Defines an assignment ID with a value that is unique to an instance of an implementation of a given interface (i.e. an
object), irrespective of the method invoked on it. This ID may be used, for example, to identify single or multiple event
notifications enabled by an object; or by a requesting object to modify or stop functionality (e.g. event notifications, call
load control) associated with a previously supplied assignment ID.
The assignment ID is identical to a TpInt32 type.
5.1.9 TpSessionID
Defines a session ID with a value that is at least unique within the context of a specific instance of an SCF. An instance
of an SCF is a single service manager instance plus the associated subordinate instances. For example, a single
MultiPartyCallControlManager instance plus all associated MultiPartyCall and MultiPartyCallLeg instances. The
session ID is used to identify different sessions (e.g. different call or call leg sessions) of an interface capable of
handling multiple sessions.
Example 1, myCallObject may implement the IpCall interface. If so, myCallObject may handle multiple call sessions,
and each call session will be identified by a call session ID value (e.g. 1, 2, 3) that is unique within the context of the
SCF instance.
ETSI
8 ETSI ES 202 915-2 V1.2.1 (2003-08)
Example 2, myCallAndCallLegObject may implement the IpCall and IpCallLeg interfaces. If so,
myCallAndCallLegObject may handle multiple call sessions and multiple call leg sessions. Each call session will be
identified by a call session ID value (e.g. 1, 2, 3) that is unique within the context of the SCF instance. Similarly, each
call leg session will be identified by a call leg session ID value (e.g. 1, 2, 3, 4, 5, 6) that is also unique within the context
of the SCF instance. Because call session IDs and call leg session IDs are different data types, overlapping values are
permitted and their uniqueness still remains.
The session ID is identical to a TpInt32 type.
5.1.10 TpSessionIDSet
Defines a Numbered Set of Data Elements of TpSessionID.
5.1.11 TpAny
Defines a type that can hold any type. This is not restricted to only the primitive types.
5.1.12 TpAttribute
This is a Sequence of Data Elements containing the attribute name, type, and value. The attribute Value is
interpreted based on the value of the attribute Type.
Sequence Element Name Sequence Element Type Notes
AttributeName TpString The name of the attribute.
AttributeType TpAttributeType The type of the attribute. Valid values for Type must
include at least TpString, TpInt32 and TpFloat.
AttributeValue TpAny The values for the attribute. This model allows
multi-valued attributes. Cannot be an empty list.

5.1.13 TpAttributeType
This data type is identical to a TpString, and is defined as a string of characters that uniquely identifies the type of an
attribute. Other Network operator specific capabilities may also be used, but should be preceded by the string "SP_".
The following values are defined.
Character String Value Description
NULL An empty (NULL) string indicates no attribute type.
P_STRING Attribute type is type TpString.
P_INT32 Attribute type is type TpInt32.
P_FLOAT Attribute type is type TpFloat.

5.1.14 TpAttributeList
This is a Numbered List of Data Elements of type TpAttribute.
5.1.15 TpAttributeSet
This is a Numbered Set of Data Elements of type TpAttribute.
5.1.16 TpInt64
Defines a signed 64-bit integer.
ETSI
9 ETSI ES 202 915-2 V1.2.1 (2003-08)
5.1.17 TpVersion
This data type is identical to TpString. It is used to uniquely identify the implemented version of the framework or
an SCF. The syntax for this datatype is defined as:
P__
Where:
is one of the strings listed in the table below.
Character String Value Description
PARLAY Specification released by The Parlay Group.
ETSI Specification released by ETSI.
3GPP Specification released by 3GPP.

consists of numbers separated by underscores (e.g. 3_1). It is recommended that not more than
the two most significant numbers (major and minor version) of the version are used.
Examples of version strings are:
Character String Value Description
P_PARLAY_3_1 Parlay v3.1.
P_ETSI_2_0 ETSI v2.0.
P_3GPP_4_3 3GPP Release 4.3.
Note that different version strings can be aliases of each other all pointing to the same SCF/Framework version.
5.1.18 TpStringSet
Defines a Numbered Set of Data Elements of type TpString.
5.1.19 TpStringList
Defines a Numbered List of Data Elements of type TpString.
5.2 Other Data Sorts
The APIs assumes that the following data syntaxes can be supported.
5.2.1 Sequence of Data Elements
This describes a sequence of data types. This may be defined as a structure (for example, in C++) or simply a sequence
of data elements within a structure.
EXAMPLE: The TpAddress data type may be defined in C++ as:
typedef struct {
TpAddressPlan  Plan;
TpString   AddrString;
TpString   Name;
TpAddressPresentation Presentation;
TpAddressScreening Screening;
TpString  SubAddressString;
} TpAddress;
ETSI
10 ETSI ES 202 915-2 V1.2.1 (2003-08)
5.2.2 Tagged Choice of Data Elements
This describes a data type which actually evaluates to one of a choice of a number of data elements. This data element
contains two parts: a tag data type (the tag part) which is used to identify the chosen data type, and the chosen data type
itself (the union part). This form of data type is also referred to as a tagged union.
This data type can be implemented (for example, in C++) as a structure containing an integer for the tag part, and a
union for the union part.
This data type is implementation specific. Please refer to the appropriate IDL documents (and the resulting language
mappings) to see how this data type is implemented.
EXAMPLE: The TpCallError data type may be defined in C++ as:
typedef struct {
TpCallErrorType Tag;
union {
TpCallErrorInfoUndefined   Undefined;
TpCallErrorInfoRoutingAborted RoutingAborted;
TpCallErrorInfoCallAbandoned  CallAbandoned;
TpCallErrorInfoInvalidAddress InvalidAddress;
TpCallErrorInfoInvalidState  InvalidState;
TpCallErrorInfoInvalidCriteria InvalidCriteria;
} callErrorInfo;
} TpCallError;
5.2.3 Numbered Set of Data Elements
This describes a data type which comprises an integer which indicates the total number of data elements in the set (the
number part), and an unordered set of data elements (the data part). Set data types do not contain duplicate data
elements.
EXAMPLE: The TpAddressSet data type may be defined in C++ as:
typedef struct {
TpInt32 Number;
TpAddress Set[Number];
} TpAddressSet;
5.2.4 Reference
This describes a reference (or pointer) to a data type.
5.2.5 Numbered List of Data Elements
This describes a data type which comprises an integer which indicates the total number of data elements in the set (the
number part), and an ordered set of data elements (the data part). List data types can contain duplicate data elements.
EXAMPLE: The TpStringList data type may be defined in C++ as:
typedef struct {
TpInt32 Number;
TpString List[Number];
} TpStringList;
5.3 Interface Related Data Definitions
5.3.1 IpInterface
Defines the address of a generic interface instance.
5.3.2 IpInterfaceRef
Defines a Reference to type IpInterface.
ETSI
11 ETSI ES 202 915-2 V1.2.1 (2003-08)
5.4 Exception Classes
5.4.1 Underlying Technology Exceptions
All methods contain a signature showing, amongst other things, the explicit exceptions that they may throw. In addition
to these exceptions, all methods can throw a number of implicit exceptions. These exceptions do not need to be included
within the method signatures and are given below.
These exceptions would be thrown by the underlying technology (e.g. CORBA, Java) as a result of problems
encountered, for example, with the way the API method is invoked. They are a minimum set of exceptions that must be
throwable by the underlying technology. Depending upon the underlying technology, additional method exceptions may
also be thrown.
Description
Invalid Parameter: A method has been passed an invalid parameter
argument
Invalid Parameter Value: A method parameter has been passed a value that
is out of range
Parameter Missing: A method has not been passed a mandatory parameter
argument
5.4.2 TpCommonExceptions
Defines the structure of the exception class which is applicable to all methods.
Structure Element Name Structure Element Type Structure Element Description
ExceptionType TpInt32 Carries a constant from the list in the table below
ExtraInformation TpString Carries extra information to help identify the source of the
exception, e.g. a parameter name

5.4.3 Constants associated with TpCommonExceptions
Name Value Description
P_RESOURCES_UNAVAILABLE 000Dh The required resources in the network
...