Titel: MDA Administration Manual€¦ · vi COL–RIBRE–MA–0018–00 4 01.09.1997 A 08.10.1998 ii Dok.Nr./Doc. No.: Ausgabe Überarbtg. Seite Datum von /Issue: /Rev.: /Page: /Date:

Dokument Typ:

Titel:

Lieferbedingungs-Nr.:

Produktgruppe:

Schlagwörter:

Klassifikations Nr.:

Konfigurationsteil-Nr.:

Produktklassifizierungs-Nr.:

Freigabe Ordnungs-Nr.:

Bearbeitet:

Geprüft:

Abteilung: Firma:

Document Type:

Title:

DRL/DRD No.:

Product Group:

Headings:

Classification No.:

Configuration Item No.:

Classifying Product Code:

Release Order No.:

Prepared by:

Agreed by:

Department: Company:Genehmigt:Approved by:

Abteilung: Firma:Department: Company:

Genehmigt:Approved by:



Manual

MDA Administration Manual

N/A

MDA – Team RIO 62 DASA/RI BRE

PR 1216401

N/A

N/A

1216401

8–QABA

N/A

A. Werkman RIO 62 DASA/RIBRE

R. Zimmermann RIO 62 DASA/RIBRE

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998

Dok.Nr./Doc. No.:AusgabeÜberarbtg. Datum

/Issue:/Rev.: /Date:

Datum/Date:

Raumfahrt-Infrastruktur

��

FORM 0672.0V.7 Daimler–Benz Aerospace AG, D–28199 Bremen – All Rights Reserved – Copyright per DIN 34

vi

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998ii

Dok.Nr./Doc. No.:AusgabeÜberarbtg.Seite

Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


DOCUMENT CHANGE RECORD

Issue / Rev. Issue date Pages / Section affected

Remarks

1/– 11.07.94 all initial version

2/– 30.11.94 3.1.3 Update section Create mdb_installation rangesInsert section Data–API installationUpdate table of contents

2/B 18.07.95 3.1.3 Update Oracle 7 Installation

3/– 01.12.95 all new document number

3/A 09.09.96 3.1.3.3, 3.1.4, 3.2

3.1.43.1.53.1.5.2

Change of environment variable and administrationscriptsNew section MDB version upgrade conceptTar file options changedNew section copying the DADIMA export files

3/B 04.04.97 all Solaris Port update

4/– 01.09.97 3 update section with regard to Tk/Tcl library installationand related changes in the .cshrc file.

4/A 08.10.98 all MDA V4.2 related changes

vi

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998iii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


1 INTRODUCTION 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Identification and Scope 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Purpose 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 APPLICABLE AND REFERENCE DOCUMENTS 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Applicable Documents 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Reference Documents 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 MDA INSTALLATION, DEINSTALLATION, AND ADMINISTRATION 3. . . . . . . . . . . 3.1 MDA Installation 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.1 Installation conventions and prerequisites 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1.1 Procedure conventions 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.1.2 System Administrator 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.2 Installation Environment 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2.1 Hardware 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2.2 Software 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2.3 Necessary unix accounts 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.2.4 Setting up Oracle Configuration 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.2.4.1 Rollback Segments and Tablespaces 10. . . . . . . . . . . . . . . . . . . 3.1.2.4.2 MDA Installation and Demonstration Users 11. . . . . . . . . . . . . . 3.1.2.4.3 Oracle Configuration 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.3 MDB Version Upgrade Concept 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.3.1 MDB Version Upgrade 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.3.2 MDB Version Upgrade with Change of the MDB Instance 16. . . . . . . . . . .

3.1.4 Loading of the MDA tape 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.5 Installation of software 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.6 MDB Instance (ESA_TRAINING) 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.6.1 SID Range Tool Installation 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.6.2 Define MDB Instances using the SID Range Tool 19. . . . . . . . . . . . . . . . . . 3.1.6.3 SID Range Tool Deinstallation 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.7 Copying the DADI–MA Export Files 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.8 Install MDB 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.9 Initialize MDB 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.10 Load Demonstration or other Data 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.11 Install Users 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.12 Upgrade old MDB Data 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.13 Certification Test Procedure 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.13.1 Start of I_MDB GUI 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.13.2 Navigate in I_MDB GUI 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.13.3 Check End Item Data 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.13.4 Check Print Report Capability 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.13.5 Check Consistency Checker Capability 28. . . . . . . . . . . . . . . . . . . . . . . . . . 3.1.13.6 Run down 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.2 MDA Deinstallation 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 Save the Contents of the MDB Database 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.2 Deinstall MDB Users 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vi

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998iv


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.2.3 Deinstall the MDB 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Administration 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A ACRONYMS A-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B DEFINITIONS B-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vi

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998v


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


Figure 1.MDB Version Export and Import 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

vi

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998vi


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


This page is intentionally left blank.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.19981


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


1 INTRODUCTION

1.1 IDENTIFICATION AND SCOPE

This document is the Administration part of the Users and Operations Manual for MDA.

1.2 PURPOSE

With the administration part of the User’s and Operations Manual the purchaser of MDA will be able to in-stall the software and all of its necessary environment on a Sun Sparc server machine. The main part willcover the installation and administration of the MDA software itself.

If you install only the MDA software on a present Solaris and Oracle installation, make a complete backupbefore you start.

The installation of the MDA software is straightforward and do not have any different cases.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.19982


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


2 APPLICABLE AND REFERENCE DOCUMENTS

Document No. Issue / Revision

Document Title

___________________________________________________________________________

2.1 APPLICABLE DOCUMENTS

2.1.1 SPE 1216 401 002 2/C 05.11.1993

MDA Requirements Specification

2.1.2 COL–RIBRE–ICD 4/– 04.08.97

System to MDA Interfaces

2.2 REFERENCE DOCUMENTS

2.2.1 ADD 1216 401 002 2/A 18.06.1993

MDA Architectural Design Document

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.19983


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3 MDA INSTALLATION, DEINSTALLATION, AND ADMINISTRATION

This chapter describes how to install the MDA software into its operating environment, including the de-tailed manual steps to be followed, how to deinstall the software and the administration of the MDA software.There are a few prerequisites to both the system administrator who installs the software and to the systemenvironment where the software is installed. This prerequisites are described in the first section of thischapter. The second section describes the preparation of the operating environment for the installation, thethird the installation of the software from the tape, the fourth describes the initialisation of the system. Thefinal three sections describe the deinstallation and the administration of the MDA software and a certificationtest procedure, which checks whether the installation was successful.

3.1 MDA I NSTALLATION

Check whether all you need is delivered. That is one 150 MB tape with the MDA distribution, the releasenotes, and this users and operations manual. The following short overview will sketch all actions to be per-formed to complete the installation:

• Installation Conventions and PrerequisitesA short introduction for what is expected from the administrator who installes the softwareand some hints on the understanding of the installation procedure

• Installation EnvironmentOne section describes the installation environment. This includes all preconditions of thenecessary hardware. Also the environment has to be set up as required. Moreover, the MPSadministration users have to be created for UNIX and Oracle.

• Loading of the MDA distribution tape

• Creation of the mdb sid rangesThe necessary ranges for the installation are:

Oracle User Oracle Export User Installation Name Installation Range Necessary for

MPS MPS_EXPORT ESA_TRAINING 2 – 100 000 ESA Demo andTraining, no op-erational use!

• Initialise mdbThe above mentioned instance has to be installed and initialized by scripts delivered byMDA.

• Install Demonstration and training UsersThe necessary test users are:

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.19984


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


User Name Necessary for

mdaaiv Demo / Training

mdatest Demo / Training

sidadmin SID Range Tool

• Certification Test Procedure

3.1.1 Installation conventions and prerequisites

3.1.1.1 Procedure conventions

The installation script will maintain the following conventions:

Every machine interaction will be shown in a gray box, as depicted in the following paragraph. Machineprompts and messages will be kept in plain courier font:

Machine prompt>

Inputs of the user will be in bold courier font:

Machine prompt> User‘s input<Return>

Generic entries which have to be filled out or replaced by the user will be in bold italic courier font:

disk description

Comments within the machine interaction boxes, which will not be present on the screen, will be in italiccourier font:

(Lots of output here)

If there is a lot of output between two user commands, and that output is not important for understandingthe procedure, it is suppressed and replaced by three dots in a column, occasionally with a comment aboutthe time it will last or some errors which could be ignored.

