Dok. Nr. ASTRIUM - Airbuscs.astrium.eads.net/cgs/docs/manual/CGS631/CGS_Release...The purpose of...

Dok. Nr./No: CGS-RIBRE-TN-0001 Ausgabe/Issue: 13 Datum/Date: 13.10.2006 Überarbtg./rev: - Datum/Date: ASTRIUM

FORM 0019.1M.0 CGS_6.3.1_SW_Release_Notes.doc Copyright by Astrium - All Rights Reserved

Titel: Title: CGS 6.3.1 SW Release Notes

Dokumenten Typ: Document Type:

Technical Note

Dokumentenklasse: Document Class:

N/A Klassifikations-Nr.: Classification No.:

N/A

Dokumentenkategorie: Document Category:

N/A Konfigurations-Nr.: Configuration Item No.:

1130992

Produktklassifizierungs-Nr.:Classifying Product Code:

N/A

Freigabe Nr.: Release No.:

N/A

Bearbeitet: Prepared by:

S. Marz

Org. Einh.: Organ. Unit:

TE55 Unternehmen: Company:

EADS ST

Geprüft: Agreed by:

J. Bitomsky


TE5Q Unternehmen: Company:

EADS ST

Genehmigt: Approved by:

J. Frank Org. Einh.: Organ. Unit:

TE55 Unternehmen: Company:

EADS ST

Genehmigt: Approved by:


Unternehmen: Company: Agency:

Dok. Nr./No: CGS-RIBRE-TN-0001 Ausgabe/Issue: 13 Datum/Date: 13.10.2006 Überarbtg./rev: - Datum/Date: ASTRIUM


Attribut-Liste/List of Attributes

Vertrags Nr.: Contract No.:

Dokument Ref.Nr.: Document Ref.No.:

Lieferbedingungs Nr.: DRL/DRD No.:

Seitenzahl Dokument-Hauptteil: Pages of Document Body:

2

Schlagwörter: Headings:

Erstellungssystem: S/W Tool:

Word 97

CGS SW Release Notes

Kurzbeschreibung: Abstract:

This document issue provides the description of the CGS SW release 6.3.1 based on CGS 6.3.0release.

Dok. Nr./No: CGS-RIBRE-TN-0001 Ausgabe/Issue: 13 Datum/Date: 13.10.2006 Überarbtg./rev: - Datum/Date: ASTRIUM Seite/Page: i von/of: ii


DCR Daten/Dokument-Änderungsnachweis/Data/Document Change Record

Überarbeitung Revision

Datum Date

Betroffener Abschnitt/Paragraph/Seite Affected Section/Paragraph/Page

Änderungsgrund/Kurze Änderungsbeschreibung Reason for Change/Brief Description of Change

2/-

30.04.2004 All Initial release (6.2.0)

2/A

13.05.2004 All Bug Fixes (6.2.0.1)

2/B

07.07.2004 All Extended Functionality for Aeolus (6.2.1)

2/C

27.08.2004 All Extended UCL Debugger Functionality (6.2.2)

2/D

10.09.2004 All Bug Fixing for 6.2.2

2/E


2/F


2/G

22.10.2004 All Final version for 6.2.2 (B14)

2/H

17.12.2004 All version for 6.2.3 (B15)

2/I

28.01.2005 All version for 6.2.3 (B18)

3/-

11.02.2005 All version for 6.2.3 (B20)

4/-

18.02.2005 All Final version for 6.2.3

5/-

11.02.2005 All version for 6.2.4 (B21)

6/-

22.04.2005 All Final version for 6.2.4

7/-

03.06.2005 All version for 6.2.5 (B24)

8/-

03.06.2005 All Final version for 6.2.5 identical to 7/-

9/-

14.10.2005 All Final version for 6.3.0_LINUX_B27

10/-

14.10.2005 All Final version for 6.3.0 identical to 9/-

11/-

06.12.2005 All version for 6.3.0.1

12/-

03.04.2006 All version for 6.3.0

13/-

13.10.2006 All version for 6.3.1

Dok. Nr./No: CGS-RIBRE-TN-0001 Ausgabe/Issue: 13 Datum/Date: 13.10.2006 Überarbtg./rev: - Datum/Date: ASTRIUM Seite/Page: ii von/of: ii


Table of Contents 1 INTRODUCTION........................................................................................................................ 1 1.1 Identification and Scope............................................................................................................. 1 1.2 Purpose...................................................................................................................................... 2 1.3 Document Layout ....................................................................................................................... 2 2 APPLICABLE AND REFERENCE DOCUMENTS.................................................................... 3 3 RELEASE OVERVIEW.............................................................................................................. 5 3.1 CCU Version Identification ......................................................................................................... 5 3.2 Integrated Products.................................................................................................................... 5 3.3 Release Media & their Contents ................................................................................................ 6 3.4 Identification of the Generation and Test Environment .............................................................. 6 4 SW RELEASE STATUS............................................................................................................ 7 4.1 Release Status........................................................................................................................... 7 4.2 Test Status................................................................................................................................. 7 4.3 Commercial Baseline ................................................................................................................. 7 4.4 Compatibility Statement ............................................................................................................. 7 4.5 New or Updated Components.................................................................................................... 7 4.6 New features in CGS_6.3.1 ....................................................................................................... 8 4.6.1 CGS START CENTER............................................................................................................... 8 4.6.2 CGS CONFIGURATION .......................................................................................................... 11 4.6.3 CGS I_MDB ON KDE............................................................................................................... 13 4.6.4 CGS SYSTEM LIBRARY CHANGES ...................................................................................... 14 4.6.5 CGS TOOLS ............................................................................................................................ 16 4.6.6 CGS WINDOW TITEL AND NAMING...................................................................................... 16 4.6.7 CIS SOCKET INTERFACE...................................................................................................... 16 4.6.8 DYNAMIC STRING PARAMETER IN TELEMETRY PACKETS.............................................. 17 4.6.9 TELEMETRY PACKET TYPE SWARM................................................................................... 19 4.6.10 ORACLE RAC CAPABILITY.................................................................................................... 19 4.6.11 USS DISPLAYS ....................................................................................................................... 19 4.6.12 mdb Tool: new placeholder {name}......................................................................................... 21 4.7 SW PROBLEM STATUS.......................................................................................................... 22 4.7.1 SPR Status and Impact Analysis ............................................................................................. 22 4.7.2 Temporary fixed Problems....................................................................................................... 27 4.7.3 Further Open Problems............................................................................................................ 27 4.7.4 Known Restrictions .................................................................................................................. 27 5 INSTALLATION PROCEDURES ............................................................................................ 28

Dok. Nr./No: CGS-RIBRE-TN-0001 Ausgabe/Issue: 13 Datum/Date: 13.10.2006 Überarbtg./rev: - Datum/Date: ASTRIUM Seite/Page: iii von/of: ii


5.1 Complete Installation................................................................................................................ 28 5.2 Patch Installation (based on CGS 6.3.0).................................................................................. 28 5.2.1 Needed passwords .................................................................................................................. 28 5.2.2 Installation steps ...................................................................................................................... 28 5.3 Oracle RAC installation for CGS.............................................................................................. 30 5.3.1 Prerequisites ............................................................................................................................ 30 5.3.2 Oracle RAC installation............................................................................................................ 30 5.3.3 Oracle Database Instance Creation ......................................................................................... 30 5.3.4 CGS Tablespace creation ........................................................................................................ 30 5.3.5 Installation CGS application databases ................................................................................... 31 6. ACRONYMS ............................................................................................................................ 32

