CGS Interface Control Document (Issue 4/A)...COL–RIBRE–IRN–CGS–8020 16/07/98 Packet Length...

Titel:Title:

Dokument Nr.:Document No.:

Ausgabe Nr.:Issue No.:

Überarbeitung:Revision:

Klassifikations Nr.:Class. Prod. Code:

Ausgabedatum:Issue Date:

Überarbeitungsdatum:Revision Date:

Liste der zu liefernden Dokumente/Dok.–Anforderungs–Beschreibung(LLD/DAB):Document Requirements List / Doc. Requirements Description (DRL/DRD):

Bearbeitet:Prepared by:

Geprüft:Agreed by:

Firma:Company:

Vertrags–Nr.:Contract–No.:

ProjektmanagerProject Manager

Firma:Company:

ProjektmanagerProject Manager

CGS Interface Control Document– for CGS V4.2.0 –

COL–RIBRE–ICD–0025–00

4

A

8–QA

17/04/98

31/03/99

3.704

CGS Engineering DASA–RI

P. Athmann DASA–RI

R. Zimmermann, DASA–RI

DaimlerChrysler Aerospace

Raumfahrt Infrastruktur

Daimler–Benz Aerospace – All Rights Reserved – Copyright per DIN 34




Dok.-Nr/Doc. No.:Ausgabe /Issue:

Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

i

COL–RIBRE–ICD–0025–004A

17/04/9831/03/99

von /of: xii

DOCUMENT CHANGE RECORD

Issue/Rev. Issue date Pages/Section RemarksAffected

1/– 22/03/96 all First issue of this ICD for CGS V2.2 andV3.0.

2/– 24/03/97 all Update for CGS V3.1.3:Incorporation of CGS V3.1.2/V3.1.3 IRNs

3/– 04/08/97 all Update for CGS V4.1:Incorporation of CGS V3.1.3 / V3.2 / V4.0/ V4.1 IRNs

4/– 17/04/98 all Update for CGS V4.1:Incorporation of CGS V3.1.3 / V4.0 / V4.1IRNs

4/A 31/03/99 all Update for CGS V4.2.0:Incorporation of CGS V4.1/V4.2.0 IRNs asidentified on next pages.Update Applicable Documentation

TEAM COORD. IRNB COORD.CGS IRN–NO. CHANGE TOPIC

DATE STATUS DATE STATUSOR.

EFFECTIVITY

CG

SI

SD

E

SW

ES

MD

A

CLS

GW

DU

FW

DU

TS

CV

HC

I

TE

S

DB

S

TE

V

NW

SW

TS

S

CS

S

CG

S

DATE

MD

BIC

D

Daimler–Chrysler Aerospace


Dok.-Nr / Doc. No.:Ausgabe / Issue:Überarbtg. / Rev.:Seite / Page:

Datum / Date:Datum / Date:

ii

4 17/04/9831/03/99

of xii



CGS V4.1.1 IRNs appr.after 17/04/98 (CGS+MDB ICD issue 4/–)

COL–RIBRE–IRN–CGS–7070 17/03/98 Oracle Config File P R R R R P AW 18/3/98 Coordinated 6/5/98 Approved

COL–RIBRE–IRN–CGS–7072 23/3/98 mismatch ICD/ installation scripts P R R R R R R R R R R R R R R P TS 6/5/98 Coordinated 6/5/98 Approved

CGS V4.1.1.8 IRNsCOL–RIBRE–IRN–CGS–8008 27/05/98 Restricted Datatypes: CCSDS/datatypes P P PA 29/05/98 Coordinated 19/6/98 Approved

COL–RIBRE–IRN–CGS–8014a 18/06/98 Checksum in CCSDS Packets R P R R R P UH 25/06/98 Coordinated 03/07/98 Approved

CGS V4.1.1.9 IRNsCOL–RIBRE–IRN–CGS–8003b14/08/98 UCL System Library Extensions/Updates P P PHa 25/08/98 Coordinated 11/09/98 Approved

COL–RIBRE–IRN–CGS–8011a 20/06/98 UCL Ground_Command_to_onboard modifications P P PHa 24/06/98 Coordinated 3/07/98 Approved

COL–RIBRE–IRN–CGS–8016 22/06/98 HK Values for Conditional Monitoring P P PHa 24/06/98 Coordinated 3/07/98 Approved

COL–RIBRE–IRN–CGS–8026 10/09/98 MODEL_CONNECTION: new procedure P P WT 11/09/98 Coordinated 11/09/98 Approved

TEAM COORD. IRNB COORD.CGS IRN–NO. CHANGE TOPIC

DATE STATUS DATE STATUSOR.

EFFECTIVITY

CG

SI

SD

E

SW

ES

MD

A

CLS

GW

DU

FW

DU

TS

CV

HC

I

TE

S

DB

S

TE

V

NW

SW

TS

S

CS

S

CG

S

DATE

MD

BIC

D

Daimler–Chrysler Aerospace


Dok.-Nr / Doc. No.:Ausgabe / Issue:Überarbtg. / Rev.:Seite / Page:

Datum / Date:Datum / Date:

iii

4 17/04/9831/03/99

of xii



CGS V4.2.0 IRNsCOL–RIBRE–IRN–CGS–8001c17/12/98 FWDU:change due to CR–0218:Rules Clarif. P P PHe 20/12/98 Coordinated 15/1/99 Approved

COL–RIBRE–IRN–CGS–8017b 15/11/98 Commercial Baseline P R R R R R R R R R R R R R R P PA 19/11/98 Coordinated 25/11/98 Approved

COL–RIBRE–IRN–CGS–8020 16/07/98 Packet Length in CCSDS Packets R P R R R P MD 17/07/98 Coordinated 29/7/98 Approved

COL–RIBRE–IRN–CGS–8022a 4/11/98 CALIBRATION package: Unsigned Integer R P R R R R P PHa 04/11/98 Coordinated 15/1/99 Approved

COL–RIBRE–IRN–CGS–8027a 8/3/99 Cshrc file: ORA_NLS33 env.variable P R R R R R R R R R R R R R R P MD 9/03/99 Coordinated 15/3/99 Approved

COL–RIBRE–IRN–CGS–8036 5/11/98 TES_API: Use of UNIX Signals P P PA 16/11/98 Coordinated 15/1/99 Approved

COL–RIBRE–IRN–CGS–8038 4/11/98 ADT_GDU_DESCR: 255 Param.,Mem.Dealloc R R P R P PHa 4/11/98 Coordinated 15/1/99 Approved

COL–RIBRE–IRN–CGS–8039 4/11/98 ADT_ADU_DESCR: Flag for Physical Address R R P R P PHa 4/11/98 Coordinated 15/1/99 Approved

COL–RIBRE–IRN–CGS–8040 17/11/98 DBS_DEFINITIONS: Repres. Clause(SPR–5512). R R R P R R P PA 17/11/98 Coordinated 15/1/99 Approved

COL–RIBRE–IRN–CGS–8046 22/12//98 MODEL_CONNECTION,CSS_DEFINITIONS P P WT 22/12/98 Coordinated 15/1/99 Ext.Coord





Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

iv


17/04/9831/03/99

von /of: xii

TABLE OF CONTENTS