.

. (Ignore error messages)

.

If OpenWindows is started after login as a user, the machine interaction cannot be described as a plain se-quence of commands. Instead the interaction will be continued in the shelltool window of the OpenWindowsdesktop. To logout simply exit from OpenWindows.

Always before the user has to interact with the system, all actions to be performed will be described in detail.

Within some programmes, two different kinds of user input are used:

· enterThe keyboard input has to be finished with the <Return> –key.

· typeThe keyboard input (a single keystroke) is processed as soon as you type a character.

Single keys with a special meaning are surrounded by the up– and down–sign (< and >, respectively). Specialkeys, which have to be pressed simultaneously, will be included in one pair of up– and down–signs concat-

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.19985


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


enated with a hyphen. Simultaneously means, that the keys have to be pressed in the sequence they appearfrom left to right, but that every key has to be kept down during the complete operation.

Special keys which have to be pressed in a sequence will be included in a couple of up– and down–signs eachand then be concatenated by hyphens externally. Sequentially means the key has to be pushed down and thenreleased before the next key is pressed down. Examples:

Keys with a special meaning:<Return><Tab>

Keys to be pressed simultaneously<Shift–Return><Control–Backspace>

Keys to be pressed sequentially<Escape>–<a><Pause>–<o>–<”>

3.1.1.2 System Administrator

The administrator who installs MDA is expected to have a basic knowledge of UNIX, i. e. commands, shells,editors, etc. As far as the software is installed from scratch, there cannot be done any harm to the system incase of an error, besides of the loss of time. If you would like to modify an existing system already set up,be sure to have a most recent complete backup of your system, because acting as root may cause damage ofthe installed system in case of an error, even if taking the most rigid precaution.

The administrator needs access to the root account to perform some of the necessary actions. Some UNIXusers have to be created. If there are standard procedures for that, they shall be used. Otherwise, look in theSunOS manuals how to create user accounts in a Sun networked environment. The environment for the usershave to be adapted to the needs of MDA. That is done by introducing some alias and setenv commends inthe .cshrc and .login files. There will be a listing of the suggested changes. If some of the suggestions areallready implemented in your .cshrc or .login files, ignore them. If in doubt, the SunOS system and networkadministrator shall be asked. In case of a conflict between following suggestions and the allready installedenvironment, the MDA suggestions shall be preferred, because otherwise the software will not work proper-ly.

3.1.2 Installation Environment

To install the MDA delivery the following preconditions have to be met:

3.1.2.1 Hardware

· Sun Sparc workstation with 40 MB RAM as a minimum and a 17” b&w display. The PROM–version must be 2.0 or greater and the keyboard of type 5 or greater.

· 600 MB free disk space

· 1/4” GIC–150 tape–station

· Access to a laserwriter over the network or directly connected to the workstation

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.19986


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.2.2 Software

· Sun Solaris 2.6

· Oracle V7.3.4.2

3.1.2.3 Necessary unix accounts

Now we describe what users have to be created for the current installation. Add the following groups:

• dba and

• mda

Add the following account

• mps

• mdatest

• mdaaiv

• sidadmin:

Create a .cshrc and a .login file for the users mps, mdatest, mdaaiv and sidadmin and place them in the homedirectories of each of them. These .cshrc and .login files should contain the following lines:

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.19987


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


This is the cshrc add–on for an MDA user.

setenv OPENWINHOME /usr/openwinsetenv LD_LIBRARY_PATH $OPENWINHOME/libsetenv XAPPLRESDIR $OPENWINHOME/lib/app–defaults

setenv MDA_HOME Your_MDA_Home_Directory (depending on the installation)

setenv GSAF_HOME_HOME $MDA_HOME/..

setenv ORACLE_HOME Your_Oracle_Home_Directorysetenv ORACLE_BASE our_Oracle_Base_Directorysetenv ORACLE_SID Your_Oracle_SIDYsetenv LD_LIBRARY_PATH $ORACLE_HOME/lib:${LD_LIBRARY_PATH}setenv TNS_ADMIN $ORACLE_HOME/network/admin

setenv BDE_ERROR_LIMIT 1000alias bde_print $MDA_HOME/bin/common/print

setenv CGS_ARCH sun5

setenv TWO_TASK Your_actual_value

if ( $PATH !~ *$MDA_HOME/bin/common* ) thenset path = ($path $MDA_HOME/bin/common)endifif ( $PATH !~ *$MDA_HOME/bin/sun5/MDATCL/bin* ) thenset path = ($path $MDA_HOME/bin/sun5/MDATCL/bin)endif

if ( $PATH !~ *$ORACLE_HOME/bin* ) thenset path = ($ORACLE_HOME/bin $path)endif

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.19988


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


This is the login add–on for an MDA user

# @(#)local.login 1.3 93/09/15 SMIstty –istrip

################################################################################### Set up the search path##################################################################################

set path = (.\ ~\ ~/bin\ $OPENWINHOME/bin\ $OPENWINHOME/bin/xview\ /usr/5bin\ /usr/ucb\ /usr/bin\ /bin \ $path)

################################################################################### Set up cd path##################################################################################set cdpath = (.. ~ )

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

if (”‘tty‘” != ”/dev/console” || $TERM != ”sun”) exit/usr/openwin/bin/openwinlogout

3.1.2.4 Setting up Oracle Configuration

Oracle is user customizable. Depending on the amont of data and user specific needs it is necessary to setup an oracle configuration. For this purpose tablespaces, rollback segments and specific configuration para-meters have to be defined.

ORACLE has its own user administration, and each user, who would like to use the database and MDA hasto have an ORACLE account besides of a UNIX account. If the users are not present in oracle, you have tocreate them. If the users are present but do not have the right privileges and the correct table spaces, you canfollow the same procedure as described below. You can verify whether the users are there, if you use the MDAscript list_mdb_users, which is located in $MDA_HOME/config/oracle_env. The users need the connect andresource privileges. Anyway it does not hurt to perform the creation of the users. This is done by hand usingsqlplus.

You can create an ORACLE user from any account because you have to log in internally as the ORACLEadministrator system. At first you have to enter ORACLE by calling sqlplus. Then you create the user by

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.19989


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


granting access types (here connect and resource) to the user. You have to put the word ’ops$’ in front of theusername. This means that the user gets the auto login capability of ORACLE. If a UNIX user starts tu useORACLE and logs in to the DBMS, and there is an ORACLE account named ’ops$UserName’, the authenti-fication of ORACLE is switched off and the user gets access to ORACLE without a password. This is abso-lutely necessary for the MDA purposes. After the user is created, you have to assign the default tablespaceTS_MPS.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199810


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.2.4.1 Rollback Segments and Tablespaces

Login: oracle7<Return>Password: YourPassword <Return>machine# sqlplus<Return>Enter user–name: system<Return>Enter password: YourPassword <Return>

SQL> alter tablespace RBS add datafile ’ YourDatabaseDirectory /dbs/RBS_FILE2’ size 150M;

SQL> alter tablespace SYSTEM add datafile ’YourDatabaseDirectory /dbs/SYSTEM_FILE2’ size 100M;

sql> alter rollback segment rbs01 offline;sql> alter rollback segment rbs02 offline;sql> drop rollback segment rbs01;sql> drop rollback segment rbs02;

sql> create public rollback segment RS storage (optimal 1500K next 250k minextents 5);SQL> alter rollback segment RS online;

sql> create public rollback segment RS_LARGE tablespace rbs storage(optimal 2750K next 550K minextents 5);sql> create public rollback segment R01 tablespace rbs storage (optimal 1500K next 250k minextents 5);SQL> create public rollback segment R02 tablespace rbs storage (optimal 1500K next 250k minextents 5);SQL> create public rollback segment R03 tablespace rbs storage (optimal 1500K next 250k minextents 5);

SQL> alter rollback segment RS_LARGE online;SQL> alter rollback segment R01 online;SQL> alter rollback segment R02 online;SQL> alter rollback segment R03 online;

SQL> create tablespace TS_MPS datafile ’ YourDatabaseDirectory /dbs/TS_MPS’<Return> 2 size 100M default storage (<Return> 3 initial 5K next 5K minextents 1 maxextents 99<Return> 4 pctincrease 50) online;<Return>

Tablespace createdSQL> alter tablespace TEMP 2 add datafile ’ YourDatabaseDirectory /dbs/TEMP’<Return> size 50M;