Dok. Nr./No: CGS-RIBRE-TN-0001 Ausgabe/Issue: 13 Datum/Date: 13.10.2006 Überarbtg./rev: - Datum/Date: ASTRIUM Seite/Page: 1 von/of: 30


1 Introduction

1.1 Identification and Scope This document is the CGS 6.3.1 SW Release Notes. The release is identified by document CGS SRO [AD 2.1.1].

CI Name : CGS SW

CI Number : 1130992

CI Variant : 6.3.1



1.2 Purpose The purpose of this software release is a delivery to CGS AIV to qualify it.

1.3 Document Layout This document has the following layout:

Chapter 1 provides the document identification and identifies under which CI this document is prepared. It also identifies the next higher level component CI. Chapter 1 also provides an overview of the purpose of the document and the overall document structure.

Chapter 2 provides the list of documents which are applicable or are referenced.

Chapter 3 provides an overall description of the release. Thus in this chapter all SW products being integrated are listed including the temporary fixes necessary to run the SW. This chapter also provides the identification of CCU versions being used for the SW product integration (if any).

Chapter 4 provides an overview of the release status. This includes a statement on the current test status and the identification of SPRs being fixed with this release.

Chapter 5 provides the installation instruction for the CGS SW.

Appendix A provides a list of abbreviations being used

Appendix B provides a list of terms being used in a certain sense.

Appendix C provides the file listing of the delivery.



2 Applicable and Reference Documents

CGS Documents: name issue date Technical Note CGS-RIBRE-TN-0001 CGS SW Release Notes (Linux) 13 13.10.2006 CGS-RIBRE-TN-0002 The CGS Authorization Concept 2/B 04.09.2006 SW Release Order CGS-RIBRE-SRO-0006 CGS Software Release Order (Linux) 13 13.10.2006 User Manuals CGS-RIBRE-SUM-0001 CGS User Manual 4/- 30.08.2006 CGS-RIBRE-SUM-0002 CGS Installation Manual (Linux) 2/B 26.07.2004 CGS-RIBRE-SUM-0003 MDA Reference Manual 1/C 27.03.2006 CGS-RIBRE-SUM-0004 MDA Administration Manual - see COL 1/- CGS-RIBRE-SUM-0005 DADIMA Reference Manual 1 09.11.2001 CGS-RIBRE-SUM-0006 DADIMA Administration Manual 1 09.11.2001 CGS-RIBRE-SUM-0007 GWDU User's and Operations Manual 2 28.08.2006 CGS-RIBRE-MA-0001 UCL Debugger User Manual 1 01.09.2004

CGS-RIBRE-MA-0003

call - A tool to add a graphical user interface to command line based programs 1/- 01.03.2006

CGS-RIBRE-MA-0004 "mdb - MDB Access Tool" 1/- 01.03.2006 CGS-RIBRE-MA-0005 "generate - Text Generation Tool" 1/- 01.03.2006 CGS-RIBRE-MA-0006 CDU Merge Users Manual 1 14.03.2006

CGS-RIBRE-MA-0007 Start Center - A generic user interface for multi-process systems 1/- 01.08.2006

COL-RIBRE-MA-0018-00 MDA Administration Manual 4/B 31.03.2000 COL-RIBRE-MA-0030-00 MDA Introduction Manual 3/B 04.04.1997 COL-RIBRE-MA-0037-00 DADIMA Introduction Manual 3 04.04.1997

COL-RIBRE-MA-0046 SID Range Tool Users and Operations Manual 1 15.09.1997

Reference Manuals

CGS-RIBRE-STD-0001 User Control Language (UCL) Reference Manual 3/- 01.12.2005

CGS-RIBRE-STD-0002 High Level Command Language (HLCL) Reference Manual 3/A 04.05.2006

CGS-RIBRE-STD-0003 Virtual Stack Machine and I-Code Reference Manual 3/- 01.12.2005

COL-RIBRE-STD-0008 Reference Manual for Crew Procedure Language and Software, Commanding 1/F 31.10.2001

Requirements Specifications

CGS-RIBRE-SPE-0001 Columbus Ground System (CGS) Requirement Specification 2/D 23.03.2004

CGS-RIBRE-SPE-0002 CGS Test Case Specification and Test Procedure 4/- 30.08.2006



Design Documentation

COL-RIBRE-ADD-0006 Columbus Ground System (CGS) Software Architectural Design Document 4/B 30.10.1998

Interface Definitions CGS-RIBRE-ICD-0001 System to CGS ICD 1/- 31.01.2002

CGS-RIBRE-ICD-0002 MDB Standard Entities and Application Program Interface 1/-



3 Release Overview

3.1 CCU Version Identification This CGS SW Release provides no mission database content.

3.2 Integrated Products In following table all SW components are identified necessary to build this release of the CGS SW.

• CGSI • CLS • DBS / Command History • GWDU • HCI • MDA / CGS_MDB_V6_3_1 • TES • TEV • TSCV • TSS • CGS_API



3.3 Release Media & their Contents The VTC SW System is delivered on a as being identified in Table 1.

Data Carrier ID Title / Contents Receiver CGS-RIBRE-DC-0175 CGS_6.3.1_B6_LINUX (Master) Dcc CGS-RIBRE-DC-0176 CGS_6.3.1_B6_LINUX (Backup) CGS CM CGS-RIBRE-DC-0177 CGS_6.3.1_B6_LINUX optional (Master) Dcc CGS-RIBRE-DC-0178 CGS_6.3.1_B6_LINUX optional (Backup) CGS CM CGS-RIBRE-DC-0179 CGS_6.3.1_B6_LINUX Test SW (Master) Dcc CGS-RIBRE-DC-0180 CGS_6.3.1_B6_LINUX Test SW (Backup) CGS CM CGS-RIBRE-DC-0181 CGS_6.3.1_B6_LINUX Debug Executable (Master) Dcc CGS-RIBRE-DC-0182 CGS_6.3.1_B6_LINUX Debug Executable (Backup) CGS CM

Table 1 : Identification of Data Carriers

This delivery contains online documentation only.

3.4 Identification of the Generation and Test Environment The CGS SW Generation environment is described in chapter 5 of the release notes of ref. [AD 2.1].

This version is internal identified by PDB checkpoint CGS_6.3.1_B6_LINUX.



4 SW Release Status

4.1 Release Status The release status is: FORMAL RELEASE

The SPRs fixed in this release have been regression tested as documented in the CGS SPRdb.

It has been assessed that the code changes have no impact to the qualification status of other SW modules of CGS as released in former versions.

4.2 Test Status This CGS SW was tested on commercial baseline. The test status is delta qualified by CGS - AIV.

4.3 Commercial Baseline Suse Linux Enterprise Server 8 / ServicePack3

Oracle 9.2.0.5

Gipsy 4.2.2 based on glibc 2.2

with patch for call pr-3437

with libdvt11.0.so for Gipsy 4.2.2 / Linux of 14.06.2005

Dataviews 9.9

CGS API with gnat 5.0.4a

CIS CORBA Server built with Top Graph'X OrbAda 2.6.2 (CORBA 2.5, GIOP 1.2)

This CGS SW release shall be executed on Intel PC with SUSE Linux Enterprise Server 8 (SLES8) based environments.

For using Oracle RAC installation only (see 5.3):

Suse Linux Enterprise Server 9 / ServicePack 2

Oracle RAC 10gR2 (Version 10.2.0.2)

4.4 Compatibility Statement The software is based on CGS 6.3.0.