CHAPTER 1 : INTRODUCTION 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 Identification and Scope 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Purpose 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Reader Guide 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.4 Type of Described Interfaces 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.5 Versions Identification 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.6 Document Modification 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAPTER 2 : APPLICABLE AND REFERENCE DOCUMENTS 5. . . . . . . . . . . . . . . .

2.1 Applicable Documents 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.2 Reference Documents 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAPTER 3 : GENERAL DESCRIPTION 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 CGS Functional Overview 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAPTER 4 : INFRASTRUCTURE INTERFACES 14. . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Communication Services 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1.1 Internet Port Number Allocation 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1.2 Commercial Product Versions 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2 Operating System Services 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.1 Operating System 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2 File System Structure 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2.1 Home Directories for CGS Products 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2.1.1 Sun Platform 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2.1.1.1 GSAF Home Directory 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2.1.1.2 CGS Home Directory 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2.1.1.3 Product Home Directories 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2.1.2 HP Platform 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2.2 Subdirectories for CGS Products 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

v


17/04/9831/03/99

von /of: xii

4.2.2.2.1 Start–Up Scripts 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2.2.2 Executable Images (Platform dependent) 19. . . . . . . . . . . . . . . . . . . . . . 4.2.2.2.3 Environment 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2.2.4 Utilities and Tools (Platform dependent) 19. . . . . . . . . . . . . . . . . . . . . . . 4.2.2.2.5 Configuration Data 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2.2.6 Runtime Data 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2.2.7 Libraries 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.2.3 Special Checkout related Directories 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2.3.1 Test Node Directory on the HP Test Nodes 20. . . . . . . . . . . . . . . . . . . . . 4.2.2.3.2 Test Node Directories on the SUN Database Server 21. . . . . . . . . . . . . .

4.2.2.4 Home Directories For CGS Extensions And Add–Ons 21. . . . . . . . . . . . . . . 4.2.2.4.1 Special Application Software (SAS) 21. . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2.4.2 Command And Measurement Adaptation Software (CMAS) 22. . . . . . . 4.2.2.4.3 Mission Database Support Software (MDB_SS) 22. . . . . . . . . . . . . . . . .

4.2.3 Common User Environment Files 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.2.3.1 Central Scripts 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.3.1.1 Central ”login” Script 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.3.1.2 Central ”cshrc” Script 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.3.1.3 Central ”logout” Script 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3 Relational Database Management System 32. . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.1 Functional Interface 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.1.1 General 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.2 Database Installation and Configuration 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.2.1 Predefined Object Names 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2.1.1 User Accounts 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2.1.2 Tablespaces 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2.1.3 Public Synonyms 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2.1.4 CRT Device Names 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.2.2 ORACLE Configuration Parameters 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2.2.1 INIT.ORA Configuration File 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2.2.2 Rollback Segments 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


4.4 Communication Services 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.4.1 Internet Port Number Allocation 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


4.5 Presentation Services 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.6 DataViews Services 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7 CGS Top Level User Interface 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.1 Error Services 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

vi


17/04/9831/03/99

von /of: xii

4.7.1.1 Definition of Terms 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.1.2 Provided Operations 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.1.3 Reporting Options 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.1.4 Addressing the Error Message 43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.1.5 Displaying and Logging the Error Message 43. . . . . . . . . . . . . . . . . . . . . . .

4.7.1.6 Central Logging 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.1.7 Supplying a Timestamp 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.1.8 Supplying Extra Text 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.1.9 Error Message Number 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.1.10 Error Message Components 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.1.11 Handling of Messages 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.2 Error Report Package 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.3 Error Services Package 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.4 Timestamp Services Package 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.5 File Information 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.5.1 File Names and Locations 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.5.1.1 Error Message Database 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.5.1.2 Session Error Log 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.5.1.3 Process Response Log 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.7.5.2 Error Message Database Format 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.8 Other Commercial Products Version 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.9 CGS_Library 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.9.1 Informal Interface 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.9.2 Formal Interface 62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CHAPTER 5 : SOFTWARE DEVELOPMENT INTERFACES 63. . . . . . . . . . . . . . . . . . .

5.1 Documentation Format 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1.1 Format of Imported Documents 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1.1.1 Interface Description 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1.1.2 Interface Definition 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.1.2.1 Document Location Conventions 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.1.2.2 Document Filename Conventions 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.1.2.3 Importable DOCUMENT Contents 65. . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2 Generic Compiler Interface 67. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2.1 Generic C Compiler Environment Integration Interface 67. . . . . . . . . . . . . . . . .

5.2.2 Generic Ada Compiler Environment Integration Interface 67. . . . . . . . . . . . . . .

5.3 Generic Tool Interface 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

vii


17/04/9831/03/99

von /of: xii

CHAPTER 6 : MISSION PREPARATION INTERFACES 69. . . . . . . . . . . . . . . . . . . . . . .

6.1 Package MPS_DEFINITIONS 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.1 Exceptions 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.1.1 Exceptions due to internal MDB / ORACLE errors 70. . . . . . . . . . . . . . . . .

6.1.1.2 SID_ERROR 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.1.3 AUTHORIZATION_ERROR 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.1.4 USE_ERROR 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.1.5 ENVIRONMENT_ERROR , CDU/CCU_ERROR 70. . . . . . . . . . . . . . . . . .

6.1.1.6 PARAMETER_ERROR 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.1.7 CONSISTENCY_ERROR 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1.2 Formal Description 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2 MDB Standard Entities and Application Programmer Interface 92. . . . . . . . . .

6.3 CLS Global 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3.1 General CLS Definitions 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3.2 Runtime Representation of UCL Types 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.4 Flexible Tool Invocation Interface 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.5 Foreign Key Support / PUI Support 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.6 MDB Batch Data Entry Format 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7 I–Code Definition 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7.1 Functional Description 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7.2 I–Code Record Layout 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7.3 I–Code Record Description 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7.4 Architecture of the Stack Machine 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7.5 I–Code Instructions 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7.5.1 Instruction Format 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7.5.2 Conventions 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7.5.3 Detailed I–code Instructions Table 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.1 Instructions with implied parameter 114. . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.2 Load Instructions 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.3 Load Address Instructions 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.4 Store Instructions 122. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.5 MOVE and CAT Instructions 125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.6 Stack Instructions 126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.7 Numerical Instructions 127. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.8 Comparison Instructions 137. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.9 BOOLEAN negation 147. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.10 Allocation Instructions 147. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

viii


17/04/9831/03/99

von /of: xii

6.7.5.3.11 Jump Instructions 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.12 Special Jump Instructions 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.13 Iterative Instructions 150. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.14 Switch Instructions 151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.15 Procedure/Function Call Instructions 153. . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.16 Conversion Instructions 155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.17 Miscellaneous Instructions 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.18 System Instructions 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7.5.3.19 No–operation Instruction 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7.6 Sample AP and Corresponding I–Code 163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.7.7 Procedural Interface 166. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.8 Parameter Encoding 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.8.1 Functional Description 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.8.2 Parameter Classes 176. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.8.3 Encoding Scheme 177. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.8.3.1 External Scheme 177. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.8.3.2 Internal Scheme 178. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.8.4 Example (Call of a library procedure) 179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.8.5 Stack Machine Representation of AP Parameters 180. . . . . . . . . . . . . . . . . . . . . .