SQL> quit<Return>machine#

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199811


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.2.4.2 MDA Installation and Demonstration Users

machine# sqlplus<Return>Enter user–name: system<Return>Enter password: YourPassword <Return>

SQL> grant connect, resource, create sequence, create trigger to mps identified bymps;<Return>SQL> alter user mps default tablespace ts_mps temporary tablespace temp;<Return>SQL> alter user mps quota unlimited on TS_MPS;<Return>

SQL> grant connect, resource to mps_export identified by mps_export;<Return>SQL> alter user mps_export default tablespace ts_mps temporary tablespacetemp;<Return>SQL> alter user mps_export quota unlimited on TS_MPS;<Return>

SQL> grant connect, resource to ops$sidadmin identified by sidadmin;<Return>SQL> alter user ops$sidadmin default tablespace ts_mps temporary tablespacetemp;<Return>

SQL> grant connect to ops$mdatest identified by mdatest;<Return>SQL> alter user ops$mdatest default tablespace ts_mps temporary tablespacetemp;<Return>

SQL> grant connect to ops$mdaaiv identified by mdaaiv;<Return>SQL> alter user ops$mdaaiv default tablespace ts_mps temporary tablespacetemp;<Return>

SQL> exit<Return>

machine# exit<Return>

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199812


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.2.4.3 Oracle Configuration

Finally, you have to verify whether the ORACLE initialisation in the dbs subdirectory is correct for MDAneeds. The information is included in the file initoracle7.ora in the directory ~oracle7/dbs . Thecontents should be as follows:

# $Header: initx.orc 7001300.3 93/06/16 12:28:26 mkrishna Osd<unix> $ Copyr (c)1992 Oracle# include database configuration parametersifile = your_directory /oracle7/dbs/configoracle7.ora

rollback_segments = (RS, RS_LARGE, R01, R02, R03)

# tuning parameters

db_files = 20#db_file_multiblock_read_count = 8 # SMALL db_file_multiblock_read_count = 16 # MEDIUM # db_file_multiblock_read_count = 32 # LARGE

#db_block_buffers = 200 # SMALL db_block_buffers = 550 # MEDIUM # db_block_buffers = 3200 # LARGE

#shared_pool_size = 3500000 # SMALLshared_pool_size = 6000000 # MEDIUM# shared_pool_size = 9000000 # LARGE

log_checkpoint_interval = 10000

processes = 50 # SMALL #processes = 100 # MEDIUM # processes = 200 # LARGE

# dml_locks = 100 # SMALL dml_locks = 200 # MEDIUM# dml_locks = 500 # LARGE

#log_buffer = 8192 # SMALLlog_buffer = 32768 # MEDIUM# log_buffer = 163840 # LARGE

#sequence_cache_entries = 10 # SMALL sequence_cache_entries = 30 # MEDIUM # sequence_cache_entries = 100 # LARGE

#sequence_cache_hash_buckets = 10 # SMALL sequence_cache_hash_buckets = 23 # MEDIUM # sequence_cache_hash_buckets = 89 # LARGE

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199813


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


# audit_trail = true # if you want auditing# timed_statistics = true # if you want timed statisticsmax_dump_file_size = 10240 # limit trace file size to 5 Meg each # log_archive_start = true # if you want automatic archiving# mts_dispatchers=”ipc,1”# mts_max_dispatchers=10# mts_servers=1# mts_max_servers=10# mts_service=oracle713# mts_listener_address=”(ADDRESS=(PROTOCOL=ipc)(KEY=oracle713))”

OS_AUTHENT_PREFIX = ”OPS$” # required by MDAREMOTE_OS_AUTHENT = TRUE # required by MDA

open_cursors = 255 # required by MDAdml_locks = 2000 # required by MDAenqueue_resources = 4020 # required by MDADB_BLOCK_BUFFERS=1000 # required by MDA

You can change the contents with your favorite editor, e. g. vi. After that shutdown and restart oracle to takethe changes in effect.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199814


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.3 MDB Version Upgrade Concept

MDA also supports a full data Upgrade. This means that all data, like system trees, user trees, end items, etc.may be reused if an update of the MDB versions has to be done. A MDB version upgrade is a change of thedata dictionary structure, e.g. definition of new end item types, aggregates, tool invocation, etc.

The MDB version export and import has always to be performed for one and the same MDB instance. Theexported MDB version is stored on the file system.

��

��

��

��

��

Figure 1.MDB Version Export and Import

An explanation about the SID range concept is included in the MDA Introduction Manual.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199815


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.3.1 MDB Version Upgrade

During the definition phase of end item types for a specific project, the MDB version will change quite often.When the user has started to insert system trees, user trees or end items into the MDB he wishes to find eitherall or at least an actual part of the data in the MDB after a MDB version upgrade.

MDA supports a full data Upgrade, a selective data upgrade is not yet supported. A full data upgrade means,that all data like system trees, user trees, end items, etc. may be reused if an update of the MDB version hasto be done. A MDB version upgrade is a change of the data dictionary structure, e.g. definition of new enditem types, aggregates, tool invocation, etc.

The Upgrade function ensures that all data being contents of the old MDB version are available in the newMDB version after the upgrade if they are compatible with the new Data Dictionary structure.

To perform a full MDB version data upgrade is necessary that the MDB Instance Name and SID Range hasnot been changed.

The following steps have to be executed for a MDB version upgrade:

1. Create the new MDB version Data Dictionary with the DADIMA Tool

2. Export the definitions performed with the DADIMA Tool

3. Copy DADIMA export files to the MDA installation directory

4. Deinstall all MDA/MDB users except the MDB owner(script deinstall_user or deinstall_all_users )

5. Export the MDB contents

(script export_mdb )

6. Deinstall the MDB

(script deinstall_mdb )

7. Install new MDB version(script install_mdb )

8. Initialize new MDB version

(script initialize_mdb )

9. Import saved (exported) MDB contents

(script import_mdb )

10. Install the MDB users(script install_user )

Steps 1 to 3, which is the Data Dictionary structure creation, will be performed by the data structure supplieror it may be executed by your own.

It is essential to execute the upgrade in the above listed sequence. If step 5. would be done prior step 4., itcould happen that a user continues I_MDB definitions when the export is running. If step 10. would be doneprior to step 9., it could happen that a user makes I_MDB definitions prior the import has been executed. Thislead to a SID conflict which prevents a MDB version import.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199816


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.3.2 MDB Version Upgrade with Change of the MDB Instance

When a SID–range is more or less completely ”consumed”, there is only one way to expand the range: Create a new MDB instance. Thus an upgrade of the MDB version might be correlated with a change of the instance.

The MDB version upgrade with change of the MDB instance is separated into two single steps:

1. Perform the MDB version upgrade

2. Change the MDB instance

It has to be ensured that the installation of MDB users is done last. In detail the following activities must becarried out:

The sequence of performing a full MDB version data upgrade is based on a MDB instance that has not beenchanged, which relates to a unique SIDs and an unchanged SID Range. The following steps have to be ex-ecuted for a MDB version upgrade:

1. Create the new MDB version Data Dictionary with the DADIMA Tool

2. Export the definitions performed with the DADIMA Tool

3. Copy DADIMA export files to the MDA installation directory

4. Deinstall all MDA/MDB users except the MDB owner

5. Export the MDB contents

6. Deinstall the MDB

7. Install new MDB version

8. Initialize new MDB version

9. Import saved (exported) MDB contents

10. Generate a new MDB instance with the SID Range Tool

11. Execute a special script ”Change MDB instance” (not yet implemented) which makesthe new instance and SID range active.

12. Install the MDB users

It is essential to execute the MDB version upgrade and change of MDB instance in the above listed order.The MDB version upgrade and the SID range upgrade via MDB instance change must be separated. TheRe–installation of MDB users has to be the last step to ensure SID uniqueness.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199817


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.4 Loading of the MDA tape

The delivery comprises one tape with one tar file on it:

· MDA executables and test data delivery

All the other software is either already installed at the receiving site or has to be provided by the customer.

To install the MDA delivery tape, login as mps and mount the tape on the tape drive. Then enter the followingsequence of commands. After the tar commands, a sequence of files is loaded from tape. The associated di-rectories are created by the tar command.