The SAS build with the CGS API (CGS version 6.3.0) are not compatible to CGS version 6.3.1, due to some changes inside general packages you need to recompile the SAS sources with the new CGS API.

The Corba clients build with the CGS IDL (CGS version 6.3.0) are compatible to CGS version 6.3.1.

4.5 New or Updated Components All software components are updated.



4.6 New features in CGS_6.3.1 What's new in CGS_6.3.1 (in difference to CGS 6.3.0)?

4.6.1 CGS START CENTER

The new Start Center can be used as an alternative to the CGS Task Selector. It can be started with the command

cgs

The following pages give a short overview. A detailed description can be found in the Start Center User Manual:

CGS-RIBRE-MA-0007 Start Center - A generic user interface for multi-process software systems

The Start Center presents the different processes in a tree structure, hierarchically grouped in subsystems (process groups):

The processes (the leaves of the tree) are shown with different symbols indicating the current status of the process, whether it is currently running, has been started before, has terminated with success or failure etc.

Both subsystems and processes may be assigned preconditions that must be fulfilled, before a process can be started. As long as there are unfulfilled preconditions, the process is blocked (shown with the red blocked symbol). A blocked subsystem (process group) blocks all processes and sub-subsystems within that subsystem.

The left picture shows the tree view containing just the process tree. This is the standard view. Clicking on the vertical yellow arrow switches between the tree view and the minimized view:

Clicking on the horizontal orange-colored arrow opens or closes, resp., the detail view with different information about the selected process or subsystem. In the picture, the Preconditions subpage is opened, it lists all preconditions assigned to the selected item together with an indication whether a precondition is fulfilled or not.



Each subsystem and process have a descriptive text, it is shown in the Info subpage (opened by clicking on the Info tab):

A process may be started in either of two ways:

•

•

by double-clicking a process symbol in the process tree,

by selecting a process symbol and clicking on the Start button in the tool bar of the tree subwindow.

If the detail view is open, it now switches to the Output subpage that shows all output of the process. Text written to its standard output channel is shown in black, and text written to its standard error channel is shown in red:



It depends on the configuration, whether a running process may be stopped by clicking the Stop button in the tool bar of the tree subwindow. For processes that cannot be stopped this way the Stop button is disabled.

Configuration of the Start Center The Start Center is configured with XML files following the same concept as the general CGS configuration. These XML files can, therefore, be created and maintained with the Configuration Editor.

Both administrators and users may extend the process tree with their own processes and even modify certain properties of the process tree. The Start Center allows several configurations on several levels, where each additional configuration is merged to the previous configurations in a way that new configuration elements are added to the existing configurations, and new attributes overlay and hide existing attributes.

The cgs command exploits this capability and evaluates configuration files on four levels, if these files exist:

System level: $CGS_HOME/etc/start_center/start_center.xml

Project level: $CGS_HOME/etc/project/start_center.xml

Local computer: $CGS_HOME/local/config/start_center.xml

User level: $HOME/.cgs/config/start_center.xml

A basic CGS installation provides only the system level configuration. Project administrators and users may extend and modify the basic configuration by just placing additional start_center.xml configuration files in the appropriate directories. They will be automatically evaluated by the cgs command.

For configuration details see the Start Center User Manual (see above).



Remark: For processes, which are started via shell script in background, the status of start script is displayed, not the status of the process itself. This may be useful for multiple start of the same process. Do not start in this case the process directly, use an start script instead, which start the process in background and finished then.

4.6.2 CGS CONFIGURATION • New configuration parameters are:

NWSW.Alv_Msg_Poll_Interval NWSW ALIVE-MSG-CHECK SERVICES

Defines the interval between two checks for Alive-Msg-Timeouts in [ms] Lower limit: 100

NWSW.Proc_Alv_Msg_To_Task_Stack_Size NWSW ALIVE-MSG-CHECK SERVICES

Stack size in bytes of that NWSW task, that executes the Alive-Msg-Notification callbacks. Lower limit: 100000

NWSW.Ignore_Alive_Message_Check NWSW IGNORE-ALIVE-MSG-CHECK

This switch is for debugging purposes. If it is true, the Cb_Alive_Msg_To_Occ will not be called. A message will be written to stdout instead. Range: true/false Recommended value: false

CLS.DEPENDENCIES

This group contains options related to CLS dependency handling.

CLS.DEBUG

This group contains logging options for debugging purposes.

OTC_KERNEL.COMMUNICATION.RemoveSynopticTimeOut

Defines the time in milliseconds TES will wait until the remove_picture library call is timed out.

OTC_KERNEL.COMMUNICATION.USSResponseTimeOut

Defines the time in milliseconds Online Control will wait for USS responses.

ONLINE_TEST_CONTROL.SYNOPTIC_DISPLAYS.EnableMonitoringFlag

Enable monitoring flags for standard elements. If a user defined monitoring flags for usage with compound/composite display elements, the flags were used on standard elements, too. For that reason, the measurement value was hidden by monitoring status flag on small-sized elements. Monitoring flags are now used for compound/composite elements, only (the default). Acquisition and processing status flags are still displayed on standard elements.



CIS.DEBUG.EnableCORBAControl (default : FALSE)

Setting to TRUE enables external control of debug output for a running CIS process by a client for the 'Internal' CORBA interface. Since there is no access control for this interface, and debug output has impact on CIS performance and disk space consumption, this is a potential security risk and therefore disabled as default.

CIS.corbaInterface.Enabled (default : TRUE)

Determines whether CIS Corba Interface shall be activated. When False, CIS will not provide the Corba Interface.

CIS.SocketInterface.Enabled (default : FALSE)

Determines whether CIS Socket Interface shall be activated. When False, CIS will not provide the Socket Interface. For information about the socket interface see section CIS Socket Interface.

TES.KERNEL.DATA_PROCESSOR.ADU.USE_LIMIT_SET_NUMBER_AS_CONDITION (A) Allow or inhibit the usage of the MDB - defined Limit Set Number in enditem condition

description as additional condition for the Action Type DISABLE_MONITORING only. For all other conditon actions this parameter has no effect!

If this value is set to true, the condition is evaluated as follow:

condition false => do nothing

condition true => condition Action Type = DISABLE_MONITORING =>

ACTION ITEM REFERENCE = measurement, variable, derived: if condition Limit Set Number = current limit set OR condition Limit Set Number = 0 => disable_monitoring

ACTION ITEM REFERENCE = monitoring list, virtual pathname:

if condition Limit Set Number = current limit set (for at least one single enditem)

OR condition Limit Set Number = 0 => disable_monitoring

else => do nothing (*)

condition Action Type <> DISABLE_MONITORING => perform action

(*) In this case, the condition is not marked as triggered, because the limit set check is

part of the condition. Remember: The condition action is performed once only as long as the condition result is unchanged! Range: true/false Recommended value: false

TSCV.Internal.Pcs_Timeout

(E) Timeout for process creation server to start an application from TSCV.



TSCV.User.Batch_Session_Extension (default : FALSE)

(U) Extends session name (User, Time) also for batch mode.

• Changed configuration parameters:

The following parameters have been moved:

TES.KERNEL.GDU.TABLE.TAI_EPOCH_START_DAY -> SYSTEM.TIME.TAI_EPOCH.START_DAY

TES.KERNEL.GDU.TABLE.TAI_EPOCH_START_MONTH -> SYSTEM.TIME.TAI_EPOCH.START_MONTH

TES.KERNEL.GDU.TABLE.TAI_EPOCH_START_YEAR -> SYSTEM.TIME.TAI_EPOCH.START_YEAR