6.9 Flight Synoptic Display Representation Format 181. . . . . . . . . . . . . . . . . . . . . . .

6.10 FWDU Supported Sammi API Interfaces 182. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.10.1 File Naming Conventions 182. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.10.2 Logical Server Name 183. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.10.3 Commands to the On–Board System 184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.10.3.1 Software Commanding 184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.10.3.2 Pre–Defined Commands 184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.10.3.3 Window Association Information (WAF) 185. . . . . . . . . . . . . . . . . . . . . . . . .

6.10.4 FWDU Applied Type Mapping 188. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.10.4.1 Mapping between On–board and CGS standard end item types 188. . . . . . . .

6.10.4.2 Mapping between CGS standard end item types and Sammi data types 188. .

CHAPTER 7 : CHECKOUT AND SIMULATION INTERFACES 190. . . . . . . . . . . . . . . . .

7.1 Test Setup Invocation Interface 191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2 VICOS Types Definition 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3 HCI Abstract Data Types 200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.1 General Concepts 200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

ix


17/04/9831/03/99

von /of: xii

7.3.2 Operations 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.2.1 SET Operations 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.2.2 GET Operations 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.2.3 ALTERNATIVE Function 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.2.4 PACK Operation 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.2.5 UNPACK Operation 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.2.6 PACKED_SIZE Function 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.2.7 ADD Operations 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.2.8 Operations on tables 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.2.9 Exceptions 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.2.10 Particular Remarks 203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.2.10.1 On Synchronisation 203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.2.10.2 On Packing/Unpacking 203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.3 ADT Physical Address 204. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.4 ADT CCSDS Packet 211. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.3.5 Binary Buffer ADT 224. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.4 Calibration 231. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.5 TES DEFINITIONS 247. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.6 TES Abstract Data Types 252. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.6.1 General Concepts 252. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.6.2 Operations 253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.6.2.1 SET Operations 253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2.1.1 GET Operations 253. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2.1.2 ALTERNATIVE Function 254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2.1.3 PACK Operation 254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2.1.4 UNPACK Operation 254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2.1.5 PACKED_SIZE Function 254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2.1.6 ADD Operations 254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2.1.7 Operations on tables 254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2.1.8 Exceptions 254. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2.1.9 Particular Remarks 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2.1.10 On Synchronisation 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6.2.1.11 On Packing/Unpacking 255. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.6.3 ADT Raw Value 256. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.6.4 ADT Engineering Value 264. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.6.5 ADT ADU Description 270. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.6.6 ADT ADU 280. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.6.7 ADT GDU Description 293. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.6.8 ADT GDU 305. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

x


17/04/9831/03/99

von /of: xii

7.7 TES Application Programmer Interface 312. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.8 VICOS Housekeeping Values 330. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.9 System Libraries 337. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.9.1 UCL Ground System Library 337. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.9.1.1 Routines Summary 337. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.9.1.2 UCL Ground System Library Specification 338. . . . . . . . . . . . . . . . . . . . . . .


7.9.2 UCL Ground_Commands_To_Onboard System Library 406. . . . . . . . . . . . . . . .


7.9.2.2 UCL Ground_Commands_to_Onboard System Library Specification 406. .


7.9.3 TCL System Library 422. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


7.9.3.2 TCL_LIBRARY Specification 423. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.9.3.3 TCL ASCII Format Specification 434. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.10 Onboard Commands and Responses 436. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.10.1 Software Commands (SWOP_Command) 436. . . . . . . . . . . . . . . . . . . . . . . . . . .

7.10.1.1 CCSDS Header for Software Commands 436. . . . . . . . . . . . . . . . . . . . . . . . .

7.10.1.2 CCSDS Data Field for Software Commands 436. . . . . . . . . . . . . . . . . . . . . .

7.10.1.3 Response Packet 437. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10.1.3.1 CCSDS Header 437. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10.1.3.2 CCSDS Data Field 437. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.10.2 FLAP Execution Requests 438. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.10.2.1 CCSDS Header for FLAP Execution Requests 438. . . . . . . . . . . . . . . . . . . .

7.10.2.2 CCSDS Data Field for FLAP Execution Requests 438. . . . . . . . . . . . . . . . . .

7.10.2.3 Response Packet for FLAP Execution Requests 439. . . . . . . . . . . . . . . . . . . 7.10.2.3.1 CCSDS Header 439. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10.2.3.2 CCSDS Data Field 439. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.11 DBS Types and Constants Definitions 440. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.12 DBS Application Programmer Interface 455. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.13 TEV Types and Constants Definitions 464. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.14 TEV Application Programmer Interface 483. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.15 Test Evaluation Invocation Interface 538. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.15.1 TEV Invocation for Interactive Mode 538. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.15.2 TEV Batch Mode 538. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.15.3 TEV in Office Mode 539. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

xi


17/04/9831/03/99

von /of: xii

7.16 EXCEL Representation Format 540. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.17 Command and Measurement Adaptation System 541. . . . . . . . . . . . . . . . . . . . . .

7.18 Data Types supported by CGS in TES_API and CMAS_IF 607. . . . . . . . . . . . .

7.18.1 CGS Data Types Supported 607. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.18.2 CGS Data Types: UCL to Raw Value Conversion 609. . . . . . . . . . . . . . . . . . . . .

APPENDIX A : ACRONYMS 612. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

APPENDIX B : DEFINITIONS 620. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

xii


17/04/9831/03/99

von /of: xii

TABLE OF FIGURESFigure 1.3–1 CGS Interface Control Document Structure 3. . . . . . . . . . . . . . .

Figure 4.2.2.3.2–1 Example of Mounting Test Node Directories on the Database Server. 21

Figure 6.7–1 I–Code Record 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6.7–2 Stack Machine Runtime Layout 109. . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6.8.3–1 External Parameter Encoding Scheme 177. . . . . . . . . . . . . . . . . . . .

Figure 6.8.3–2 Internal Parameter Enoding Scheme 178. . . . . . . . . . . . . . . . . . . . .

Figure 6.8.3–1 Encoded Parameter List 179. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6.8.3–1 Global Data Frame 180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

1


17/04/9831/03/99

von /of: 492

CHAPTER 1 :INTRODUCTION




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

2


17/04/9831/03/99

von /of: 492

1.1 Identification and Scope

This is the Interface Control document for the COLUMBUS Ground System software.

The authorized abbreviation for this software is CGS.

The approved identification and nomenclature of the document is the following :

CGS Interface Control Document– for CGS V4.2.0 –


The scope of this document is to cover all aspects of CGS related to external interfaces.

1.2 Purpose

The purpose of this document is to describe functionally and formally how CGS interacts with the other SWproducts of the Columbus Ground System (CGS) and with other external systems.

It establishes in a single document an interface agreement between the Columbus System and the CGS productwith respect to those interfaces identified in section 1.1.

Hereby it is the objective to control the interface of the CGS product such that it provides services to all inter-faced Columbus products in a manner suited to their needs.

The contents of this document are applicable to the design and the development of the CGS product.

1.3 Reader Guide

In principle, the structure of this document follows the general ICD layout, as described in the Columbus Soft-ware Development Standards (refer to document 2.2.2.1). But the presentation of the provided and required in-terfaces has been modified because it simplifies the different CGS product ICDs handling. For the CGS compo-nent, the following structure has been adopted :




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