login: mpspassword: YourPassword <<Return>.. (openWindows is started). (Within a shelltool window enter:) machine% tar –xvfp Your_device_name <Return>.. (all the MDA files are copied into the current directory).machine%

After that, remove the tape from the tape drive. Now the MDA software components were loaded.

3.1.5 Installation of software

The install_mda scripts makes use of the environment variable GSAF_HOME, which is a standard CGS vari-able pointing to the root directory of $MDA_HOME.

login: mpspassword: YourPassword <<Return>

machine% cd $MDA_HOME/util/commonmachine% setenv GSAF_HOME $MDA_HOME/..machine% install_mdaMDA installation

Did you run deinstall_mda first?Do you want to continue (Y/N)? yCopying from your_mda_home_directory /.. environment to your_mda_home_directory /.. environmentx dded_delivery, 0 bytes, 0 tape blocksx dded_delivery/oratcl–2.4b3, 0 bytes, 0 tape blocks

.

.( Ingnore lots of Tk/Tcl installation messages)

.MDA installation: Ready.

After the installation of MDA the Tcl/Tk library has to be installed. Usually this library is installed with theCGSI product. In case the MDA product is installed in a stand alone version, this library has to be installedin addition following the steps below:

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199818


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


machine% cd $MDA_HOME/bin/sun5/MDATCLmachine% uncompress tcltk_for_oracle_binaries.tar.Zmachine% tar xvf tcltk_for_oracle_binaries.tarmachine%

3.1.6 MDB Instance (ESA_TRAINING)

This delivery of MDA already contains the MDB Instance definition ESA_TRAINING with the correspon-ding SID–Range 1 to 100000. This MDB Instance is foreseen for demonstration and training purposes only.Within this MDB Instance it is not possible to create and maintain operational data.

In case another MDB Instance than ’ESA_TRAINING’ shall be installed, a new range has to be created usingthe SID Range Tool.

3.1.6.1 SID Range Tool Installation

login: sidadm inpassword: YourPassword <<Return>.machine% cd $MDA_HOME/util/sid_range_toolmachine% install_sid_range_tool

install_sid_range_tool startedSQL*Plus: Release 3.1.3.2.1 – Production on Tue Sep 10 14:52:25 1996Copyright (c) Oracle Corporation 1979, 1992. All rights reserved.Connected to:Oracle7 Server Release 7.1.3.0.0 – Production ReleasePL/SQL Release 2.1.3.0.0 – ProductionTable created.Index created.Disconnected from Oracle7 Server Release 7.1.3.0.0 – Production ReleasePL/SQL Release 2.1.3.0.0 – Productioninstall_sid_range_tool finished

In case data of an former installation has to be imported perform the following steps:

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199819


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


login: sidadminpassword: YourPassword <<Return>.machine% cd $MDA_HOME/util/sid_range_toolmachine% imp_sid_range_tool_data

imp_sid_range_tool_data startedThe data to be imported has to be stored in file:

––> /usr/columbus/users30/werkman/sid_ranges.dmpImport: Release 7.1.3.0.0 – Production on Tue Sep 10 14:56:19 1996Copyright (c) Oracle Corporation 1979, 1994. All rights reserved.Connected to: Oracle7 Server Release 7.1.3.0.0 – Production ReleasePL/SQL Release 2.1.3.0.0 – ProductionExport file created by EXPORT:V07.01.03. importing OPS$WERKMAN’s objects into OPS$WERKMAN. . importing table ”T_MDA_INSTALLATION_NODES_DEF” xxx rows importedImport terminated successfully without warnings.imp_sid_range_tool_data finished

3.1.6.2 Define MDB Instances using the SID Range Tool

In order to define further MDB instances invoke the SID Range Tool as follows:

login: sidadminpassword: YourPassword <<Return>.machine% cd $MDA_HOME/util/sid_range_toolmachine% start_sid_range_tool

The tool is displayed at the screen and allows the user to define further MDB instances. After definition theuser has to generate MDB installation files. The MDB installation files are generated by the SID Range Tooland located in the sidadm home directory.

In order to make these files visible for the MDB installation, they have to be copied into the MDB installationdirectory. Follow steps below:

machine su – mpsmachine% cd ~sidadminmachine% cp –r mdb_installations $MDA_HOME/config

Now the new defined MDB Instance is prepared for installation using the install_mdb command as discribedin section 3.1.8.

3.1.6.3 SID Range Tool Deinstallation

Before deinstallation of the SID Range Tool the defined data has to be exported into an OS–File:

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199820


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


login: sidadminpassword: YourPassword <<Return>.machine% cd $MDA_HOME/util/sid_range_toolmachine% exp_sid_range_tool_data startedexp_sid_range_tool_data started

Export: Release 7.1.3.0.0 – Production on Tue Sep 10 15:56:55 1996Copyright (c) Oracle Corporation 1979, 1994. All rights reserved.Connected to: Oracle7 Server Release 7.1.3.0.0 – Production ReleasePL/SQL Release 2.1.3.0.0 – ProductionNote: grants on tables/views/sequences/roles will not be exportedNote: indexes on tables will not be exportedNote: constraints on tables will not be exportedAbout to export specified tables .... exporting table T_MDA_INSTALLATION_NODES_DEF xxx rows exportedExport terminated successfully without warnings.exp_sid_range_tool_data finished

The exported data is stored in file: ––> /usr/columbus/users30/werkman/sid_ranges.dmp

After exporting the data the SID Range Tool may be deinstalled:

login: sidadminpassword: YourPassword <<Return>.machine% cd $MDA_HOME/util/sid_range_toolmachine% deinstall_sid_range_tool

deinstall_sid_range_tool startedDo you want to perform the deinstallation ? [n] ySQL*Plus: Release 3.1.3.2.1 – Production on Tue Sep 10 16:00:01 1996Copyright (c) Oracle Corporation 1979, 1992. All rights reserved.Connected to:Oracle7 Server Release 7.1.3.0.0 – Production ReleasePL/SQL Release 2.1.3.0.0 – ProductionDrop table T_MDA_INSTALLATION_NODES_DEFTable dropped.Disconnected from Oracle7 Server Release 7.1.3.0.0 – Production ReleasePL/SQL Release 2.1.3.0.0 – Production

deinstall_sid_range_tool finished

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199821


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.7 Copying the DADI–MA Export Files

When the user who has generated the data structure, has performed the ”Export to MDB” in DADI–MA, allgenerated files are stored in the

$MDA_HOME/MDA/util/dadi/dadi_export

directory.

The export files have to be copied from the DADI–MA scope into the MDB Installation scope, before theMDB can be installed with these data. The MDB installation script access the information from the

$MDA_HOME/MDA/config/mdb/install

directory.

When the export files are not yet in the MDB installation scope, it is necessary to transfer the generated exportfiles from the DADI–MA scope into the MDB installation scope, by the following steps:

machine% ( Move to the MDB installation directory )

machine% cd $MDA_HOME/config/mdb/install<Return>( Remove the old export files )

machine% \rm –r dadi_export<Return>

( Copy the export files into the MDB installation directory)machine% \cp –r $MDA_HOME/util/dadi/dadi_export .<Return>

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199822


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.8 Install MDB

Now fill the above created tablespace with the necessary information to use MDA. Therefore you have tologin as mps and call the script install_mdb .

Login: mps<Return>Password: YourPassword <Return>.. (OpenWindows is started, all windows appear).(In a shelltool window enter:)

machine% cd $MDA_HOME/config/mdb/install/admin_scripts/<Return>machine% install_mdb<Return>...... (some messages and user input for logging file here)...Enter OWNER NAME of the Oracle MDB account [MPS] : TheOwnerName <Return>Enter OWNER PASSWORD of the Oracle MDB account [MPS] : ThePassword <Return>

Enter OWNER NAME of the temporary Oracle MDB account [MPS_EXPORT]: TheTemporaryOw-nerName <Return>Enter OWNER PASSWORD of the temporary Oracle MDB account [MPS_EXPORT] : TheTempo-raryPassword <Return>

The following Instances can be installed : ...

(a list of existing instances appears)...Enter MDB INSTANCE NAME [CCP] or . to quit : InstanceName <Return>______________________________________________________________________________Start installation of Instance InstanceName...

( a lot of installation messages, ca. 20 minutes )...______________________________________________________________________________The MDB and the temporary MDB structures are installed.The next step is the filling of the structures with data by ’initialize_mdb’.______________________________________________________________________________