TES.KERNEL.CCSDS.USE_PACKET_TYPE_TO_EXTEND_APID -> DATA_SYSTEM.CCSDS.EXTENDED_APID

ONLINE_TEST_CONTROL.TEST_NODE_STATUS -> ONLINE_TEST_CONTROL.EXECUTION_NODE_STATUS

System.Time.TAI_Epoch.Start_Year

(U) The CCSDS-Recommended epoch start time (TAI) Range: integer'range Recommended value: 1_980

System.Time.TAI_Epoch.Start_Month

(U) The CCSDS-Recommended epoch start time (TAI) Range: integer'range Recommended value: 1

System.Time.TAI_Epoch.Start_Day

(U) The CCSDS-Recommended epoch start time (TAI) Range: integer'range Recommended value: 6

Data_System.CCSDS.Extended_ApId

(U) indicates if the packet type field in COF specific CCSDS primary header a) should be considered for calculating of sequence count (internal operation) b) should be set during setting APID (via system library command SET_CCSDS_APID)

This enlarges the APID range from 0 .. 2^11 - 1 to 0 .. 2^12 - 1. or not Range: true/false Recommended value: true

ONLINE_TEST_CONTROL.GRAPH_FACILITY.TEMPLATES.NAMES

Defines a new element LineValueGraph and its connected attributes.

ONLINE_TEST_CONTROL.SYNOPTIC_DISPLAYS.Status_Display.Synoptic_Icons

Move all defaults for icons from $CGS_HOME/etc to $CGS_HOME/etc/icons.

4.6.3 CGS I_MDB ON KDE • The I_MDB tool is now able to run on KDE window manager without major problems (SPR-

100281).



4.6.4 CGS SYSTEM LIBRARY CHANGES • ground_library

New options for display_picture: -docked | -undocked procedure DISPLAY_PICTURE (in PICTURE: PICTURE_NAME; in WORKSTATION: NODE_NAME := \\; in OPTIONS: VALUE_STRING := ""; out ID: PICTURE_ID; out STATUS: UCL_RETURN); -- #61 -- Description: -- Displays a synoptic display on a specific workstation. -- Parameters: -- IN: -- PICTURE : name of synoptic display (pathname) -- WORKSTATION : the work station (pathname) to show the synoptic display: -- by default the work station from which the command -- originates, directly or via a AP. -- OPTIONS : options specifying attributes for window where picture -- is displayed -- -- Syntax: -position X Y -- -size W H -- -docked | -undocked (only applicable for USS displays) -- -- X,Y: coordinates; W: Width, H: Height -- -- Example: "-position 100 200 -size 600 150 -undocked" -- -- OUT: -- ID : returns identifier to be used by REMOVE_PICTURE when removing -- this synoptic display. -- STATUS : UCL return status -- OK -- WORKSTATION_NOT_CONNECTED -- WORKSTATION_NOT_READY -- SYNOPTIC_RESOURCES_EXCEEDED -- TIMEOUT

• ground_values New features for SET_LIMIT procedures (SPR-100175). The SET_LIMIT procedures

SET_HIGH_LIMIT SET_INTEGER_HIGH_LIMIT SET_UNSIGNED_HIGH_LIMIT SET_DOUBLE_FLOAT_HIGH_LIMIT SET_LOW_LIMIT SET_INTEGER_LOW_LIMIT SET_UNSIGNED_LOW_LIMIT SET_DOUBLE_FLOAT_LOW_LIMIT SET_DELTA_LIMIT SET_INTEGER_DELTA_LIMIT SET_UNSIGNED_DELTA_LIMIT SET_DOUBLE_FLOAT_DELTA_LIMIT SET_EXCEPTION_COUNT SET_EXPECTED_STATE SET_EXPECTED_VALUE SET_DANGER_HIGH_LIMIT SET_INTEGER_DANGER_HIGH_LIMIT SET_UNSIGNED_DANGER_HIGH_LIMIT SET_FLOAT_DANGER_HIGH_LIMIT SET_DANGER_LOW_LIMIT SET_INTEGER_DANGER_LOW_LIMIT SET_UNSIGNED_DANGER_LOW_LIMIT SET_FLOAT_DANGER_LOW_LIMIT SET_DANGER_DELTA_LIMIT



SET_INTEGER_DANGER_DELTA_LIMIT SET_UNSIGNED_DANGER_DELTA_LIMIT SET_FLOAT_DANGER_DELTA_LIMIT

are now able to create limit definition during execution session, independ on the MDB settings. These settings can be reused with the TSCV warm start function.

Example: guarded procedure SET_DANGER_HIGH_LIMIT (in ITEM: ANALOG_MONITOR_ITEM_NAME; in LIMIT: LONG_REAL; out STATUS: UCL_RETURN); -- #100 -- Description: -- Changes the danger high limit of an enditem. -- If the item is an -- integer LIMIT is rounded to the nearest integer. -- unsigned integer LIMIT is rounded to the nearest unsigned integer. -- real LIMIT is rounded to the nearest real. -- -- Note: If no danger limits defined in the MDB, this routine sets the danger -- limits initial. Without nominal limits, this routine fails. Define -- nominal limits before. The limits can be reused by the TSCV warm -- start function. -- -- Parameters: -- IN: -- ITEM : name of item to change the limit -- LIMIT : value to set danger high limit to -- OUT: -- STATUS returns the UCL Return Code values : -- OK -- INVALID_TESTNODE_MODE -- INVALID_ITEM_NAME -- INVALID_LIMIT

• start_program / start_hci_application changed keywords for starting Online Control applications

Starting Online Control applications via HLCL/UCL using HCI.TEST_NODE_STATUS and HCI.GONOGO_WINDOW is still supported for backward compatibility, but will be removed with one of the next releases. Replace TEST_NODE_STATUS by EXECUTION_NODE_STATUS and GONOGO_WINDOW by OUT_OF_LIMIT_DISPLAY.



4.6.5 CGS TOOLS • CGS Tools does now provide all HK variables of the MTP and CIS via System Interface

Browser.

4.6.6 CGS WINDOW TITEL AND NAMING • Due to the usage of CGS for mission purposes, the term "TEST" has been removed from many

CGS windows (SPR-14924).

4.6.7 CIS SOCKET INTERFACE

With this release of CGS, the original MOIS socket interface of CIS from CGS 5, implementing the interface specified in CS-RIBRE-ICD-0001 Rev. 1/A, has eventually been re-activated.

Some basic tests to verify the functions of the socket interface have been performed with a simple test client (cf. SPR-100795 retest); for full verification, a test with a real MOIS client will have to be performed.

CIS may serve the MCS Corba interface and the MOIS socket interface in parallel. To select the desired interface, two configuration parameters have been added: CIS.corbaInterface.Enabled (default : TRUE) CIS.socketInterface.Enabled (default : FALSE) i.e. with the default settings, the Corba interface is enabled and the socket interface is disabled (MCS configuration).

For complete operation, i.e. to provide the functions 'send_TC' and 'wait_for_ADU', CIS needs a UCL user library providing corresponding functions for its HLCL executor. The sources for specification and body of this library can be found at: $CGS_HOME/gsaf/cgsi/lib/ucl/mois_cis_lib_.ucl resp. $CGS_HOME/gsaf/cgsi/lib/ucl/mois_cis_lib.ucl

The MDB path resp. nickname for this library is configurable via the configuration parameter:



•

CIS.socketInterface.CisUclLibrary (default: nickname MOIS_CIS_LIB)