3


17/04/9831/03/99

von /of: 492

––1 | Introduction––2 | Applicable and Reference Documents––3 | General Description––4 | ”Product Name” Provided Interfaces––4.1 | Interface A––4.2 | Interface B

...––5 | ”Product Name” Required Interface of ”Product Y”––5.1 | Interface C

...––6 | ”Product Name” Required Interface of ”Product Z”––6.1 | Interface D

...––n | Language Interface (optional)––n+1 | Representation Interface (optional)––n+2 | Implementation Interface (optional)––n+3 | Product Link Interface––Appendix A | Acronyms––Appendix B | Definitions

...

Figure 1.3–1 CGS Interface Control Document Structure

The chapter 2 provides the applicable and reference documents mentioned in this ICD.

The chapter 3 gives an overview of the role of CGS within the complete CGS component.

The chapter 4 contains the interfaces provided by CGS to the rest of the system, as listed in the chapter 3.

The chapter 5 and the following ones contain the interfaces CGS requires from the rest of the system, as listedin the chapter 3. Each component interfacing CGS is treated in a separate chapter.

The chapter n describes language conventions, if there are some defined.

The chapter n+1 describes data representation conventions, if there are some defined.

The chapter n+2 describes protocol implementation conventions, if there are some defined.

The chapter n+3 gives necessary information to set links between products.

The appendix A provides the list of the acronyms used in this ICD.

The appendix B lists the definitions of the key terms used in this ICD.

1.4 Type of Described Interfaces

This document deals with application program interface, language interface and representation interface only.

The reader will not find the description of the CGS user interface. This type of interface, if any, will be describedin detail in the CGS Architectural Design Document and/or in the CGS User Manual .

1.5 Versions Identification

The CGS software component is developed and made available in several versions.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

4


17/04/9831/03/99

von /of: 492

Each version provides a particular set of functionalities identified in the CGS Software Requirements Specifica-tion.

This document contains the interface definitions for the CGS for CGS version V4.2.0.

The sections and texts not relevant for the CGS current version shall not be part of this document.

1.6 Document Modification

In the Columbus software standard life cycle (refer to document 2.2.2.1), the ICD is a document which is in-itially produced during the requirements phase, when the interfaces are identified, and subsequently updatedduring the Architectural and Detailed Design phases, when the formal definition of the interface is added. There-fore this ICD will be subject to modifications during the complete CGS design phase.

Changes from one issue/revision to the next one are highlighted by addition of bars in the margins.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

5


17/04/9831/03/99

von /of: 492

CHAPTER 2 :APPLICABLE AND

REFERENCE DOCUMENTS




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

6


17/04/9831/03/99

von /of: 492

2.1 Applicable Documents

The following documents, of the issue shown, are external documents called up in the current document andwhich are considered to form part of this document, i.e. the called up section(s) of the applicable documentshould be treated as if they were an integral part of the document. In case of conflict, the newer documentsupersedes the older one.

2.1.1 Specifications

2.1.1.1 COLUMBUS Ground System Infrastructure (CGSI)S/W Product Requirement Specification,

SPE 1216 471 Issue 1/B 03/11/93

2.1.1.2 Software Development Environment (SDE), Reduced Operational Capability (ROC)S/W Assembly Requirement Specification

SPE 1081 716 003 Issue 1/B 08/09/93

2.1.1.3 Software Entity Software (SWES)S/W Product Requirements Specification,

SPE 1218 850 002 Issue 1/– 28/05/93

2.1.1.4 Mission Database Application (MDA)S/W Product Requirement Specification,

SPE 1216 401 002 Issue 2/C 05/11/93

2.1.1.5 COLUMBUS Language System (CLS)S/W Product Requirement Specification,

COL–RIBRE–SPE–0119 Issue 2/A 19/06/97

2.1.1.6 Ground Window Definition Utility (GWDU)S/W Product Requirement Specification,

COL–RIBRE–SPE–0035 Issue 4/– 04/07/97

2.1.1.7 Flight Window Definition Utility (FWDU)S/W Product Requirement Specification,


2.1.1.8 Test Setup, Configuration and Validation (TSCV)S/W Product Requirement Specification,

COL–RIBRE–SPE–0043 Issue 6/D 17/07/97

2.1.1.9 Human Comuter Interface (HCI)S/W Product Requirement Specification,


2.1.1.10 Test Execution Software (TES)S/W Product Requirement Specification,


2.1.1.11 Database Sevices (DBS)S/W Product Requirement Specification,


2.1.1.12 Test Evaluation Software (TEV)S/W Product Requirement Specification,


2.1.1.13 Network Software (NWSW)S/W Product Requirement Specification,

SPE 1216 844 001 Issue 7/– 06/05/93




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

7


17/04/9831/03/99

von /of: 492

2.1.1.14 Time Services Software (TSS)S/W Product Requirement Specification,

SPE 1235 055 Issue 1/A 19/05/93

2.1.1.15 Core Simulation Software (CSS)S/W Product Requirement Specification,


2.1.1.16 COLUMBUS Ground System (CGS)S/W Assembly Requirement Specification,

COL–RIBRE–SPE–0032 Issue 6/C 31/03/99

2.1.2 Standards

2.1.2.1 User Control Language (UCL) Re ference ManualCOL–RIBRE–STD–0010 Issue 4/– 13/03/98

2.1.2.2 High Level Command Language (HLCL) Reference ManualCOL–RIBRE–STD–0009 Issue 2/A 13/03/98

2.1.2.3 Reference Manual for Crew Procedure Language (CPL) and Software CommandingCOL–RIBRE–STD–0008 Issue 1/E 18/05/98

2.1.3 Design Documents

None.

2.1.4 Technical Notes

2.1.4.1 CGS_Library DescriptionCOL_RIBRE_TN_1113; Iss. 1F; 4.8.1997

2.1.5 Manuals

2.1.5.1 Life*CODE Integrator Manual TBD TBD

2.1.5.2 Life*ADA Integrator Manual Issue 1.1 July 1995CSD/TRJ/USM/005

2.1.5.3 Generic Tool Integration User Manual Issue 2.0 May 1995

2.1.5.4 Interleaf 5, File Formats Manual Release 5.3

2.1.5.5 MDA Reference ManualCOL–RIBRE–MA–0031–00 Issue 4/A 25/09/98

andDADI–MA Reference Manual

COL–RIBRE–MA–0032–00 Issue 4/A 25/09/98

2.1.5.6 Sammi Application Development Kit (ADK) Version 3.0 31/03/94System Administrator’s Guide

2.1.6 Interface Control Documents

2.1.6.1 MDB Standard Entities and Application Programmer InterfaceCOL–RIBRE–ICD–0069 Issue 4/A 31/3/99




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

8


17/04/9831/03/99

von /of: 492

2.1.6.2 Space Station Manned Base to Columbus Attached Pressurized Module Interface Control Document.SSP 42001 Revision K TBD




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

9


17/04/9831/03/99

von /of: 492

2.2 Reference Documents

The documents specified in this section serve only as reference material.

2.2.1 Specifications

None.

2.2.2 Standards

2.2.2.1 Columbus Software Development Standards,STD 1213 800 000 Issue 5/–, 22/11/91.