machine%

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199823


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.9 Initialize MDB

Now the mdb internal data dictionary has to be initialized:

machine% cd $MDA_HOME/config/mdb/install/admin_scripts<Return>machine% initialize_mdb<Return>...... (some messages and user input for logging file here)...Enter OWNER NAME of the Oracle MDB account [MPS] : TheOwnerName <Return>Enter OWNER PASSWORD of the Oracle MDB account [MPS] : ThePassword <Return>...... (Lots of messages here, ca. 10 minutes)..._____________________________________________________________________________ The MDB is initialized. The work with the MDB may now be started if the users are already installed.Otherwise users may be installed with the ’install_user’ script.______________________________________________________________________________

machine%

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199824


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.10 Load Demonstration or other Data

To load the demonstration and test data perform the following steps:

machine% cd $MDA_HOME/config/mdb/upgrade<Return>machine% cp mdb* ~/machine% import <Return>______________________________________________________________________ This script will import data to a MDB installation______________________________________________________________________ Do you wish to start the import [y] ?

Enter OWNER NAME of the Oracle MDB account [MPS] : TheOwnerName <return>Enter OWNER PASSWORD of the Oracle MDB account [MPS] : ThePassword <return> Enter BASENAME of the datafiles (INCLUDING THE PATH BUT WITHOUT TRAILING ’.<number>’)~/mdb.exp <return> (may be different for other imports than demo data) The logging–file stores all display outputs during the script execution in the users HOME (/usr/columbus/users32/mda320) directory Default logging filename: import_to_mda_test.98_10_08.logEnter logging–file name [import_to_mda_test.98_10_08.log] : ...... (Lots of messages here, ca. 10 minutes)...

machine%

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199825


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.11 Install Users

Each user who shall be able to use MDA has to be created by the mdb script install_user.

Note that the below described steps have to be performed for each user who shall be able to use the mdb soft-ware.

Change directory to the $MDA_HOME/config/oracle_env directory. Then call the script install_user. Youare asked for the MPS account and password and you shall use the dafaults. Follow the procedure below:

machine% cd $MDA_HOME/config/oracle_env<Return>machine% install_user<Return>...... (some messages and user input for logging file here)...Enter OWNER NAME of the Oracle MDB account [MPS] : TheOwnerName <Return>Enter OWNER PASSWORD of the Oracle MDB account [MPS] : ThePassword <Return>


Enter Oracle USER NAME (ops...) of new user : TheOps$Account <Return>Enter Oracle PASSWORD of new user : ThePassword <Return> Enter privilege CONFIGURATION_MANAGER or NORMAL_USER: ThePrivilege <Return>

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

.

. (Lots of Messages)

.___________________________________________________________________________ The user is successfully installed.___________________________________________________________________________

machine% exit<Return> (leave OpenWindows)

Perform the install_user procedure also for OPS$MDATEST with privilege ’NORMAL_USER’.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199826


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.12 Upgrade old MDB Data

To upgrade old MDA data to the current MDB version data perform the following steps:

machine% cd $MDA_HOME/config/mdb/upgrade<Return>machine% upgrade<Return>_________________________________ This script will upgrade MDB data_________________________________ Do you wish to start the upgrade [y] ? Enter the ORACLE system–account’s password: <password><Return> Enter temporary ORACLE account name to use for upgrade $THIS USER MUST NOT BE INSTALLED BEFORE IN ORACLE!$(Default MDB_UPGRADE): upgrade_account<Return> The following upgrades are usefully:CGS_MDB_V4_1_1_to_CGS_MDB_V4_2_0 Enter the upgrade: CGS_MDB_V4_1_1_to_CGS_MDB_V4_2_0<Return> Enter BASENAME of the datafiles generated by the export of the MDB (INCLUDING THE PATH BUT WITHOUT TRAILING .<number>)~/mdb.exp<Return> ....... (Lots of messages here, ignore warnings)...... FinishedStored in ~//upgraded_CGS_MDB_V4_1_1_to_CGS_MDB_V4_2_0.98_10_08.0 ... ~/upgraded_CGS_MDB_V4_1_1_to_CGS_MDB_V4_2_0.98_10_08.4 ... Finished export De–Installing ORACLE–user ’upgrade_account’ of MDB upgrade ...Revoke succeeded.User dropped.machine%

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199827


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.13 Certification Test Procedure

In the course of this certification test procedure, we will have a one time use of all capabilities of the mdbsoftware to certify the correct installation. The procedure will not determine any quality of the software.Login as mdatest. Then in a shell tool window call I_MDB.

3.1.13.1 Start of I_MDB GUI

Login: mdatest<Return>.. (OpenWindows is started). (in a shell tool window, enter:)machine% I_MDB &<Return>The I_MDB GUI pops up.Within the ”Element Configurations:” subwindow area, double–left–click on SSMBA subwindow ”I_MDB:System Tree Versions” appears.Within the ”I_MDB:System Tree Versions” subwindow, double–left–click on Version 1The I_MDB Navigation window shows the ”Pathname:” \SSMB(1) and the corresponding”System Tree Nodes” of the next level.

3.1.13.2 Navigate in I_MDB GUI

Within the ”System Tree Nodes:” subwindow, double–left–click on C_DH and then onMDMThe Pathname: subwindow shows your progress in the navigation to the target. Inthe future we will ask you for navigating to a certain node by the notation:Navigate to \SSMB(1)\C_DH\MDM\SUBFLOOR(1.0.0)\AFT_END, where the numbers after thenames within parantheses denote the versions which you have to select during theversion–select–subwindows of the corresponding user–requests. You can always navi-gate upwards, if you double–left–click on a node within the ”Pathname:” subwindowof the I_MDB Navigation window.Navigate to SUBFLOOR(1.0.0)\AFT_ENDWithin the ”User Tree Nodes:” subwindow, the end item node ”BASE_UNIT” and thevirtual node ”BOARD” are shown.

3.1.13.3 Check End Item Data

Left–click on the end item node ”BASE_UNIT”The node is highlighted.From the right–button–menu, select ”Open => Support Information...”The subwindow ”Engineering Support Information” appears. Verify that the fieldsare filled with some data.With the left mouse button, pull the pin–button off the top bar of the window.The ”Engineering Support Information” subwindow disappears.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199828


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.1.13.4 Check Print Report Capability

Navigate to \SSMB(1)\C_DH\MDMDouble–left–click on the CDU PORTSIDEThe ”I_MDB: CDU Versions” subwindow appears.Within the ”I_MDB: CDU Versions” subwindow, from the top level menu button selectwith the right mouse button ”Command => Print...”The ”Report Handler” subwindow appears.With a left click, select the button ”Execute” on the bottom of the ”Report Han-dler” subwindowThe message ”report_generator has been started” appears on the bottom of the ”Re-port Handler” subwindow. After a short period of time (around one minute), theOpenWindows Text Editor appears with the printed results of the report.From the top bar OpenWindows standard menu, select ”QUIT” with the right mousebuttonThe ”Text Editor” window disappears.With the left mouse button, pull the pin button off the ”Report Handler” subwindowThe ”Report Handler” subwindow disappears

3.1.13.5 Check Consistency Checker Capability

Within the ”I_MDB: CDU Versions” subwindow, from the top level menu button selectwith the right mouse button ”Command => Consistency Checker...”The ”Consistency Handler” subwindow appears.With a left click, select the button ”Execute” on the bottom of the ”ConsistencyHandler” subwindowThe message ”Consistency Checker has been started” appears on the bottom of the”Consistency Handler” subwindow. After a short period of time (around 10 seconds),the OpenWindows Text Editor appears with the printed results of the ConsistencyChecker.From the top bar OpenWindows standard menu of the Text Editor window, select”QUIT” with the right mouse buttonThe ”Text Editor” window disappearsWith the left mouse button, pull the pin button off the ”Consistency Handler”subwindowThe ”Consistency Handler” subwindow disappears

3.1.13.6 Run down

With the left mouse button, pull the pin button off the ”I_MDB: CDU Versions”subwindowThe ”I_MDB: CDU Versions” subwindow disappearsFrom the top bar OpenWindows standard menu of the ”I_MDB Navigation” window, se-lect ”QUIT” with the right mouse buttonThe ”I_MDB Navigation” window disappears

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199829


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.2 MDA D EINSTALLATION