For databases upgraded from CGS 5 to 6, note that the sources of MOIS_CIS_LIB had to be adapted for CGS 6 and must be re-compiled.

With ICD CS-RIBRE-ICD-0001 Rev. 1/A, the socket protocol had been extended to transmit timetags also with date (initial version only provide time of day). Therefore, the format of the acquisition_time of TM parameters (only use of timetags so far) can now be controlled by setting the configuration parameter: CIS.socketInterface.AcquisitionTimeWithDate

to TRUE (with date) resp. FALSE (without date, default) using the CGS configuration_editor.

Further configuration parameters for the socket interface: CIS.socketInterface.ServerPort (default : 7008) CIS.socketInterface.MaxNumberOfConnections (default : 20) CIS.socketInterface.MaxNumberOfTMParameters (default : 100)

4.6.8 DYNAMIC STRING PARAMETER IN TELEMETRY PACKETS • CGS is now able to handle dynamic string parameter in telemetry packets. For that reason

different MDB data structures has been updated. The defaults are chosen, that the old behaviour is guaranteed.

All old and new created EGSE_BYTESTREAM_MEASUREMENT's are of type static by default.

All old and new created telemetry packet descriptions are with absolute position of measurements by default.

MDB changes

o EGSE_BYTESTREAM_MEASUREMENT

For the EGSE_BYTESTREAM_MEASUREMENT an additional flag shall used to identify whether this measurement is of kind dynamic or static. The default is static, the default is valid for missing flag attribute too. This flag is called later on dynamic flag; the measurement marked with this flag is called Dynamic String Parameter.

Depend on the settings of dynamic flag, the user need to specify an additional size in Bits for the length field of the string (called length size in Bits). The length may be zero. In this case an end sign has to specify as an 8 bit integer. In case of definition of length size > 0 the end sign is obsolete. Alternative A (string with previous length field): The string is split into two parts:

---------------------------------------------------------------- | L (ength in Bytes) | L character, for each character one Byte | ---------------------------------------------------------------- ^ ^ ^ |----- n Bits ------| ----- L Bytes ----------------------------| with the string characters following the length definition immediately.



•

Alternative B (end sign terminated string): The string is split into two parts: ---------------------------------------------- | L character, for each character one Byte |E| ---------------------------------------------- ^ ^ ^ |----- L Bytes ----------------------------|-| | one byte end sign with the string characters terminated by end sign.

In case of Dynamic String the 'Raw Value Size in Bytes' is obsolete.

o ADU_DESCRIPTION (CCSDS, PUS, UNSTRUCTURED)

For ADU description an additional flag shall used to identify whether the parameter position is absolute or relative to the previous parameter. The default is absolute, the default is valid for missing flag attribute too. This flag is called later on position flag; the ADUs marked with this flag is called Dynamic ADUs. The location in the parameter description of an ADU denotes either

static ADUs: the absolute position in the packet part or

dynamic ADUs: the offset to the previous parameter (or start of packet part).

USAGE in Packets

o Usage in ADUs with fixed position parameters (CCSDS, PUS, UNSTRUCTURED)

The start point of the first parameter is defined by Source and Offset/Location information within the measurement enditems description of this ADU for this parameter.

static ADUs : The next parameter is read depend on the Source and Location information within the measurement enditems description of this ADU.

dynamic ADUs:The next parameter is read depend on the Source and Offset (Location)

information within the measurement enditems description of this ADU and is relative to the previous measurement.

For the dynamic string parameter with defined length size (see alternative A) first the length L is evaluated, and then L characters read after length field. The calibration rules (use slice of string as engineering value) are unchanged. For the dynamic string parameter with defined end sign (see alternative B) character by character will read up to end sign. The end sign itself is not part of the raw value. The calibration rules (use slice of string as engineering value) are unchanged. The parameter length definitions in the ADU parameter description are valid for all parameter, except dynamic string parameter.

o Usage in STRUCTURED_ADU

The start point of the parameter is defined by: - the end of the previous parameter or - packet start position (STRUCTURED_ADU)

The end of a dynamic string parameter is defined by:



•

•

- n Bits of Length definition + L Bytes (alternative A) or - after end sign (alternative B)

This is usable for dynamic string parameter in structured ADUs. o Usage in PUS_STRUCTURE_ID

The start point of the parameter is defined by: - the end of the previous parameter or - 'Reference to Structure ID or Table' definitions 'Offset of Measurements to Header in

Bits' in ADU description The end of a dynamic string parameter is defined by:

- n Bits of Length definition + L Bytes (alternative A, depend on alignment definitions) or - after end sign (alternative B)

This is usable for arbitrary dynamic string parameter at any position in data part of packet in any CCSDS packet.

Restrictions

In this version it is not allowed to use dynamic string parameter in PUS_SUBSTRUCTURE_ID, which are referenced directly by ADU (not over a measurement list table).

4.6.9 TELEMETRY PACKET TYPE SWARM • CGS is now able to handle TM packets of type SWARM (Swarm Packet Utilisation Standard

(S-PUS) (SW-IF-EAD-SY-0004 / 1.0 / 06.04.2006)) .

4.6.10 ORACLE RAC CAPABILITY • CGS is now able to deal with an ORACLE RAC installation for ORACLE 10g. For detailed

installation instruction see chapter 5.3.

4.6.11 USS DISPLAYS

For detailed information see: CGS User Manual section 7.3.2.4.13 : USS Displays.

Unified Synoptic System (USS) Displays are the next generation of synoptic displays integrated with CGS. This section will provide a description how USS is integrated with CGS. For a detailed description of USS itself, see USS User Manual.

GWDU to USS Display Conversion

CGS provides conversion of a single GWDU Display as well as a complete CCU to USS display format, but the conversion is restricted to frequently used GWDU display objects and attributes. For a complete list of supported display elements, see USS User Manual, section 5.4.5 Conversion of GWDU Display Objects. Before migrating to USS Displays it is recommended to make a backup of the mission data base and to create a deep copy of the CCU that can be used to run the conversion process. A copy of the CCU can be created with the CU Version Manager. Remark: quit CU Version Manager before starting the conversion



•

•

process since it locks the new CCU. To convert all GWDU displays of a CCU, start I_MDB and open the CCU Versions dialog. Select the CCU and execute

Command > Tools > Convert to USS

After confirmation, the conversion process is performed in four steps. The first one is the generation of the so called XML SCOE files. The XML SCOE files provide an offline view of the selected CCU used by USS. They are stored at location $HOME/uss-project/scoe and can be used when the converted displays shall be modified by hand afterwards. If the XML SCOE files are up to date, this step is omitted. The next step is the generation of specific GWDU XML files for each GWDU displays in the CCU scope. These XML files are stored in a temporary directory for the final conversion step. During GWDU XML generation, the GWDU editor pops up for each GWDU display. When finished, it displays a report about generated files. The third step modifies the CCU. It moves all GWDU displays to a virtual node called GWDU_COPIES and removes the alias name. In the fourth step the GWDU displays are converted to USS displays and stored in the CCU under the same path where the old GWDU display was located with the same alias name. Using the path and alias name of the GWDU displays ensures navigation between the new USS displays. When the conversion process has been finished, a dialog pops up asking whether to remove the directory containing the temporary files. In general, this can be confirmed. Sophisticated user may use the temporary display files and snapshots for further processing (e.g. to define a new hierarchy for the displays). Conversion of a single GWDU display can be invoked directly on the end item using the context menu

Tools > Convert to USS The conversion steps are the same as already described above.