2.2.3 Design Documents

None.

2.2.4 Technical Notes

None.

2.2.5 Manuals

None.

2.2.6 Other Documents

None.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

10


17/04/9831/03/99

von /of: 492

CHAPTER 3 :GENERAL DESCRIPTION




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

11


17/04/9831/03/99

von /of: 492

3.1 CGS Functional Overview

CGS is the ’backbone’ assembly providing core or essential services and actually making up most of its func-tionality of the various ground based Facilities within the different Space Programmes (e.g. GSRF, DMS–R,COF, MPLM, NASA). CGS exists in several configurations each targeted at some specific operational environ-ment or user task. Major Facilities currently identified are:

* Software Design and Development Facility (SDDF). Used for design and development (cod-ing, unit test, product–level integration & partial qualification) of flight SW and data.

* Electrical Ground Support Equipment (EGSE). This facility is used for system–level integra-tion, verification and qualification of Flight HW and SW.

* Software, Integration and Test Equipment (SITE). Used for system–level integration, verifi-cation and qualification of Flight SW.

A Facility is made up from CGS software configurations, standard hardware and additional hardware/softwareAdd Ons, e.g. Software Design and Development support services, Ground Test equipment etc. CGS is a genericreference concept, encompassing specific CGS ’Add On’ software and CGS will be extended to establish theFacilities. Each Facility will be different although each follow a logical model.

CGS provides software services as required for the Facilities. These services are needed for the design, develop-ment and integration, test and qualification related activities for the Flight Configuration.

The overall functionality of CGS will support the following functionality:

Design and Development Support for Ground and Flight Systems including:

Columbus Ground System Infrastructure (CGSI) provides the basic service layer to allCGS S/W Applications, supporting Servers (SUN–4), Test Nodes (HP 9000 – 700/800Series) and graphical Workstations (SUN–4) under the UNIX Operating System.

Software Development Environment (SDE) provides standard S/W Life Cycle support:

S/W Requirements Phase Support including Definition and Analysis Support inSADT for S/W Requirements and Definition Support for S/W Interface ControlDocuments,

S/W Architectural / Detailed Design Phase Support including HOOD Methodol-ogy for Application S/W Architectural and Detailed Design and Program DesignLanguage for Application S/W Detailed Design,

S/W Coding / Testing Support including Syntax Editing for Ada and C sourcecode. S/W Compiler Systems and additional S/W Development Tools might beintegrated to through a standard generic Compiler and Tool Interface,

Traceability Support over the S/W Life Cycle including traceability between dif-ferent contractual level (”vertical traceability”) and traceability from requirementsto design on the same level (”horizontal traceability”),

S/W Documentation Handling,

and S/W Configuration Management, based on contractual Configuration Items.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

12


17/04/9831/03/99

von /of: 492

The Software Entity Software (SWES) provides support for Ada Precompilation of SWand Transfer of Onboard SW into the Mission Database (MDB).

The Mission Database Application (MDA) constitutes the set of utilities which supportor enable various activities typically performed during the preparation phase of a check-out / simulation test or mission and provides data entry and reporting, configuration man-agement and support to off-line generation of onboard database/flight image. MDA iscentered around the Mission Database which serves as a central repository for all test /mission–related information.

The Columbus Language System (CLS) comprises several language related softwarecomponents for UCL, HLCL and CPL:

The CLS Editor is the XView based user front–end for editing UCL, HLCL orCPL command sequences and for the specification of SW Commands within theinteractive database environment of MDA,

The UCL Compiler translates automated procedures (APs) and libraries writtenin the User Control Language (UCL) into an intermediate code (I–Code),

The HLCL Interpreter constitutes the interactive commanding interface of differ-ent applications running on various workstations in the ground system. It in-terprets and executes interactive commands and automated command sequenceswritten in the High Level Command Language (HLCL),

The HLCL Command Window is an XView based interactive window interfaceto the HLCL Interpreter.

The Ground Window Definition Utility (GWDU) provides functionality to generatecheckout and simulation orientated ground synoptic displays. These layouts contain ani-mated functional drawings which will be used to display e.g. checkout, simulation, sub-system and payload status information and to read in dedicated commands from thehuman user. This product will be based on the Ground Symbol and Display Standard.

The Flight Window Definition Utility (FWDU) provides functionality to generate flightsynoptic displays. These layouts contain animated functional drawings which will beused to display subsystem and payload status information and to read in dedicated com-mands from the human user. This product will be based on the Flight Symbol and DisplayStandard.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

13


17/04/9831/03/99

von /of: 492

Integration, Test and Qualification Support for Flight Systems:

The Test Setup, Configuration and Verification Software (TSCV) configures a requiredsystem configuration for a Checkout Test / Simulation. It enables the test nodes to be acti-vated for a given test. TSCV implements the generation of a test session in the masterarchive. TSCV further supports the user to identify and control the currently used S/WConfiguration.

The Human Computer Interface (HCI) provides all services related to user input / outputon workstations during execution of a Checkout Test / Simulation Session. It providesdifferent interfaces to the window system and the HCI devices (keyboard,mouse,screen)and includes services for synoptic display update, user help and user guidance throughtest operations. It provides the commanding interface and the message output during on-line test execution.

The Test Execution Software (TES) implements the support for test operations and auto-matic testing / monitoring of the Unit under Test (UUT). It is driven by the test definitionsdone by MDA and the configuration setup by TSCV. It provides a generic data and con-trol interface to the UUT and all services required for realtime enditem data processing.

Data Base Services (DBS) provides low level management and access to checkout testrelated result data items stored in the Test Results Database or files.

Test Evaluation Software (TEV) provides all services to evaluate a.m. data generated andstored during checkout test execution. It provides services for data selection and datapresentation. It further implements the final archiving of test results as well as the selec-tive exporting / importing of parts of the Test Result Database.

Network Software (NWSW) provides low level message based interprocess communica-tion as well as file transfer and directory services in a non NFS environment.

Timing Services Software (TSS) provides the synchronization of local computer clocksin a distributed environment with respect to the actual (local) time. In addition, TSS alsoprovide low level SMT distribution, access and handling.

The Core Simulation Software (CSS) provides support for Simulation Model Develop-ment, Simulation Preparation and Execution / Control of Models.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

14


17/04/9831/03/99

von /of: 492

CHAPTER 4 :INFRASTRUCTURE

INTERFACES




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

15


17/04/9831/03/99

von /of: 492

4.1 Communication Services

4.1.1 Internet Port Number Allocation

Informal Interface Description

An Internet port is a logical communication channel in a host. These ports total 65535 and are accessed by portnumbers. Some of the numbers are reserved by system services such as TELNET, FTP etc. Others are reservedfor applications such as ORACLE/SQL*net.

This section defines the ports reserved for system services, etc.

Formal Interface Description

The following port numbers are reserved:

Service Portnumber/Protocol aliases and comments

System services 0–1023

ingreslock 1524/tcp

orasrv 1526/tcp ORACLE

1259/tcp Reserved for Atherton BackPlane

1259/udp Reserved for Atherton Backplane

rlb 1260/tcp # remote loopback diagnostic

nft 1536/tcp # NS network file transfer

netdist 2106/tcp # update(1m) network distribution service

rfa 4672/tcp # NS remote file access

