diff --git a/README.cygwin b/README.cygwin index b3c21235ae7ee103ed7f9dfe6f4eb98d58dc6510..97bfdb62953bb32e31a28c89f8fc5a8a1d63ba25 100644 --- a/README.cygwin +++ b/README.cygwin @@ -14,7 +14,7 @@ Please be aware that due to the incompatibility of EPL and GPL licenses, one may and distribute the result. ( see https://mmilinkov.wordpress.com/2010/04/06/epl-gpl-commentary/). However from pure technical standpoint Titan can be compiled on GPL-licensed Cygwin as detailed below. -Last tested cygwin version: 3.1.7 +Last tested cygwin version: 3.2.0 Cygwin setup - If Cygwin is installed already, refresh your Cygwin installation @@ -26,7 +26,7 @@ Cygwin setup (A) Download and execute the latest cygwin installer utility, please use the 64-bit version installer: https://cygwin.com/setup-x86_64.exe - Latest setup version 2.904 (64 bit) + Latest setup version 2.908 (64 bit) (B) Select Install from Internet (recommended to save local disk space) @@ -105,9 +105,9 @@ Cygwin setup Starting with Cygwin 1.7.34 or later, set "db_home" in file "/etc/nsswitch.conf". Fore example set: - "db_home: /cygdrive/c/Users/<yourUserId>/My_Home". + "db_home: /cygdrive/c/Users/<yourUserId>/Documents/My_Home". - After changing the your home directory, + After changing your home directory, copy the .bashrc and the .profile file from the old home directory to the new home directory (from <your cygwin installation directory>/home/<yourUserId> to "/cygdrive/c/Users/<yourUserId>/Documents/My_Home") @@ -126,21 +126,21 @@ Cygwin setup Note: It is not a requirement, but is a kind of best practice to place Titan into a subfolder within your "unix" home directory. Edit the <your cygwin installation directory>/home/<yourUserId>/.bashrc - file. Add these lines to it: + file ( or "/cygdrive/c/Users/<yourUserId>/Documents/My_Home/.bashrc"). Add these lines to it: export TTCN3_DIR=${HOME}/titan.core export PATH=${TTCN3_DIR}/bin:${PATH} export LD_LIBRARY_PATH=${TTCN3_DIR}/lib:${LD_LIBRARY_PATH} or(K) Using TITAN from source code - (K1)Get the latest source code from GitHub: + (K1)Get the latest source code from GitLab: - First time: cd ~/git - git clone https://github.com/eclipse/titan.core.git + git clone https://gitlab.eclipse.org/eclipse/titan/titan.core.git //Folder titan.core will be created - Updating the already existing local repository: cd ~/git/titan.core - git pull https://github.com/eclipse/titan.core.git + git pull https://gitlab.eclipse.org/eclipse/titan/titan.core.git (K2) Download and install JDK from Oracle's download site: http://www.oracle.com/technetwork/java/javase/downloads/index.html diff --git a/README.linux b/README.linux index 4d2637c4414ed649d573f48b7858e319412a1384..3cbfc8e3ff18507b298a0fd091457aa3d1063889 100644 --- a/README.linux +++ b/README.linux @@ -1,4 +1,4 @@ -cd****************************************************************************** +****************************************************************************** * Copyright (c) 2000-2021 Ericsson Telecom AB * All rights reserved. This program and the accompanying materials * are made available under the terms of the Eclipse Public License v2.0 @@ -55,13 +55,13 @@ suse: sudo zypper install libpcap-devel libpcap1 2.Clone or update the titan directory from git into /home/<user_id>/titan.core cd /home/<user_id>/ -git clone https://github.com/eclipse/titan.core.git titan.core +git clone https://gitlab.eclipse.org/eclipse/titan/titan.core.git titan.core or Update the already existing local repository: cd /home/<user_id>/titan.core -git pull https://github.com/eclipse/titan.core.git +git pull https://gitlab.eclipse.org/eclipse/titan/titan.core.git 3. Configure the build diff --git a/docker/Dockerfile.alpine b/docker/Dockerfile.alpine index 4ab240ab4d14a5b6ef3030bf7f1d85da749fd625..f0b76bb095332d97ed61dbf28e67e3a9b56a0713 100644 --- a/docker/Dockerfile.alpine +++ b/docker/Dockerfile.alpine @@ -16,9 +16,9 @@ RUN echo 'sh' >> /home/titan/.bashrc ## CLONE TITAN WORKDIR /home/titan -RUN git clone https://github.com/eclipse/titan.core.git +RUN git clone https://gitlab.eclipse.org/eclipse/titan/titan.core.git WORKDIR /home/titan/titan.core/ -RUN git checkout tags/7.2.1_final +RUN git checkout tags/7.2.2 ## SET UP ENV VARIABLES ENV TTCN3_DIR=/home/titan/titan.core/Install diff --git a/docker/Dockerfile.ubuntu b/docker/Dockerfile.ubuntu index 66bdfa757c69a3c18133bee8b0fb00f251be9bee..fe98637aa2e3bea81735c38f4ebddca7ed1e0f37 100644 --- a/docker/Dockerfile.ubuntu +++ b/docker/Dockerfile.ubuntu @@ -23,10 +23,10 @@ ENV PATH=$TTCN3_DIR/bin:$PATH \ ## CLONE TITAN WORKDIR /home/titan/ -RUN git clone https://github.com/eclipse/titan.core.git -# Checkout release 7.2.1 +RUN git clone https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins.git +# Checkout release 7.2.2 WORKDIR /home/titan/titan.core -RUN git checkout tags/7.2.1_final +RUN git checkout tags/7.2.2 ## SET Makefile.personal # TTCN3_DIR := /home/titan/titan.core/Install diff --git a/mctr2/mctr/ttcn3_start b/mctr2/mctr/ttcn3_start index 9df39db7c29098592cfd8de085c97bc25a472e19..450d01016793174500ba281760d8a480ef4f4123 100755 --- a/mctr2/mctr/ttcn3_start +++ b/mctr2/mctr/ttcn3_start @@ -37,6 +37,7 @@ exec expect "$0" "$@" ## ETH/XZR Adam Delic 2012.02.22 v1.7 ## ## ETH Adam Knapp 2021.03.03 v1.8 ## ## ETH Adam Knapp 2021.04.15 v1.9 ## +## ETH Adam Knapp 2021.05.12 v1.10 ## ##################################################### puts "ttcn3_start: Starting the test suite" @@ -262,7 +263,7 @@ expect { if {$isJAR == 0} { spawn $ETS $hostname $port } else { - spawn java -jar $ETS $hostname $port + spawn java -Dfile.encoding=UTF-8 -jar $ETS $hostname $port } set hc_id $spawn_id expect { diff --git a/usrguide/PRI/PRI.adoc b/usrguide/PRI/PRI.adoc index b15b1e636e84875efa3d303531ad30a3e48f1c28..c089bab0a6f6fb33cab18a0f3a89ffdd58b542ad 100644 --- a/usrguide/PRI/PRI.adoc +++ b/usrguide/PRI/PRI.adoc @@ -51,21 +51,21 @@ Legend: R = Revised, N = New, C = Cancelled, E = Equal [width="100%",cols="25%,25%,25%,25%",options="header",] |=== |Name |Old Revision |New Revision | -|link:https://github.com/eclipse/titan.core/blob/master/usrguide/releasenotes/releasenotes.adoc[Release Notes for TITAN TTCN-3 Test Executor] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.core/blob/master/usrguide/installationguide/installationguide.adoc[Installation guide for TITAN TTCN-3 Test Executor] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.EclipsePlug-ins/blob/master/org.eclipse.titan.help/docs/Eclipse_installationguide/Eclipse_installationguide.adoc[Installation Guide for TITAN Designer and TITAN Executor for the Eclipse IDE] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.core/blob/master/usrguide/userguide/UserGuide.adoc[User Guide for TITAN] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.core/blob/master/usrguide/referenceguide/ReferenceGuide.adoc[Programmers Technical Reference for TITAN TTCN-3 Test Executor] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.EclipsePlug-ins/tree/master/org.eclipse.titan.designer/docs/Eclipse_Designer_userguide/DesignerUserGuide.adoc[User Guide for the TITAN Designer for the Eclipse IDE] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.EclipsePlug-ins/tree/master/org.eclipse.titan.executor/docs/Eclipse_Executor_userguide/ExecutorUserGuide.adoc[User Guide for the TITAN Executor for the Eclipse IDE] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.core/blob/master/usrguide/apiguide/Apiguide.adoc[API Technical Reference for TITAN TTCN-3 Test Executor] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.core/blob/master/titan_executor_api/doc/Titan_Executor_API_User_Guide.adoc[Titan Executor API user guide] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.EclipsePlug-ins/blob/master/org.eclipse.titanium/docs/Titanium_referenceguide/Titanium_referenceguide.adoc[Programmers Tech. Reference Guide for Titanium] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.core/blob/master/usrguide/java_referenceguide/JavaReferenceGuide.adoc[Programmers Tech. Reference Guide for the Java Codegenerator] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.EclipsePlug-ins/blob/master/org.eclipse.titanium.refactoring/docs/Titanium_Refactoring_Description/Titanium_Refactoring_Description.adoc[Titanium Refactoring Description] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.EclipsePlug-ins/blob/master/org.eclipse.titanium/docs/Titanium_Description/Titanium_Description.adoc[Titanium Description] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.core/blob/master/usrguide/SoC_TITAN/SoC_TITAN.adoc[Statement of Compliance for Eclipse Titan] | 7.2.1 | 7.2.2 |R -|link:https://github.com/eclipse/titan.core/blob/master/usrguide/SoC_XML_TITAN/SoC_XML_TITAN.adoc[Statement of Compliance for use of XML schema in Eclipse Titan] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/releasenotes/releasenotes.adoc[Release Notes for TITAN TTCN-3 Test Executor] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/installationguide/installationguide.adoc[Installation guide for TITAN TTCN-3 Test Executor] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/blob/master/org.eclipse.titan.help/docs/Eclipse_installationguide/Eclipse_installationguide.adoc[Installation Guide for TITAN Designer and TITAN Executor for the Eclipse IDE] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/userguide/UserGuide.adoc[User Guide for TITAN] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/referenceguide/ReferenceGuide.adoc[Programmers Technical Reference for TITAN TTCN-3 Test Executor] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/tree/master/org.eclipse.titan.designer/docs/Eclipse_Designer_userguide/DesignerUserGuide.adoc[User Guide for the TITAN Designer for the Eclipse IDE] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/tree/master/org.eclipse.titan.executor/docs/Eclipse_Executor_userguide/ExecutorUserGuide.adoc[User Guide for the TITAN Executor for the Eclipse IDE] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/apiguide/Apiguide.adoc[API Technical Reference for TITAN TTCN-3 Test Executor] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/titan_executor_api/doc/Titan_Executor_API_User_Guide.adoc[Titan Executor API user guide] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/blob/master/org.eclipse.titanium/docs/Titanium_referenceguide/Titanium_referenceguide.adoc[Programmers Tech. Reference Guide for Titanium] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/java_referenceguide/JavaReferenceGuide.adoc[Programmers Tech. Reference Guide for the Java Codegenerator] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/blob/master/org.eclipse.titanium.refactoring/docs/Titanium_Refactoring_Description/Titanium_Refactoring_Description.adoc[Titanium Refactoring Description] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/blob/master/org.eclipse.titanium/docs/Titanium_Description/Titanium_Description.adoc[Titanium Description] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/SoC_TITAN/SoC_TITAN.adoc[Statement of Compliance for Eclipse Titan] | 7.2.1 | 7.2.2 |R +|link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/SoC_XML_TITAN/SoC_XML_TITAN.adoc[Statement of Compliance for use of XML schema in Eclipse Titan] | 7.2.1 | 7.2.2 |R |=== = Reason for revision diff --git a/usrguide/apiguide/2-test_ports.adoc b/usrguide/apiguide/2-test_ports.adoc index b999a0abbf41b1634274dca6218d53b3a73a786c..d9d889baae42af70cadc81f3cb46dd2fd250f018 100644 --- a/usrguide/apiguide/2-test_ports.adoc +++ b/usrguide/apiguide/2-test_ports.adoc @@ -403,7 +403,7 @@ Test Port parametersfootnote:[Test Port parameters have been introduced in versi For instance, using Test Port parameters can be used to convey configuration data (that is, some options or extra information that is necessary for correct operation) or lower protocol layer addresses (for example, IP addresses). -Test Port parameters shall be specified by the user of executable tests in section `[TESTPORT_PARAMETERS]` of the run-time configuration file (see section `[TESTPORT_PARAMETERS]` in link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]). The parameters are maintained for each test port instance separately; wildcards can be used as well. In the latter case the parameter is passed to all Test Port matching the wildcard. +Test Port parameters shall be specified by the user of executable tests in section `[TESTPORT_PARAMETERS]` of the run-time configuration file (see section `[TESTPORT_PARAMETERS]` in link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]). The parameters are maintained for each test port instance separately; wildcards can be used as well. In the latter case the parameter is passed to all Test Port matching the wildcard. Each Test Port parameter must have a name, which must be unique within the Test Port only. The name must be a valid identifier, that is, it must begin with a letter and must contain alphanumerical characters only. @@ -739,7 +739,7 @@ The address value stored in the port queue is used in `receive`, `trigger`, `get == Provider Port Types -Test Ports that belong to port types marked with `extension` attribute `"provider"` have a slightly different API. Such port types are used to realize dual-faced ports, the details of which can be found in section "Dual-faced ports" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. +Test Ports that belong to port types marked with `extension` attribute `"provider"` have a slightly different API. Such port types are used to realize dual-faced ports, the details of which can be found in section "Dual-faced ports" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. The purpose of this API is to allow the re-use of the Test Port class with other port types marked with attribute `user` or with ports with translation capability (link:https://www.etsi.org/deliver/etsi_es/202700_202799/202781/01.04.01_60/es_202781v010401p.pdf[Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Configuration and Deployment Support]). The user port types may have different lists of incoming and outgoing message types. The transformations between incoming and outgoing messages, which are specified entirely by the attribute of the user port type, are done independently of the Test Port. The Test Port needs to support the sending and reception of message types that are listed in the provider port type. diff --git a/usrguide/apiguide/4-logger_plug-ins.adoc b/usrguide/apiguide/4-logger_plug-ins.adoc index 744390bc74489a4d03bd76bc5edcc4e7f6211fcf..6d8a23f0acf6502813f65731e98e4ceed3f567b2 100644 --- a/usrguide/apiguide/4-logger_plug-ins.adoc +++ b/usrguide/apiguide/4-logger_plug-ins.adoc @@ -77,11 +77,11 @@ void log(const TitanLoggerApi::TitanLogEvent& event, bool log_buffered, bool separate_file, bool use_emergency_mask); ---- -The first parameter event is the event itself, the second parameter `log_buffered` indicates, whether the event is coming from an internal buffer or not, `separate_file` and `use_emergency_mask` are configuration options for emergency logging. The `use_emergency_mask` flag indicates that the given event is an emergency event and should be handled in a special way by the plug-ins, the `separate_file` flag indicates that all the emergency events should be handled separately (for example written into a separate file). For more details on emergency logging please check link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. In this function, the plug-in can handle the log events individually depending on the event’s type (that is, the alternative selected in the union `event.logEvent().choice()).` +The first parameter event is the event itself, the second parameter `log_buffered` indicates, whether the event is coming from an internal buffer or not, `separate_file` and `use_emergency_mask` are configuration options for emergency logging. The `use_emergency_mask` flag indicates that the given event is an emergency event and should be handled in a special way by the plug-ins, the `separate_file` flag indicates that all the emergency events should be handled separately (for example written into a separate file). For more details on emergency logging please check link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. In this function, the plug-in can handle the log events individually depending on the event’s type (that is, the alternative selected in the union `event.logEvent().choice()).` `TitanLoggerApi::TitanLogEvent` is a generated type defined in TitanLoggerApi.xsd, which can be found in `${TTCN3_DIR}/include`. This file contains all the necessary type definitions a logger plug-in should be aware of. The corresponding header files generated from this XSD file can be found in `${TTCN3_DIR}/include/{RT1/RT2}`. The mapping between TTCN-3 types and {cpp} types is defined in link:5-mapping_ttcn3_data_types_to_c+\+_constructs.adoc[Mapping TTCN–3 Data Types to {cpp} Constructs]. //The mapping between XSD and TTCN-3 types is defined in *Error! Reference source not found.* == Execution -When a logger plug-in is compiled (the SO is ready) it should be configured in the configuration file. For details check link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. Additionally, `LD_LIBRARY_PATH` should contain the directory of the plug-in and `${TTCN3_DIR}/lib` as well. If the runtime linker (the loader) is unable to find any of the given logger plug-ins an error will be given. +When a logger plug-in is compiled (the SO is ready) it should be configured in the configuration file. For details check link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. Additionally, `LD_LIBRARY_PATH` should contain the directory of the plug-in and `${TTCN3_DIR}/lib` as well. If the runtime linker (the loader) is unable to find any of the given logger plug-ins an error will be given. diff --git a/usrguide/apiguide/5-encoding_and_decoding.adoc b/usrguide/apiguide/5-encoding_and_decoding.adoc index 3faf5a8cf8edaacedb20ca5e21836f6266878133..164c900cebdc28a1f49f15793ef63b6ced792cca 100644 --- a/usrguide/apiguide/5-encoding_and_decoding.adoc +++ b/usrguide/apiguide/5-encoding_and_decoding.adoc @@ -3,7 +3,7 @@ :table-number: 2 :toc: -This tool is equipped with several standard encoding/decoding mechanisms. A part of these functions reside in the core library, but the type-dependent part must be generated by the compiler. In order to reduce the code size and compilation time, the code generation for encoding functions (separately for different encoders) can be switched off if they are not needed. For details, see section "Command line syntax" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. +This tool is equipped with several standard encoding/decoding mechanisms. A part of these functions reside in the core library, but the type-dependent part must be generated by the compiler. In order to reduce the code size and compilation time, the code generation for encoding functions (separately for different encoders) can be switched off if they are not needed. For details, see section "Command line syntax" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. To make it easier to use the encoding features, a unified common API was developed. With help of this API the behaviour of the test executor in different error situations can be set during coding. There is also a common buffer class. The details of the above mentioned API as well as the specific features of the certain encoders are explained in the following sections. @@ -305,7 +305,7 @@ void MyPort2::outgoing_send(const OCTETSTRING& send_par) == RAW -You can use the encoding rules defined in the section "RAW encoder and decoder" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] to encode and decode the following TTCN–3 types: +You can use the encoding rules defined in the section "RAW encoder and decoder" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] to encode and decode the following TTCN–3 types: * boolean @@ -424,7 +424,7 @@ void MyPort2::outgoing_send(const OCTETSTRING& send_par) == TEXT -You can use the encoding rules defined in the section "TEXT encoder, decoder" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] to encode and decode the following TTCN–3 types: +You can use the encoding rules defined in the section "TEXT encoder, decoder" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] to encode and decode the following TTCN–3 types: * boolean @@ -642,7 +642,7 @@ void MyPort2::outgoing_send(const OCTETSTRING& send_par) ---- == JSON -The encoding rules defined in the section "JSON Encoder and Decoder" of the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] can be used to encode and decode the following TTCN–3 types: +The encoding rules defined in the section "JSON Encoder and Decoder" of the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] can be used to encode and decode the following TTCN–3 types: * anytype @@ -807,7 +807,7 @@ void MyPort2::outgoing_send(const OCTETSTRING& send_par) == OER -The encoding rules defined in the section "OER Encoder and Decoder" of the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] can be used to encode and/or decode the values of ASN.1 types. +The encoding rules defined in the section "OER Encoder and Decoder" of the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] can be used to encode and/or decode the values of ASN.1 types. === Error Situations diff --git a/usrguide/apiguide/6-mapping_ttcn3_data_types_to_c++_constructs.adoc b/usrguide/apiguide/6-mapping_ttcn3_data_types_to_c++_constructs.adoc index 1d23b59d357645d6e9fed6af4d61122939384e44..8d3fd07b5fcf6ea6b84b0f51abb4a03fde2ef09e 100644 --- a/usrguide/apiguide/6-mapping_ttcn3_data_types_to_c++_constructs.adoc +++ b/usrguide/apiguide/6-mapping_ttcn3_data_types_to_c++_constructs.adoc @@ -1853,7 +1853,7 @@ extern CHARSTRING encode_base64(const OCTETSTRING& msg); extern OCTETSTRING decode_base64(const CHARSTRING& b64); ---- -See the section "Additional predefined functions" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[ Programmer"s Technical Reference] for more details. +See the section "Additional predefined functions" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[ Programmer"s Technical Reference] for more details. [[using-the-signature-classes]] == Using the Signature Classes diff --git a/usrguide/apiguide/7-tips_and_troubleshooting.adoc b/usrguide/apiguide/7-tips_and_troubleshooting.adoc index e8bed557669bbcc67342511a26f7029d722023d8..6e26e1799db66b1e701542d9c0cf58f1d3f8e50f 100644 --- a/usrguide/apiguide/7-tips_and_troubleshooting.adoc +++ b/usrguide/apiguide/7-tips_and_troubleshooting.adoc @@ -98,7 +98,7 @@ In unbuffered mode the message will be put into log immediately as a separate li [source, subs="+quotes"] static void TTCN_Logger::log(int severity, const char *fmt, …); -The parameter severity is used for filtering the log messages. The allowed values of the parameter are listed in table "First level (coarse) log filtering" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. We recommend using in Test Ports only `TTCN_WARNING`, `TTCN_ERROR` and `TTCN_DEBUG`. The parameter `fmt` is a pointer to a format string, which is interpreted as in `printf(3)`. The dots represent the optional additional parameters that are referred in format string. There is no need to put a newline character at the end of format string; otherwise the log file will contain an empty line after your entry. +The parameter severity is used for filtering the log messages. The allowed values of the parameter are listed in table "First level (coarse) log filtering" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. We recommend using in Test Ports only `TTCN_WARNING`, `TTCN_ERROR` and `TTCN_DEBUG`. The parameter `fmt` is a pointer to a format string, which is interpreted as in `printf(3)`. The dots represent the optional additional parameters that are referred in format string. There is no need to put a newline character at the end of format string; otherwise the log file will contain an empty line after your entry. Here is an example, which logs an integer value: [source] @@ -132,7 +132,7 @@ In buffered mode, the following member functions are available. [[begin-event]] ==== begin_event -`begin_event` creates a new empty event buffer within the logger. You have to pass the severity value, which will be valid for all fragments (the list of possible values can be found in the table "First level (coarse) log filtering" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[ Technical Reference]. If the logger already has an unfinished event when begin event is called the pending event will be pushed onto an internal stack of the logger. That event can be continued and completed after finishing the newly created event. +`begin_event` creates a new empty event buffer within the logger. You have to pass the severity value, which will be valid for all fragments (the list of possible values can be found in the table "First level (coarse) log filtering" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[ Technical Reference]. If the logger already has an unfinished event when begin event is called the pending event will be pushed onto an internal stack of the logger. That event can be continued and completed after finishing the newly created event. [source, subs="+quotes"] static void TTCN_Logger::begin_event(int severity); diff --git a/usrguide/apiguide/8-references.adoc b/usrguide/apiguide/8-references.adoc index 79ac88ad3904cdf9cb30669fc277b5f909548e72..f72c3e5dab6f12365bae84d841ec1336d49c98bd 100644 --- a/usrguide/apiguide/8-references.adoc +++ b/usrguide/apiguide/8-references.adoc @@ -28,16 +28,16 @@ * [9] link:https://tools.ietf.org/html/rfc3629[RFC3629: UTF-8, a transformation format of ISO 10646] [[_10]] -* [10] link:https://github.com/eclipse/titan.core/blob/master/usrguide/userguide/UserGuide.adoc[User Guide for TITAN TTCN-3 Test Executor] +* [10] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/userguide/UserGuide.adoc[User Guide for TITAN TTCN-3 Test Executor] [[_11]] -* [11] link:https://github.com/eclipse/titan.core/blob/master/usrguide/installationguide/installationguide.adoc/[Installation guide for TITAN TTCN-3 Test Executor] +* [11] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/installationguide/installationguide.adoc/[Installation guide for TITAN TTCN-3 Test Executor] [[_12]] -* [12] link:https://github.com/eclipse/titan.core/blob/master/usrguide/releasenotes/releasenotes.adoc[Release Notes for TITAN TTCN-3 Test Executor] +* [12] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/releasenotes/releasenotes.adoc[Release Notes for TITAN TTCN-3 Test Executor] [[_13]] -* [13] link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide/ReferenceGuide.adoc[Technical Reference for TITAN TTCN-3 Test Executor] +* [13] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/referenceguide/ReferenceGuide.adoc[Technical Reference for TITAN TTCN-3 Test Executor] [[_14]] * [14] link:http://tldp.org/HOWTO/Program-Library-HOWTO/index.html[David A. Wheeler, Program Library HOWTO] diff --git a/usrguide/installationguide/installationguide.adoc b/usrguide/installationguide/installationguide.adoc index dd90fb9e414f993af8be7b5b90ac24b93b299b06..cc59d31f4787df15350c20d79a1b66daacb4fb35 100644 --- a/usrguide/installationguide/installationguide.adoc +++ b/usrguide/installationguide/installationguide.adoc @@ -237,15 +237,15 @@ NOTE: On Ubuntu 18.04 the default clang version is 6.0.0. == Obtaining the source code to your local machine -The name of the source code repository of Titan is titan.core in the github. Follow steps as follows. +The name of the source code repository of Titan is titan.core in Eclipse GitLab. Follow steps as follows. . First time execute these commands: + `cd ~/git + -git clone https://github.com/eclipse/titan.core.git` + +git clone https://gitlab.eclipse.org/eclipse/titan/titan.core.git` + This way a folder "titan.core", the "titan repository" will be created with the TITAN source code and build system. + To update the already existing repository execute these commands: + `cd ~/git/titan.core + -git pull https://github.com/eclipse/titan.core.git` +git pull https://gitlab.eclipse.org/eclipse/titan/titan.core.git` . Follow the instructions in the file "`titan.core/README.<your platform>`" . Continue with the next paragraph of this document. @@ -387,7 +387,7 @@ If a host-limited key is needed, perform it in the same way but do it as system = References [[_1]] -* [1] link:https://github.com/eclipse/titan.core/blob/master/usrguide/userguide/UserGuide.adoc[User Guide for TITAN TTCN-3 Test Executor] +* [1] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/userguide/UserGuide.adoc[User Guide for TITAN TTCN-3 Test Executor] [[_2]] -* [2] link:https://github.com/eclipse/titan.core/blob/master/usrguide/referenceguide/ReferenceGuide.adoc[Programmers Technical Reference for TITAN TTCN-3 Test Executor] +* [2] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/referenceguide/ReferenceGuide.adoc[Programmers Technical Reference for TITAN TTCN-3 Test Executor] diff --git a/usrguide/java_referenceguide/11-encoding_and_decoding.adoc b/usrguide/java_referenceguide/11-encoding_and_decoding.adoc index 65146506953992c3551ebc04eaa42ebc0d1e3961..1247272bea1fd1a093028d40eb005e4373886884 100644 --- a/usrguide/java_referenceguide/11-encoding_and_decoding.adoc +++ b/usrguide/java_referenceguide/11-encoding_and_decoding.adoc @@ -186,7 +186,7 @@ BER encoding and decoding is not yet supported on the Java side. == RAW -You can use the encoding rules defined in the section "RAW encoder and decoder" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] to encode and decode the following TTCN–3 types: +You can use the encoding rules defined in the section "RAW encoder and decoder" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] to encode and decode the following TTCN–3 types: * boolean @@ -309,7 +309,7 @@ XML encoding and decoding is not yet supported on the Java side. == JSON -The encoding rules defined in the section "JSON Encoder and Decoder" of the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] can be used to encode and decode the following TTCN–3 types: +The encoding rules defined in the section "JSON Encoder and Decoder" of the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference] can be used to encode and decode the following TTCN–3 types: * anytype diff --git a/usrguide/java_referenceguide/12-mapping_ttcn3_data_types_to_java_constructs.adoc b/usrguide/java_referenceguide/12-mapping_ttcn3_data_types_to_java_constructs.adoc index 396419ab2e41321f25854c56a3ab483c259144b5..fca58290ee7ee0b32e9ae996e1fd0aea71135971 100644 --- a/usrguide/java_referenceguide/12-mapping_ttcn3_data_types_to_java_constructs.adoc +++ b/usrguide/java_referenceguide/12-mapping_ttcn3_data_types_to_java_constructs.adoc @@ -1905,7 +1905,7 @@ TitanCharString encode_base64(final TitanOctetString msg); TitanOctetString decode_base64(final TitanCharString b64); ---- -See the section "Additional predefined functions" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[ Programmer"s Technical Reference] for more details. +See the section "Additional predefined functions" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[ Programmer"s Technical Reference] for more details. [[using-the-signature-classes]] == Using the Signature Classes diff --git a/usrguide/java_referenceguide/13-tips_&_troubleshooting.adoc b/usrguide/java_referenceguide/13-tips_&_troubleshooting.adoc index bdc8c940fbffcfd9e17cdbb509c19b8ec616acfd..d753cbbcf62dfc07c3132bb6a4507711a7e029b0 100644 --- a/usrguide/java_referenceguide/13-tips_&_troubleshooting.adoc +++ b/usrguide/java_referenceguide/13-tips_&_troubleshooting.adoc @@ -129,7 +129,7 @@ In unbuffered mode the message will be put into log immediately as a separate li [source, subs="+quotes"] log(final Severity msg_severity, final String formatString, final Object... args ); -The parameter severity is used for filtering the log messages. The allowed values of the parameter are listed in table "First level (coarse) log filtering" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. We recommend using in Test Ports only `TTCN_WARNING`, `TTCN_ERROR` and `TTCN_DEBUG`. The parameter `formatString` is a format string, which is interpreted as in the `String.format` function. The dots represent the optional additional parameters that are referred in format string. There is no need to put a newline character at the end of format string; otherwise the log file will contain an empty line after your entry. +The parameter severity is used for filtering the log messages. The allowed values of the parameter are listed in table "First level (coarse) log filtering" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. We recommend using in Test Ports only `TTCN_WARNING`, `TTCN_ERROR` and `TTCN_DEBUG`. The parameter `formatString` is a format string, which is interpreted as in the `String.format` function. The dots represent the optional additional parameters that are referred in format string. There is no need to put a newline character at the end of format string; otherwise the log file will contain an empty line after your entry. Here is an example, which logs an integer value: [source] @@ -153,7 +153,7 @@ In buffered mode, the following member functions are available. [[begin-event]] ==== begin_event -`begin_event` creates a new empty event buffer within the logger. You have to pass the severity value, which will be valid for all fragments (the list of possible values can be found in the table "First level (coarse) log filtering" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[ Technical Reference]. If the logger already has an unfinished event when begin event is called the pending event will be pushed onto an internal stack of the logger. That event can be continued and completed after finishing the newly created event. +`begin_event` creates a new empty event buffer within the logger. You have to pass the severity value, which will be valid for all fragments (the list of possible values can be found in the table "First level (coarse) log filtering" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[ Technical Reference]. If the logger already has an unfinished event when begin event is called the pending event will be pushed onto an internal stack of the logger. That event can be continued and completed after finishing the newly created event. [source, subs="+quotes"] void begin_event(final Severity msg_severity); diff --git a/usrguide/java_referenceguide/14-references.adoc b/usrguide/java_referenceguide/14-references.adoc index e2d43dbbceba9feeb4ac557f519bd10a01b9bd4a..6a7bc35733bdadc41c9029ce4117c52dfacc0b63 100644 --- a/usrguide/java_referenceguide/14-references.adoc +++ b/usrguide/java_referenceguide/14-references.adoc @@ -37,19 +37,19 @@ * [12] link:https://tools.ietf.org/html/rfc3629[RFC3629: UTF-8, a transformation format of ISO 10646] [[_13]] -* [13] link:https://github.com/eclipse/titan.core/blob/master/usrguide/userguide/[User Guide for TITAN TTCN-3 Test Executor] +* [13] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/userguide/[User Guide for TITAN TTCN-3 Test Executor] [[_14]] -* [14] link:https://github.com/eclipse/titan.core/blob/master/usrguide/installationguide/[Installation guide for TITAN TTCN-3 Test Executor] +* [14] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/installationguide/[Installation guide for TITAN TTCN-3 Test Executor] [[_15]] -* [15] link:https://github.com/eclipse/titan.core/blob/master/usrguide/releasenotes/[Release Notes for TITAN TTCN-3 Test Executor] +* [15] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/releasenotes/[Release Notes for TITAN TTCN-3 Test Executor] [[_16]] -* [16] link:https://github.com/eclipse/titan.core/blob/master/usrguide/apiguide/[API Technical Reference for TITAN TTCN-3 Test Executor] +* [16] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/apiguide/[API Technical Reference for TITAN TTCN-3 Test Executor] [[_17]] -* [17] link:https://github.com/eclipse/titan.EclipsePlug-ins/tree/master/org.eclipse.titan.designer/docs/Eclipse_Designer_userguide/[User Guide for the TITAN Designer for the Eclipse] +* [17] link:https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/tree/master/org.eclipse.titan.designer/docs/Eclipse_Designer_userguide/[User Guide for the TITAN Designer for the Eclipse] [[_18]] * [18] link:https://www.etsi.org/deliver/etsi_es/201800_201899/20187301/04.03.01_60/es_20187301v040301p.pdf[ETSI ES 201 373-1 V4.3.1 (2011-06)] @@ -79,4 +79,4 @@ * [26] link:https://www.etsi.org/deliver/etsi_es/202700_202799/202782/01.03.01_60/es_202782v010301p.pdf[ETSI ES 202 782 V1.3.1. (2015-06 Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: TTCN-3 Performance and Real Time Testing)] [[_27]] -* [27] link:https://github.com/eclipse/titan.core/blob/master/usrguide/referenceguide/[Programmers' Technical Reference Guide for the TITAN TTCN-3 Toolset] +* [27] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/referenceguide/[Programmers' Technical Reference Guide for the TITAN TTCN-3 Toolset] diff --git a/usrguide/java_referenceguide/9-test_ports.adoc b/usrguide/java_referenceguide/9-test_ports.adoc index 53052abc13a9adde57f9ddce0c48138f928f7636..c53fc657994cbf1ea589732495f09e4a588a11ee 100644 --- a/usrguide/java_referenceguide/9-test_ports.adoc +++ b/usrguide/java_referenceguide/9-test_ports.adoc @@ -185,7 +185,7 @@ Test Port parameters shall contain information which is independent from the TTC For instance, using Test Port parameters can be used to convey configuration data (that is, some options or extra information that is necessary for correct operation) or lower protocol layer addresses (for example, IP addresses). -Test Port parameters shall be specified by the user of executable tests in the `[TESTPORT_PARAMETERS]` section of the run-time configuration file (see section `[TESTPORT_PARAMETERS]` in link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]). The parameters are maintained for each test port instance separately; wildcards can be used as well. In the latter case the parameter is passed to all Test Port matching the wildcard. +Test Port parameters shall be specified by the user of executable tests in the `[TESTPORT_PARAMETERS]` section of the run-time configuration file (see section `[TESTPORT_PARAMETERS]` in link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]). The parameters are maintained for each test port instance separately; wildcards can be used as well. In the latter case the parameter is passed to all Test Port matching the wildcard. Each Test Port parameter must have a name, which must be unique within the Test Port only. The name must be a valid identifier, that is, it must begin with a letter and must contain alphanumerical characters only. @@ -468,7 +468,7 @@ The address value stored in the port queue is used in `receive`, `trigger`, `get == Provider Port Types -Test Ports that belong to port types marked with `extension` attribute `"provider"` have a slightly different API. Such port types are used to realize dual-faced ports, the details of which can be found in section "Dual-faced ports" in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. +Test Ports that belong to port types marked with `extension` attribute `"provider"` have a slightly different API. Such port types are used to realize dual-faced ports, the details of which can be found in section "Dual-faced ports" in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer's Technical Reference]. The purpose of this API is to allow the re-use of the Test Port class with other port types marked with attribute `user` or with ports with translation capability (link:https://www.etsi.org/deliver/etsi_es/202700_202799/202781/01.04.01_60/es_202781v010401p.pdf[Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; TTCN-3 Language Extensions: Configuration and Deployment Support]). The user port types may have different lists of incoming and outgoing message types. The transformations between incoming and outgoing messages, which are specified entirely by the attribute of the user port type, are done independently of the Test Port. The Test Port needs to support the sending and reception of message types that are listed in the provider port type. diff --git a/usrguide/referenceguide/13-references.adoc b/usrguide/referenceguide/13-references.adoc index f6d7ed1c03a7726837971119b452174761d9d85e..eac42a15e73334048d798d9c7dd43b460c73c9d5 100644 --- a/usrguide/referenceguide/13-references.adoc +++ b/usrguide/referenceguide/13-references.adoc @@ -37,19 +37,19 @@ * [12] link:https://tools.ietf.org/html/rfc3629[RFC3629: UTF-8, a transformation format of ISO 10646] [[_13]] -* [13] link:https://github.com/eclipse/titan.core/blob/master/usrguide/userguide/[User Guide for TITAN TTCN-3 Test Executor] +* [13] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/userguide/[User Guide for TITAN TTCN-3 Test Executor] [[_14]] -* [14] link:https://github.com/eclipse/titan.core/blob/master/usrguide/installationguide/[Installation guide for TITAN TTCN-3 Test Executor] +* [14] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/installationguide/[Installation guide for TITAN TTCN-3 Test Executor] [[_15]] -* [15] link:https://github.com/eclipse/titan.core/blob/master/usrguide/releasenotes/[Release Notes for TITAN TTCN-3 Test Executor] +* [15] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/releasenotes/[Release Notes for TITAN TTCN-3 Test Executor] [[_16]] -* [16] link:https://github.com/eclipse/titan.core/blob/master/usrguide/apiguide/[API Technical Reference for TITAN TTCN-3 Test Executor] +* [16] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/apiguide/[API Technical Reference for TITAN TTCN-3 Test Executor] [[_17]] -* [17] link:https://github.com/eclipse/titan.EclipsePlug-ins/tree/master/org.eclipse.titan.designer/docs/Eclipse_Designer_userguide/[User Guide for the TITAN Designer for the Eclipse] +* [17] link:https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/tree/master/org.eclipse.titan.designer/docs/Eclipse_Designer_userguide/[User Guide for the TITAN Designer for the Eclipse] [[_18]] * [18] link:https://www.etsi.org/deliver/etsi_es/201800_201899/20187301/04.03.01_60/es_20187301v040301p.pdf[ETSI ES 201 373-1 V4.3.1 (2011-06)] diff --git a/usrguide/releasenotes/releasenotes.adoc b/usrguide/releasenotes/releasenotes.adoc index c26b64de61eff8efd6ff4f0877bba63c4827aaed..85766ccb5d40c99ccbe9b47c0afbec7c8919bb6a 100644 --- a/usrguide/releasenotes/releasenotes.adoc +++ b/usrguide/releasenotes/releasenotes.adoc @@ -112,13 +112,13 @@ This a bugfix release, with the following new features: This release introduces two major new features in the form of two new experimental Eclipse plug-ins: -* a Java codegeneration plug-in, see: https://github.com/eclipse/titan.core/blob/master/usrguide/java_referenceguide/JavaReferenceGuide.adoc +* a Java codegeneration plug-in, see: https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/java_referenceguide/JavaReferenceGuide.adoc and also: -https://github.com/eclipse/titan.core/blob/master/usrguide/JavaCodegenExecTutorial.pdf +https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/JavaCodegenExecTutorial.pdf * a Refactoring plug-in, see: -https://github.com/eclipse/titan.EclipsePlug-ins/blob/master/org.eclipse.titanium.refactoring/docs/Titanium_Refactoring_Description/Titanium_Refactoring_Description.adoc +https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/blob/master/org.eclipse.titanium.refactoring/docs/Titanium_Refactoring_Description/Titanium_Refactoring_Description.adoc Apart from the above, this version has the following new features of the Titan compiler and excutor: @@ -1402,7 +1402,7 @@ Released on Jun 12, 2009 * Support for XML encoding and decoding is introduced, together with a new command line tool that converts XSD files into TTCN-3 modules. -* The TTCN-3 type Anytype is now supported with some restrictions (see section 4.2 of the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer Reference Guide]). +* The TTCN-3 type Anytype is now supported with some restrictions (see section 4.2 of the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer Reference Guide]). * A new runtime was introduced, that requires much less code to be generated and compiled at the cost of minor decrease in runtime performance. The original runtime is advised to be used in load test scenarios (for this it is called load test runtime), while the new runtime is advised to be used in function test scenarios (for this it is called function test runtime). @@ -2418,7 +2418,7 @@ Released on November 5, 2004. * Log Browser saves the configured view (columns shown) in the resource file. -* The Configuration Editor of the GUI has been rewritten. Now it also handles the comments in the configuration file. The comments should be above the assignments. See Part II of the link:https://github.com/eclipse/titan.core/tree/master/usrguide/userguide[TITAN TTCN–3 User Guide] for further details. +* The Configuration Editor of the GUI has been rewritten. Now it also handles the comments in the configuration file. The comments should be above the assignments. See Part II of the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/userguide[TITAN TTCN–3 User Guide] for further details. * The GUI does not open Process output tabs for the external text editor, Log browser and the font / look and feel configuration programs. @@ -2911,7 +2911,7 @@ Released on September 19, 2003. * It is now possible to give a `match` operation as an argument to the TTCN–3 log statements. This logs the matching process field-by-field (like in case of failed receive statements) instead of the boolean result. -* The following new Main Controller commands were introduced: `info`, `stop`, `pause`, `continue`, `log`. See Section 12.3.1 of the link:https://github.com/eclipse/titan.core/tree/master/usrguide/userguide[TITAN TTCN–3 User Guide] for details. +* The following new Main Controller commands were introduced: `info`, `stop`, `pause`, `continue`, `log`. See Section 12.3.1 of the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/userguide[TITAN TTCN–3 User Guide] for details. *Fixed bugs* @@ -3063,7 +3063,7 @@ Released on June 4, 2003. * When execution was started in parallel mode and the MC detected a version or module checksum mismatch for one of the HCs, the error message appeared only in the log file of the corresponding HC. Now the error message given by the MC (indicating the reason of the failure) is printed to the standard error of the HC as well. -* The expect script called `*ttcn3 start*` (see Section 12.3.4 of the link:https://github.com/eclipse/titan.core/tree/master/usrguide/userguide[TITAN TTCN–3 User Guide] for details) was missing from the binary packages and the scripts delivered with versions 1.2.plx are not compatible with the command line interface of the new MC. A new version of the script was added to the packages. This seems to be more robust when handling console messages coming from the HC or TCs because the former one could cause deadlocks if the messages arrived too frequently. +* The expect script called `*ttcn3 start*` (see Section 12.3.4 of the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/userguide[TITAN TTCN–3 User Guide] for details) was missing from the binary packages and the scripts delivered with versions 1.2.plx are not compatible with the command line interface of the new MC. A new version of the script was added to the packages. This seems to be more robust when handling console messages coming from the HC or TCs because the former one could cause deadlocks if the messages arrived too frequently. * When the `-l` command line switch was used with the ETS (in order to obtain the list of test cases and control parts) and the initialization of constants has failed the program exited with abort signal abnormally in both single and parallel modes. The exception caused by this fatal error is now caught and the program terminates with non-zero exit status after printing the error message. @@ -3245,7 +3245,7 @@ Released on October 11, 2002. * The missing documentation of RAW and BER PDU encoders/decoders was added. -* Two new log processing tools: `logmerge` and `logfilter`. See sections 13.1 and 13.2 of the link:https://github.com/eclipse/titan.core/tree/master/usrguide/userguide[TITAN TTCN–3 User Guide]. +* Two new log processing tools: `logmerge` and `logfilter`. See sections 13.1 and 13.2 of the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/userguide[TITAN TTCN–3 User Guide]. * The ETSes can print the list of the test cases and modules. @@ -3323,7 +3323,7 @@ Released on July 29, 2002. * The extra matching attributes (i.e.`ifpresent` or `length` matches) can be used for compound templates as well. Because of a mistake, the TTCN–3 BNF allows them only with single values. -* New command line options of the compiler: `-n`, `-o`, `-p`, `-u` and `-w`. See the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN TTCN–3 Programmer´s Technical Reference] for details. +* New command line options of the compiler: `-n`, `-o`, `-p`, `-u` and `-w`. See the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN TTCN–3 Programmer´s Technical Reference] for details. * The format of timestamps in log file can be configured. The event type names can also be logged for each event. These options are useful for log post-processing. @@ -3380,7 +3380,7 @@ Released on February 11 2002. * The template attribute `ifpresent` is supported for optional record/set fields. -* An HTML report generator was added to the official package. See Section 13.4 of the link:https://github.com/eclipse/titan.core/tree/master/usrguide/userguide[TITAN TTCN–3 User Guide] for details. +* An HTML report generator was added to the official package. See Section 13.4 of the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/userguide[TITAN TTCN–3 User Guide] for details. *Fixed bugs* @@ -3735,7 +3735,7 @@ Although there were no direct changes done to the testport API, the version hand * The version of gcc using the GCC_VERSION macro -For more information please consult section 4.23.2 of the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN programmers reference guide]. +For more information please consult section 4.23.2 of the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN programmers reference guide]. [[test-port-version-1-8-pl1]] == Version 1.8.pl1 @@ -3861,7 +3861,7 @@ No changes. [[test-port-version-1-5-pl0]] == Version 1.5.pl0 -* The {cpp} API for invoking the RAW and BER encoding/decoding functions has significantly changed. The purpose of changes was to provide a common, unified and more flexible interface for both encoding methods. See the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN TTCN–3 Programmer´s Technical Reference] for more details. (INCOMPATIBLE) +* The {cpp} API for invoking the RAW and BER encoding/decoding functions has significantly changed. The purpose of changes was to provide a common, unified and more flexible interface for both encoding methods. See the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN TTCN–3 Programmer´s Technical Reference] for more details. (INCOMPATIBLE) [[test-port-version-1-4-pl5]] == Version 1.4.pl5 @@ -3904,7 +3904,7 @@ No changes. * The symbolic constants NULL ADDRESS, MTC ADDRESS and SYSTEM ADDRESS were renamed to NULL COMPREF, MTC COMPREF and SYSTEM COMPREF, respectively. (INCOMPATIBLE) -* Usage of TTCN–3 `address` type is now supported. See the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN TTCN–3 Programmer´s Technical Reference]. (ADDITION) +* Usage of TTCN–3 `address` type is now supported. See the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN TTCN–3 Programmer´s Technical Reference]. (ADDITION) [[test-port-version-1-2-pl4]] == Version 1.2.pl4 @@ -4019,9 +4019,9 @@ No changes. 5. link:https://www.itu.int/rec/T-REC-X.682-200207-S[ITU-T, X.682, Information Technology Abstract Syntax Notation One (ASN.1): Constraint specification International Telecommunication Union, July 2002] -6. link:https://github.com/eclipse/titan.core/blob/master/usrguide/installationguide/[Installation guide for TITAN TTCN-3 Test Executor] +6. link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/installationguide/[Installation guide for TITAN TTCN-3 Test Executor] -7. link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[Programmer’s Technical Reference for TITAN TTCN-3 Executor] +7. link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[Programmer’s Technical Reference for TITAN TTCN-3 Executor] -8. link:https://github.com/eclipse/titan.core/blob/master/usrguide/userguide/[User Guide for TITAN TTCN-3 Test Executor] +8. link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/userguide/[User Guide for TITAN TTCN-3 Test Executor] diff --git a/usrguide/userguide/1-about_the_document.adoc b/usrguide/userguide/1-about_the_document.adoc index d2a89c1182359ad83e1e62c8ad0a45b9a83f816a..2ac066945154ae7203a24fc157927acf75f5d04b 100644 --- a/usrguide/userguide/1-about_the_document.adoc +++ b/usrguide/userguide/1-about_the_document.adoc @@ -6,7 +6,7 @@ The purpose of this document is to provide detailed information on using the TIT == Target Groups -This document is intended for users of the TITAN TTCN–3 Test Toolset. In addition to this document, readers requiring additional information on creating and building test suites or writing test ports are referred to the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor]. +This document is intended for users of the TITAN TTCN–3 Test Toolset. In addition to this document, readers requiring additional information on creating and building test suites or writing test ports are referred to the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor]. NOTE: Test port writing requires a sound knowledge of {cpp} programming. diff --git a/usrguide/userguide/2-overview_of_titan.adoc b/usrguide/userguide/2-overview_of_titan.adoc index 848818885c45a042ac8eb66e6ee3df0b7139861f..bd273c2e538e3b572650afd429ce815f4519de64 100644 --- a/usrguide/userguide/2-overview_of_titan.adoc +++ b/usrguide/userguide/2-overview_of_titan.adoc @@ -1,7 +1,7 @@ = Overview of TITAN This Test Executor is an implementation of the TTCN–3 Core Language standard with support of ASN.1. There are limitations to supported TTCN–3 language constructs in the Test Executor. In addition, there are some non-standard extensions to the TTCN–3 language implemented by TITAN. Information on these limitations and extensions and also some clarifications of how the standard has been implemented in TITAN, refer to the -link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor]. +link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor]. == Components diff --git a/usrguide/userguide/3-creating_executable_test_suites_from_the_command-l.adoc b/usrguide/userguide/3-creating_executable_test_suites_from_the_command-l.adoc index 2b19e750237b51092d5729ed36413a9ce8ae3b47..17c661339625e072eae90eb57a9af85be8baf518 100644 --- a/usrguide/userguide/3-creating_executable_test_suites_from_the_command-l.adoc +++ b/usrguide/userguide/3-creating_executable_test_suites_from_the_command-l.adoc @@ -67,7 +67,7 @@ The `Makefile` for a project can be generated using the Makefile generator tool [source,subs="+quotes"] ** $TTCN3_DIR/bin/ttcn3_makefilegen [options] <Main module> {Module}* {Test_Port}* {Other_File}* ** -* `[options]` can be one or more of the options that are listed in the TITAN Programmer's Technical Reference for link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor]. +* `[options]` can be one or more of the options that are listed in the TITAN Programmer's Technical Reference for link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor]. * `<Main module>` is the main TTCN–3 Core Language module. The argument can be either a file name (with or without path) or a module name. The name of the desired executable will be derived from the name of this module unless the `-e` option is used. @@ -385,7 +385,7 @@ Creates or updates the object files created from the {cpp} source files. This co Creates Test Port skeleton header and source files for all port types in the input TTCN-3 modules. Existing Test Port files will not be overwritten. * `*make shared_objects*` -Creates the shared object files from object files, compiled with `-fPIC`. This target is present only when dynamic linking is enabled. For detailed information, refer to the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer’s Reference]. +Creates the shared object files from object files, compiled with `-fPIC`. This target is present only when dynamic linking is enabled. For detailed information, refer to the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer’s Reference]. * `*make run*` + @@ -521,4 +521,4 @@ if applicable) should be added to `LD_LIBRARY_PATH` in addition to `$TTCN3_DIR/l Otherwise, the resulting executable may not run. If moving the executable from one machine to another, all the generated shared object (.so) files should be copied as well. -For more information about the `-l` command line switch, please consult the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor]. +For more information about the `-l` command line switch, please consult the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor]. diff --git a/usrguide/userguide/4-executing_test_suites.adoc b/usrguide/userguide/4-executing_test_suites.adoc index a6a5ca30136ed5e00da42bf9efac35f93578eb5b..34f9d355bea6027e3af92618379ed21502be9ade 100644 --- a/usrguide/userguide/4-executing_test_suites.adoc +++ b/usrguide/userguide/4-executing_test_suites.adoc @@ -9,7 +9,7 @@ The behavior of the executable test program is described in the run-time configu Each section of the configuration file begins with a section name within square brackets. Different sections use different syntax, thus the section name determines the possible syntax of the members. -Refer to the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor] for details of the runtime configuration file including descriptions of each of its sections and examples. +Refer to the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor] for details of the runtime configuration file including descriptions of each of its sections and examples. [[Running-Non-parallel-Test-Suites]] == Running Non-parallel Test Suites @@ -28,7 +28,7 @@ The ETS also accepts the command line options `-l` and `-v` with the following s * `*-l*` + -Lists the names of all control parts and individually executable test cases of the ETS to standard output. The list is suitable as the `[EXECUTE]` section of a configuration file. Refer to link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor] for more details. +Lists the names of all control parts and individually executable test cases of the ETS to standard output. The list is suitable as the `[EXECUTE]` section of a configuration file. Refer to link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor] for more details. * `*-p*` + @@ -93,7 +93,7 @@ This section controls the behavior of the main controller when executing a test TITAN processes the configuration file sequentially. If a section occurs several times in the configuration file, all sections will be processed without an error message. -Refer to the corresponding chapter of the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor] for details of the runtime configuration file including descriptions of each of its sections and examples. +Refer to the corresponding chapter of the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor] for details of the runtime configuration file including descriptions of each of its sections and examples. == Running Parallel Test Suites @@ -149,7 +149,7 @@ Parallel Test Components are also instances of the same executable test program. [[the-ttcn-3-main-controller]] === The TTCN–3 Main Controller -The binary executable of Main Controller is `$TTCN3_DIR/bin/mctr_cli`. It takes the optional configuration file (<<The-Run-time-Configuration-File, The Run-time Configuration File>>) as its single argument. The variables in the section `[MAIN CONTROLLER]` of the configuration file determine important MC properties, for detailed information refer to the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor]. +The binary executable of Main Controller is `$TTCN3_DIR/bin/mctr_cli`. It takes the optional configuration file (<<The-Run-time-Configuration-File, The Run-time Configuration File>>) as its single argument. The variables in the section `[MAIN CONTROLLER]` of the configuration file determine important MC properties, for detailed information refer to the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor]. The Main Controller has two operation modes: interactive and batch mode. In interactive mode the user can control and monitor the test execution from a CLI. Batch mode is useful for automated and unattended execution of parallel and distributed tests. The actual operation mode depends on the configuration file and is determined at program startup. If the option `NumHCs` is set in the `[MAIN CONTROLLER]` section, the MC starts in batch mode, otherwise interactive mode is selected. @@ -261,7 +261,7 @@ From version 1.3.pl0 the MC checks the version of each connected HC automaticall During test execution all test components create separate log files. Each log file has the same format as presented in non-parallel mode. Logging into the same, NFS shared directory makes the log analysis easier. -The name of log files can be explicitly set in the configuration file using a metacharacter substitution mechanism. If the file names are not set, the backward compatible default naming convention is used. It is important to ensure that every component has its own unique log file name. Refer to the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor] for more details. +The name of log files can be explicitly set in the configuration file using a metacharacter substitution mechanism. If the file names are not set, the backward compatible default naming convention is used. It is important to ensure that every component has its own unique log file name. Refer to the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor] for more details. In parallel mode the log messages sent to the console are transmitted through the network and printed on the user interface of MC in normal cases. Thus it is an unwise thing to log all messages to the console without filtering when the test suite is used for load generation. If the control connection from a TC or HC to MC is broken due to any error, the console log messages are written to the standard error of the ETS locally. @@ -283,7 +283,7 @@ The messages coming from the standard output or standard error of MC, HC and the ==== This script does not support distributed test execution when more than one HC has to be started. -From TITAN version 7.2.1, `ttcn3_start` script also accepts executable JAR file type as the first input parameter. The JAR file shall contain a TITAN Java project, more specifically TTCN-3 codes are compiled by the TITAN Java compiler and packed into an executable JAR that starts in parallel mode. For more information please refer to https://github.com/eclipse/titan.EclipsePlug-ins/tree/master/org.eclipse.titan.executor/docs/Eclipse_Executor_userguide[User Guide of the TITAN Executor for the Eclipse IDE plug-in]. +From TITAN version 7.2.1, `ttcn3_start` script also accepts executable JAR file type as the first input parameter. The JAR file shall contain a TITAN Java project, more specifically TTCN-3 codes are compiled by the TITAN Java compiler and packed into an executable JAR that starts in parallel mode. For more information please refer to https://gitlab.eclipse.org/eclipse/titan/titan.EclipsePlug-ins/tree/master/org.eclipse.titan.executor/docs/Eclipse_Executor_userguide[User Guide of the TITAN Executor for the Eclipse IDE plug-in]. ==== Examples for the invocation of `ttcn3_start`: diff --git a/usrguide/userguide/5-log_processing.adoc b/usrguide/userguide/5-log_processing.adoc index 51c90e0c2e79bea2eaab55bbafcab922e8745a9b..ab4395937574237dd5ddb526e8b15a59538e5259 100644 --- a/usrguide/userguide/5-log_processing.adoc +++ b/usrguide/userguide/5-log_processing.adoc @@ -77,7 +77,7 @@ Prints `version` and license key information and exits. The utility can handle one file at a time, giving more input files results an error. If no input file is given, it reads the log from standard input. `Logfilter` can be efficiently used as the middle stage of a pipeline, combined with `logmerge` and `logformat`. -Event types to be included or excluded should be given without the `TTCN` prefix, that is, as they appear in the log file. Undefined event type(s), that are not listed in the link:https://github.com/eclipse/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor], specified as filter parameters will cause warning message(s), but will not cause the utility to quit. If there are parameters specified both to include and to exclude one or more event types, the program will quit with an error message, because in this case it is not well defined how to handle other event types. All possible error and warning messages will be printed to standard error. +Event types to be included or excluded should be given without the `TTCN` prefix, that is, as they appear in the log file. Undefined event type(s), that are not listed in the link:https://gitlab.eclipse.org/eclipse/titan/titan.core/tree/master/usrguide/referenceguide[TITAN Programmer's Technical Reference for TITAN TTCN-3 Test Executor], specified as filter parameters will cause warning message(s), but will not cause the utility to quit. If there are parameters specified both to include and to exclude one or more event types, the program will quit with an error message, because in this case it is not well defined how to handle other event types. All possible error and warning messages will be printed to standard error. == The `logformat` Utility diff --git a/usrguide/userguide/6-references.adoc b/usrguide/userguide/6-references.adoc index 19808014468019f06207836c3e221c705c35a370..651cf7d88d9a6c04f111a3004138d2c10471523c 100644 --- a/usrguide/userguide/6-references.adoc +++ b/usrguide/userguide/6-references.adoc @@ -1,13 +1,13 @@ = References [[_1]] -* [1] link:https://github.com/eclipse/titan.core/blob/master/usrguide/installationguide/[Installation guide for TITAN TTCN-3 Test Executor] +* [1] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/installationguide/[Installation guide for TITAN TTCN-3 Test Executor] [[_2]] -* [2] link:https://github.com/eclipse/titan.core/blob/master/usrguide/referenceguide/[Programmers Technical Reference for TITAN TTCN-3 Test Executor] +* [2] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/referenceguide/[Programmers Technical Reference for TITAN TTCN-3 Test Executor] [[_3]] -* [3] link:https://github.com/eclipse/titan.core/blob/master/usrguide/releasenotes/[Release Notes for TITAN TTCN-3 Test Executor] +* [3] link:https://gitlab.eclipse.org/eclipse/titan/titan.core/blob/master/usrguide/releasenotes/[Release Notes for TITAN TTCN-3 Test Executor] [[_4]] * [4] TTCN–3 Style Guide 1/0113-FCPCA 101 35