Starting USS Editor The USS Editor can be started via either via top level user interface (Task Selector, CGS Start Center) or via I_MDB. When starting the USS Editor via top level user interface, it might come up with an <Error loading property file>. In this case, press Ok and specify a SCOE path on the Preferences/MDB-SCOE dialog. If a GWDU to USS display conversion has been performed, a valid SCOE file is already present at default location.

When starting via context menu of a USS display end item in I_MDB, SCOE files are automatically generated and selected.

Starting USS Executor



The USS Executor can be started via top level user interface like the editor. It is recommended to define an active HCI instance for each workstation node where to run an USS Executor. If the workstation node (HCI instance) is participating in an active test configuration, the USS Executor will automatically connect to CIS. When running together with Online Control, USS displays can be displayed/removed via HLCL and UCL commanding using the same commands as for GWDU synoptics. USS displays started through Online Control are included in screen setups, too.

4.6.12 mdb Tool: new placeholder {name}

The mdb tool has a new format placeholder {name} for its subcommands list and iterate. The placeholder is replaced with the nickname (alias), if it exists, else with the pathname of the items. See the manual CGS-RIBRE-MA-0004.



4.7 SW PROBLEM STATUS

4.7.1 SPR Status and Impact Analysis For this release 178 SPR’s are solved.

ID TITLE SPR-10241 TES needs to be stopped if connection to TSS lost SPR-10568 Filter of CGS message not working correctly SPR-10773 ExcelMDB: update of not changed data in MDB SPR-11633 HCI crash SPR-12308 Missleading parameter name in TES configuration file SPR-13628 ExcelMDB: linux verion has problems with non-existing files SPR-13981 FILE_IO_LIB: Problem with ADD_FILE_TO_TEST_SESSION SPR-14013 Data sets and event lists cannot be merged SPR-14518 TEV: Excel file names limited to 8 characters SPR-14690 CGS Logfiles / Cleanup script SPR-14740 Erroneously placed parameter for primary header not rejected SPR-14741 Internal: GDU parameters to be aligned cause Constraint_Error SPR-14867 Bytestream measurements in PUS packets SPR-14872 Wrong error category for consistency check re. overlapping data in ADUs SPR-14924 CGS Nomenclature for Mission Operations SPR-15186 CIS / Command History errors SPR-15495 Use "Initial Time Frame" shall means select all data SPR-15686 CIS uses all CPU time SPR-15729 TEV: Pathname error during "Build Listing..." SPR-15738 RUNTIME_ERROR when calling SET_BYTE procedure SPR-15745 TEV: Measurement not found in any ADU? SPR-15757 Generation of CU Difference Report fails SPR-15800 HLCL misleading error message SPR-15810 HLCL undefined procedure names SPR-15812 string operation not implemented for bitset SPR-15836 Exception raised in ADT_CCSDS_PACKET.COF_SPECIFIC.SET_TIME SPR-15844 Pathname Support responds with Error SPR-15845 Title Editor Dialog did not disable Graph Editor Widgets SPR-15864 Script saveCGSconf contains wrong pathnames SPR-15871 Undelete Text Graph leads to GWDU Crash SPR-15879 TES dont save changed limit set, when enable_monitoring is performed SPR-15896 TEV segmentation fault during Event Listing SPR-15914 TEV cannot print result files SPR-15919 default colours for barchart are RED for all measurements SPR-15929 Primitive Objects in Groups SPR-15949 PRIV: check permission after other checks SPR-16030 Error when moving running synoptic display across screens SPR-16082 CU version manager allows multiple CDU versions of same CDU within a toplevel CCU version

http://sprdb.intra.space.corp/cgs/cgi-bin/search-spr-id.cgi?sprid=10241








































SPR-16174 TEV: Data set window remains busy after user error SPR-16178 GWDU: Misleading wrong warning requesting 2 variables SPR-16186 Wrong Start Date of Default_Test_Session SPR-16220 TEV: LEXICAL_ERROR raised for too long Titles SPR-16223 TEV: Title not properly loaded from definition SPR-16236 TSCV window remains busy after 'Reload' window dismiss SPR-16360 Graph Facility: Value Field Missing in Graph Templates SPR-16423 Incorrect Process-ID returned from Process-Creation-Server SPR-16492 CLS: Indexed assignment to string wrong in UCL Debugger SPR-16505 TEV: User events in descending order SPR-16507 Debug output in TEV not removed SPR-16575 HCI crash SPR-16579 cgs_daemon uses more than 90% CPU (sometimes) SPR-16630 FILE_IO_LIB incompatible with former (SAS based) version SPR-16647 CONSTRAINT_ERROR from TES during UCL debugging session SPR-16728 Exception raised by TES during 'UCL Browser:LOAD' SPR-16756 Consistency check for uniqueness of Activity ID within an activity block not working SPR-16819 TEV: No data set generated but no error message SPR-16820 TEV: Internal state not fully restored SPR-16843 TEV: 'Too long filename' message for empty list of files SPR-100032 Incorrect CSV Files SPR-100036 CMd History access failed after Client Reboot SPR-100037 TES_RPI.Get_CCU_Scope returns wrong CCU internal version SPR-100039 HCI is blocked after quitting explorer SPR-100050 install_user script for CGS V6 limitation SPR-100058 Wrong C format string for text dynamic. SPR-100059 AP scope info not updated during reload SPR-100082 LAYOUT_ERROR raised during CIS shutdown SPR-100083 Parameters of end items (e.g. SWOPs) in wrong order SPR-100104 Manual Stack (MCS Tools) cannot connect to Command History SPR-100114 Configuration Editor: Input Discarded on Errors SPR-100115 mcs-dbs error and warning messages, commanding after CS failover. SPR-100116 I_MDB import fails in case of different MDB versions SPR-100121 Entries in CMD History Report not ordered correctly SPR-100123 Cmd History storage error after Oracle Shutdown SPR-100126 The upgrade from CGS 4.5 to CGS 6.2 fails for SWEUs SPR-100128 Out-of-date items after CLS batch compile SPR-100134 Start.Message_Window script will not work properly SPR-100164 TEV does not delete temporary Files SPR-100165 TEV ASCII Data Listings in wrong Order SPR-100170 TEV crash when no result file specified SPR-100175 Set limits at runtime SPR-100182 CIS constraint error when requesting more than 900 items SPR-100202 UCL Debugger Test Script in bash Syntax SPR-100208 CommandHistory does not set LAST_FILE flag
















