dc_server 5000/tcp # Teamwork Data Controller Server

lanmgrx.osB 5696/tcp # LAN Manager/X for B.00.00 OfficeShare

grmd 5999/tcp # graphics resource manager

spc 6111/tcp # sub–process control

nfsd 2049/udp # NFS remote file system

CGS Applications 7000/tcp–7999/tcp VICOS Applications

CGS Applications 8000/tcp–8999/tcp CSS Applications

Notes:

# The X10_LI server for each display listens on ports 5800 + display number.

# The X10_MI server for each display listens on ports 5900 + display number.

# The X11 server for each display listens on ports 6000 + display number.

# Do not associate other services with these ports.

# Refer to the X documentation for details.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

16


17/04/9831/03/99

von /of: 492

4.1.2 Commercial Product Versions

CGSI Product Platform Commercial Product Version

CommunicationServices SUN TCP/IP (*)

SUN NFS (*)SUN Ethernet Software (*)

HP TCP/IP (**)HP NFS (**)HP Ethernet Software (**)

(*) Products so marked are an integral part of SunOS

(**) Products so marked are an integral part of HP–UX




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

17


17/04/9831/03/99

von /of: 492

4.2 Operating System Services

4.2.1 Operating System


CGSI provides the Operating System for SUN and HP. FORCE as a third platform is used for the executionof simulation models only.

Sun Platform

The System V option is installed and enabled.

Network Information Services (NIS) are installed and running.

Newsprint software for Postscript printers.

UUCP is installed and configured.

HP Platform


FORCE Platform



CGSI Product Platform Commercial Product Version

OS Services SUN SOLARIS 2.6 incl. Sun recommended patches (Generic_105181–03)

HP 9000/700 HP–UX 10.20 A+ Y2K Patch Bundle




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

18


17/04/9831/03/99

von /of: 492

4.2.2 File System Structure

4.2.2.1 Home Directories for CGS Products

CGSI provides to each CGS product a single home directory as defined in the following subsections.

4.2.2.1.1 Sun Platform

4.2.2.1.1.1 GSAF Home Directory

For CGS and its extensions and add–ons in the frame of GSAF, a global home directory, addressed bymeans of the environment variable

$GSAF_HOME

exists. This directory is created during CGS installation. By default, the pathname

/usr/gsaf

will be used, but this is not mandatory and can be changed during installation.

The directory $GSAF_HOME and associated subdirectories and files will be owned by the user, whois doing the installation of CGS (and its products).

4.2.2.1.1.2 CGS Home Directory

The following home directory is assigned to CGS as a common pool for SW and data:

$GSAF_HOME/cgs

The home directory is addressed by means of the environment variable CGS_HOME. This directorywill be used to store common SW and data as well as general scripts for installation / administrationetc. used by more than one CGS Product.

4.2.2.1.1.3 Product Home Directories

The following home directories are assigned to the lower level CGS Products:

$GSAF_HOME/

where is one of the following:cgsi, sde, mps, mda, gwdu, fwdu, cls, vicos, tscv, hci, tes, dbs, tev, nwsw, tss, css.

The home directory is addressed by means of the environment variable _HOMEwhere is one following:

CGSI, SDE, MDA, GWDU, FWDU, CLS, TSCV, HCI, TES, DBS, TEV, NWSW, TSS, CSS.

Note: The installation of the CGS Product SWES will be done under the directory structure of SDE.

Within CGS scripts, SW etc, the explicit usage of ~username as reference scheme has to be avoidedin any case. All references in scripts, SW etc. shall be based on the environment variables as definedabove.

It is recommended that non–CGS Products (e.g. FES, CMAS etc.) will be installed parallel to the CGSProducts directly under $GSAF_HOME with the same substructure as defined in section 4.2.2.2.

4.2.2.1.2 HP Platform

On each HP platform the GSAF top level directory (as described in section 4.2.2.1.1.1) must be visibleand mounted into the same pathname as for the SUN platform.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

19


17/04/9831/03/99

von /of: 492

The ”..._HOME” variables address the specified directories in the same way as specified for SUN plat-form.

4.2.2.2 Subdirectories for CGS Products

Each product has its subdirectories relative to its home directory for the location of executable images,data, utilities etc. as defined in sections 4.2.2.2.1 to 4.2.2.2.7 etc. CGSI will create these subdirectories.Any extension in order to add another subdirectory in parallel to this level require explicit authorizationby CGS Engineering.

Note: For SDE and SWES, the directory structure already established under $SDE_HOME will be keptwithout any changes!

4.2.2.2.1 Start–Up Scripts

The following directory is provided for Product related start–up scripts:

$_HOME/bin/common

where is one of the products specified in section 4.2.2.1.1.3. Product start–up scriptswill setup the necessary environment for the execution of product SW and then subsequentially callthe target dependant executable image(s) as defined in section 4.2.2.2.

Note: For the external invocation of CGS Product SW always the start–up script under

$_HOME/bin/common

shall be called and not directly the target dependant executable image !

4.2.2.2.2 Executable Images (Platform dependent)

The following directory is provided for Product related executable images:

$_HOME/bin/

where is one of the products specified in section 4.1.2.1.1.3 and is one of thefollowing: sun5, hp_ux8.

4.2.2.2.3 Environment

The following directory is provided for Product related environment setup (e.g. specific login, logout,cshrc):

$_HOME/user_env

where is one of the products specified in section 4.2.2.1.1.3.

4.2.2.2.4 Utilities and Tools (Platform dependent)

The following directory is provided for executables / scripts etc of Product related utilities and tools(e.g. installation / deinstallation of users, product SW etc.):

$_HOME/util/

where is one of the products specified in section 4.1.2.1.1.3 and is one of thefollowing: sun5, hp_ux8.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

20


17/04/9831/03/99

von /of: 492

For the installation of users the following file name syntax shall be used:

install_user

Configuration data files as inputs to these scripts shall be placed under

$_HOME/config.

4.2.2.2.5 Configuration Data

The following directory is provided for static configuration data of a Product (e.g. license files, productversion identification files etc, usually defined by the Product Administrator):

$_HOME/config

where is one of the products specified in section 4.2.2.1.1.3 .

4.2.2.2.6 Runtime Data

The following directory is provided for Product SW generated data files at runtime:

$_HOME/data

where is one of the products specified in section 4.2.2.1.1.3 .

4.2.2.2.7 Libraries

The following directory is provided for Product specific library code including Application Program-mers Interfaces (e.g. Ada, C, SQL etc):

$_HOME/lib/

where is one of the products specified in section 4.2.2.1.1.3 and is one of thefollowing: sun5, hp_ux8

Whenever library code including Application Programmers Interfaces is crossing Product boundaries(i.e. CGS wide libraries), the location shall be:

$CGS_HOME/lib/

instead, where is one of the following: sun5, hp_ux8.

4.2.2.3 Special Checkout related Directories

4.2.2.3.1 Test Node Directory on the HP Test Nodes

Additionally, for each test node (HP platform) one directory in the local filesystem on the HP machinewill be created during CGS installation.

By default, the pathname

/test_node/‘hostname‘

will be used, but this is not mandatory and can be changed during installation.

This directory has to be created with the same ownerships as the directory tree under $GSAF_HOMEon the SUN platform.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

21