The following text describes how to deinstall and remove all installations which have been made to installthe mdb software. It is important to perform the steps in the right sequence because otherwise there couldbe problems to execute a certain deinstallation step. The deinstallation is performed in a reverse sequenceas the installation procedure.

The following actions are necessary to remove mdb from the operational environment:

• Save Contents of Database

• Deinstall mdb Users

• Deinstall mdb

3.2.1 Save the Contents of the MDB Database

Before the mdb can be upgraded, or in case the software shall be removed from the system and the data shallbe kept, the data has to be saved into an export file. This is done by a script delivered with the MDB software.Login as mps:

Perform the following steps for an MDA version before MDA V4.2.0:

machine% cd $MDA_HOME/config/mdb/upgrade<Return>machine% export_mdb<MDB_Version> <Return>_____________________________________________________________________________This procedure exports the MDB data of a specific MDB account

The data are stored in the HOME directory:HomeDirectoryNamewithin the files mdb.exp1 and mdb.exp2._____________________________________________________________________________Do you want to perform the export ? [y] <Return>...... (some messages and user input for logging file here)...Enter OWNER NAME of the Oracle MDB account [MPS] : TheOwnerName <Return>Enter OWNER PASSWORD of the Oracle MDB account [MPS] : ThePassword <Return>

_____________________________________________________________________________Start Export....... (Lots of messages here, ignore warnings)..._____________________________________________________________________________Export finished._____________________________________________________________________________machine%

Rename export files to make them compatible for import with MDA V4.2:

machine% mv ~/mdb.exp1 ~/mdb.exp.0machine% mv ~/mdb.exp2 ~/mdb.exp.1

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199830


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


Perform the following steps for MDA V4.2.0:

machine% cd $MDA_HOME/config/mdb/upgrade<Return>machine% export <Return>______________________________________________________________________ This script will export tables of an ORACLE MDB–account______________________________________________________________________ Do you wish to start the export [y] ?

Enter OWNER NAME of the Oracle MDB account [MPS] : TheOwnerName<return>Enter OWNER PASSWORD of the Oracle MDB account [MPS] : ThePassword <return> Enter export file name [.../export.xxx.98_10_08] : Creating MDB export parameter files for account xxx... Finished ....... (Lots of messages here, ignore warnings)... ... FinishedStored in .../export_MDB.mps_devel.98_10_08.0 ... .../export_MDB.mps_devel.98_10_08.4 ... Finished export

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199831


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.2.2 Deinstall MDB Users

To deinstall the MDB users you have to login as mps and to use the deinstall_user script in $MDA_HOME/config/oracle_env. Perform the following instructions:

machine% cd $MDA_HOME/config/oracle_env<Return>machine% deinstall_user<Return>...... (some messages and user input for logging file here)...Enter OWNER NAME of the Oracle MDB account [MPS] : TheOwnerName <Return>Enter OWNER PASSWORD of the Oracle MDB account [MPS] : ThePassword <Return>


Enter Oracle USER NAME (ops...) of new user : TheOps$Account <Return>Enter Oracle PASSWORD of new user : ThePassword <Return>

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––Start user de–installation... (Lots of Messages).___________________________________________________________________________ The user is successfully de–installed.___________________________________________________________________________

machine%

This finishes the deinstallation of a user. You have to remove all of the MDA users this way if you want toupgrade to a new MDA version.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199832


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.2.3 Deinstall the MDB

Now you have to deinstall the database. This has to be performed if you get a new delivery of the MDA soft-ware. You call the script deinstall_mdb for each of the installation and export account, usually MPS andMPS_EXPORT:

machine% cd $MDA_HOME/config/mdb/install/admin_scripts<Return>machine% deinstall_mdb<Return>...... (some messages and user input for logging file here)...Enter OWNER NAME of the Oracle MDB account [MPS] : TheOwnerName <Return>Enter OWNER PASSWORD of the Oracle MDB account [MPS] : ThePassword <Return>

Enter OWNER NAME of the temporary Oracle MDB account [MPS_EXPORT]: TheTemporaryOw-nerName <Return>Enter OWNER PASSWORD of the temporary Oracle MDB account [MPS_EXPORT] : TheTempo-raryPassword <Return>______________________________________________________________________________Start de–installation....

( a lot of installation messages, ca. 20 minutes )...______________________________________________________________________________The MDB and the temporary MDB are successfully de–installed.______________________________________________________________________________

machine%

This finishes the deinstallation of the MDA software.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199833


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


3.3 ADMINISTRATION

Besides of the normal administration of SunOS and ORACLE, which is described in detail in the respectivemanuals, the MDA software does not need a certain administration routine. For a dedicated backup of theMDA databases you can use the export database script described in the section before. For a basic ORACLEdatabase maintenance refere to the ORACLE manual. For user and network administration and for a SunOSbased system backup, refer to the SunOS System Administration Manual.

34

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.199834


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


This page is intentionally left blank.

A-2

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998A-1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


A ACRONYMS

AD Applicable document

ADT Abstract Data Type

AP Automated Procedure

APM Attached Pressurized Module

CCU Configuration Control Unit

CDI Configuration Data Item

CDU Configuration Data Unit

CEGSE Core EGSE

CM Configuration Management

CSS Core Simulation Software

CU Configuration Unit

DBA Database Administrator

DMS Data Management Subsystem

DSA DMS Simulator Assembly

EDB Engineering Database

EPS Electrical Power Subsystem

EGSE Electrical Ground Support Equipment

FMTG Fault Management data Tables Generator

GNC Guidance, Navigation and Control

GDI Ground Data Item

HCI Human – Computer Interface

HLCL High–Level Command Language

ICD Interface Control Document

IEEE Institute of Electrical and Electronic Engineers

MCC Mission Control Center

MCS Manned Core Station

MDA Mission Database Application

MDB Mission DataBase

MDE Model Development Environment

MODB Master Object Data Base

MIPS Million Instructions per Second

MPE Mission Preparation Environment

MPS Mission Preparation Software

A-2

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998A-2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


MPSS Mission Preparation and Support Software

MTL Master Timeline

MTTC Minimum Telemetry and Telecommand

NASA National Aeronautics and Space Administration

OS Operating System

PA Product Assurance

P/L Payload

POCC Payload Operations Control Center

RAM Random Access Memory

RODB Runtime Object Data Base

SSF Space Station Freedom

SQL Structured Query Language

STAU Standard Acquisition Unit

SWEU Software Exchangeable Unit

SWRU Software Replaceable Unit

TBD To be defined

TBS To be supplied

TC Telecommand

TM Telemetry

UCL User Control Language

UIL User Interface Language

B-11

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998B-1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


B DEFINITIONS

A

Access rights define what access various users or applications have to objects or entities.

Accuracy Accuracy is the software characteristic that provides the required precisionin calculations and outputs.

Action Actions are high–level commands which provide for a flight configurationcontrol at higher levels than elementary commands and Automated Pro-cedures (AP). They are pre–planned, goal–oriented operations of eitherPayload Elements or Subsystems. An Action may be linked to lower–levelactions reflecting the hierarchical decomposition of the on–board oper-ation. On Action level, all necessary pre–checks are carried out to ensurea safe implementation of an automated operation consistent with the actualmission phase and flight element configuration.

Anomaly Management Anomaly management is the software characteristic that ensures continu-ity of operations under and recovery from abnormal conditions.

Application Program or set of programs performing some specialized user–orientedfunction (as opposed to general–purpose programs like a DBMS, or an op-erating system).

Application Independence Application independence is the software characteristic that ensures thatthe software is not dependent on any database system, microcode, com-puter architecture or algorithms.

Archive Refers to the process of relegating obsolete data to external backing stor-age. The reverse operation (copying archived data back to active storage)is known as restore.

Auditing process of examining recent transactions to determine if illegal or fraudu-lent activity has occurred.

Audit Log permanent record of important events that occur in a computer system.

Augmentability Augmentability is the software characteristic that ensures expansion of ca-pability for functions and data.

Authorized User see User

Automated Procedure A program written in the User Control Language (UCL).

B

C

CDU domain is a set of item types

Child in a hierarchical structure, denotes an immediate descendant of a givencomponent. A child is thus located one hierarchical level below its parent.

Client A process or program that makes use of services provided by another pro-cess or program (called service provider or server)

B-11

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998B-2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


Coincidental Cohesion A random grouping of activities.