SPR-100217 Remove Monitoring Status Indicator for standard elements SPR-100249 Print File in Graph Tool does not work SPR-100259 Selection of ADUs and GDUs from archive files on SMT does not work SPR-100268 MCS TOOLS cannot prepare DMS_Issue_Discrete_Cmd_Sw cmds SPR-100281 I_MDB hangs when running under KDE SPR-100302 Confusing User Interface in Message Handler Properties Window SPR-100303 HLCL subscription at CIS fails with InsufficientPrivileges SPR-100307 MCS tools command editor shows command parameters in wrong order SPR-100311 Acquisition status of HK variables subscribed via CIS not correct SPR-100315 Start USS editor for USS_DISPLAY enditem from IMDB SPR-100323 missing possibility to define units for integer types SPR-100325 missing possibility to define units for integer types SPR-100327 missing possibility to define units for integer types SPR-100341 Missing acquisition time source and kind in CIS IDL SPR-100344 Missing endpoint for VTC_ACS commands in MCS Tools SPR-100353 I_MDB chrashed by opening of multi-record window in case of long strings SPR-100372 CMDH / DBS zombie processes SPR-100409 Missing acquisition time source and kind in CIS IDL SPR-100417 Inconsistent formatting of command source code SPR-100459 TEV hangs sometimes when "list session" is selected SPR-100499 CGS Reconnections after DB Server failure SPR-100544 Raw Data Dump tool does not display the CCSDS packet header time in Full Mode SPR-100561 CIS services for TM packet acquisition not yet implemented SPR-100572 Load External not possible from enditem SPR-100573 P_MDB (MDA) reconnect to RAC SPR-100574 Command History reconnect to RAC SPR-100583 Error in Final Archive Functionality SPR-100598 Virtual Nodes and Alias Names in System Topology Table SPR-100602 CGS Reconnections after DB Server failure SPR-100604 User Events Selection Dialog provides irrelevant Events SPR-100605 User Events always ordered by LT SPR-100640 GWDU should not write data to $HOME/gwdu by default SPR-100644 Client_Watchdog mechanism erroneous (CONSTRAINT_ERROR) SPR-100648 Calibration does not work correcly for invalid description SPR-100665 TSCV can't communicate with test node with CGS Internal Number > 4 SPR-100676 DBS RPI logs error messages after disconnect TRDB SPR-100678 CGS TOOLS not starting correctly on HCI_02 host SPR-100692 CIS cannot get remote values from TES SPR-100694 CORBA HLCL status variables may not reflect internal interpreter status SPR-100698 cgs installation manual not included in delivery SPR-100705 CGS Reconnections after DB Server failure - no cmd_history live update SPR-100706 CGS message file not correctly installed SPR-100707 BDE import cannot import T_UNDEF_VALUES_BYTESTREAM SPR-100708 MDB data retrieval via EXCEL-MDB tool fails SPR-100711 Privtool could not import a privfile
















































SPR-100712 DBS Store Event File Problem SPR-100713 Oracle RAC Support for MCS SPR-100720 Oracle problem during boot SPR-100723 Oracle problem during boot SPR-100724 TRDB/CmdHistory to check, that applications handle missing Oracle correct SPR-100726 Oracle problem during boot SPR-100732 Unable to generate enditem report for USS Displays SPR-100735 Missing cls_editor information in user manual SPR-100740 CDU Merge Tool fails to export merge rules SPR-100741 R1025: USS shall be integrated into the CGS environment. SPR-100746 EuTEF: Invalid Length Field in CCSDS Packet SPR-100748 Dynamic string parameter missing SPR-100749 Dynamic string parameter missing SPR-100750 Dynamic string parameter missing SPR-100751 p_data_processor.iterate_on_values blocks data processor SPR-100752 Make timeout for process startup configurable SPR-100753 Unable to close test session of another user (TSCV) SPR-100754 Configurator generates wrong ORACLE_HOME in config files SPR-100756 Buttons are not accessible SPR-100757 Incorrect conversions of some GWDU displays SPR-100758 Library commands cannot be executed from USS synoptics SPR-100759 Only one character displayed in USS synoptics SPR-100761 Cannot open test session other than default test session SPR-100763 Impossible to generate GWDU XML Report for a single GWDU display SPR-100768 BDE import did not work correctly SPR-100769 Problem with HLCL Command Window and AP start SPR-100770 Missing Functionality in the CGS Configurator SPR-100772 Cleanup disk script is not complete SPR-100777 Problem with start_tev start script SPR-100778 generate scoe XML uses bad log dir SPR-100794 Alignment does not work correctly SPR-100795 CIS Socket Interface for MOIS clients not available SPR-100798 Problems when disconnecting from CIS SPR-100813 Installation Configurator does not start installer SPR-100815 Bad default calibration for Byte Stream Measurements SPR-100816 acquisition time is not displayed SPR-100818 OOL window does't display values SPR-100819 DDS: Error dispatching data to CIS_01 SPR-100822 Irritating informational messages for ADUs in SCOE log file SPR-100823 CONSTRAINT_ERROR@socket-alive_msg_info.adb:279 SPR-100826 "Failed to log engineering value" message many times SPR-100829 Command History Crash SPR-100832 Performance of MDB_VICOS.Get_Locations_For_Meas_In_ADU SPR-100839 USS Editor: Set as element default not working for behaviour properties SPR-100842 cis_client_hlcl ASSIGNMENT: Unknown variable 'STRICT'
















































SPR-100843 incorrect device address in gdu SPR-100848 USS Editor Java NPE when removing element from "Edit Data Source" SPR-100857 stop_acquisition for ADU without measurements returns INVALID_ITEM_NAME SPR-100858 CIS: constraint_error SPR-100860 changed return status for start_acquistion / issue








4.7.2 Temporary fixed Problems

4.7.3 Further Open Problems • SPR-100844 - It is not possible to align dynamic string parameter. CGS can handle unaligned

parameter only.

• SPR-100859 - For security reasons it was decided to deliver CGS 6.3.1 without freeze function for HCI.

• SPR-100868 - SAS linked with the CGS API and using posix.process_primitives.exit_process are hanging. Use the system call _exit (not exit !) instead of posix.process_primitives.exit_process.

• SPR-100880 - CLS batch compile to slow

Change CGS default configuration: Set CLS.Dependencies.Load_Tree to False and CLS.Dependencies.Load_Exclude to True

4.7.4 Known Restrictions • It is not possible to prepare a telecommand (SWOP, FLAP, PUS_TC, and TC) via CIS, if this

telecommand is defined with garded parameters in the parameter lists.

• Not all interfaces for the new CGS IDL 2.0 are implemented in CGS:

Note: unsupported 'oneway void' calls are stubs, just generating a debug message '<Procedure_Name> -- to be implemented --' with debug output enabled.

o partially supported by CGS:

Interfaces TelemetryPacket/TelemetryPacketClient (existing telemetry packet related methods were moved there from interfaces Telemetry/TelemetryClient ; item identification lists related stuff moved from Telemetry to TelemetryBase to be reusable by TelemetryPacket(Client)): - TelemetryPacket.(un-)subscribePackets work now, CIS will deliver

subscribed packets via TelemetryPacketClient.processPacket until unsubscribed.

- TelemetryPacket.(un-)subscribePacketAcquisitions for notification about all packet acquisition status changes are not yet supported; subscribe will raise RequestFailed.

- Callback packetAcquisitionChanged is never called by CIS.

o - not (yet) supported by CGS:

Calibration description as telemetry property: - not yet supported by CGS: no calibration updates are sent by CIS

Telemetry report deliveries:

- Telemetry data reports not yet supported: - Telemetry.getTelemetryReport raises ServiceNotAvailable. - Telemetry.cancelTelemetryReport is empty. - TelemetryClient.telemetryReportDelivery is never called by CIS.



5 Installation Procedures This software shall be used on Intel PC with SUSE Linux Enterpriser Server 8 (SLES8).

5.1 Complete Installation For a complete installation follow the instructions of CGS installation manual ref. [AD 2.1]. Remark: The actual CGS installation manual is on CD below /<mountpoint>/doc/manual.

5.2 Patch Installation (based on CGS 6.3.0) For a patch installation follow the next instructions:

5.2.1 Needed passwords 1. <cgsadmin> (UNIX user) 2. root (UNIX user) 3. <MDB_ADM> (oracle user) 4. oracle system (oracle user)

5.2.2 Installation steps

1. login as <cgsadmin> on DB server host

2. cgs shutdown via task_selector

3. quit task_selector

4. terminate the cgs_daemon in shell: killall -9 cgs_daemon

5. stop command history / central distributor (on command history server)