17/04/9831/03/99

von /of: 492

This directory will be referenced by the environment variable:

$TN_HOME

on each host (HP and SUN).

Also below this directory, two directories ”archive” and ”replay” have to be created, also owned bythe same user as for $TN_HOME. These directories will be used by the CGS products to store archivefiles produced during a normal session (directory ”archive”) or used for replay purposes (directory ”re-play”).

4.2.2.3.2 Test Node Directories on the SUN Database Server

Additionally for each installed HP test node, a directory in the local filesystem of the SUN DatabaseServer will be created during CGS installation.

The pathname for these directories needs to be exactly the same as for the test nodes (see section4.2.2.3.1).

These directories have to be created with the same ownerships as the directory tree under$GSAF_HOME on the SUN platform.

For all a.m. directories, the corresponding directories of the test nodes need to be mounted (see alsoFigure 4.2.2.3.2–1 below).

/usr/test_node/hostn/usr/test_node/host2/usr/test_node/host1

/usr/test_node/host1 /usr/test_node/host2 /usr/test_node/hostn

DB Server(SUN)

UNIX Mounts

archive archive archive

Test Node 01(HP)

Test Node 02(HP)

Test Node xy(HP)

replay replay replay

Figure 4.2.2.3.2–1 Example of Mounting Test Node Directories on the Database Server.

4.2.2.4 Home Directories For CGS Extensions And Add–Ons

4.2.2.4.1 Special Application Software (SAS)

The CGS product TES is able to start special application Software (SAS).

For all SAS related data (executables, data, config files, results, etc.), CGS provides a global directory

$GSAF_HOME/sas

This directory will be owned by the owner of $GSAF_HOME.

CGS Software expects that SAS executables be stored in a directory




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

22


17/04/9831/03/99

von /of: 492

$GSAF_HOME/sas/bin

such that they can be started from here. Therefore, the executables must either by physically presentin this directory or visible here through UNIX softlinks into other parts of the filesystem, possiblyowned by the user.

It is important that all SASes are executable for CGS, i.e. the corresponding permissions have to beset appropriately.

CGS does not use any other directory structure below $GSAF_HOME/sas, however, it is recom-mended that SASes follow the breakdown given in para. 4.2.2.2.

4.2.2.4.2 Command And Measurement Adaptation Software (CMAS)

The CGS product CSS communicates with Command And Measurement Adaptation Software(CMAS) to facilitate hardware in the loop testing.

For all CMAS related data (executables, data, config files, results, etc.), CGS provides a global direc-tory

$GSAF_HOME/cmas


CGS Software expects that CMAS executables be stored in a directory

$GSAF_HOME/cmas/bin

such that they can be started from here. Therefore, the executable(s) must either by physically presentin this directory or visible here through UNIX softlinks into other parts of the filesystem, possiblyowned by the user.

It is important that all CMASes are executable for CGS, i.e. the corresponding permissions have to beset appropriately.

CGS does not use any other directory structure below $GSAF_HOME/cmas, however, it is recom-mended that CMASes follow the breakdown given in para. 4.2.2.2.

4.2.2.4.3 Mission Database Support Software (MDB_SS)

The CGS product MDA provides the capability for Mission Database Support Software to facilitatemission specific database operations.

For all MDB_SS related data (executables, data, config files, results, etc.), CGS provides a global di-rectory

$GSAF_HOME/mdb_ss


CGS Software expects that MDB_SS executables be stored in a directory

$GSAF_HOME/mdb_ss/bin

such that they can be started from here. Therefore, the executable(s) must either by physically presentin this directory or visible here through UNIX softlinks into other parts of the filesystem, possiblyowned by the user.

It is important that all MDB_SSes are executable for CGS, i.e. the corresponding permissions have tobe set appropriately.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

23


17/04/9831/03/99

von /of: 492

CGS does not use any other directory structure below $GSAF_HOME/mdb_ss, however, it is recom-mended that MDB_SSes follow the breakdown given in para. 4.2.2.2.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

24


17/04/9831/03/99

von /of: 492

4.2.3 Common User Environment Files


This section lists the script files which are used to set the environment of all CGS users.

The user environment files described in these sections are C–shell script files.

Through the use of the login and cshrc files CGSI initialises the CGS user environment for a CGS user on login.The cshrc file is also executed for each subsequent shell that is invoked. CGSI uses the logout script files to tidyup a user session on logout.

After establishing a common environment for all CGS users these script files provide the facility for a productto provide further, product specific, tailoring of the user environment by executing the product supplied scripts.

Finally the script files provide the facility for an individual CGS User to carry out his or her own individualenvironment tailoring through the use of user supplied script files.


The CGSI provided central scripts for the supported target platforms, as defined in section 4.2.3.1, are implem-ented as target–independant shell scripts. Central scripts are provided for login, cshrc and logout.




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

25


17/04/9831/03/99

von /of: 492

4.2.3.1 Central Scripts

4.2.3.1.1 Central ”login” Script

###################################################################### # Product: CGSI CI–Number: 1216471## Function: Central CGSI login file. Will be called by the users’ local .login script.######################################################################

unsetenv CGS_ERRORset DISPLAY_MOTD = $CGSI_HOME/bin/common/display_motdumask 022 switch ( ‘uname –s‘)case ”SunOS”:

# Set terminal characteristics for remote terminals:set noglobeval ‘tset –Q –s –m ’dialup:?vt100’ –m ’network:?vt100’ –m ’su:?vt100’‘unset noglobset term=$TERM

# Set up cd pathset cdpath = (.. ~ )

# Skip remaining setup if not an interactive shellif ($?USER == 0 || $?prompt == 0) exit

# Set mail characteristicsset mail = /var/mail/$userbiff y

# Set helpful environment variablessetenv MORE ’–c’

breaksw

case ”HP–UX”:################################################################### Set terminal characteristics for remote terminals:##################################################################eval ‘tset –s –Q –m ’:vt100’‘stty erase ”^H” kill ”^U” intr ”^C” eof ”^D” susp ”^Z” hupcl ixon ixoff tostop tabs

################################################################### Set up the shell environment##################################################################setenv TERM sunset noclobber

breaksw default: setenv CGS_ERROR ”Unsupported Architecture”endsw

###################################################################### Display any ”message of the day”##################################################################### if (–e $DISPLAY_MOTD) then $DISPLAY_MOTDendifunset DISPLAY_MOTD




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

26


17/04/9831/03/99

von /of: 492

###################################################################### Source the SDE’s ”login” file#####################################################################

if (–e $SDE_HOME/user_env/login) then source $SDE_HOME/user_env/loginendif




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

27


17/04/9831/03/99

von /of: 492

4.2.3.1.2 Central ”cshrc” Script

################################################################################# # Product: CGSI CI–Number: 1216471## Date: 22.02.96 Version: 4.3## Name: Cshrc Type: Cshell script## Authors: P. Athmann, J. Hoyng, A. Ringleb, U. Hohnhorst## Function: Central CGSI cshrc file. Will be called by the users’ # local .cshrc script.# Change History: # PIRN 8027 1/A (08.03.99): MD# –– Added SWES_HOME# PIRN 3094 1/B (22.02.96):# – New architecture sun5,# – new environment variables CMAS_HOME, SAS_HOME# – included $CGSI_HOME/oracle/.cshrc## PIRN 3086 1/A (10.11.95):# – Execute dbs_cshrc file# – Define TN_HOME variable## PIRN 3083 1/C (10.11.95)# – New default for GSAF_HOME## COL–RIBRE–CGS–IRN–5017# GSRF–RIBRE–CGS–SPR–2945# – TN_HOME problems fixed#################################################################################