Commonality Commonality is the software characteristic that ensures the use of interfacestandards for protocols, routines, and data representations.

Common coupling A type of coupling characterised by two modules referring to the same glo-bal data (area).

Communicational Cohesion A grouping of activities such that each activity uses the same input dataand/or contributes to producing the same output data (without regard toorder of execution).

Compilation Unit Smallest unit of code that is accepted by the compiler. In UCL, there are3 types of Compilation Units: Automated Procedure (AP), Library Spec-ification, and Library Implementation (or Library body).

Completeness Completeness is the software characteristic that ensures full implementa-tion of the functions required.

Component Component is a generic term used to cover any item in the higher levelsof the software architecture (i.e. product, assembly and subsystem).

Configuration Unit (CU) Collection of MDB items treated as a single unit for configuration manage-ment purposes.CUs are of two kinds: (a) Configuration Data Units (CDU), which contain the actual data(b) Configuration Control Units (CCU), which contain reference informa-tion (CU name, version number, etc.) about other CUs, just like a directoryin a file system.

Configuration Control Unit (CCU)A Configuration Control Unit is a Configuration Unit used to define andcontrol other Configuration Units. It identifies which specific combina-tions of CDU instances make up a particular configuration. A Configur-ation Control Unit may, in turn, point to lower–level control units, thusleading to a hierarchical configuration tree whose topmost (root) compo-nent corresponds to an entire Columbus Flight Configuration.

Configuration Data Unit (CDU)Configuration Data Units are composite entities containing the actual dataitems (grouped into individual units for configuration management pur-poses).

Conjunction (weak/strong conjunction)Refers to the weighting mechanism in FDIR/CONNEX reasoning.For strong conjunction: M of M possible premisses (symptoms) must be observed to believe a con-clusion (failure) with a proximity ratio of 1.For weak conjunction: N of M possible premisses (symptoms) must be observed to believe a con-clusion (failure) with a proximity ratio of N/M.

Connection Matrix Refers to a matrix CM( i,j ) where the columns represent the symptomvectors of the individual anomalies and rows each stand for a symptom.

B-11

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998B-3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


Consistency Consistency is the software characteristic that ensures uniform design andimplementation techniques and notations.

Consistency state LOCAL VALID,LOCAL INVALIDGLOBAL VALID

Control coupling A type of, coupling in which one module communicates information toanother module for the explicit purpose of influencing the execution of thelatter.

Correctness Correctness is the degree to which the software component satisfies thespecified requirements.

Coupling The degree of dependence of one module on another; specifically, ameasure of the chance that a defect in one module will appear as a defectin the other, or the chance that a change to one module will necessitate achange to the other.

CU Instance see Version

D

Database A common or integrated collection of interrelated data whose purpose isto serve one or more applications.

Database Management System (DBMS)The software responsible for the actual definition, storage and manipula-tion of data in a Database at both the physical and logical level.

Database Administrator (DBA)The person(s) responsible for the operation and maintenance of a DBMS.

Data Entry / Data MaintenanceGenerally refers to the process of entering and/or updating data in the data-base. In this context, the term ”maintain” refers to any operation which altersthe state of the Database, i.e. add (insert) new data, modify existing data,or delete data.

Database integrity Refers to the state in which the database is considered to be undamaged(both physically and logically).

Database Server Refers to the processor (network node) physically hosting the Databaseand providing DB access services to local or remote applications (clients).

Data Coupling A form of coupling in which one module communicates information toanother in the form of elementary parameters.

DBA see Database Administrator

DBMS see Database Management System

Default a value supplied by the system when a user does not specify a requiredparameter, qualifier, or attribute.

B-11

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998B-4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


Deadlock Situation in which two or more user processes cannot complete their trans-actions because each process is holding a resource that the other processrequires in order to complete.

Diagnosis Assumption about the faults or failures of a system obtained by examin-ation of the symptoms.

Display (or Screen Display) In this context, refers to an area on the physical screen surface assigned toapplications for the purpose of communicating with the human users. Itmay comprise one or several individual partitions (windows) each as-signed to a different application.

Distributed Database A collection of databases that can be operated and managed separately andalso share information.

Distributivity Distributivity is the degree to which software functions are geographicallyor logically separated within the system.

E

End–Item see MDB item

Efficiency Efficiency is the ratio of ’actual’ versus ’budgeted’ resource utilisation bythe software component. Resources include, but are not necessarily limitedto, processor time, memory size and communication bandwidth.

Efficiency of CommunicationEfficiency of communication is the characteristic of software that ensuresminimum utilisation of communication resources in performing functions.

Efficiency of Processing Efficiency of processing is the characteristic of software that ensures mini-mum utilisation of processing resources in performing functions.

Efficiency of Storage Efficiency of Storage is the software characteristic that ensures minimumutilisation of storage resources.

Expandability Expandability is the extent of effort required to expand (add new) softwarecapabilities or performance.

Exception An out–of–limits condition or a status inconsistent with the value obtainedby the monitoring function. In both cases, the current operational state istaken into account. An exception may also be derived from other values.

Export In the MPS context, this term refers to the process of extracting data froma DB and preparing it for inclusion (import ) into another DB.

F

Failure The termination of the ability of a functional unit to perform its requiredfunctions (ISO). A failure may occur when a fault is encountered. In the FDIR terminology, a failure is defined as the behavior of a functionalunit which is different from that expected.

Fault An accidental condition that causes a functional unit to fail to perform itsrequired functions (ISO). A fault if encountered, may cause a failure.

B-11

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998B-5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


Flexibility Flexibility is the extent of effort required to change (modify existing) soft-ware to accommodate changes in requirements.

Functional Cohesion A grouping of activities such that each and every activity contributes to theexecution of the same single, problem–related function.

Functional Overlap Functional overlap is the commonality of functions between softwarecomponents.

Functional Scope Functional scope is the commonality of functions within a software com-ponent.

G

Generality Generality is the characteristic of software that ensures the breadth of thefunctions performed with respect to the application.

GLOBAL VALID All consistency rules are fulfilled. That implies that all internal referencesare existing and external references do not exist.

Ground Software All software that executes in any COLUMBUS ground computer or in theflight configuration computers during pre–launch ground operations.

H

Heterogeneous system refers to a system comprising different types of processors or operatingsystems.

Homogeneous system refers to a system in which all processors are of the same type or family(usually from one vendor).

Hierarchical Name Tree see Name Tree

I

Implication Strength Entry in the connection matrix CM (i,j), in the range between zero andunity, representing the measure of evidence which the symptom in the i–throw bears to the anomaly in the j–th column.

Import In the MPS context, this term refers to the process of receiving or includingdata from an external (possibly remote) DB into the local DB.

Inadvertent operation The unintentional operation of a function as a result of HW or SW failure,human error, or natural or induced environmental effects.

Independence Independence is the software characteristic that ensures that the softwaredoes not depend on its environment (e.g. the computing system, operatingsystem, utilities, I/O routines, and libraries).

Integrity Integrity is the extent to which the software component controls access tosystem resources. (Resources here include database items, functions, andsoftware controlled hardware).

Intermediate code (I–code) The binary code generated by the UCL compiler. It is interpreted at runtime.

B-11

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998B-6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


Interoperability Interoperability is the extent of effort required to facilitate the interface ofone software component with other systems or software components.

Issue see Version

MDB–Item instance an occurrence of a particular MDB item in a given CU version.

J

K

L

Library see Symbol Library, UCL Library

LOCAL INVALID Internal references are not existing or other consistency rules as defined inthe MPSICD are not fulfilled.

LOCAL VALID All internal references and all other consistency rules are correct. Externalreferences are still existing and cannot be checked.

Logical Cohesion A grouping of activities based on a real or imagined similarity of imple-mentation (without regard to data flow, order, or time of execution).

M

Maintainability Maintainability is the extent of effort required to find and fix errors in thesoftware component.

MDB instance One installation of a MDB with a specific SID range.

MDB installation node Server where one or more MDB’s are installed.

MDB Item, MDB Object In the context of this document, these two terms are used interchangeablyto denote a uniquely identifiable entity that has been defined in the MissionDatabase ( and corresponds to a real–world HW or SW entity). An MDBObject or Item may be decomposed into lower–level items according to thehierarchical nametree conventions, see Nametree below. An End–Item is an MDB item located at the lowest hierarchical level (leafor terminal node), and hence cannot be further decomposed.

