TeMIP Graphical ASCII Toolkit GAT V1.0.0-1 Release Notes Revision: V1.0.0-1 (level E) Date: 26-Mar-1997 Contents 1 Introduction 4 1.1 Installation prerequisites 4 1.2 Licenses 4 1.3 Mir file changes 5 1.4 How to use a customization developped with GAT T100-1.5 2 Release Notes 7 2.1 GUI 7 2.1.1 Fixed problems and improvements 7 2.1.1.1 Using "SET OF" type. 7 2.1.1.2 Generate kit option 7 1 2.1.2 Known problems and restrictions 7 2.1.2.1 Common Desktop Environment 7 2.1.2.2 Cannot quit GAT GUI 8 2.1.2.3 Test application failure 8 2.2 Kit procedures 8 2.2.1 Fixed Problems and improvements 8 2.2.1.1 Customized ASCII module generated kit 8 2.2.2 Known problems and restrictions 9 2.3 Compilation 9 2.3.1 Fixed Problems and improvements 9 2.3.1.1 Model library linking 9 2.3.1.2 Changing information in the main window 9 2.3.2 Known problems and restrictions 9 2.4 Communication Servers 9 2.4.1 Fixed Problems and improvements 9 2.4.1.1 Unsubscribe hangs when a message is being delivered 9 2.4.1.2 Maximum size attribute removed 10 2.4.2 Known problems and restrictions 10 2.4.2.1 Failure of the communication server on a 4-CPU system 10 2.4.2.2 Dialogue with a "Send/Redirect" command on top of RS232 communication server 10 2.5 ASCII Run Time module 10 2.5.1 Fixed Problems and improvements 10 2.5.1.1 Handling multiple responses 10 2.5.1.2 Associated CC list attribute removed 2 10 2.5.1.3 Ascii module on a multi CPU 11 2.5.1.4 Component version 11 2.5.2 Known problems and restrictions 11 2.5.2.1 Failure of the AM 11 2.6 Customization examples 11 2.6.1 Fixed Problems and improvements 11 2.6.2 Known problems and restrictions 11 1 Introduction This document provides the latest information about GAT software. It describes restrictions, known problems, suggestions and recommended procedures. Please read this document before installing or using this software. 1.1 Installation prerequisites GAT V1..0.0 requires: · TeMIP 3.1 (V310 SSB) installed with Visual TeMIP Developper toolkit. · Cxx 5.4 compiler · OSF 3.2 G 1.2 Licenses 3 The license mechanism has changed . GAT V1.0.0 toolkit needs the following licence: TEMIP-GAT-DK-USER The run time customized access module needs the following licence: TEMIP-GAT-RT-USER The run time communication servers need the following licence: TEMIP-GAT-RT-USER 1.3 Mir file changes The MIR file contents for both the communication server and the run time Ascii AM have changed. So before installing this new version of GAT you should de-install any subset produced with the gat AND remove the corresponding MIR files in /var/mcc (for example the tcp/ip communication server mir file names are "*tcp_cs*, the Ascii am mir file names were **). Note that the name of the MIR files for the Ascii AM has changed (it is now ** ). 1.4 How to use a customization developped with GAT T100-1. To be able to open an existing customization you should perform the following steps: · open a new customization after having installed the new version of GAT (V100-1) and save it. · In the location where you saved the new customization (for example /usr/users/My_cust), replace the source of the customization with yours: - master.gat (in /usr/users/My_cust), - AE.gat (in /usr/users/My_cust/src), - Dialog.gat (in /usr/users/My_cust/src), - Message.gat (in /usr/users/My_cust/src), - Types.gat (in /usr/users/My_cust/src), - AMHRule.gat (in /usr/users/My_cust/src), 4 - ICGRule.gat (in /usr/users/My_cust/src), - Model.gat (in /usr/users/My_cust/src). · The Model.gat file needs to be changed to have the correct spelling for the identifiers partition. Follow the procedure below to update this file. - $ cd /usr/users/My_cust/src - $ cp Model.gat Model.gat.old - $ sed "s/Identifier PRT_IDENT/Identifiers PRT_IDENT/" Model.gat > Model.gat.new - $ mv Model.gat.new Model.gat - $ cd .. · You can now edit your customization with the GAT GUI as usual. · To compile your new cutomization you should proceed to a change in the main window (for example change the version and put it back to the initial value), and invoke the "Make AM" from the AM menu. 2 Release Notes 2.1 GUI 2.1.1 Fixed problems and improvements 2.1.1.1 Using "SET OF" type. The files generated by the GUI for the "Set of" type are not correct. So the "Sequence of Record" type should be used instead. This has been fixed. Note that the "Set of" type can only be used for local attributes. 2.1.1.2 Generate kit option 5 The "Generate Kit" option can now be invoked even if the user is not root. Note that the user account used to generate the kit should be present on the system where the run time kit will be installed, otherwise warning messages wil be displayed during installation. There are still options that require root privilege (for example update dictionary). 2.1.2 Known problems and restrictions 2.1.2.1 Common Desktop Environment When the GUI provided with the toolkit is displayed on a system with CDE (Common Desktop Environment) installed, the default size of the window is not always the correct size. You may have to resize manually the window to see all the information displayed. 2.1.2.2 Cannot quit GAT GUI If you open a customization located in /usr/users/My_cust from a subdirectory of this customization, it is impossible to quit or exit the GAT GUI after a "Save". The following sequence results in this problem: $ cd /usr/users/My_cust/tmp $ temip_gat& open customization in /usr/users/My_cust Save customization ==> cannot quit or exit. To recover from this situation you must kill the GAT GUI process. 2.1.2.3 Test application failure In some circumstances the test application fails. 2.2 Kit procedures 6 2.2.1 Fixed Problems and improvements 2.2.1.1 Customized ASCII module generated kit An ASCII AM kit generated by GAT consists of seven subsets. In the example below, the kit name (specified in the GUI) is TAM and the version is 113: · GATBASE113 · GATTAMDIC113 · GATTCP113 · GATRS232113 · GATX25113 · GATTAMAM113 · GATTAMPM113 All those subsets can now be installed with a single setld command (you can now choose the "All the above" option). 2.2.2 Known problems and restrictions 2.3 Compilation 2.3.1 Fixed Problems and improvements 2.3.1.1 Model library linking The model library was always re-linked even if not needed. This has been fixed. 2.3.1.2 Changing information in the main window Changing information in the main window (for example the version) did not result in the necessary compilation. This has been fixed. 2.3.2 Known problems and restrictions 7 2.4 Communication Servers 2.4.1 Fixed Problems and improvements 2.4.1.1 Unsubscribe hangs when a message is being delivered When deleting an ASCII global entity referencing a CC as monitor CC (and there are no more entities referencing this CC) whereas some messages are being delivered to the target entity (AMH entity of the ASCII AM), then the directive never returned. This has been fixed. 2.4.1.2 Maximum size attribute removed New behaviour: as soon as the Raw Data Buffer Size will be reached (buffer full) and no message can be identified, the Raw Data Buffer will be emptied. 2.4.2 Known problems and restrictions 2.4.2.1 Failure of the communication server on a 4-CPU system We have encountered a failure of the communication server on a quadri-CPU system. This problem shows up under stressed conditions when the communication server receives a burst of alarms. This problem does not happen on a single or bi-CPU system. 2.4.2.2 Dialogue with a "Send/Redirect" command on top of RS232 communication server Using RS232 CS, no session can be made available for a directive after a redirect. The only way to send a new directive is to suspend/resume the CC. 2.5 ASCII Run Time module 2.5.1 Fixed Problems and improvements 8 2.5.1.1 Handling multiple responses In case a reponse argument if of type "Sequence of records", when one of the field being of type integer or enumeration cannot be mapped (because the corresponding value was not present in the message parsed), this field was assigned to "0" (zero). This has been fixed: this field does not appear anymore. 2.5.1.2 Associated CC list attribute removed The associated CC list attribute of the AMH entity has disappeared. This is because we had a limitation on the number of communication channels that could be subscribed for a given Ascii AM. The information is now handled by the communication server ("Number Of Subscription" attribute on the communication channel entity). 2.5.1.3 Ascii module on a multi CPU We have fixed a problem of failure of the run time Ascii AM on a multi CPU. The problem was encountered when receiving burst of alarms on a multi cpu system. 2.5.1.4 Component version The component version attribute of the self management contained the version of the customized AM which is already contained in Customization version. This has been fixed, The component version is now V1.0.0. 2.5.2 Known problems and restrictions 2.5.2.1 Failure of the AM We have encountered a failure of the ASCII AM under stressed conditions (burst of alarms or when issuing a register on an Ascii entity). 2.6 Customization examples 9 2.6.1 Fixed Problems and improvements In addition to the LAB_AM example customization, we have developped a TL1 customization example. This customization is located in /usr/kits/GAT100/toolkit/etc/examples/TL1 directory. A documentation associated with this customization is available in: /usr/kits/GAT100/toolkit/etc/examples/TL1/etc. 2.6.2 Known problems and restrictions 10 11