umask 022unsetenv CGS_ERROR set architecture = ‘uname –s‘switch ($architecture)case ”SunOS”:

set hardpathssetenv OPENWINHOME /usr/openwinsetenv LD_LIBRARY_PATH $OPENWINHOME/libsetenv XAPPLRESDIR $OPENWINHOME/lib/app–defaultsset path = ( . \

~/bin \$OPENWINHOME/bin \/usr/sbin \/usr/bin \/usr/ucb \/usr/ccs/bin \/usr/local/bin )

setenv REMOTE_SHELL rsh set os_release = ‘uname –r‘ if ( $os_release =~ 4.* ) then

setenv CGS_ARCH sun4 else if ( $os_release =~ 5.* ) then

setenv CGS_ARCH sun5else

setenv CGS_ERROR ”Unsupported Architecture”endif




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

28


17/04/9831/03/99

von /of: 492

unset os_releasebreaksw

case ”HP–UX”:set path = (. \

~/bin \/usr/sbin \/usr/bin \/opt/ansic/bin \/usr/ccs/bin \/usr/contrib/bin \/usr/bin/X11 \/usr/contrib/bin/X11 )

alias rsh remshsetenv REMOTE_SHELL remshsetenv CGS_ARCH hp_ux8breaksw

default: setenv CGS_ERROR ”Unsupported Architecture $architecture”endsw unset architecture

# exit the script, if CGS_ERROR is setif ($?CGS_ERROR ) then

echo ” ”echo ” *** Error in CGSI Cshrc script ***”echo $CGS_ERRORecho ” ”echo ”exit with status 1”exit 1

endif ################################################################################# Define CGS variables################################################################################ setenv LOGNAME ‘whoami‘setenv USER ‘whoami‘ ############################################################################## Define product home environment variables## Note: Default Pathname will be /usr/gsaf, but can be# ===== changed below during CGSI Installation !#############################################################################

if ($?GSAF_HOME) then:else

setenv GSAF_HOME /usr/gsafendif if (–d ”$GSAF_HOME”) then

setenv CGS_HOME $GSAF_HOME/cgssetenv CGSI_HOME $GSAF_HOME/cgsisetenv SDE_HOME $GSAF_HOME/sdesetenv SWES_HOME $SDE_HOME/swessetenv MDA_HOME $GSAF_HOME/mdasetenv GWDU_HOME $GSAF_HOME/gwdusetenv FWDU_HOME $GSAF_HOME/fwdusetenv CLS_HOME $GSAF_HOME/clssetenv TSCV_HOME $GSAF_HOME/tscv




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

29


17/04/9831/03/99

von /of: 492

setenv HCI_HOME $GSAF_HOME/hcisetenv TES_HOME $GSAF_HOME/tessetenv DBS_HOME $GSAF_HOME/dbssetenv TEV_HOME $GSAF_HOME/tevsetenv NWSW_HOME $GSAF_HOME/nwswsetenv TSS_HOME $GSAF_HOME/tsssetenv CSS_HOME $GSAF_HOME/csssetenv CMAS_HOME $GSAF_HOME/cmassetenv SAS_HOME $GSAF_HOME/sas

elseecho ” ”echo ” Error in CGSI Cshrc script: ”echo ” Directory $GSAF_HOME doesn’t exist”echo ” Environment variables could not be set”

echo ” ”endif

############################################################################## setup Oracle environment############################################################################# setenv ORACLE_BASE ‘(cd $ORACLE_HOME/../.. && pwd)‘setenv ORACLE_HOME ORACLE_HOME # MODIFY value during installationsetenv ORACLE_SID oracle7 # MODIFY value during installation

if ( –e $ORACLE_HOME ) then if ($?LD_LIBRARY_PATH == 0) then setenv LD_LIBRARY_PATH $ORACLE_HOME/lib else switch ($LD_LIBRARY_PATH) case *$ORACLE_HOME/lib* : breaksw case ”” : setenv LD_LIBRARY_PATH $ORACLE_HOME/lib breaksw default : setenv LD_LIBRARY_PATH $ORACLE_HOME/lib:${LD_LIBRARY_PATH} breaksw endsw endif

switch ($PATH) case *$ORACLE_HOME/bin* : breaksw case *[:] : setenv PATH ${PATH}$ORACLE_HOME/bin: breaksw case ”” : setenv PATH $ORACLE_HOME/bin breaksw default : setenv PATH ${PATH}:$ORACLE_HOME/bin breaksw endsw

setenv ORA_NLS33 $ORACLE_HOME/ocommon/nls/admin/datad2kendif

############################################################################## setup DBS environment#############################################################################

if ( –e $DBS_HOME/user_env/dbs_cshrc ) then




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

30


17/04/9831/03/99

von /of: 492

source $DBS_HOME/user_env/dbs_cshrcendif

############################################################################## Define Test Node (dependant) home environment variable## Note: Default Pathname will be /usr/test_node, but will be changed below# ===== during CGSI Installation !#############################################################################setenv TN_HOME /usr/test_node/‘hostname‘

############################################################################## Set helpful variables#############################################################################set filecset ignoreeofset history=50 ############################################################################ Source the SDE’s ”cshrc” file########################################################################### if (–e $SDE_HOME/user_env/cshrc) then source $SDE_HOME/user_env/cshrcendif




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

31


17/04/9831/03/99

von /of: 492

4.2.3.1.3 Central ”logout” Script

######################################################################################## # Product: CGSI CI–Number: 1216471## Date: 06.02.95 Version: 1.0## Name: Logout Type: Cshell script## Authors: P. Athmann, J. Hoyng, A. Ringleb, U. Hohnhorst## Function: Central CGSI logout file. Will be called by the users’ local .logoutscript.######################################################################################## clear ############################################################################ Source the SDE’s ”logout” file###########################################################################

if (–e $SDE_HOME/user_env/logout) then source $SDE_HOME/user_env/logoutendif

echo ”‘hostname‘: ‘whoami‘ logged out at ‘date‘”echo ”Goodbye\!”




Überarbtg./ Rev.:

Seite/Page:

Datum/Date:

Datum/Date:

32


17/04/9831/03/99

von /of: 492

4.3 Relational Database Management System


This chapter defines the interface provided by CGSI to the CGS products for access to and use of the RDBMSservices.

A general section details the basic interface as specificed by the commercial product documentation. This isfollowed by individal subsections with the specific details for each of the CGS products.


4.3.1 Functional Interface

4.3.1.1 General

The CGSI RDBMS services are implemented by means of the ORACLE database management system.

See chapter 4.3.3 for details on product version.

4.3.2 Database Installation and Configuration

All instances of the CGSI RDBMS Services are installed and configured in accordance with the following sub-sections.

For each of the predefined objects names identified CGS product–specific defintions are described in the ap-propriate product subsection.

Date post:	18-Apr-2020
Category:	Documents
Upload:	others
View:	9 times
Download:	0 times