Mission The performance of a coherent set of investigation or operations in spaceto achieve space programme goals. A single mission may require morethan one flight, and more than one mission may be accomplished on asingle flight.

Mission Database (MDB) This the central repository for all HW / SW configuration informationabout Columbus Flight Elements, Payloads and associated Ground Sup-port Equipment. Access to the MDB is controlled and managed by MPS.

Modularity Modularity is the characteristic of software that ensures a highly cohesivecomponent structure with optimum coupling.

MPS User see User

B-11

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998B-7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


N

Nametree Hierarchical (tree) structure within the MDB which portrays the hierarchi-cal decomposition of Columbus Flight Configurations into systems, sub-systems, equipment, etc. The topmost node of the nametree (called the rootnode) designates the Flight Configuration, whereas terminal nodes (leafnodes) represent the items that cannot (or need not) be further decomposed,i.e. the so–called end–items.Each MDB object is thus identifiable by a pathname indicating the suc-cession of nodes to be traversed to reach that particular item in the Name-tree.

Network a group of computers (workstations) and/or terminals that are linked to-gether to allow the sharing of resources (data and peripherals).

Node any component of a network or tree structure.(e.g. LAN node, nametree node)

O

Operability Operability is the ease by which a person can use a system comprising soft-ware and hardware.

Operating System (OS) The system software that controls the computer and its parts, performingthe basic tasks such as allocating memory, and allowing computer compo-nents to communicate.

Operator The person who operates any system comprising software and hardwareusing the provided computer input devices (e.g. keyboard, pointing device,voice input, pushbuttons, switches etc) and/or computer output devices(e.g. screen, printer, lamps etc).

P

Parent In a hierarchical structure, denotes an immediate ancestor of a given com-ponent.

Pathname see Nametree

Portability Portability is the extent of effort required to transfer the software compo-nent from one hardware or software system environment to another.

Procedural Cohesion A grouping of activities based on order of execution in a particular imple-mentation (without regard to dataflow).

Protocol Rules and conventions for organizing data to be sent from one machine toanother. The protocol enables the destination machine to recognize that thedata is addressed to it, check the data to make sure that it is valid, unpackand decode the data, etc.

Proximity Ratio A measure of the correspondence of observed pattern to predefined pat-tern. For failures and faults the proximity ratio is defined as the quotientof observed to expected symptoms.

B-11

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998B-8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


Q

R

Reconfigurability Reconfigurability is the characteristic of software that ensures continuityof system operation when one or more processors, storage units, or com-munication links fail.

Reconfiguration A procedure which changes the status of used hardware and software items

Recovery This is the process where a Database which is damaged (or assumed to beso) is restored to a previous state known to be consistent.

Reliability Reliability is the extent to which the software component consistently per-forms the specified functions or any interface requirements.

Report In the context of this document, a report may be defined as any human–re-adable description of one or more MDB items. It is an assorted collectionof information usually presented to the user in form of a table or itemizedlist (tabular format).A report’s specification contains the instructions for generating the report,e.g. data selection criteria, formatting instructions, and sort order. Thisspecification may be stored in the MDB. On request, a report is generated, i.e. the predefined instructions are ex-ecuted, and the resulting output routed either to the workstation’s screen(on–screen report), to the printer or to a user–selected file.

Response time For interactive transactions, this refers to the time elapsing between the”end of input” signal (e.g. pressing the ENTER, ACCEPT, or COMMITkey) and the first character of the reply reaching the user’s terminal.

Restore This refers to the process of copying archived data back to active storage

Reusability Reusability is the extent of effort required to convert a portion of the soft-ware component for use in another application.

Re–Used Software Software re–used from other projects without modification except for re-configuration.

Revision see Version

S

Safety safety is the absence of hazardous conditions.

Safety Management safety management is the characteristic of software that separates criticaland non–critical software to prevent or to reduce the probability of unsafeconditions from occurring

Screen Display see Display

Self–Descriptiveness Self–descriptiveness is the characteristic of software that ensures explana-tion of the implementation of functions.

B-11

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998B-9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


Semantics Refers to the set of rules dealing with the contextual meaning of the lan-guage elements (symbols, constants, variables, etc.)

Server A process providing services to other cooperating processes.A DB server is the processor (network node) physically hosting the Data-base and providing DB access services to local or remote applications (cli-ents)

Simplicity Simplicity is the characteristic of software that ensures definition and im-plementation of functions in the most direct and understandable way.

Software Exchangeable Unit (SWEU)All COLUMBUS ground software is configured into SWEUs. An SWEUis any software unit or component which can be replaced as a single item.As such it is primarily a configuration management item and is handled inthe same way as an (onboard) SWRU for CM purposes. ( See also SWRU).

Software Replaceable Unit (SWRU)All COLUMBUS flight software is configured as a set of SWRUs. SomeSWRUs can be replaced online. Others are replaced by reloading the pro-cessor. All SWRUs are configuration management items in the same wayas SWEUs.

SWRU Support SetRefers to the set of data and procedures required to control and automatethe generation and exchange of SWRUs. The SWRU Support Set typicallyincludes: offline generation procedure, maintenance information, verifica-tion information, replacement procedure and other general information(identification, version, generation date, size, criticality, target processortype, etc.).

Stamp Coupling A type of coupling characterised by two modules referring to the samecomposite data structure.

Survivability Survivability is the extent to which the software component continues toperform its required functions even when a portion of the system has failed.

SWRU Support SetRefers to the set of data and procedures required to control and automatethe generation and exchange of SWRUs. The SWRU Support Set typicallyincludes: offline generation procedure, maintenance information, verifica-tion information, replacement procedure and other general information(identification, version, generation date, size, criticality, target processortype, etc.).

Symptom Indicator of faults or failures.

System Accessibility System accessibility is the characteristic of software that ensures controland auditing of access to the software and data.

System Administrator A person responsible for the operation and maintenance of the operatingsystem of a computer.

System clarity System clarity is the characteristic of software that ensures the clear de-scription of program structure in a direct, understandable manner.

B-11

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998B-10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


System Compatibility System compatibility is the characteristic of software that ensures the hard-ware, software and communication compatibility of two software compo-nents.

T

Testability Testability is the extent of effort required to verify software operation andperformance.

Traceability Traceability is the software characteristic that provides a thread of originfrom the implementation to the requirements with respect to the specifieddevelopment envelope and operational environment.

Transaction single thread of related activities representing a sequence of operations in-itiated by the occurrence of a stimulus and ending with the required re-sponse.

Two–stage Command A command which requires confirmation from the originator before it isexecuted.

U

Unit Unit is a generic term used to cover any lower level item of breakdown inthe software architecture e.g. module, object etc.

Usability Usability of a software component is a characteristic which can bemeasured by the time end effort required to learn the human interface, pre-pare input, and interpret the output of that software component.

User Throughout this document the term User or MPS User refers to any per-son using MPS–provided services. Users are grouped into different classesor categories and will be assigned different privileges based on the taskthey perform.

User Control Language (UCL)Columbus Test and Operations language (used for real–time control &monitoring purposes in both the onboard and ground environment)

UCL Library Encapsulation mechanism for UCL data structures and operations. (can beviewed as a collection of functions, procedures, types, etc.) A UCL Li-brary corresponds to a package in Ada or a module in Modula–2.

V

Version In the course of its life cycle, a Configuration Unit (CU) usually undergoesseveral modifications due to evolving user requirements, design changes,etc.It will thus possibly exist within the MDB in many different forms or in-stances (CU occurrences) commonly referred to as versions, e.g. DMSVersion 3.2.1.

In the Configuration Management (CM) context, however, the various CU

B-11

COL–RIBRE–MA–0018–004 01.09.1997A 08.10.1998B-11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


��


occurrences. are classified according to the types of changes that havebeen made. The terms versions, issues, and revisions are then used todifferentiate between the following 3 cases:– Modifications due to requirements changes which result in a new ver-sion– Modifications due to design changes which result in a new issue.– Modifications due to bug fixes, repairs or other corrections (affectingneither the design nor the requirements) which result in a new revision.

(In the above example, the CU Identifier ”DMS Version 3.2.1”, therefore,refers to Version 3, Issue 2, Revision 1 of the DMS)

Visibility Visibility is the software characteristic that provides monitoring of the de-velopment and operation of software.

W

X

Y

Z