in shell: $CGS_HOME/gsaf/dbs/bin/common/stop_cmd_history in shell: $CGS_HOME/gsaf/dbs/bin/common/stop_central_distributor

6. insert CGS basic CD CGS_6.3.1

7. mount CD

8. install all products from CD

in shell: /<mountpoint>/installer.sh Select Continue, Continue, Install, -- for CGS Previous, TOOLS, Continue, Install -- for TOOLS Exit

9. unmount CD 10. register version

in shell: vit_manager -upd_item cgs VERSION 6.3.1_B6_LINUX



11. insert CGS optional CD CGS_6.3.1 REMARK: This and the next four steps are optional, but CGS recommends strongly to install gsaf part of optional CD.

12. mount CD

13. install all optional products from CD

in shell: /<mountpoint>/installer.sh

Select Continue, Continue, Install, -- for CGS optional Previous, Select for Installation Source path /<mountpoint>/addon Continue, Install -- for add-ons (unsupported) Exit

14. unmount CD 15. register version

in shell: vit_manager -upd_item cgs_optional VERSION 6.3.1_B6_LINUX

16. update configuration.xml (optional) Insert needed configuration parameter, if necessary. For detailed information refer section 4.5 part 2.

17. update CGS directory structure in shell:

$CGS_HOME/patches/CGS_6.3_1/patch_cgs.sh 18. update the MDB / MDB stored procedures in shell:

$CGS_HOME/patches/CGS_6.3_1/patch_mdb.sh -- needs ca. 5 minutes verify output: MDB patch successfully installed verify output: Temp MDB patch successfully installed REMARK: The next command is only necessary for an update of the internal data structure of the MDB (e.g. new data structure delivery for extended databases (user defined data types)). During initialization all user entries in the flexible tool invocation and flexible reports are deleted. This command is optional and the usage shall be decided by projects. $CGS_HOME/gsaf/mda/config/mdb/install/admin_scripts/initialize_mdb $CGS_HOME/gsaf/mda/config/mdb/install/admin_scripts/update_plsql_stored_procedures REMARK: The next command is only necessary for a better performance of MDB access. This command is optional and the usage shall be decided by projects. $CGS_HOME/gsaf/mda/config/mdb/install/admin_scripts/gather_mdb_stats

19. reboot server and if the server is ready, reboot all clients



5.3 Oracle RAC installation for CGS

5.3.1 Prerequisites CGS was tested with ORACLE RAC 10gR2 (Version 10.2.0.2) running on SuSE SLES9 SP2. To install CGS on ORACLE 10gR2 Oracle 9.2.5 must be installed on one of the CGS client machines. Also the CGS_HOME directory must be available on this client machine. The installation of the Oracle instance and the CGS tablespaces will not be done with help of CGS installation configurator.

5.3.2 Oracle RAC installation

Follow installation instructions of ORACLE 10gR2. provided by ORACLE

5.3.3 Oracle Database Instance Creation The database instance used for CGS databases can be created with dbca tool from ORACLE when logged in on the database cluster as ORACLE administrator user. The database can be created from General Purpose database template. Note, that the database must be created with US7ASCII character set! The database must use automatic storage management. After creation of the database instance the $ORACLE_HOME/network/admin/tnsnames file on the client which will be used for the CGS database installation must be adapted. An example entry is shown below:

cgscl1 = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = cgscl1-vip)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = cgscl2-vip)(PORT = 1521)) (LOAD_BALANCE = yes) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = cldb1.astrium) (FAILOVER_MODE = (BACKUP = cldb1.astrium) (TYPE = SELECT) (METHOD = PRECONNECT) (RETRIES = 180) (DELAY = 5) ) ) )

This adaptation must be done on each CGS client machine which uses the database cluster. After adaptation of the tnsnames file login as CGS Administrator. At first you have to start the CGS configurator and to change the value for the TWO_TASK variable. Save the configuration and create the dotfiles. Logout and again login as CGS Administrator. Check with sqlplus that the new TWO_TASK is working and a correct connection to the cluster dabase can be established.

5.3.4 CGS Tablespace creation CGS needs tablespaces for the following products:

• Mission Database • Result Database



• Command History

The CGS script "create_tablespaces" for the creation of the CGS tablespaceses requires an database which uses ORACLE automatic storage management. The script is located in $CGS_HOME/gsaf/cgsi/config/Oracle/rac. The script needs as parameter the name of the application for which the tablespaces will be created. To create the tablespaces for the mission database login as CGS administrator on the client host and execute the command: cd $CGS_HOME/gsaf/cgsi/config/Oracle/rac/ ./create_tablespaces -mdb At next some privileges for the database must be configured. Execute the following commands: cd $CGS_HOME/gsaf/cgsi/config/Oracle/rac/ ./create_addational_grants

5.3.5 Installation CGS application databases

When using RAC the CGS databases will not be installed with help of CGS installation configurator. The installation scripts must be executed on command line. The mission database can be installed by executing the following commands on the client machine as CGS administrator:

$CGS_HOME/gsaf/mda/config/mdb/install/admin_scripts/install_mdb $CGS_HOME/gsaf/mda/config/mdb/install/admin_scripts/initialize_mdb

The result database can be installed by executing the following commands on the client machine as CGS administrator:

$CGS_HOME/gsaf/dbs/util/common/install_trdb rac The database for the command history application can be installed by executing the following commands on the client machine as CGS administrator:

$CGS_HOME/gsaf/dbs/util/common/command_history/install_cmd_history rac Beginning from now the normal CGS installation actions can be followed.



6. Acronyms AD Applicable Document ADD Architectural Design Document AP Automated Procedure ASCII Americal Standard Code for Information Interchange ATP Authorization to Proceed ATV Autonomous Transfer Vehicle CCB Configuration Control Board CCU Configuration Control Unit CCSDS Consultative Commitee for Space Data System CGS Core Ground System CDU Configuration Data Unit CLS CGS Language System COTS Commercial Off-The-Shelve CPL Crew Procedure Language CPU Central Processing Unit D&D Design and Development DMS Data Management System DOF Degree of Freedom EGSE Electrical Ground Support Equipment EM Engineering Model EQM Engineering Qualification Model ESA European Space Agency ETM Electrical Test Model FDIR Fault Detection, Isolation and Recovery FM Flight Model GMT Greenwich Mean Time GNC Guidance Navigation Control GPS Global Positioning System HCI Human-Computer Interface HL High Level HLCL High Level Command Language HW Hardware ICD Interface Control Document IF InterFace ISS International Space Station LL Low Level MDB Mission Database MET Mission Elapsed Time MMS Matra Marconi Space N/A Not Applicable PDB Project Data Base PROM Programmable Read Only Memory RAM Random Access Memory RD Reference Document RFW Request for Waiver ROM Read Only Memory RV RendezVous S/C SpaceCraft SCCB Software Configuration Control Board SOC Statement of Compliance SPR Software Problem Report SRD Software Requirements Document



SUM Software User Manual SW SoftWare SWRU Software Replaceable Unit TBC To Be Confirmed TBD To Be Defined TC TeleCommand TM TeleMetry TRR Test Readiness Review UCL User Control Language URD User Requirements Document UTC Universal Time Coordinated VCD Verification Control Document VTP Validation Test Plan

Dok. Nr. ASTRIUM - Airbuscs.astrium.eads.net/cgs/docs/manual/CGS631/CGS_Release...The purpose of...

Documents

Transcript of Dok. Nr. ASTRIUM - Airbuscs.astrium.eads.net/cgs/docs/manual/CGS631/CGS_Release...The purpose of...