mda reference manual cgs–ribre–sum–0003 8–qa 03.07

Titel: MDA Reference ManualTitle:

Dokument No.: CGS–RIBRE–SUM–0003 Klassifikations Nr: 8–QADocument No.: Class. Prod. Code:

Ausgabe Nr.: 2 Ausgabedatum: 03.07.2015Issue No.: Issue Date:

Ueberarbeitung: – Ueberarbeitungsdatum: –Revision: Revision Date:

Liste der zu liefernden Dokumente / Dok.–Anforderungs–Beschreibung (LLD/DAB):

Document Requirements List / Doc. Requirements Description (DRL/DRD):

Bearbeitet: I. Lenz Firma: AIRBUSDEFENCE& SPACE

Prepared by: Company:

Geprueft: S. Marz Firma: AIRBUSDEFENCE& SPACE

Agreed by: Company:

Vertrags–Nr:Contract–No.: _____________________

_________________________________ _________________________________Projekt Manager Projekt Manager

Project Manager Project Manager

Ast

rium

–SI/C

OL

Previous Doc.–No.: COL–RIBRE–MA–0031–00

CGS–RIBRE–SUM–00032 03.07.2015– –

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

/Issue:/Rev.: /Date:

Datum/Date:

FORM 0672.0V.7 EADS Space Transportation GmbH, D–28199 Bremen – All Rights reserved – Copyright per DIN 34

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –i

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

Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:

FORM 0672.0V.7 EADS Space Transportation GmbH, D–28199 Bremen – All Rights Reserved – Copyright per DIN 34

DOCUMENT CHANGE RECORD

Issue / Rev. Issue date Pages / Section affected

Remarks

1/– 11.07.94 all initial version

2/– 30.11.94 4.44.511124.3

New section Direct End Item AccessNew section Foreign KeyNew section Data APINew section Customer Specific ImplementationsUpdate section default starting point

2/A 17.02.95 4.41214.1.3

Update section Direct End Item AccessNew section Batch Data Entry (BDE)Update section Consistency Checker

2/B 28.07.95 4.65.15.36.16.27.2.57.3.48.2.591011121314

New section for Flexible Tool InvocationUpdate Create Element ConfigurationUpdate Import File sectionUpdate System Tree Nodes sectionUpdate System Tree Versions sectionUpdate Export File sectionUpdate Export File sectionUpdate Export File sectionUpdate Report Generation sectionUpdate Consistency Checker sectionUpdate Data–API sectionNew section for Configuration Data Item, CDINew section for MDA Batch Data Entry, BDEUpdate MBF section

2/C 20.09.95 4.5&4.61411.4.411.4.511.4.614App. D

Shifted to new chapter 15 Advanced OpsNew section for CSS HandlingNew section for Aggregate ViewsNew section for Write ProceduresNew section for CGS MappingNew section CSS Data and I/F HandlingUpdate API examples

3/– 01.12.95 all67.2.87.2.98.2.48.2.59.2.59.2.610.3.810.4.611.4.211.4.411.4.511.4.611.4.713.213.313.41618.2

New document number and document layoutNew section for Mission SupportUpdate section for Distribute System Tree VersionUpdate section for Import System Tree VersionUpdate section for Archive/Distribute CDU VersionUpdate section for Import/Restore CDU VersionUpdate section for Archive/Distribute CCU VersionUpdate section for Import/Restore CCU VersionNew section for CCU Category ReportNew section for CDU Category ReportUpdate section for End–Item ViewsNew section for Aggregate ViewsNew section for Write ProceduresNew section for Aggregate Delete ProceduresNew section for MappingNew section Special ChecksNew section CDI ChecksNew section User defined Consistency ChecksNew chapter for CSS Data and I/F HandlingUpdate section Matrix–X Integration

3/A 09.09.96 17.318

New section for UCL interface handlingNew chapter for the Detailed Data Editor (DDED)

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –ii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3/B 04.04.97 2.1 New MDA ICD reference

3/B 04.04.97 18.4 DDED: new examples for composite aggregates

3/B 04.04.97 11.2.4, 11.2.5 New expamples for end item and aggregate views

3/B 04.04.97 15 BDE exit status in case of abnormal termination changedfrom 255 to 42

4/– 06.12.97 8 Add move subtree functionalityAdd userdefinable SIDs functionality

4/– 06.12.97 9 Incorporate ’Including CDIs’ option for create CCUversion functionality.

4/– 06.12.97 11 – Add new API–Views– Add procedure calls and exception description for CONVERT_CDU_VERSION and CONVERT_CCU_VERSION procedures and functions.– Add package MDB_API_CEI description

4/– 06.12.97 15 – Redefine constaints for Batch Configuration File– Incoorporate description for BDE_CEI

4/– 06.12.97 16 Remove description for no longer supported ’LoadImage’ and ’Write Image’ functionality (has been movedto CSS).

4/– 06.12.97 18 Update section Detailed Data Editor (DDED)

4/A 25.09.98 15.3 Incoorporate description for BDE_CU

4/A 25.09.98 11.2.13 Incoorporate description for MDB_API_CU

4/B 22.04.99 20 – Add ASV

4/C 22.02.2000 4,5,6,7,8,9,20 – Changes in I_MDB layout

4/C 22.03.2000 15.1.9, 15.4.315.1.2

– BDE error messages– changes in BDE config file for load long data

4/C 22.03.2000 13.1.3, 13.2.2 Consistency Checker: – Add PL/SQL procedure Check_reference_no

4/D 26.06.2001 13, F New Consistency Checker

01/– 26.06.2001 18, previous F DDED, remove old Consistency Checker

01/– 08.11.2001 13.7, 10 Add Consistency Checker in Batch ModeRemove contents in chapter 10

01/A 01.09.2003 9.2.9, 21, 22 Update CU version manager and ExcelMDB, add FileLoader/Extractor

01/C 20.03.2006 8 Introduction of Restricted CDU Versions

01/D 25.10.2006 22 File Loader/Extractor (SPR–100576)

01/E 31.10.2008 4.3 Update section default starting point

01/F 29.01.2010 22.3.4 File Extractor (SPR–100579)

01/G 05.04.2012 7.1.1013

Add System Tree Nodes to a frozen System Tree VersionConsistency Checker

9/– 03.07.2015 21 ExcelMDB (SPR–103338)

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –iii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


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

2 APPLICABLE AND REFERENCE DOCUMENTS 2–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 APPLICABLE DOCUMENTS 2–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 REFERENCE DOCUMENTS 2–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 KEY FEATURES 3–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 COMMON OPERATIONS 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 NAVIGATING THROUGH THE NAME TREE 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1.1 Navigator window 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1.1 Paging Mechanism 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1.1.1.1 Goto the Top 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1.1.2 One Page down 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1.1.3 Goto a –2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1.1.4 One Page up 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1.1.5 Goto the Bottom 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1.1.2 Pulldown Menus 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1.2.1 File 4–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1.2.2 Edit 4–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1.2.3 Properties 4–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1.1.2.3.1 Properties–>Selection 4–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1.2.3.2 Properties–>Tool 4–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.1.2.3.3 Properties–>Options 4–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1.1.3 Pulldown Menus in the lower part of the ’I_MDB Navigator’ 4–4. . . . . . . 4.1.2 Selecting an Object 4–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.3 Deselecting an Object 4–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.4 Open 4–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1.4.1 Executing the ’Open’ operation 4–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.4.2 Navigate to the Name Tree Root Node 4–7. . . . . . . . . . . . . . . . . . . . . . . . . 4.1.4.3 Navigate into a System Tree Version 4–7. . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.4.4 Navigate to a specific System Tree Node within a System Tree Version 4–84.1.4.5 Navigate to a CDU Root Node 4–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.4.6 Navigate into a CDU (Test) Version 4–9. . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.4.7 Navigate to a specific User Tree Node 4–9. . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.4.8 Navigate to a specific CCU 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.4.9 Navigate into a specific CCU Version 4–10. . . . . . . . . . . . . . . . . . . . . . . . . . 4.1.4.10 Navigate to Enditems via direct type access. 4–11. . . . . . . . . . . . . . . . . . . . . 4.1.4.11 Navigate to System and User Tree Nodes within a specific CCU Version . . . .

4–11

4.2 PATHNAME & SID 4–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1 Show SID 4–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2 Translate SID into Pathname 4–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3 SET DEFAULT STARTING POINT 4–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –iv


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


4.4 DIRECT END ITEM ACCESS 4–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.5 QUIT A WINDOW 4–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.6 EXIT FROM INTERACTIVE MISSION DATABASE 4–14. . . . . . . . . . . . . . . . . . . . . . .

5 ELEMENT CONFIGURATION 5–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.1 Create 5–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.2 Delete 5–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.3 Import 5–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.4 Set Default Starting Point 5–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5.5 Show System Tree Versions 5–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 MISSION SUPPORT 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1 Select a Mission 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.2 Create a Mission 6–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.3 Delete a Mission 6–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7 SYSTEM TREE 7–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.1 System Tree Nodes 7–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.1 Browse CCU Versions 7–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.2 Open 7–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.3 Pathname & SID 7–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.4 Set Default Starting Point 7–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.5 Show CCU Versions 7–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.6 Create a System Tree Node 7–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.7 Delete a System Tree Node and Subtree 7–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.8 Copy and Paste a System Tree Node 7–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.9 System Tree Node Properties 7–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.10 Add System Tree Nodes to a frozen System Tree Version 7–10. . . . . . . . . . . . . . . . .

7.1.10.1 Source System 7–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.10.2 Target System 7–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2 System Tree Version 7–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.1 Create a System Tree Version 7–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.1.1 Create a System Tree Version by Copying 7–12. . . . . . . . . . . . . . . . . . . . . . . 7.2.1.2 Create an empty System Tree Version 7–14. . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.2 Delete a System Tree Version 7–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.3 Select a System Tree Version 7–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.4 Deselect a System Tree Version 7–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.5 Open a System Tree Version 7–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.6 Print a System Tree Version 7–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.7 Data Distribution 7–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.7.1 Distribute a System Tree Version 7–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.7.2 Import a System Tree Version 7–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.8 Show 7–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.8.1 Show System Tree Versions 7–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –v


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


7.2.8.2 Show System Tree Version Properties 7–20. . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.8.3 Show Exports 7–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.8.4 Show Imports 7–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7.2.9 Add System Tree Versions 7–23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.10 System Tree Version Properties 7–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 CDU (USER TREE) 8–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1 CDU Root Node and User Tree Nodes 8–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1.1 Create 8–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1.1 Create the CDU Root Node 8–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1.2 Create a User Tree Node 8–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1.3 Create a specific End Item 8–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1.4 Create a specific End Item by Copying an existing End Item 8–7. . . . . . . . 8.1.1.5 Create a subtree of User Tree nodes by Copying a subtree 8–7. . . . . . . . . .

8.1.2 Delete 8–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.2.1 Delete the CDU Root Node 8–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.2.2 Delete a subtree or a User Tree Node 8–10. . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.2.3 Delete an End Item 8–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1.3 Move a subtree of User Tree nodes 8–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.4 Open 8–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.5 Pathname & SID 8–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.6 Set Default Starting Point 8–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.7 Show 8–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1.7.1 Show CDU Root Node Properties 8–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.7.2 Show User Tree Node Properties 8–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1.8 Update 8–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.8.1 Update User Tree Node Properties 8–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.1.8.1.1 Update the description of a User Tree node 8–14. . . . . . . . . . . . . . . . . . 8.1.8.1.2 Update/change the owner of a User Tree node 8–14. . . . . . . . . . . . . . . . 8.1.8.1.3 Update/change the owner of a User Tree subtree 8–15. . . . . . . . . . . . . . 8.1.8.1.4 Update/change the SID Number of a User Tree Node 8–15. . . . . . . . . .

8.1.8.2 Update specific End Item detailed data 8–15. . . . . . . . . . . . . . . . . . . . . . . . . 8.1.8.2.1 Example: Update End Item MDM_IO_BOARD 8–16. . . . . . . . . . . . . . 8.1.8.2.2 Example: Update End Item Support Information 8–16. . . . . . . . . . . . . . 8.1.8.2.3 Example: Update End Item Channel Description 8–17. . . . . . . . . . . . . .

8.2 CDU Version 8–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.1 Consistency Checker 8–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.2 Create 8–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.2.2.1 Create an empty CDU Version 8–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.2.2 Create a CDU Version by copying an old CDU Version 8–23. . . . . . . . . . . . 8.2.2.3 Create a CDU Version by copying a CDU Test Version 8–24. . . . . . . . . . . . 8.2.2.4 Create an Issue of a CDU Version 8–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.2.5 Create an Issue of a CDU Version by copying a CDU Test Version 8–27. . . 8.2.2.6 Create a Revision of a CDU Version 8–29. . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.2.7 Create a Revision of a CDU Version by copying a CDU Test Version 8–30.

8.2.3 Delete a CDU Version 8–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –vi


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8.2.4 Open 8–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.5 Print 8–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.6 Set Default Starting Point 8–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.7 Data Distribution and Archiving 8–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.2.7.1 Distribute/Archive a CDU Version 8–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.7.2 Import/Restore a CDU Version 8–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.2.8 Show 8–37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.8.1 Show CDU Versions 8–37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.8.2 Show CDU Version Properties 8–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.8.3 Show Exports 8–39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.8.4 Show Imports 8–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.2.9 Update CDU Version Properties 8–42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.9.1 Update the description of a CDU Version 8–42. . . . . . . . . . . . . . . . . . . . . . . 8.2.9.2 Update/change the owner of a CDU Version 8–42. . . . . . . . . . . . . . . . . . . . . 8.2.9.3 Update the status of a CDU Version to REVIEW 8–43. . . . . . . . . . . . . . . . . 8.2.9.4 Update the status of a CDU Version to FROZEN 8–44. . . . . . . . . . . . . . . . . 8.2.9.5 Update the CDU domain of a CDU Version 8–44. . . . . . . . . . . . . . . . . . . . .

8.3 CDU Test Version 8–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.1 Consistency Checker 8–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.2 Create 8–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.3.2.1 Create an empty CDU Test Version 8–47. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.2.2 Create a CDU Test Version by copying a CDU Version 8–50. . . . . . . . . . . . 8.3.2.3 Create a CDU Test Version by copying an old CDU Test Version 8–50. . . .

8.3.3 Delete a CDU Test Version 8–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.4 Open 8–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.5 Print 8–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.6 Set Default Starting Point 8–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.7 Data Distribution and Archiving 8–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.8 Show 8–52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.9 Update 8–52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8.4 Restricted CDU Version 8–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.1 Concept 8–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.2 CDU Version Restrictions Administration 8–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.3 Consistency Checker 8–55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.4 Create 8–55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.5 Delete a Restricted CDU Version 8–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.6 Open 8–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.7 Print 8–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.8 Set Default Starting Point 8–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.9 Data Distribution and Archiving 8–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.10 Show 8–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.11 Update 8–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9 CCU 9–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 CCU (CCU Name) 9–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.1.1 Create 9–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –vii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


9.1.2 Delete 9–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2 CCU Version 9–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.1 Browse CCU Versions 9–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.2 Consistency Checker 9–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.3 Create 9–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2.3.1 Create an empty CCU Version 9–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.3.2 Create a CCU Version by copying an old one 9–6. . . . . . . . . . . . . . . . . . . . 9.2.3.3 Create an Issue of a CCU Version 9–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.3.4 Create a Revision of a CCU Version 9–7. . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2.4 Delete a CCU Version 9–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.5 Open 9–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.6 Pathname & SID 9–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.7 Print 9–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.8 References 9–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2.8.1 Maintain References 9–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.8.2 Create References to other CCU Versions 9–11. . . . . . . . . . . . . . . . . . . . . . . 9.2.8.3 Create References to other CDU (Test) Versions 9–11. . . . . . . . . . . . . . . . . . 9.2.8.4 Delete References to other CCU Versions 9–12. . . . . . . . . . . . . . . . . . . . . . . 9.2.8.5 Delete References to other CDU Versions 9–12. . . . . . . . . . . . . . . . . . . . . . .

9.2.9 CU Version Manager . . . . . 9–14

9.2.9.1 The CU Version Manager tool modes 9–14. . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.9.2 The CU Version Manager main window 9–14. . . . . . . . . . . . . . . . . . . . . . . . 9.2.9.3 CU version creation constraints 9–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.9.4 CU version deletion constraints 9–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.9.5 how to create CU versions 9–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2.9.5.1 Select on or more CUs 9–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.9.5.2 Assign an action to selected CUs 9–18. . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.9.5.3 Assign a new name or path to C+ CUs 9–19. . . . . . . . . . . . . . . . . . . . . . 9.2.9.5.4 create new CU versions in the MDB 9–19. . . . . . . . . . . . . . . . . . . . . . .

9.2.9.6 how to delete CU versions 9–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.9.6.1 Select on or more CUs 9–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.9.6.2 Press the action button D 9–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.9.6.3 delete CU versions in the MDB 9–20. . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2.9.7 Reference creation and removal 9–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.9.8 Log file 9–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2.10 Data Distribution and Archiving 9–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.10.1 Distribute/Archive a CCU Version 9–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.10.2 Import/Restore a CCU Version 9–23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2.11 Set Default Starting Point 9–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.12 Show 9–25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9.2.12.1 Show CCU Versions 9–25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.12.2 Show CCU Version Properties 9–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.12.3 Show Exports 9–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2.12.4 Show Imports 9–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

10 REPORT GENERATION 10–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –viii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11 MDA DATA APPLICATION PROGRAMMING INTERFACE (DATA–API) 11–1. . . . . . . . . 11.1 General Description of the Data–API 11–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Using the Data–API 11–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.2.1 Description of the MDB_API Package 11–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.1.1 Procedure MDB_API.COMMIT 11–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.1.2 Procedure MDB_API.ROLLBACK 11–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.1.3 Procedure MDB_API.CONFIG_API 11–5. . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.1.4 Procedure / Function MDB_API.CONVERT_CDU_VERSION 11–7. . . . . 11.2.1.5 Procedure / Function MDB_API.CONVERT_CCU_VERSION 11–9. . . . .

11.2.2 API Exceptions 11–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.3 Description of the MDB_API_WRITE Package 11–12. . . . . . . . . . . . . . . . . . . . . . . . . 11.2.4 Description of End–Item Views 11–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.5 Description of Aggregate Views 11–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.6 Description of Write Procedures 11–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.7 Description of Aggregate Delete Procedures 11–17. . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.8 Description of the Pathname–SID Relation View 11–19. . . . . . . . . . . . . . . . . . . . . . . . 11.2.9 Description of the Foreign Key–SID Relation View 11–19. . . . . . . . . . . . . . . . . . . . . . 11.2.10 Description of the User Tree Nodes View 11–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.11 Description of the V_ENT_EI_TYPE View 11–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2.12 Description of CREATE_END_ITEM_API Package 11–23. . . . . . . . . . . . . . . . . . . . .

11.2.12.1 Procedure MDB_API_CEI.CREATE_USER_NODE 11–23. . . . . . . . . . . . . . 11.2.12.2 Procedure MDB_API_CEI.CREATE_USER_NODE_TMP 11–24. . . . . . . . . 11.2.12.3 Procedure MDB_API_CEI.UPDATE_USER_NODE 11–24. . . . . . . . . . . . . . 11.2.12.4 Procedure MDB_API_CEI.READ_NODE_DESCRIPTION 11–25. . . . . . . . 11.2.12.5 Procedure MDB_API_CEI.EXIST_NODE 11–26. . . . . . . . . . . . . . . . . . . . . . 11.2.12.6 Procedure MDB_API_CEI.EXIST_USER 11–27. . . . . . . . . . . . . . . . . . . . . . 11.2.12.7 Procedure MDB_API_CEI.EXIST_TYPE 11–27. . . . . . . . . . . . . . . . . . . . . . 11.2.12.8 Procedure MDB_API_CEI.IS_CM_USER 11–28. . . . . . . . . . . . . . . . . . . . . . 11.2.12.9 Procedure MDB_API_CEI.WHO_AM_I 11–28. . . . . . . . . . . . . . . . . . . . . . . 11.2.12.10 Procedure MDB_API_CEI.DELETE_USER_SUBTREE 11–28. . . . . . . . . .

11.2.13 MDB_API_CU – MDA Data Application Programming Interface (Data–API) toBDE_CU 11–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.2.13.1 Procedure MDB_API_CU.IS_CM_USER 11–30. . . . . . . . . . . . . . . . . . . . . . . 11.2.13.2 Procedure MDB_API_CU.GET_SYSTEM_TREE_VERSION_STATUS . . . .

11–3111.2.13.3 Procedure MDB_API_CU.GET_MDB_INSTANCE 11–31. . . . . . . . . . . . . . 11.2.13.4 Procedure MDB_API_CU.SWITCH_TO_LOAD 11–32. . . . . . . . . . . . . . . . . 11.2.13.5 Procedure MDB_API_CU.SWITCH_TO_STORE 11–32. . . . . . . . . . . . . . . . 11.2.13.6 Procedure MDB_API_CU.EXISTS_CDU 11–32. . . . . . . . . . . . . . . . . . . . . . 11.2.13.7 Procedure MDB_API_CU.CREATE_CDU 11–33. . . . . . . . . . . . . . . . . . . . . . 11.2.13.8 Procedure MDB_API_CU.EXISTS_CDU_VERSION 11–34. . . . . . . . . . . . . 11.2.13.9 Procedure MDB_API_CU.CREATE_CDU_VERSION 11–35. . . . . . . . . . . . 11.2.13.10 Procedure MDB_API_CU.UPDATE_CDU_VERSION 11–36. . . . . . . . . . . . 11.2.13.11 Procedure MDB_API_CU.EXISTS_CCU 11–38. . . . . . . . . . . . . . . . . . . . . . . 11.2.13.12 Procedure MDB_API_CU.CREATE_CCU 11–38. . . . . . . . . . . . . . . . . . . . . . 11.2.13.13 Procedure MDB_API_CU.EXISTS_CCU_VERSION 11–39. . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –ix


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11.2.13.14 Procedure MDB_API_CU.CREATE_CCU_VERSION 11–40. . . . . . . . . . . . 11.2.13.15 Procedure MDB_API_CU.UPDATE_CCU_VERSION 11–41. . . . . . . . . . . . 11.2.13.16 Procedure MDB_API_CU.DELETE_CCU_REFERENCES 11–43. . . . . . . . 11.2.13.17 Procedure MDB_API_CU.ADD_CCU_REFERENCE 11–44. . . . . . . . . . . . .

12 CONFIGURATION DATA ITEM (CDI) 12–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.1 General Description of the CDI 12–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 Using the CDI 12–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.2.1 Description of provided CDI Procedures for Write Access 12–4. . . . . . . . . . . . . . . . 12.2.1.1 Parameter Description 12–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1.2 Procedure COMMIT 12–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1.3 Procedure ROLLBACK 12–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1.4 Procedure LOCK_CCU 12–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1.5 Procedure CREATE_CDI 12–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1.6 Procedure DELETE_CDI 12–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1.7 Procedure INSERT_XREF 12–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1.8 Procedure INSERT_CODE 12–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1.9 Procedure INSERT_REPORT 12–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1.10 Procedure INSERT_TEXT 12–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.2.2 Description of provided CDI Views for Read Access 12–9. . . . . . . . . . . . . . . . . . . . . 12.2.2.1 View CDI_GENERATION_INFO 12–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.2 View CDI_REPORT 12–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.3 View CDI_CODE 12–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.4 View CDI_TEXT 12–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2.5 View CDI_XREF_LIST 12–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.2.3 Program example for using CDI in ADA 12–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.3 CDI Maintenance in I_MDB 12–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13 CONSISTENCY CHECKER 13–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.1 Overview 13–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.2 Executing Consistency Checks 13–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2.1 Consistency Checker Main Window 13–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2.2 Consistency Checker File Menu 13–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2.3 Post Processor Window 13–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.2.3.1 Manual Post Processor Start 13–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2.3.2 Automatic Post Processor Start 13–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.2.3.2.1 Post Processor Detail Data 13–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.3 Consistency Checker Messages 13–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.4 Consistency Status 13–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4.1 Consistency Status of a CDU (User Tree) Version 13–14. . . . . . . . . . . . . . . . . . . . . . . 13.4.2 Consistency Status of a CCU Version 13–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4.3 Consistency Status by different Error Cases 13–15. . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.4.3.1 Error in End Item 13–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4.3.2 Error between End Items 13–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.4.3.2.1 CDU Scope 13–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –x


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.2.2 CCU Scope 13–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4.3.3 Attribute or Foreign Key Aggregate is not unique in Scope 13–18. . . . . . . . .

13.4.3.3.1 CCU Scope 13–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4.3.3.2 CDU Scope 13–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.4.3.4 Reference Out of Scope 13–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4.3.5 Reference OK 13–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4.3.6 Too many References 13–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.4.3.6.1 MINIMUM = 1, MAXIMUM = 1 13–22. . . . . . . . . . . . . . . . . . . . . . . . . 13.4.3.6.2 MINIMUM =1, MAXIMUM = 2 13–25. . . . . . . . . . . . . . . . . . . . . . . . . .

13.4.3.7 Error between End Items 13–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4.3.8 Uniqueness Violation 13–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.4.3.8.1 MAXIMUM = 1 13–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.4.3.8.2 MAXIMUM = 2 13–32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.5 predefined consistency checks 13–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6 user defined consistency checks 13–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.6.1 User defined PL/SQL Procedures 13–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.2 Check Categories and Check Classes 13–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.6.2.1 Table CC_CATEGORIES 13–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.2.2 Table CC_CLASSES 13–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.6.3 Consistency Checker High Level Program Flow 13–37. . . . . . . . . . . . . . . . . . . . . . . . 13.6.4 Package CC_SETUP 13–39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.6.4.1 Procedure REMOVE_ALL_CHECKS 13–39. . . . . . . . . . . . . . . . . . . . . . . . . 13.6.4.2 Procedure REMOVE_PROJECT_CHECKS 13–39. . . . . . . . . . . . . . . . . . . . . 13.6.4.3 Procedure REMOVE_CHECK 13–39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.4.4 Procedure INSERT_CHECK 13–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.4.5 Procedure ADD_MESSAGE_TEXT_TO_CHECK 13–42. . . . . . . . . . . . . . . 13.6.4.6 Procedure ADD_TYPE_TO_CHECK 13–43. . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.4.7 Procedure ADD_FIXED_STATEMENT_TO_CHECK 13–43. . . . . . . . . . . . 13.6.4.8 Procedure ADD_DYN_STATEMENT_TO_CHECK 13–44. . . . . . . . . . . . . .

13.6.5 Error Reporting Procedures 13–45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.5.1 Procedure REPORT_CHECK_IN_END_ITEM_NOK 13–45. . . . . . . . . . . . . 13.6.5.2 Procedure REPORT_CHECK_BETWEEN_EIS_NOK 13–48. . . . . . . . . . . . 13.6.5.3 Procedure REPORT_CHECK_UNIQUE_NOK 13–51. . . . . . . . . . . . . . . . . . 13.6.5.4 Procedure REPORT_CHECK_IN_SCOPE_NOK 13–53. . . . . . . . . . . . . . . . . 13.6.5.5 Procedure REPORT_ERROR_BETWEEN_END_ITEMS 13–54. . . . . . . . . . 13.6.5.6 Procedure REPORT_MISSING_REFERENCE 13–55. . . . . . . . . . . . . . . . . . 13.6.5.7 Procedure REPORT_TOO_MANY_REFERENCES 13–56. . . . . . . . . . . . . . 13.6.5.8 Procedure REPORT_REFERENCE_OK 13–57. . . . . . . . . . . . . . . . . . . . . . . . 13.6.5.9 Procedure REPORT_UNIQUENESS_VIOLATION 13–58. . . . . . . . . . . . . . .

13.6.6 Create Consistency Checks 13–59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.6.1 Consistency Checker Setup Script 13–59. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.6.6.1.1 Description of Procedure Parameters 13–59. . . . . . . . . . . . . . . . . . . . . . . 13.6.6.1.2 Simple Case 13–60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.6.1.3 Complex Case 13–62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.6.6.2 Check Procedure 13–64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.7 consistency checker in batch mode 13–66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xi


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


14 MAPPING 14–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1 CGS Mapping 14–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.2 User Defined Mapping 14–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2.1 Mapping in a CDU scope 14–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2.2 Mapping in a CCU scope 14–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15 MDA BATCH DATA ENTRY FACILITY 15–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1 Batch data Entry Aggregate Loading 15–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.1 General Overview of Aggregate Loading 15–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1.1.1 BDE Provided Operations 15–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.1.1.1 BDE LOAD Operation 15–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.1.1.2 BDE STORE Operation 15–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.1.1.3 BDE RESET Operation 15–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1.2 BDE Input Files 15–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.2.1 BDE Batch Configuration File 15–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1.2.1.1 Configuration File Format 15–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.2.1.1.1 Configuration File Header 15–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.2.1.1.2 Configuration File Body (File/Aggregate Identification) 15–7. . . . . . . 15.1.2.1.1.3 Configuration File Examples 15–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1.2.2 User Data Files 15–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.2.2.1 General input file set-up for BDE jobs 15–10. . . . . . . . . . . . . . . . . . . . . . 15.1.2.2.2 Data File Format / Record Structure 15–11. . . . . . . . . . . . . . . . . . . . . . .

15.1.2.2.2.1 Formatted ASCII Data Files 15–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.2.2.2.2 Unformatted Large Data (Streams) 15–13. . . . . . . . . . . . . . . . . . . . . . . . 15.1.2.2.2.3 Unformatted Large Data combined with other attribute types 15–14. . . .

15.1.2.2.3 MDA Data Types supported by BDE 15–14. . . . . . . . . . . . . . . . . . . . . . . 15.1.3 BDE Output Files 15–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1.3.1 BDE Reports 15–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.3.1.1 BDE Load Operation Report 15–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.3.1.2 BDE Load Error Report 15–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.3.1.3 BDE Store Operation Report 15–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.3.1.4 Oracle’s SQL*Loader Reports 15–16. . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1.4 Using BDE 15–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.4.1 Prerequisites 15–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1.4.1.1 BDE User Account 15–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.4.1.2 BDE User’s Home Directory Structure 15–17. . . . . . . . . . . . . . . . . . . . . 15.1.4.1.3 BDE Runtime Options 15–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1.4.2 BDE Job Preparation and Execution 15–19. . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.4.2.1 Operational Phases 15–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.4.2.2 BDE Execution Summary and Return Codes 15–23. . . . . . . . . . . . . . . . . 15.1.4.2.3 BDE Usage Examples 15–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1.4.3 Summary of Constraints 15–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.5 BDE Error Messages 15–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.1.5.1 Overview 15–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.5.2 System Errors 15–29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.5.3 Usage Errors 15–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.1.5.4 Data Errors / Item Identifier Errors 15–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.5.5 Other Errors (system / programming errors, exceptions, etc.) 15–32. . . . . . . .

15.2 Batch data Entry Create End Item 15–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.1 General Description of the BDE_CEI 15–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.2 BDE_CEI Provided Operations 15–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.2.2.1 BDE_CEI_LOAD 15–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.2.2 BDE_CEI_STORE 15–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.2.3 BDE_CEI_RESET 15–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.2.3 BDE_CEI Input Files 15–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.4 BDE_CEI Batch Configuration File 15–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.5 User Data Files 15–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.2.5.1 General input file set-up for BDE_CEI jobs 15–35. . . . . . . . . . . . . . . . . . . . . 15.2.6 BDE_CEI Output Files 15–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.2.6.1 BDE_CEI Reports 15–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.6.1.1 BDE_CEI Load Operation Report 15–36. . . . . . . . . . . . . . . . . . . . . . . . . 15.2.6.1.2 BDE_CEI Load Error Report 15–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.6.1.3 BDE_CEI Store Operation Report 15–37. . . . . . . . . . . . . . . . . . . . . . . . .

15.2.7 Using BDE_CEI 15–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.7.1 Prerequisites 15–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.2.7.1.1 BDE_CEI User account attributes 15–38. . . . . . . . . . . . . . . . . . . . . . . . . 15.2.7.1.2 Configure the users directory structure 15–38. . . . . . . . . . . . . . . . . . . . .

15.2.7.1.2.1 Directory ”input” 15–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.7.1.2.2 Directory ”report” 15–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.2.7.1.3 BDE_CEI Runtime Options 15–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.7.1.3.1 BDE_CEI Batch Configuration File Specification 15–39. . . . . . . . . . . . 15.2.7.1.3.2 BDE_CEI Error Limit 15–39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.2.7.2 BDE_CEI Invocation 15–39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.7.2.1 Invocation of BDE_CEI 15–40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.2.7.3 BDE_CEI General Constraints 15–42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.8 BDE_CEI Error Messages 15–43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.2.8.1 Error Overview 15–43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.8.2 User Data Errors 15–44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2.8.3 Other Errors (system / programming errors, Database problems, etc.) 15–44.

15.3 Batch Data Entry Create Configuration Unit Facility 15–46. . . . . . . . . . . . . . . . . . . . . . . . 15.3.1 General Description 15–46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.2 Provided Operations 15–47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.3.2.1 Load operation 15–47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.2.2 Store operation 15–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.2.3 Reset operation 15–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.3.3 BDE_CU Input Files 15–49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.3.1 BDE_CU Batch Configuration File 15–49. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.3.2 User Data File 15–49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.3.3.2.1 Create CDU without Version 15–49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.3.2.2 Create CDU Version 15–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.3.2.3 Create CCU without Version 15–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.3.2.4 Create CCU Version 15–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xiii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.3.3.2.5 Create CCU references 15–50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.4 BDE_CU Output Files 15–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.3.4.1 Load Activity Report 15–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.4.2 Load Area File 15–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.4.3 Load Error Report 15–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.4.4 Store Activity Report 15–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.4.5 Store Error Report 15–52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.4.6 Reset Activity Report 15–52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.3.5 Using BDE_CU 15–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.5.1 User Privilege 15–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.5.2 User Directory Structure 15–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.5.3 Runtime Options 15–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.3.5.3.1 BDE Configuration File Specification 15–53. . . . . . . . . . . . . . . . . . . . . . 15.3.5.3.2 BDE Error Limit 15–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.3.5.4 BDE_CU Invocation 15–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.6 BDE_CU Constraints 15–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.3.6.1 BDE_CU General Constraints 15–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.6.2 Create CDUs in batch mode 15–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.6.3 Create CDU versions in batch mode 15–56. . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.6.4 Create CCUs in batch mode 15–56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.6.5 Create CCU versions in batch mode 15–57. . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.6.6 Create CCU references in batch mode 15–57. . . . . . . . . . . . . . . . . . . . . . . . . .

15.3.7 BDE_CU Error Messages 15–62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.7.1 Overview 15–62. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.7.2 System Errors 15–63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.7.3 Usage Errors 15–63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.7.4 Data Errors 15–63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.7.5 API errors 15–64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3.7.6 Other Errors (system / programming errors, exceptions, etc.) 15–64. . . . . . . .

15.4 CREATE_BDE_FILES 15–65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.1 General Description 15–65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.2 Provided Operations 15–65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.4.2.1 General 15–65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.2.2 CREATE_BDE_FILES Store CCU 15–66. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.2.3 CREATE_BDE_FILES Store CDU 15–66. . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.4.3 CREATE_BDE_FILES Output Files 15–68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.3.1 BDE Configuration File 15–68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.3.2 BDE_CEI Input Data File 15–68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.3.3 BDE_CU Batch Configuration File 15–69. . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.3.4 BDE_CU User Data File 15–69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.3.5 BDE Aggregate Data Files 15–69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.4.4 Using CREATE_BDE_FILES 15–71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.4.1 CREATE_BDE_FILES Invocation 15–71. . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.4.4.1.1 Invocation via I_MDB 15–71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.4.1.2 Invocation via C–Shell 15–71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.4.4.2 The CREATE_BDE_FILES main window 15–72. . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xiv


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.4.5 CREATE_BDE_FILES Constraints 15–74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.6 CREATE_BDE_FILES Error Messages 15–75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15.4.6.1 Overview 15–75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.6.2 System Errors 15–75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4.6.3 Other Errors (system / programming errors, exceptions, etc.) 15–75. . . . . . . .

16 CSS DATA AND INTERFACE HANDLING 16–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.1 CSS Start 16–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17 ADVANCED OPERATIONS 17–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1 Foreign Key Support 17–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.2 Flexible Tool Invocation 17–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.3 CLS Interface Handling 17–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17.3.1 CLS in Manual Mode 17–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.3.2 CLS in Batch Mode 17–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18 DETAIL DATA EDITOR 18–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.1 DDED Start 18–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2 DDED Main Window 18–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.3 Data Entering for NON–COMPOSITE Aggregates 18–5. . . . . . . . . . . . . . . . . . . . . . . . . .

18.3.1 Single Record Aggregate data editing 18–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.3.2 Multi Record Aggregate data editing 18–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.4 Data Entering for Composite Aggregates 18–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.5 Pathname Support (PNS) 18–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19 CUSTOMER SPECIFIC IMPLEMENTATIONS 19–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.1 Mission Built Facility – MBF 19–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.1.1 MBF Identifier Support 19–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.1.2 Foreign Key Support 19–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.1.3 Consistency Checker – MBF related special checks 19–1. . . . . . . . . . . . . . . . . . . . . . 19.1.4 Batch Data Entry 19–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.2 Matrix–X Integration 19–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

20 ADD SYSTEM TREE VERSION 20–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.1 Start the addition of CCU/CDU Version 20–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.2 System Tree Version Window 20–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.3 CCU/CDU Version Browser 20–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

20.3.1 Single/Multi Selection on ’System Tree Path’ or ’CDU Path’ list 20–4. . . . . . . . . . . 20.3.2 Single/Multi Selection on Version(s) list 20–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.3.3 Command Menu 20–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.3.4 Edit Menu 20–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.3.5 Version List Menu 20–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

20.4 CCU/CDU Version Collection 20–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20.4.1 Collected List Menu 20–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

20.5 Progress Window 20–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xv


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


20.6 CCU and CDU Version Browser Filter 20–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21 EXCELMDB 21–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1 Overview 21–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.1.1 Structure of a Mixed Spreadsheet 21–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1.2 Structure of a Multirecord Spreadsheet 21–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.2 Getting started 21–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.1 Client installation (Windows PC) 21–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.2 Server installation 21–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.2.2.1 REXEC/FTP 21–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.2.2 SSH/SFTP 21–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.2.3 JAVA installation 21–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.2.3 ExcelMDB Client Configuration 21–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.3.1 Connection Groups 21–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.3.2 Connection Details 21–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.2.4 Start ExcelMDB 21–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.3 ExcelMDB functionality 21–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.1 Open MDB Browser 21–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.2 Create Excel spreadsheet header 21–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.3 Modify Excel Spreadsheet Header 21–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.4 Update Excel Spreadsheet 21–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.5 Read Enditems from CCU/CDU 21–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.6 Write Worksheet Data Into MDB 21–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.7 Write Workbook Data Into MDB 21–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.8 Extract CDU Versions 21–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.9 Create Difference File (Pathname by Pathname) 21–12. . . . . . . . . . . . . . . . . . . . . . . . 21.3.10 Create Difference File (Cell by Cell) 21–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.3.11 Convert .txt –> .xls (MDB Template) 21–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.4 Batchmode 21–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4.1 Starting the ExcelMDB batchmode 21–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4.2 The ExcelMDB batchmode GUI 21–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.4.2.1 The main menu 21–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4.2.2 The toolbar 21–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.4.2.3 The job table 21–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.4.3 Project execution 21–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.5 Requirements 21–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.6 LIMITATIONS 21–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22 FILE LOADER/EXTRACTOR 22–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.1 Overview 22–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2 File LOADER 22–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22.2.1 Pre–conditions 22–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.2 Start on Enditem of Type EXTERNAL_FILE 22–1. . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.3 Start on CCU or CDU Version 22–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22.2.3.1 Without Loader Info File 22–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xvi


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


22.2.4 Use of Loader Info File (obsolete) 22–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22.3 file extractor 22–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.1 Start on Enditem of Type EXTERNAL_FILE 22–3. . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.2 Start on CCU or CDU Version 22–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.3 Common 22–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.4 Batch Mode 22–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

C EXAMPLES OF MDA REPORTS C-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C-1 CCU Version References Report C-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C-2 CDU Difference Report C-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C-3 CCU Version Report C-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C-4 CDU Detail Report C-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C-5 CDU Name Tree Report C-19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C-6 System Tree Difference Report C-22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C-7 CCU Cross Reference Report C-26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C-8 CCU End Item Xref Report C-28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D EXAMPLES OF MDA API PROCEDURES D–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D-1 Data Access Procedure D–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D-2 Usage of MDB_API Procedures D–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D-3 Using Write Procedures with the Data–API D–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E EXAMPLE OF BDE SESSIONS E–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E-1 Batch Configuration Files E–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E-2 Input Data Files E–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E-3 BDE Execution / Sample runs E–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E-4 BDE Log Files for Case 1: Nominal Operation E–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E-5 BDE Log Files for Case 2: Non–Nominal Operation E–34. . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xvii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 1. I_MDB Navigator 4–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2. TOOL Properties 4–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3. Options Properties 4–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4. Commands on CDU Root Node 4–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4. I_MDB: System Tree Version 4–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5. Translator 4–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6. Direct End Item Access via end–item type. 4–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7. Open detailed data for selected end–item (via end item type) 4–14. . . . . . . . . . . . . . . . . . .

Figure 8. System Tree Version Import / Restore Window 5–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 9. System Tree Versions 5–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 10. System Tree Versions window 6–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 11. Create Mission window 6–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 12. ’Delete Mission’ confirmation window 6–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 13. Browse CCU Version 7–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 14. Selected System Tree Root Node within a specific System Tree Version 7–3. . . . . . . . . .

Figure 15. CCU Versions 7–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 16. Element Node with its System Tree Version and System Tree Nodes 7–5. . . . . . . . . . . . .

Figure 17. Create System Tree Node window 7–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 18. Delete System Tree Node 7–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 19. Copy System Tree Node 7–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 20. System Tree Node Properties 7–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 21. Create System Tree Version 7–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 22. System Tree Version window after creating a new sys. tree vers. by copy operation 7–13.

Figure 23. Confirmation window 7–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 24. Report Generator ’System Tree Version’ 7–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 25. System Tree Version Data Distribution / Data Archiving window 7–17. . . . . . . . . . . . . . . .

Figure 26. System Tree Version Import / Restore Window 7–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 27. I_MDB: System Tree Versions 7–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 28. System tree version show exports window 7–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 29. System tree version show imports window 7–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 30. System Tree Version properties 7–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 31. Open a System Tree Node by executing a File command 8–3. . . . . . . . . . . . . . . . . . . . . .

Figure 32. Create CDU 8–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 33. I_MDB_Navigator after creating a CDU Root Node 8–4. . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 34. Create user tree node 8–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 35. Node type list help 8–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 36. User Tree Nodes area after creating a virtual Node 8–7. . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 37. I_MDB Navigator with Node Name for the Paste operation 8–8. . . . . . . . . . . . . . . . . . . .

Figure 38. User Tree Nodes area after copying a subtree 8–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xviii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 39. I_MDB Navigator with Node Name for the Move operation 8–12. . . . . . . . . . . . . . . . . . . .

Figure 40. User Tree Node Properties 8–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 41. MDM_IO_BOARD 8–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 42. Engineering Support Information 8–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 43. Channel Description 8–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 44. Detailed Channel Description 8–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 45. SIGNAL_TYPE list 8–18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 46. Consistency Checker 8–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 47. CDU Versions 8–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 48. Create CDU Version 8–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 49. User List 8–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 50. CDU domain list help 8–23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 51. CDU Versions area after creating an empty CDU Version 8–23. . . . . . . . . . . . . . . . . . . . . .

Figure 52. CDU Version List 8–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 53. CDU Version List 8–25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 54. CDU Versions area after creating a new Version by copying a Test Version 8–26. . . . . . . .

Figure 55. CDU Versions area after creating a new Issue of a CDU Version 8–27. . . . . . . . . . . . . . . .

Figure 56. CDU Versions area after creating a new Issue by copying a Test Version 8–29. . . . . . . . . .

Figure 57. CDU Versions area after creating a Revision of a CDU Version 8–30. . . . . . . . . . . . . . . . .

Figure 58. CDU Versions area after creating a Revision by copying a Test Version 8–32. . . . . . . . . . .

Figure 59. Confirmation window 8–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 60. Report Generator 8–34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 61. CDU Version Data Distribution / Data Archiving window 8–35. . . . . . . . . . . . . . . . . . . . .

Figure 62. CDU Version Import / Restore Window 8–36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 63. CDU Version Properties 8–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 64. CDU version show exports window 8–39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 65. CDU show imports window 8–41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 66. User List 8–43. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 67. CDU Versions area after updating the status of a CDU Version to ’REVIEW’ 8–44. . . . . .




Figure 71. User List 8–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 73. CDU Versions area after creating an empty CDU Test Version 8–49. . . . . . . . . . . . . . . . . .

Figure 74. CDU Versions area after creating a Test Version by copying a CDU Version 8–50. . . . . . .

Figure 75. CDU Versions area after creating a Test Version by copying an old one 8–51. . . . . . . . . . .

Figure 76. Concept of Restricted CDU Version 8–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 77. CDU Version Restrictions Administration 8–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xix


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:




Figure 80. User List 8–57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 81. CDU Versions area after creating a Restricted Version by copying a CDU Version 8–58. .

Figure 82. Create CCU 9–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 84. Consistency Checker 9–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 85. Create CCU Version 9–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 86. Created CCU Version 9–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 87. Report Generator 9–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 88. Maintain References 9–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Figure 90. CDU Browser 9–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 91. CU Version Manager main window showing CCU reference view in CREATION mode

9–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 92. 9–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 93. The CCU tree popup menu 9–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 94. The CU version selection window 9–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 95. CCU Version Data Distribution / Data Archiving window 9–22. . . . . . . . . . . . . . . . . . . . .

Figure 96. CCU Version Import / Restore Window 9–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 97. Selected System Tree Root Node within a specific System Tree Version 9–25. . . . . . . . . .

Figure 98. CCU Versions 9–26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 99. CCU Versions of another CCU 9–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 100.CCU Version Properties 9–28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 101.CCU version show exports window 9–29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 102.CCU show imports window 9–31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 103.API Components 11–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 104.End–Item View 11–13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 105.CDI Generation Flow Example 12–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 106.CDI and CCU structure 12–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 107.CDI Maintenance on a selected CCU version 12–14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 108.Maintain CDI’s window 12–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 109.Consistency Checker Main Frame 13–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 110.Consistency checker file menu 13–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 111. Create a new profile file 13–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 112.Open a profile file 13–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 113.Save a profile file 13–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 114.Save As 13–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 115.Save As 13–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xx


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 116.Post Processor Window 13–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 117.Post Processor Window 13–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 118.Post Processor Detail Data Window 13–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 119.Post Processor Detail Data Window 13–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 120.Check in end item is not ok 13–15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 121.Check between end items is not ok 13–16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 122.Check between end items is not ok 13–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 123.Attribute or Foreign Key Aggregate is not unique in CCU Scope 13–18. . . . . . . . . . . . . . . .

Figure 124.Attribute or Foreign Key Aggregate is not unique in CDU Scope 13–19. . . . . . . . . . . . . . . .

Figure 125.Reference out of Scope 13–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 126.Reference out of CDU 13–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 127.Too many References (MINIMUM = 1, MAXIMUM = 1) 13–22. . . . . . . . . . . . . . . . . . . . .






Figure 133.Error between End Items 13–27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





Figure 138.Uniqueness Violation (MAXIMUM = 1) 13–30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .





Figure 143.Uniqueness Violation (MAXIMUM = 2) 13–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 144. Consistency Checker high level flow diagram . . . . . .

13-37

Figure 145.REPORT_CHECK_IN_END_ITEM_NOK 13–45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 146.REPORT_CHECK_BETWEEN_EIS_NOK 13–48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 147.REPORT_CHECK_UNIQUE_NOK 13–51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 148.User defined End–Item–Types with mixed Aggregates 14–2. . . . . . . . . . . . . . . . . . . . . . . .

Figure 149.User defined End–Item–Type with User defined Aggregates 14–3. . . . . . . . . . . . . . . . . . .

Figure 150.Transformation of a mixed User defined Data Structure 14–3. . . . . . . . . . . . . . . . . . . . . . .

Figure 151.Transformation of a single User defined Data Structure 14–4. . . . . . . . . . . . . . . . . . . . . . .

Figure 152.Operational Mapping Scenario 14–4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 153.Initiating the CDU mapping procedure 14–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 154.Initiating the CCU mapping procedure 14–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xxi


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 155.Simplified Overview of BDE 15–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 156. General Structure of BDE Configuration File 15–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 157. Configuration File Header with CDU as target configuration 15–6. . . . . . . . . . . . . . . . . . .

Figure 158. Configuration File Header with CCU as target configuration 15–6. . . . . . . . . . . . . . . . . .

Figure 159. Format of File / Aggregate specification in Configuration File body 15–7. . . . . . . . . . . . .

Figure 160. Configuration File Example (1) 15–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 161. Configuration File Example (2) 15–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 162.General input files set-up 15–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 163.Invalid file / aggregate combinations 15–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 164. Record Structure of BDE Input Data File 15–12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 165.Loader Control File and corresponding data file (example) 15–13. . . . . . . . . . . . . . . . . . . . .

Figure 166. Required Home Directory structure 15–17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 167. BDE Operational Phases 15–19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 168.BDE Preparation Phase 15–20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 169.BDE Load Phase 15–21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 170.BDE Storage Phase 15–22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 171. BDE Return Codes 15–24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 172.Simplified Overview of BDE_CEI 15–33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 173.General input file set-up 15–35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 174.Required BDE_CEI directory structure 15–38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 175.BDE_CEI Foreground Return Codes 15–41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 176.Simplified Overview of BDE_CU 15–47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 177.Description of the BDE_CU batch configuration file 15–49. . . . . . . . . . . . . . . . . . . . . . . . .

15–53. . . . . . . . .

Figure 178.Required BDE_CU directory structure 15–53. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 179.BDE_CU Process 15–54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 180.BDE_CU Foreground Return Codes 15–55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 181.Double referenced CDU version 15–57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 182.Double referenced CDU node 15–58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 183.CCU reference to same system tree node 15–59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 184.CCU reference out of subtree 15–59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 185.Double referenced CCU version 15–59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 186.Double referenced system tree node 15–60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 187.Double referenced CCU 15–61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 188.Reference to a CCU version with a CDU version reference out of subtree 15–61. . . . . . . . .

Figure 189.Overview of CREATE_BDE_FILES 15–66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 193. The CREATE_BDE_FILES main window 15–72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 194.Entering the CSS 16–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 195.CSS Tools start via the ’CSS Scope Check’ Window 16–2. . . . . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xxii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 196.Tool start via CCU Version window 17–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 197.Tool Parameter Entry 17–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 198.Starting the Detail Data Editor 18–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 199.DDED Main Window 18–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 200.DDED window showing a single–record aggregate 18–5. . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 201.DDED window showing a single–record aggregate 18–6. . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 202.DDED window showing a composite aggregate with Foreign Key and DirscriminantIdentifier 18–10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 203.DDED window showing a composite aggregate with discriminant 18–11. . . . . . . . . . . . . . .

Figure 204.DDED window showing composite aggregate after discriminant selection 18–12. . . . . . . .

Figure 205.DDED window showing a composite aggregate with a Foreign Key 18–14. . . . . . . . . . . . .

Figure 206.Pathname Support Window 18–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 207.Direct end item access via Signal PUI 19–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 208.MX_MODEL definition in DADI–MA 19–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 209.Matrix–X Editor start 19–3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 210. (I_MDB: System Tree Versions) 20–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 211. (IMDB: System Tree Version) 20–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 212. (CCU/CDU Version Browser, main window in CCU version mode) 20–3. . . . . . . . . . . . .

Figure 213. (CCU/CDU Version Browser, main window in CDU version mode) 20–4. . . . . . . . . . . . .

Figure 214. (Command Menu) 20–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 215. (Edit Menu) 20–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 216. (Version List Menu) 20–7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 217. (CCU Version Collection) 20–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 218. (CDU Version Collection) 20–8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 219. (Progress window) 20–9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 220. (Browser Filter window in CCU incl. CDUs mode) 20–10. . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 221. (Browser Filter window in CDU mode) 20–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 222.An ExcelMDB spreadsheet of type MIXED 21–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 223.An ExcelMDB spreadsheet of type MULTIRECORD 21–3. . . . . . . . . . . . . . . . . . . . . . . . .

Figure 224. ExcelMDB Login Window 21–5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 225.The MDB Browser window 21–6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 226. The ExcelMDB Spreadsheet Header Creator window 21–8. . . . . . . . . . . . . . . . . . . . . . . .

Figure 227. The Enditem Type and Pathname selection window 21–10. . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 228. The Write Confirmation window 21–11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 229.The Project Output window showing a finished Read Job 21–17. . . . . . . . . . . . . . . . . . . . . .

xxiii

CGS–RIBRE–SUM–00032 03.07.2015– –xxiii


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


This page is intentionally left blank.

1–1

CGS–RIBRE–SUM–00032 03.07.2015– –1–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


1 INTRODUCTION

1.1 IDENTIFICATION AND SCOPE

This document is the Part 003 – MDA Reference Manual of the MDA Users and Operations Manual. Itprovides a reference to the most fundamental and commonly used features of MDA.

1.2 PURPOSE

The Mission Database Application (MDA) constitutes the set of utilities which support or enable variousactivities typically performed during mission preparation. As such its main objective is to prepare for andsupport the development of space segments and missions.

As part of MDA the Mission Database (MDB) is viewed as the central repository of information about flightconfigurations. In order to perform flight configuration operations this kind of information is stored and ma-nipulated in the database together with Hardware and Software configuration information about flight ele-ments, Payloads and Ground Support Equipment.

2–2

CGS–RIBRE–SUM–00032 03.07.2015– –2–2


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–0015–00 4/– 04.08.1997

System to MDA Interfaces

2.2 REFERENCE DOCUMENTS

2.2.1 ADD 1216 401 002 2/A 18.06.1993

MDA Architectural Design Document

2.2.2 COL–RIBRE–MA–0046 1/– 15.09.1997

SID Range Tool Users and Operation Maunal

3–2

CGS–RIBRE–SUM–00032 03.07.2015– –3–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3 KEY FEATURES

Since the MDA operates mainly on a database, its key features are based on database–oriented functions fordifferent purposes:

� data entry and retrieval interactively or in batch modeto allow users to access and manipulate data (insert/create, retrieve/read, update/change,delete)

� concurrent access to the data to many users at once (transaction management)

� users access rightsto limit access to data by unauthorized users

� report generationin a user–specified way

� consistency checkingto check the validity of data

� version controlto keep the evolution of data over time comprehensible

� configuration managementto configure only specific parts of data for special purposes like testing

� data distributionfor importing and exporting data to/from different users at different locations

The underlying conceptual model allowing these key features are described in Part 001 Manual: the MDAIntroduction.

3–2

CGS–RIBRE–SUM–00032 03.07.2015– –3–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


4 COMMON OPERATIONS

In this section all common operations like, how to navigate through the Name Tree, or how toselect a specific kind of node, or version are described.

4.1 NAVIGATING THROUGH THE NAME TREE

To work on e.g. any kind of configuration or detailed end item data you first have to navigatethrough the Name Tree until you have reached the necessary Configuration or Name Tree levelwhich allows you to do so.

Having started the Interactive Mission DataBase (I_MDB), the ’I_MDB Navigator’ window willbe displayed, which is the starting point for all navigations.

4.1.1 Navigator window

Figure 1. I_MDB Navigator

The ’I_MDB Navigator’ window is divided into four areas:

� the area in the upper part of the window containing menu buttons which you can pull-down

� the area in the middle part of the window (Pathname area) listing the Pathname of theName Tree Node you have opened; initially you will see the Root Node of the NameTree ’\’.

� the area in the lower part of the window listing the child nodes of the Name Tree Nodeyou have opened. The area name depends on the Name Tree and Configuration level.Initially you will see the Element Configurations area containing the predefined’SSMB_TEST’.

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� the area which is on the left or right side of children node area named paging area. Thebuttons in this area conduced to control the children list.

4.1.1.1 Paging Mechanism

The I_MDB has a mechanism to administrate big lists because the loading and displaying of biglists takes a lot of time. The complete list was loading in a dynamic link list and only a definedamount of the big list items will be display in the children area. Stepping through the link list ispossible with the 4 button on the left/right side of the children list.

4.1.1.1.1 Goto the Top

The beginning of the list is shown in the children area.

4.1.1.1.2 One Page down

Jump one page down in the children area.

4.1.1.1.3 Goto a Page

Jump to the selected page in the children area.

4.1.1.1.4 One Page up

Jump one page up in the children area.

4.1.1.1.5 Goto the Bottom

The end of the list is shown in the children area.

4.1.1.2 Pulldown Menus

MDA provides three different kinds of menu buttons in the upper part of the ’I_MDB Navigator’window, which you can pulldown: ’File’, ’Edit’ and ’Properties’.

In the current MDA Version, the button ’View’ does not provide any operation you can use.

Move the cursor to one of the buttons and hold down the right mouse button. The correspondingpulldown menu will be displayed. The contents of the pulldown menus differ depending on whichoperations the MDA allows at specific Configuration and Name Tree levels you have been navi-gating to.

The notation for the execution of a command in one of these pulldown menus is <menu button>–><command>, e.g. Edit–>Delete or File–>Import.... A command ending with ’...’ denotes that a popup menu will be displayed if you execute the com-mand.

4.1.1.2.1 File

The File button provides different pulldown menus depending on which specific Configurationand Name Tree level you are operating on.

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


E.g. if you are on the Element Configuration level the button provides the commandsFile–>Create Element Configuration... and File–>Import.... If you select the Element Configuration Node e.g. ’SSMB’, the button provides the commandsFile–>Show System Tree Versions..., File–>Set Default Starting Point and File–>Import....

4.1.1.2.2 Edit

The menu button Edit is usually used to operate on common nodes of the Name Tree like SystemTree or User Tree nodes. It contains pulldown menus to create, delete or copy node information.The edit operations are enabled if a node is selected.

4.1.1.2.3 Properties

The Properties button contains three different kinds of commands:

4.1.1.2.3.1 Properties–>Selection

- The Properties–>Selection... command is enabled if you have selected any commonName Tree Node like a virtual System Tree Node or a virtual User Tree Node or even anEnd Item. Notice that this command is disabled if you have selected a System Tree– orCDU Root Node for which you can only view the properties of their different Versions(refer to the ’Open’ operation).

4.1.1.2.3.2 Properties–>Tool

- Executing the Properties–>Tool... command, MDA displays the MDA ’TOOL Proper-ties’ window giving information about the currently used MDA, like MDA Version No.,MDB Instance and Version, the MDB User account you are working under and if youhave ’Configuration Management’ (CM) privilege or not. This command can always beexecuted, no matter if you have selected any node or not.

Figure 2. TOOL Properties

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


4.1.1.2.3.3 Properties–>Options

Figure 3. Options Properties

The options menu allows some adjustments for IMDB modules:

Add System Tree VersionStarting with Scope: CCU or CDU: Sets the starting option ( scope CCU/CCU ) of ’Add SystemTree Version’

Copy CDIs: Set the option whether the CDIs will be cpoied or not.

CCU BrowserCCU Browser Page Size: Sets the number of lines which will be displayed with the paging mecha-nism.

CDU BrowserCCU Browser Page Size: Sets the number of lines which will be displayed with the paging mecha-nism.

Maintain ReferencesCCU Lines: Sets the number of lines which displayes the referened CCU versions.

CDU Lines: Sets the number of lines which displayes the referened CDU versions.

NavigatorStart PNS: Starts the PNS at the beginning of the I_MDB session.

Page Placement: Sets the page panel to the left/right side of the list.

Lines: Sets the number of lines which will be displayed with the paging mechanism.

4.1.1.3 Pulldown Menus in the lower part of the ’I_MDB Navigator’

MDA also provides pulldown menus in the lower part of the ’I_MDB Navigator’ window, whichcan be activated by moving the cursor into the lower part of the ’I_MDB Navigator’ window,

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


selection of an object (ref. to next section) and holding down the right mouse button. The corre-sponding pulldown menu will be displayed usually providing some of the File and Edit com-mands already described. In both cases the same operation is performed.

Figure 4. Commands on CDU Root Node

4.1.2 Selecting an Object

There are several different kinds of objects the user can select in order to execute specific com-mands, like enabling the navigation into a specific System Tree or CDU Version.

The selectable objects are:

� Name Tree nodes, like

- Element Configuration,- System Tree Nodes and- User Tree and CDU Root Nodes including End Items

� list entries, like

- CCU names,- System Tree Versions,- CDU Versions,- CDU Test Versions or- CCU Versions and also- owner,- CDU domain

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


- etc.

� choices, like

- New Version or New Issue,- Screen, Printer or File,- etc.

� lines for text entries, like

- Description,- Filename,- etc.

To select an object, move the cursor to the object and click on the left mouse button. The selectedobject is somehow marked e.g. by a (high–lighted) surrounding box or by showing a tick in thecorresponding selection box.

Notice:The selection of e.g. a specific System Tree Version does not navigate into this Version.By selecting an object is only marked. Execute a command like Open to perform an operationon the selected object.

4.1.3 Deselecting an Object

To deselect an object, move the cursor to the selected object and click on the left mouse button.The marking will be deleted.

4.1.4 Open

In order to navigate to specific levels of the Name Tree or into specific Configurations executethe ’Open’ operation.

To navigate:

� to a specific level of the Name Tree: execute the operation on a selected node in thePathname area or the lower part area of the ’I_MDB Navigator’ window to be able tooperate on its child nodes

� into a specific Version of a System Tree, CDU or CCU: first select the Root Node of thespecific Trees and call the operation to show all existing Versions of them. Then executethe operation on a selected Version entry of the Versions list to be able to operate withinthe selected Version

4.1.4.1 Executing the ’Open’ operation

To execute the ’Open’ operation:

select the desired object and execute File–>Open in the ’I_MDB Navigator’ window

or

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


select the desired object and move the cursor into the lower part of the ’I_MDB Navigator’ win-dow, hold down the right mouse button and execute Open

or

move the cursor to the desired object and double click on the left mouse button.

4.1.4.2 Navigate to the Name Tree Root Node

If while starting the ’I_MDB’ no Default Starting Point is set, MDA automatically opens theName Tree Root Node ’\’ and all existing Element Configurations will be shown in the corre-sponding Element Configurations area. To select an Element Configuration select the elementname.

If you have already navigated to a lower level, execute the ’Open’ operation on the Name TreeRoot Node. In the Pathname area the ’\’ Node is displayed and in the Element Configurations areaall existing Element Configurations are listed.

4.1.4.3 Navigate into a System Tree Version

If you have already navigated to a lower level, execute the ’Open’ operation on the Name TreeRoot Node. In the Pathname area the ’\’ Node is displayed and in the Element Configurations areaall existing Element Configurations are listed.

To Navigate into a System Tree Version:

1. Select a specific Element Configuration and execute File–>Show System Tree Ver-sions... .

A list of all existing System Tree Versions for the selected Element Configuration is displayedshowing the version number and its status.

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 4. I_MDB: System Tree Version

2. Execute the ’Open’ operation on the desired Version as described in section ’Executing

the ’Open’ operation’.

In the ’I_MDB Navigator’ window all existing Child Nodes of the System Tree Root Node withinthe opened System Tree Version are listed in the corresponding System Tree Nodes area. In thePathname area the System Tree Root Node has been added given by its name and its opened ver-sion, e.g. ’SSMB(1)’.

4.1.4.4 Navigate to a specific System Tree Node within a System Tree Version

If you have already navigated to a lower level, just execute the ’Open’ operation on the specificSystem Tree Node in the Pathname area. Otherwise:

To Navigate to a specific System Tree Node within a System Tree Version:

1. Navigate into the corresponding System Tree Version.

2. Execute the ’Open’ operation on each predecessor System Tree Node of the SystemTree Node you are aiming at until you have reached the level where it is listed in theSystem Tree Nodes area.

4.1.4.5 Navigate to a CDU Root Node

If you have already navigated to a lower level, just execute the ’Open’ operation on its father Sys-tem Tree Node in the Pathname area. Otherwise:

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To Navigate to a CDU Root Node:

1. Navigate into a specific System Tree Version.

2. Execute the ’Open’ operation on each predecessor System Tree Node of the CDU Root

Node you are aiming at until you have reached the level where it is listed in the SystemTree Nodes area.

Notice: Each CDU Root Node is listed in the System Tree Nodes area of the ’I_MDB Navigator’window. You can identify a CDU Root Node by its Type which is ’CDU’.

4.1.4.6 Navigate into a CDU (Test) Version

If you have already navigated to a lower level, just execute the ’Open’ operation on the fatherSystem Tree Node of its corresponding CDU Root Node in the Pathname area. Otherwise:

To Navigate into a CDU (Test) Version:

1. Either navigate to the corresponding CDU Root Node and execute File–>Show CDUVersions... or

Execute the ’Open’ operation on the specific CDU Root Node as described in section

’Executing the ’Open’ operation’.

A list of all existing CDU (Test) Versions for the selected CDU Root Node is displayed given theversion number and its status.

2. Execute the ’Open’ operation on the desired Version as described in section ’Executingthe ’Open’ operation’.

In the ’I_MDB Navigator’ window all existing Child Nodes of the CDU Root Node within theopened CDU Version are listed in the corresponding User Tree Nodes area. In the Pathname areathe CDU Root Node has been added given by its name and its opened version, e.g. ’LI-BRARIES(1.0.0)’. If the opened version is a Test Version the added Node name and version is extended by its Test#and MDB Instance separated by ’–’ character, e.g. ’WATERLOOP–1–MPS_DEVELOPMENT’.

4.1.4.7 Navigate to a specific User Tree Node

If you have already navigated to a lower level, just execute the ’Open’ operation on its father UserTree Node in the Pathname area. Otherwise:

To Navigate to a specific User Tree Node:

1. Navigate into a specific CDU Version.

2. Execute the ’Open’ operation on each predecessor User Tree Node of the one you areaiming at until you have reached the level where it is listed in the User Tree Nodes area.

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


4.1.4.8 Navigate to a specific CCU

If you have already navigated to a lower level, just execute the ’Open’ operation on the corre-sponding System Tree Node (to which the specific CCU is attached) in the Pathname area. Other-wise:

To Navigate to a specific CCU:

1. Navigate to the corresponding System Tree Node to which the specific CCU is attached

and select it.

Notice: To navigate to a CCU which is attached to the System Tree Root Node of the correspond-ing System Tree Version, e.g. the ’SSMB’ Node of its System Tree Version ’1’, first navigate intothe specific System Tree Version that the Element Node (and its System Tree Version enclosedin brackets) is displayed in the Pathname area of the ’I_MDB Navigator’ window. Position thecursor on the ’SSMB’ Node in the Pathname area of the ’I_MDB Navigator’ window and selectit there.

2. Execute File–>Show CCU Versions...

The ’CCU Versions’ window is displayed listing all existing CCUs and their Versions attachedto the selected System Tree Node. If no CCUs exist the lists will be empty.

!The ’CCU Versions’ window is divided into two separate parts. The one on the left shows theNames of all existing CCUs (CCU Names area) whereby the uppermost entry is marked for selec-tion by default. The other one on the right lists all existing CCU Versions belonging to the markedCCU Name.

To display the existing CCU Versions of a different CCU, move the cursor to its Name and selectit. All existing CCU Versions belonging to that CCU will be displayed.

4.1.4.9 Navigate into a specific CCU Version

To Navigate into a specific CCU Version:

1. Navigate to the corresponding CCU.

2. Execute the ’Open’ operation on the desired Version.

In the ’I_MDB Navigator’ window all existing Child Nodes of the System Tree Node to whichthe CCU is attached, are listed in the corresponding System Tree Nodes area. In the Pathname areathe System Tree Node has been added together with the opened CCU Identification given by’CCU:’, its name and its opened version enclosed in parentheses, e.g.’CCU:ALL_MDMS(1.0.0)’.

Notice: MDA provides the possibility to navigate into a specific CCU Version and work on de-tailed data e.g. within one of its referenced CDUs, directly. This is possible because MDA doessever all references so that System Tree Nodes, CDU Root Nodes and User Tree Nodes will bedisplayed without any information about the System Tree– or CDU Versions they are belongingto. All operations on these kind of nodes may be used as described in the corresponding sectionsof this Manual.

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


4.1.4.10 Navigate to Enditems via direct type access.

For navigating to Enditems via direct end item access please refer to the corresponding sectionbelow.

4.1.4.11 Navigate to System and User Tree Nodes within a specific CCU Version

Please refer to the corresponding sections above.

4.2 PATHNAME & SID

This operation can be used to

� show the corresponding Short Identifier (SID) of a node pathname or to

� translate an SID of a node into its corresponding pathname:

4.2.1 Show SID

To Show SID:

1. Select the specific node and execute File–>Pathname & SID... or

Select the specific node, position the cursor into the specific Nodes area, hold the right

mouse button and select Pathname & SID...

The ’Translator’ window is displayed showing the pathname and the SID of the selected node.

Figure 5. Translator

Please refer also to section ’Translate SID into Pathname’.

4.2.2 Translate SID into Pathname

To translate an SID into a pathname you have to be located in a CDU Version scope, which maybe, but not necessarily, related to a CCU Version.

To Translate SID into Pathname:

1. Navigate to a specific CDU Version

2. Verify that no node is selected

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3. Execute File–>Pathname & SID...

The ’Translator’ window is displayed showing the SID ’0’ and no pathname.

4. Enter an SID and Apply.

The corresponding pathname of the SID is displayed.

Notice : The translator may be used if a node was selected but an SID of a different node thanthe one selected shall be translated. In this case call the translator as described in step 1. It showsthe corresponding SID and Pathname of the selected node and another SID can be entered. Afterpressing Apply the corresponding pathname of the entered SID will be displayed, if it exists.

To translate a node from its pathname to its SID select the corresponding node and call the transla-tor. The pathname cannot be entered directly into the translator window.

4.3 SET DEFAULT STARTING POINT

If a user has set a default starting point for I_MDB e.g. at a specific System Tree Node or at aspecific node within a CCU Version, whenever the user starts I_MDB, it will automatically navi-gate to the specified starting point.

To set a default starting point:

1. Navigate to the point in the MDB which should now the new default starting point.

2. Select File–>Set Default Starting Point from the pop–up menu.

The information about the default starting point and other options (saved by Properties–>Op-tions) are saved into file ~/.cgs/.imdb_defaults.

The default starting point options are saved in the class imdb_dsp into this I_MDB defaults file.

After close I_MDB the user can also change the next default starting point by edit this file.

If I_MDB is started with the parameter –file <filename> then the default starting point and theother options will be loaded/saved from/into the file given by the parameter –file.

Example:

1. Navigate to the point in the MDB which should now the new default starting point.

2. Select File–>Set Default Starting Point from the pop–up menu.

3. > cp ~/.cgs/.imdb_defaults ~/imdb_def/imdb_CCU_Q_ALL_V500

4. > $MDA_HOME/bin/common/I_MDB –file ~/imdb_def/imdb_CCU_Q_ALL_V500

Notice that the default starting point cannot be set to the root node.

4.4 DIRECT END ITEM ACCESS

This function is providing the direct end item access via end item type or customer defined foreignkeys. Direct end item access means that the detail data of an end item can be accessed without

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


navigation through the name tree. As soon as a user has opened a CCU or CDU version, the directend item access is enabled.

To obtain direct end–item access:

1. Navigate to a CCU or CDU version in the name tree,

2. Select File –> Direct End–Item Access...,

The ’Direct End Item Access’ window is popped up.

Figure 6. Direct End Item Access via end–item type.

3. Select the search criteria from the selector via pressing the right mouse button: Searchvia, as shown in figure 6.

The user can choose between ’End Item Type’, ’Requirements PUI, or ’Signal PUI’

4. Enter a value or a string pattern into the data entry field provided by the chosen key. A

pattern may contain one or more ’*’ which represents any number of characters or nocharacter.

5. Select from Search&Edit –> Search.

If matching items are found they will be displayed in the lower part of the window.

6. Select the desired end–item in the list of found end–items.

7. Select from Search&Edit –> Open, to access detailed data.

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 7. Open detailed data for selected end–item (via end item type)

4.5 QUIT A WINDOW

To quit a window, click on the pin in the upper left corner of the window.

4.6 EXIT FROM INTERACTIVE MISSION DATABASE

To exit from I_MDB:

1. Quit all open windows.

2. In the ’I_MDB Navigator’ window move the cursor into the extension box in the upper

left corner of the window, hold the right mouse button and execute –>Quit.

4–15

CGS–RIBRE–SUM–00032 03.07.2015– –4–15


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



5–5

CGS–RIBRE–SUM–00032 03.07.2015– –5–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


5 ELEMENT CONFIGURATION

Child nodes of the Name Tree root node ’\‘ denote flight elements, e.g. an ’APM’ or ’SSMB’. Each flightelement shall be designed for specific missions.

A mission is a kind of instance or version of a flight element, where the version is not simply specified bya number but by a mission name denoting the purpose for which the element is designed. Therefore a flightelement together with the mission for which it is designed, is called ’element configuration’: Several config-urations may be defined for one element, each configuration for one specific mission.

Note that the element name is identical to the Name Tree node name of the element. The mission is not repre-sented by a node of the Name Tree but by an instance or version of the element node.

In the following all operations on Element Configurations are described.

5.1 CREATE

To create an element configuration the following preconditions have to be met:

� The user has to have CM privilege

� The Navigation Scope is ’Root’

To Create an Element Configuration:

1. Execute File–>Create Element Configuration....

The ‘Create Element Configuration’ window appears on the screen.

2. Enter the name of the Element Configuration you want to create.

3. Press Apply to perform the Element Configuration creation.

The new Element Configuration is shown in the Navigator window.

5.2 DELETE

To delete an element configuration the following preconditions have to be met:



� The Element Configuration has no Missions and no System Tree Versions in it.

If there are existing ’System Tree Versions’ under that Element Configuration, they have to bedeleted first. Existing Versions with the status ’FROZEN’ cannot be deleted!

5–5

CGS–RIBRE–SUM–00032 03.07.2015– –5–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To Delete an Element Configuration:

1. Select the specific Element Configuration.

2. Execute Edit–>Delete or position the cursor into the Element Configurations area, hold the right mouse buttonand select Delete.

If there are no existing System Tree Versions, a pop–up window will come up, asking ’Do youreally want to delete the ELEMENT CONFIGURATION?’

3. Press the Yes button to confirm

5.3 IMPORT

Using this operation any kind of data which has been exported before from any MDB Instancemay be imported, like System Tree Versions or CDU Versions.

Notice that the file intended to be imported has previously been exported from another MDBInstance. For an import of this file the extension has to be specified as part of the filename, other-wise the file will not be imported.

It is expected that the file to be imported is within the Home Directory of the user.

In the current MDA Version do not use this operation simultaneously with other users. Make surethat no other user is importing any file on the MDB Instance you are working on.

To import a data file the following preconditions have to be met:



To Import a File:

1. Navigate to the Root Node within the Navigator window, the Root Node and Element

Configuration are not selected.

2. Execute File–>Import... to enter the ’Import / Restore’ window.

5–5

CGS–RIBRE–SUM–00032 03.07.2015– –5–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 8. System Tree Version Import / Restore Window

3. Select Import for the import type to load the distributed System Tree Version into theMDB.

4. Select the Filename field and enter the name of the import file. The field is mandatory.

5. Press Execute to start the import.

The Reset button sets the window to its initial position.Pull the push pin in the upper left window corner to leave the window unchanged.

5.4 SET DEFAULT STARTING POINT

Please refer to the common operation ’Set Default Starting Point’.

5.5 SHOW SYSTEM TREE VERSIONS

To Show System Tree Versions:

1. Select the specific Element Configuration

2. Execute File–>Show System Tree Versions... or

Position the cursor into the Element Configurations area, hold the right mouse buttonand select Show System Tree Versions...

The ’System Tree Versions’ window is displayed listing all existing System Tree Versions of theselected Element Configuration.

5–5

CGS–RIBRE–SUM–00032 03.07.2015– –5–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 9. System Tree Versions

5–5

CGS–RIBRE–SUM–00032 03.07.2015– –5–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



6–5

CGS–RIBRE–SUM–00032 03.07.2015– –6–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


6 MISSION SUPPORT

6.1 SELECT A MISSION

The user can select a mission from the ’System Tree Version’ window. This window can bereached from the I_MDB Navigator in the navigation scope ’Root’.

To select the desired Mission:

1. Navigate to the Root Node within the Navigator window

2. Open the desired Element Configuration by double clicking on it or

Select the desired Element Configuration and execute File–>Show System Tree Ver-sions... or

Select the desired Element Configuration, position the cursor into the Element Configu-rations area, press the right mouse button and select Show System Tree Versions....

Figure 10. System Tree Versions window

The ’System Tree Versions’ window is opened and shows a list of all Missions for the selectedElement Configuration. The first mission of the list is selected as default and shows all existingSystem Tree Versions of that selected mission.

6–5

CGS–RIBRE–SUM–00032 03.07.2015– –6–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3. Select another than the default mission with the mouse pointer, if required.

The System Tree Versions list will be updated according to the selected mission.

4. Open the desired System Tree Version by double clicking on it or

Select the desired System Tree Version and execute Command–>Open and DismissWindow...

6.2 CREATE A MISSION

The user can create a new mission for an existing Element Configuration.

To create a new mission, the following preconditions have to be met:


� The current instance is the element contractor instance

A mission can be created in three different ways:

– Only the mission is created

– The mission is created and a System Tree Version (including CDU versions) fromanother mission is copied into the mission just created

– The mission is created and a System Tree Version including all its CCU/CDU versionsfrom another mission is copied into the mission just created

To create a mission:

1. Select the mission to be deleted as described in ’Select a Mission’

2. In the ’MISSION’ partition of the window (left side): Execute: Edit–>Create...

6–5

CGS–RIBRE–SUM–00032 03.07.2015– –6–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 11. Create Mission window

3. In the field ’Mission Name’ type the new mission name

If a System Tree Version from another mission within that same Element Configuration has beenselected prior to executing the ’Edit–>Create...’ function it will be displayed under ’Copy SystemTree Version from...’ .Otherwise these fields will be left blank.

In case an existing System Tree Version has been copied, the Including Configuration Units haveto be selected:

4. Pull down the ’Including Configuration Units’ menu and choose between the three op-tions ’None’, ’Only CDU versions’ or ’ CCU versions & CDU versions’

5. Press the Apply button to create the new mission.

The Reset button sets the window to its initial position.Pull the push pin in the upper left corner to leave the window unchanged.

Mission NameIn this mandatory field the name of the mission to be created has to be entered

Including Configuration UnitsThis setting is only available if a system tree version has been selected to be copied. The user canselect between the configuration units also to be copied: Only the CDU versions or the CCU andthe CDU versions or no configuration unit at all (default). If no configuration unit is selected tobe copied, the System Tree Version is changed to version 1 in status DEVELOPMENT.

6.3 DELETE A MISSION

The user has the option to delete a mission.

6–5

CGS–RIBRE–SUM–00032 03.07.2015– –6–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To delete a mission, the following preconditions have to be met:


� The current instance is the element contractor instance

� The mission has no System Tree Versions in it

To delete a mission:

1. Select the mission to be deleted as described in ’Select a Mission’

2. In the ’MISSION’ partition of the window (left side): Execute Edit–>Delete

If there are no existing System Tree Versions, a pop–up window will come up, asking ’Do youreally want to delete the MISSION?’

Figure 12. ’Delete Mission’ confirmation window

3. Press the Yes button to confirm

The No button will close the window without deleting the Mission.

6–5

CGS–RIBRE–SUM–00032 03.07.2015– –6–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


7 SYSTEM TREE

The system tree reflects the contractual decomposition of an element and will possibly exist inmany different versions. If System Tree modifications are necessary it will always be a matter ofelement requirements change e.g. contractual modifications, which can only be performed by ele-ment contractors. Therefore and due to the fact that System Tree data is made persistent in theMDB before it is distributed to each subcontractor (System Tree data is frozen), the creation ofa new version is inevitable in these cases. Any changes on System Tree data will then have to beperformed within the new created version.

Managing System Tree Versions requires the user ’CM’ privilege and can only be performed onMDB element contractor instances.

The status of a Version denotes whether it can still be modified by a CM user (status ’DEVELOP-MENT’) or its contents have been frozen and can never be modified again (status ’FROZEN’).

Each node in a System Tree Version is always owned by one user.

7.1 SYSTEM TREE NODES

In this section all operations on System Tree Nodes are described.

7.1.1 Browse CCU Versions

No matter whether you have selected a node or not, you may browse through all CCU Versionswhich exist in a specific System Tree Version.

To Browse CCU Versions:

1. Navigate into the System Tree Version in which CCU Versions shall be browsed. (Referto the common operation ’Navigating through the Name Tree’.)

2. From the ‘I_MDB Navigator‘ window, execute File–>Browse All CCU Versions... .

The ’Browse CCU Version’ window is displayed listing all existing CCU Versions in the SystemTree Version.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 13. Browse CCU Version

Each entry consists of the pathname of the System Tree Node to which a CCU is attached, as wellas the CCU Name and the CCU Version Identifier.

3. To continue looking into a CCU, select one and press Apply.

For further operations please refer to section ’CCU’.

4. To leave the window unchanged, press: Cancel to go back to the ’I_MDB Navigator’window.

7.1.2 Open

Please refer to the common operation ’Navigating through the Name Tree’.

7.1.3 Pathname & SID

Please refer to the common operation ’Pathname & SID’.

7.1.4 Set Default Starting Point


7.1.5 Show CCU Versions

After executing this operation the ’CCU Versions’ window will be displayed in which the usermay operate on CCU definitions for a specific System Tree Node.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To Show CCU Versions:

1. Navigate to the desired Mission and System Tree Version.

2. Select the desired System Tree Node within the System Tree, the CCU Version shall be

shown for..

Figure 14. Selected System Tree Root Node within a specific System Tree Version

3. From the ‘I_MDB Navigator‘ window, execute File–>Show CCU Versions... .

The ’CCU Versions’ window is displayed listing all existing CCUs and their Versions attachedto the selected System Tree Node. If no CCUs exist the lists will be empty.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 15. CCU Versions

The ’CCU Versions’ window is divided into two separate parts. The one on the left shows theNames of all existing CCUs (CCU Names area) whereby the uppermost entry is marked for selec-tion by default. The other one on the right lists all existing CCU Versions belonging to the markedCCU Name.

4. To show the existing CCU Versions of a different CCU, move the cursor to its Name

and select it.

All existing CCU Versions belonging to the desired CCU will be displayed.

5. To continue operating on the CCU version, please refer to the CCU (Version) operations

for more information!

To quit the window:Pull the push pin in the upper left window corner to leave the window unchanged.

7.1.6 Create a System Tree Node

To perform this operation the user has to be located in the system tree version scope within the‘I_MDB Navigator’ window. The location information is displayed in the footer at the right side(NAVIGATION SCOPE: System Tree Version).

Before the user can create a new system tree node the following preconditions have to be met:


� The user has to be the owner of the parent node

� The system tree version has to have the status ’DEVELOPMENT’

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 16. Element Node with its System Tree Version and System Tree Nodes

To create a new system tree node:

1. Deselect any System Tree Node, if selected

2. From the ‘I_MDB Navigator‘ window, execute File–>Create Node ... to enter the

’Create System Tree Node‘ window.

Figure 17. Create System Tree Node window

After first entering the ’Create System Tree Node‘ window the fields will be empty.

3. Enter the Name of the new System Tree Node.

The Name field is mandatory and has to be filled. If the field is not filled, the error message’Name: is mandatory ‘ will be displayed.

4. Enter the name of the MDB Instance or

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Select MDB Instance ... by pressing the left mouse button.

Select the MDB Instance within the ’Instance List’ window, press the left mouse buttonand Apply.

The MDB Instance assigned to this system tree node defines which MDA Instance shall set theresponsibility to create CDU version of this node.The MDB Instance field is mandatory and has to be filled. If the field is not filled, the error mes-sage ’ MDB Instance : is mandatory ‘ will be displayed.

5. Enter the name of an owner

or Select Owner ... by pressing the left mouse button.

Then select an owner of this new system tree node to be created within the ’User List’window, press the left mouse button and Apply.

The owner field is mandatory and has to be filled. If the field is not filled, the error message ’Own-er: is mandatory‘ will be displayed.

6. Enter a short description of the new System Tree Node (optional).

7. Execute Apply to start the system tree node creation process.

The new system tree node is shown in the ‘System Tree Nodes‘ area within the ’I_MDB Naviga-tor’ window.

The Reset button sets the window to its initial position.Pull the push pin in the upper left window corner to leave the ‘Create System Tree Node‘ windowunchanged.

7.1.7 Delete a System Tree Node and Subtree

The user can delete system tree nodes and subtrees. To perform this operation the user has to belocated in the system tree version scope within the ‘I_MDB Navigator’ window. The location in-formation is displayed in the footer at the right side (NAVIGATION SCOPE: System Tree Ver-sion).

Before deleting a system tree node and subtree the following preconditions have to be met:


� The user has to be the owner of the node and all children of the node

� The user has to be the owner of the father node


To delete a system tree node:

1. Select the System Tree Node to be deleted within the ‘System Tree Node’ area of’I_MDB Navigator’ window.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 18. Delete System Tree Node

2. From the ‘I_MDB Navigator‘ window, execute Edit–>Delete.

A confirmation window is displayed: ’Do you really want to delete the SYS NODE?’.

3. Confirm with Yes to delete the selected system tree node.

7.1.8 Copy and Paste a System Tree Node

The user can create a new system tree node which is a copy of an existing one. For this a systemtree node and its subtree will be copied, and then pasted to a new position. To perform this opera-tion the user has to be located in the system tree version scope within the ‘I_MDB Navigator’window. The location information is displayed in the footer at the right side (NAVIGATIONSCOPE: System Tree Version).

Before the user can paste a system tree node the following preconditions have to be met:


� The user has to be the owner of the destination node


To copy a system tree node:

1. Select the System Tree Node to be copied within the ‘System Tree Node’ area of the

’I_MDB Navigator’ window.

2. From the ’I_MDB Navigator’ window, execute Edit–>Copy.

In the upper right corner of the ’I_MDB Navigator’ window the following message appears:SYS Node Name for Paste: NodenameNodename is the name of the node which has been selected. It is the source node.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 19. Copy System Tree Node

3. Deselect the chosen system tree node (source node) to be able to perform the ’Paste’operation.

To paste a system tree node:

1. Perform step 1 to step 3 of the system tree node copy operation.

2. Navigate to the destination where the new system tree node shall be stored,

or

enter the name of the destination system tree node if there is none existing.

3. From the ’I_MDB Navigator’ window, execute Edit–>Paste to paste the system treenode and its subtree.

Notice: The copy / paste operation is based on the actual data in the database and not on the dataof a temporary paste buffer. Thus in case the user applies some changes to the node to be copiedafter performing the copy but before performing the paste operation, the paste operation will copythe modified/actual data.

7.1.9 System Tree Node Properties

The operations provided by the properties window allows the user to change the system tree nodedata.

Before the user can modify the system tree node properties the following preconditions have tobe met:

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



� The user has to be the owner of the node


Properties of system tree versions with the status ’FROZEN‘ can only be viewed, but not modi-fied.

To modify the system tree node properties:

1. Select the System Tree Node to be modified within the ‘System Tree Nodes’ area.

2. From the ’I_MDB Navigator’ window, execute Properties–>Selection to enter the‘System Tree Node Properties‘ window.

Figure 20. System Tree Node Properties

The Name of the system tree node which properties shall be changed, is displayed at the top ofthe window.

To change the MDB Instance of the system tree node:

3. Enter the name of the MDB Instance

or Select MDB Instance ... by pressing the left mouse button.Select the MDB Instance within the ’Instance List’ window, press the left mouse button

and Apply.

The MDB Instance assigned to this system tree node defines which MDA Instance shall set theresponsibility to create CDU version of this node.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The MDB Instance field is mandatory and has to be filled. If it is not filled, the error message ’MDB Instance: is mandatory ‘ will be displayed.

To change the owner of the system tree node:

4. Select the choice button ‘Node‘ to change the owner of the Node itself Enter the name of an owner

or

Select Owner ... by pressing the left mouse button.Select an owner within the ’User List’ window, press the left mouse button and Apply.

The owner field is mandatory and has to be filled. If it is not filled, the error message ’Owner:is mandatory‘ will be displayed.

To change the owner of the system subtree:

5. Select the choice button ‘Subtree’ to change the owner of the complete Subtree Enter the name of an owner or


The owner field is mandatory and has to be filled. If it is not filled, the error message ’Owner:is mandatory‘ will be displayed.

6. Create or change the description of the system tree node (optional).

7. Execute Apply to make the changes persistent.

The Reset button sets the window to its initial position.Pull the push pin in the upper left window corner to leave the ‘System Tree Node Properties‘ win-dow unchanged.

7.1.10 Add System Tree Nodes to a frozen System Tree Version

It is also possible to create System Tree Nodes in a frozen System Tree Version for the specialcase ’System Tree Patch’. The patch script will be create on the source system and it will be exe-cute on the target system.

7.1.10.1 Source System

Managing System Tree Versions requires the user ’CM’ (Configuration Manager) privilege andcan only be performed on the MDB element contractor instance.

It is necessary to change an option in I_MDB before this user can create System Tree Nodes ina frozen System Tree Version.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To change the I_MDB option:

1. I_MDB –> Properties –> Options –> Navigator –> Patch System Tree: Yes

Then it is possible to create System Tree Nodes in frozen System Tree Versions. The user can dis-tribute such a new created System Tree Node to the file system.

To export a System Tree Node:

1. Select the System Tree Node

2. Press the right mouse key and select ’Export’

It will be created two files. Both files are the same functionality. The first is a bourne shell scriptand the second is a compiled executable. One of both files should distribute to the target system.

7.1.10.2 Target System

The provided script must execute on the target system. This script does create the missing SystemTree Node in the adequate System Tree Version.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


7.2 SYSTEM TREE VERSION

In this section all operations on System Tree Versions are described. Due to the fact that systemtrees are decompositions of element configurations, operation on element configurations are alsoincluded in this chapter.

7.2.1 Create a System Tree Version

There are two possibilities to create system tree version:

– Create a new empty system tree version

– Create a new system tree version by copying an existing system tree version

Before the user can create a system tree version the following preconditions have to be met:


� No other system tree version shall be in the status ’DEVELOPMENT’

7.2.1.1 Create a System Tree Version by Copying

For this operation there must be an existing system tree version.

To copy a system tree version:

1. Select the source System Tree Version within the ‘System Tree Version’ window.

2. Execute Edit–>Create to enter the ‘Create System Tree Version‘ window.

Figure 21. Create System Tree Version

The version identifier of the source system tree is displayed in the message ‘Copy from SystemTree Version: _‘ at the top of the window.

3. Enter the name of an owner or


7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The owner field is mandatory and has to be filled. If it is not filled, the error message ’Owner:data not found‘ will be displayed.

4. Enter a short Description of the new System Tree Version (optional)

5. Execute Apply to start the copy process and leave the window.

The new system tree version is shown in the ’System Tree Version’ window. MDA automaticallycreates an incremented version identifier and the status will be set to ’DEVELOPMENT’.

Figure 22. System Tree Version window after creating a new sys. tree vers. by copy op-eration

The Reset button sets the window to its initial position.Pull the push pin in the upper left window corner to leave the ‘Create System Tree Version‘ win-dow unchanged.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


7.2.1.2 Create an empty System Tree Version

For this operation existing system tree versions are not mandatory. If there are existing systemtree versions, none has to be selected.

To Create an empty System Tree Version:

1. Navigate to the ’System Tree Version’ window where a new version shall be created

2. Perform steps 2. to 5. of the previous chapter ’Create a System Tree Version by Copy-

ing’.Do not perform step 1.

In step 2 the message ‘Copy from System Tree Version: ’ at the top of the window will be dis-played without a version identifier.

The new system tree version is shown in the ’System Tree Version’ window. MDA automaticallycreates an incremented version identifier if there are existing system tree versions or generatesthe version identifier ‘1‘ if this version is the first one. The status will be set to ’DEVELOP-MENT’.

7.2.2 Delete a System Tree Version

The user can only delete a system tree version if the following preconditions are met:


� The system tree version is in the status ’DEVELOPMENT’

To delete a system tree version:

1. Select the System Tree Version to be deleted within the ‘System Tree Version’ window.

2. Execute Edit–>Delete

A confirmation window is displayed: ’Do you really want to delete the SYS VERSION?’

3. Confirm with Yes

to delete the selected system tree version.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–15


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 23. Confirmation window

7.2.3 Select a System Tree Version

When the system tree version window becomes visible, no system tree version is selected by de-fault.

To select a system tree version:

1. Move the cursor to the desired version row.

2. Press the left mouse button once.

The selected version will be highlighted. Selecting a system tree version is only marking it. Toperform an operation on it, a command has to be chosen.

7.2.4 Deselect a System Tree Version

The precondition to deselect a system tree version is, that there is a selected system tree version.

To deselect a system tree version:

1. Move the cursor to the selected version row.

2. Press the left mouse button once.

The selection will disappear.

7.2.5 Open a System Tree Version

Within a ‘System Tree Version‘ window a version can be opened by the following operations:

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–16


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To Open a System Tree Version:

1. Select the System Tree Version and execute Command–>Open and Dismiss Window or perform a double left mouse click on a non–selected version to open this system tree

version.

The opened system tree version with its system tree nodes is shown in the ’I_MDB navigator’window.

7.2.6 Print a System Tree Version

Within the ‘System Tree Version‘ window, a specific version can be printed.

To Print a System Tree Version:

1. Select the specific System Tree Version to be printed.

2. Execute Command–>Print...

to enter the ’Report Generator’ window.

Figure 24. Report Generator ’System Tree Version’

Please refer to the ’Report Generation’ section to specify the desired report to be generated.

7.2.7 Data Distribution

Please read first the Export / Import concept description in the Introduction Manual, section 3.3.3.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–17


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


7.2.7.1 Distribute a System Tree Version

The user can distribute a System Tree Version to the file system. The archiving stores the SystemTree Version outside the MDB. Distributed System Tree Versions can be imported by other MDBinstances. A System Tree Version can not be archived.

To perform the distribution, the following preconditions have to be met:

� The System Tree Version has to have the status ’FROZEN’

� The user has to have CM privilege.

To distribute a System Tree Version:

1. Navigate to the System Tree Version window

2. Select a version and execute Command–>To... to enter the ’Data Archiving / Data Dis-tribution’ window.

Figure 25. System Tree Version Data Distribution / Data Archiving window

Export TypeA System Tree Version will always be distributed, it cannot be archived.

ItemThe field contains the item from which the data distribution or data archiving will be performed.In this case it is the System Tree Version.

UserThe field contains the user name who wants to perform the data archiving or data distribution.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–18


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Info FileThe field contains the information file name. It contains the same information as the ’Data Ar-chiving / Data Distribution’ window in ASCII format. The ’Info File’ filename has the same pre-fix as the export file name with the extension ’.info’.

3. Select the Export File field and enter the name of the export file. The field is mandato-ry.If no extension will be entered for the filename, the extension ’.dmp’ will be added au-

tomatically. Otherwise the user may add any extension he wants. The file will be storedin the user Home–Directory.

OriginatorThe field contains the origin MDB instance.

4. Select the Receiver field and enter the receive area. The receive field is only activewhen the export type is distribution. Any name can be assigned and no check will be

performed by I_MDB.

5. Select the Remark field and enter a comment to the export (optional). The maximumnumber of allowed characters is 255.

6. Press Execute to start the export.


7.2.7.2 Import a System Tree Version

The user can import a System Tree Version that has been exported by the distribution functionfrom another MDB instance.

To perform the import, the following preconditions have to be met:


To import/restore a System Tree Version:

1. Navigate to the Root Node within the Navigator window, the Root Node and Element

Configuration are not selected.


7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–19


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 26. System Tree Version Import / Restore Window

3. Select Import for the import type to load the distributed System Tree Version into the

MDB.

4. Select the Filename field and enter the name of the import file. The field is mandatory.

5. Press Execute to start the import.


7.2.8 Show

7.2.8.1 Show System Tree Versions

To navigate from the I_MDB navigator window to the System Tree Version Window:

1. If you have navigated to a lower level, select the ‘\‘ Node in the pathname area and exe-

cute File–>Open. (Skip this step if you are in Navigation Scope: Root)

2. Select a specific Element Configuration in the I_MDB navigator window and executeFile–>Show System Tree Versions... or

Select a specific Element Configuration, position the cursor into the Element Configura-tions area, press the right mouse button and select Show System Tree Versions....

or

perform a double left mouse click on the desired element configuration.

In both cases the ’System Tree Versions’ window is displayed listing all existing System Tree Ver-sions of the selected Element Configuration with its version identifier and status.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–20


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 27. I_MDB: System Tree Versions

7.2.8.2 Show System Tree Version Properties

To show System Tree Version properties refer to section ’System Tree Version Properties’

7.2.8.3 Show Exports

The user can obtain information about all system tree version exports. This function is a part ofthe export/import information browser which can be reached from the Navigator window ofI_MDB.

To show exports:

1. Navigate to the Root Node within the Navigator window, Root Node and Element Con-figuration are not selected

2. Execute File –> Browse System Tree Version Exports ... to enter the ’Show Exports’

window.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–21


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 28. System tree version show exports window

Dedicated filters can be specified by the user in order to get information only from those versionsmatching the filter criteria. Within a filter field, wildcards ’*’ can be used as a pattern for any char-acter. Leaving a filter field blank is equivalent to ’*’.

3. Select the Element Configuration field and enter desired filter data

4. Select the Mission field and enter desired filter data

5. Select the System tree version field and enter desired filter data

6. Press the Search button to obtain a list of all system tree version exports matching the

specified filter criteria


Notice: In case no filter items are specified the user gets an export list of all existing exports ofthe system tree.

The Detail Data fields will be filled when the user selects a list item:

Export UserThis field contains the name of the user which has performed the export

DateThis field contains the date of the export

Info FileThe info file is an ASCII file which contains the detail information of the export

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–22


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Export FileThis field contains the export file name

MDB versionThis field contains the MDB version of the export

ReceiverThis field contains the receiver name of the export

RemarkThis field contains a remark of the user which has performed the export

7.2.8.4 Show Imports

The user can obtain information about all system tree version imports. This function is a part ofthe export/import information browser which can be reached from the Navigator window ofI_MDB.

To show imports:


2. Execute File –> Browse System Tree Version Imports ... to enter the ’Show Imports’window.

Figure 29. System tree version show imports window

Dedicated filters can be selected by the user in order to get information only from those versionsmatching the filter criteria. Within a filter field wildcards ’*’ can be used as a pattern for any char-acter. Leaving a filter field blank is equivalent to ’*’.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–23


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3. Select the Element Configuration field and enter desired filter data

4. Select the Mission field and enter desired filter data

5. Select the System tree version field and enter desired filter data

6. Press the Search button to obtain a list of all system tree version imports matching the

specified filter criteria


Notice: In case no filter items are specified the user gets an import list of all existing imports ofthe system tree.




Import UserThis field contains the name of the user which has performed the import

DateThis field contains the date of the import



MDB versionThis field contains the version of the current MDB

OriginatorThis field contains the originator MDB instance

ReceiverThis field contains the receiver name of the import


7.2.9 Add System Tree Versions

If a new system tree version has been developed, the CDU versions (as well as a whole CCUscope) of the previous system tree version with the status frozen can be copied to the new one.This upgrade function helps the user to save implementation time.

For more detail description see chapter 20

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–24


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Before the user can upgrade a CDU version, respectively a CCU scope, the following precondi-tions have to be met:

� The system tree status has to be ‘FROZEN‘


To upgrade a CDU version or a CCU version scope:

1. Select the System Tree Version whose contents shall be updated.

2. Execute Command–>Add System Tree Versions to start the upgrade process.

7.2.10 System Tree Version Properties

The operations provided by the properties window allow the configuration manager to changethe system tree version data. For other users this function provides a general view of the systemtree version data without any permission of modification.

The user can only modify a system tree version if the following preconditions are fulfilled:


� The system tree version is in the status ’DEVELOPMENT’

Properties of system tree version with the status ‘FROZEN‘ can only be viewed, but not modified.

To modify a system tree version:

1. Select the System Tree Version to be modified within the ‘System Tree Version’ win-

dow.

2. Execute Edit–>Properties to enter the ‘System Tree Properties‘ window.

Figure 30. System Tree Version properties

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–25


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The version identifier of the system tree is displayed in the message ‘System Tree Version: _‘at the top of the window.

To change the owner of the system tree version:

3. Enter the name of an owner

or

Select Owner ... by pressing the left mouse button.

Select an owner within the ’User List’ window, press the left mouse button and Apply.

The owner field is mandatory and has to be filled. If it is not filled, the error message ’ Owner: is mandatory‘will be displayed.

4. Create or change the Description of the system tree version (optional).

To change the system tree version Status :

5. Select the choice button ‘FROZEN‘ to convert a development version to a frozen one.

The frozen date will be set.

If the development phase is not finalised, keep the ‘DEVELOPMENT‘ status.

The fields Creation Date, Change Date and Frozen Date are user information and cannot bechanged.

6. Execute Apply to make the changes persistent.

The Reset button sets the window to its initial position.Pull the push pin in the upper left window corner to leave the ‘System Tree Version Properties‘window unchanged.

7–26

CGS–RIBRE–SUM–00032 03.07.2015– –7–26


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8 CDU (USER TREE)

A CDU (User Tree) is the completion of an element design including the definition of end item data, usuallyspecified by a subcontractor on a specific MDB instance.

As such a CDU (User Tree) is the continuation of a specific System Tree branch starting underneath a SystemTree Node. This System Tree Node has got an associated MDB instance as specified by an element contractordenoting the subcontractor (or element contractor) site which is responsible for further decomposition of anelement and final definition of end items.

The root node of the CDU which is called CDU Root Node, can only be created by CM users on an MDBinstance specified by an element contractor as just described.

Since modifications within a CDU (User Tree) are not only a matter of requirement changes but also of archi-tectural design changes like data structure modifications of interfaces and additionally of detailed data bugfixes, repairs or other detailed data corrections which must be kept visible during element configuration de-sign. Thus, if CDU (User Tree) modifications are necessary, the subcontractor has the possibility to keep thekind of modifications which shall be performed, visible by creating one of the following kinds of CDU (UserTree) Versions:

� a complete new Version of a CDU in case that requirements have to be changed or

� a new Issue of a CDU Version in case that no requirements but the architectural designhas to be changed or

� a new Revision of a CDU Version Issue in case that bugs have to be fixed, repairs orother detailed data corrections have to be performed

In the following, the term ’CDU Version’ shall include a specific issue and revision unless where otherwisestated.

A node in a CDU Version ( User Tree Node) is always owned by one user.

The status of a CDU Version denotes whether it can still be modified (status ’DEVELOPMENT’) or if itis ready for review and only a CM user can modify the data as agreed in an official review (status ’REVIEW’)or if its contents are frozen and can not be modified any longer (status ’FROZEN’).

The status can only be changed by CM users.

To each CDU Version a CDU domain is attached specifying the valid end item classes of which end itemsmay be defined within the CDU Version. The CDU domain can be different in several Versions of a CDU.

The restriction that new CDUs and Versions of them can only be created as child nodes of System Tree Nodeswith the same MDB Instance is in practice too strong. If e.g. imported data contains bugs it would save timeand money to fix the bugs immediately and to continue e.g. a subsystem test. MDA provides such a possibil-ity by allowing CDU Test Version.

A CDU Test Version (empty one or a copy of any other CDU (Test) Version) is a specific kind of CDU Versionwhich can be created independently of the restricted MDB Instance. Bug fixes can then be performed withinsuch a Test Version but it is only an interim solution. The performed modifications must afterwards go theofficial way of approval. Notice that Test Versions can never be in status ’REVIEW’.

A Restricted CDU Version is a specific kind of CDU Test Version which can be also created independentlyof the restricted MDB Instance. The access to previously defined item type – aggregate combinations is re-stricted (read–only) in this kind of CDU Version.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8.1 CDU ROOT NODE AND USER TREE NODES

In this section all operations on the CDU Root Node and the User Tree nodes are described.

Notice: The CDU Root Node which is the root node of the User Tree, is emphasized and will inthe following be named CDU Root Node instead of CDU Node (which is in contrast to the nam-ing convention in the MDA Introduction Manual). All other nodes of the CDU will be namedUser Tree nodes.

8.1.1 Create

8.1.1.1 Create the CDU Root Node

The CDU node which can be created underneath a System Tree node is the Root Node of a CDU(User Tree). It can be created if a system tree node with an associated MDB instance has alreadybeen defined (father node exists)

To create a CDU Root Node the following preconditions have to be met:

� The user has to have ’CM’ privilege

� The user has to work on the associated MDB instance.

� The corresponding System Tree Version is in status ’FROZEN’.

To Create the CDU Root Node:

1. Select the System Tree node (father node).

2. Execute File–>Open . or

position the cursor into the System Tree Nodes area, hold the right mouse button and

select Open.

A list of all existing child nodes is displayed.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 31. Open a System Tree Node by executing a File command

3. Execute File–>Create CDU... .

Figure 32. Create CDU

4. Enter the name of the CDU in the displayed ’Create CDU’ window and Apply.

The new CDU Root Node is shown in the User Tree Nodes area.


8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 33. I_MDB_Navigator after creating a CDU Root Node

8.1.1.2 Create a User Tree Node

Notice: A User Tree node (including End Items) can only be created within a specific CDU Ver-sion (in contrast to the creation of CDU Root Nodes which are the basis for CDU Versions). Ifonly a CDU Root Node exists but no CDU Version of it, a Version has to be created first.

To create a User Tree Node the following preconditions have to be met:

� If the CDU Version is in status ’DEVELOPMENT’, the user has to be the owner of thealready existing CDU Root Node or any User Tree Node (father node), underneathwhich the new one shall be created.

� If the CDU Version is in status ’REVIEW’, the user has to have ’CM’ privilege

A User Tree Node in a CDU Version cannot be created if it is in status ’FROZEN’.

To Create a User Tree Node:

1. Select the father node in a CDU Version, under which the new node shall be created

2. Execute File–>Open . or

position the cursor into the User Tree Nodes area, hold the right mouse button and selectOpen.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


A list of all existing child nodes is displayed.

3. Execute File–>Create Node... .

Notice: ’Create Node...’ is only selectable by the owner of the father node.

The ’Create user tree node’ window is displayed.

Figure 34. Create user tree node

4. Enter a Name for the new User Tree node.

The Name field is mandatory and has to be filled. If it is not filled, an error message will be dis-played.

5. Enter the User Tree node Type or

select Type... for a list of all valid type values for its specific CDU domain to which thisnew node will belong, select one and Apply.

The Type field is mandatory and has to be filled. If it is not filled, an error message will be dis-played.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 35. Node type list help

6. Enter a CI number (optional)

7. Enter an owner or select Owner... for a list of all valid users, select one and Apply.

The Owner field is mandatory and has to be filled. If it is not filled, an error message will be dis-played.

8. Enter a short description of the new User Tree node (optional).

9. Press Apply.

The new User Tree node is shown in the User Tree Nodes area.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 36. User Tree Nodes area after creating a virtual Node

8.1.1.3 Create a specific End Item

Please refer to ’Create a User Tree Node’. To enter the detailed data of the End Item please referto ’Update specific End Item detailed data’.

8.1.1.4 Create a specific End Item by Copying an existing End Item

Please refer to ’Create a subtree of User Tree nodes by Copying a subtree’.

8.1.1.5 Create a subtree of User Tree nodes by Copying a subtree

Notice: If a subtree has been copied, the root node of the subtree is copied inclusively. The subtreeto be copied may contain only one node, e.g. any virtual User Tree node which has got no childrennodes yet or any End Item. Such a single node is considered as a subtree consisting only of thesubtree root node.

Notice: The copy / paste operation is based on the actual data in the database and not on the dataof a temporary paste buffer. Thus in case the user applies some changes to the nodes to be copiedafter performing the copy but before performing the paste operation, the paste operation will copythe modified/actual data.

To create a subtree of User Tree Nodes by copying, the following preconditions have to be met:

� If the CDU Version is in status ’DEVELOPMENT’ the user has to be the owner of thealready existing CDU Root Node or any User Tree Node (father node), underneathwhich the copied one shall be pasted.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



A subtree cannot be copied into a CDU Version if it is in status ’FROZEN’ or if their CDU do-mains differ.

To Create a subtree of User Tree nodes by Copying a subtree:

1. Select the father node of the subtree to be copied (source), position the cursor into theUser Tree Nodes area, hold the right mouse button and select Copy.

The Node Name for the Paste operation is shown next to the ’Properties’ button.

Figure 37. I_MDB Navigator with Node Name for the Paste operation

2. Navigate to the User Tree node (father node) underneath which the subtree shall be

pasted and select the node.

3. Execute File–>Open or


4. Position the cursor into the User Tree Nodes area, hold the right mouse button and selectPaste.

Notice: MDA will not copy the subtree if a siblings node in the User Tree Nodes area exists whichhas got the same name as the subtree root node.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The root node of the copied subtree is shown in the User Tree Nodes area. The user is now ableto navigate through the copied subtree.

Figure 38. User Tree Nodes area after copying a subtree

8.1.2 Delete

To delete a User Tree Node, the following general preconditions have to be met:

� If the CDU Version is in status ’DEVELOPMENT’ the user has to be the owner of theUser Tree Node (End Item).


A User Tree Node (End Item) in a CDU Version which is in status ’FROZEN’ cannot be deleted.

8.1.2.1 Delete the CDU Root Node

To delete a CDU Root Node, the following preconditions have to be met:

� The user has to have ’CM’ privilege.

� There are no existing CDU Versions of this CDU Root Node.

To Delete the CDU Root Node:

1. Select the specific CDU Root Node

2. Execute Edit–>Delete or

position the cursor into the User Tree Nodes area, hold the right mouse button and selectDelete.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


A confirmation window is displayed asking ’Do you really want to delete the CDU NODE?’.

3. Confirm with Yes.

The CDU Root Node is deleted.

8.1.2.2 Delete a subtree or a User Tree Node

Notice: To delete a subtree, the root node of the subtree is deleted inclusively. The subtree to bedeleted may contain only one node, e.g. any virtual User Tree node which has got no child nodesyet or any End Item. Such a single node is considered as a subtree consisting only of the subtreeroot node.

To delete a subtree or a User Tree Node, the following preconditions have to be met:

� If the CDU Version is in status ’DEVELOPMENT’ the user has to be the owner of eachnode contained in the subtree (including the subtree root node) and of its father node(father of subtree root node).


A subtree or a User Tree Node (End Item) in a CDU Version which is in status ’FROZEN’ cannotbe deleted.

To Delete a subtree or a User Tree Node:

1. Select the root node of the subtree to be deleted

2. Execute Edit–>Delete or

position the cursor into the User Tree Nodes area, hold the right mouse button and selectDelete.

A confirmation window is displayed asking ’Do you really want to delete the USER SUB-TREE?’.


The subtree is deleted.

8.1.2.3 Delete an End Item

Please refer to ’Delete a subtree or a User Tree Node’.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8.1.3 Move a subtree of User Tree nodes

To move a User Tree Node or a Subtree of User Tree Nodes, the following preconditions haveto be met:

� If both CDU Versions are in status ’DEVELOPMENT’ the user has to be the owner ofthe source node and the owner of the destination node below which the source nodeshall be moved..

� If one or both CDU Versions are in status ’REVIEW’, the user has to have ’CM’ privi-lege.

� If the move is performed between two CDU Versions, both CDU Versions have to be ofdomain ’USER_DEF_SIDS’.

A User Tree Node (End Item) or subtree in a CDU Version which is in status ’FROZEN’ cannotbe moved.

Notice: If a subtree has been moved, the root node of the subtree is moved inclusively. The subtreeto be moved may contain only one node, e.g. any virtual User Tree node which has got no childrennodes yet or any End Item. Such a single node is considered as a subtree consisting only of thesubtree root node.

To Move a Subtree of User Tree nodes:

1. Select the father node of the subtree to be moved (source), position the cursor into theUser Tree Nodes area, hold the right mouse button and select Select for Move.

The Node Name for the Paste operation is shown next to the ’Properties’ button and may bechanged by the user by editing a new name. Thus only a renaming of a node is possible, too incase the Paste operation is performed at the same place were the Select for Move operation wasdone.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 39. I_MDB Navigator with Node Name for the Move operation

2. Navigate to the User Tree node (father node) underneath which the subtree shall bepasted and select the node.

Notice: In case the move is performed between two CDU Versions, both CDU Versions have tobe of domain ’USER_DEF_SIDS’. If the move is performed within the same CDU version thedomain can be of any kind.

3. Execute File–>Open or


4. Position the cursor into the User Tree Nodes area, hold the right mouse button and select

Paste.

Notice: MDA will not move the subtree if a siblings node in the User Tree Nodes area exists whichhas got the same name as the subtree root node.

The root node of the moved subtree is shown in the User Tree Nodes area. The user is now ableto navigate through the moved subtree.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8.1.4 Open



Please refer to the common operation ’Pathname & SID’.



8.1.7 Show

8.1.7.1 Show CDU Root Node Properties

Notice: A CDU Root Node does not have any properties. Instead, specific versions of it do haveproperties. To obtain information on User Tree Version properties please refer to the ’Show UserTree Versions Properties’.

8.1.7.2 Show User Tree Node Properties

To Show User Tree Node Properties:

1. Select the specific User Tree node and execute Properties–>Selection...

The ’User Tree Node Properties’ window is displayed.

Figure 40. User Tree Node Properties

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Name, SID Number, Type, Configuration Item (CI) number, Owner, Description, Creation date,Change Data, Software Type and Software Access Class of the User Tree node are displayed. Theboxes ’node’ and ’subtree’ are only used for updating the owner either of the node itself or of itscomplete subtree.

2. Pull the push pin in the upper left window corner to leave the window unchanged.

8.1.8 Update

Notice: A CDU Root Node cannot be updated in any way. The user may only create new (test)versions of a CDU or create a complete new CDU Root Node.

To update a User Tree Node, the following general preconditions have to be met:

� If the CDU Version is in status ’DEVELOPMENT’ the user has to be the owner of theUser Tree Node (End Item) to be updated.


A User Tree Node (End Item) in a CDU Version which is in status ’FROZEN’ cannot be updated.

8.1.8.1 Update User Tree Node Properties

For updating End Items, please refer to ’Update specific End Item detailed data’.

To update User Tree Node Properties, the following general preconditions have to be met:

� To update (change) the owner of a User Tree Node, the user has to be the owner of theowner of its father node.

� To update (change) the owner of a complete subtree (which means of each User Treenode contained in the subtree), the user has to be the owner of the subtree root node’sfather node.

To create new owners or delete existing ones from the user list, please refer to the MDAInstallation and Administration Manual.

� To update the SID Number the CDU version must be of domain ’USER_DEF_SIDS’.

8.1.8.1.1 Update the description of a User Tree node

To update the description of a User Tree node:

1. Select the specific End Item and execute Properties–>Selection... .


2. Position the cursor on Description and click on the left mouse button.

3. Update the description and Apply.

8.1.8.1.2 Update/change the owner of a User Tree node

To update/change the owner of a User Tree node:

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–15


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:





3. Select ’Node’.

4. Apply again.

The owner of the User Tree node has changed.

8.1.8.1.3 Update/change the owner of a User Tree subtree

To update/change the owner of a User Tree subtree:




3. Select ’Subtree’.

4. Apply again.

The owner of each node contained in the subtree has changed.

8.1.8.1.4 Update/change the SID Number of a User Tree Node

To update/change the SID number of a User Tree subtree:



2. Enter the new SID Number or select SID Range... for a list of all valid SID Ranges. Se-

lect Quit to exist the list of valid SID Ranges. The new SID Number has to be withinone of the valid SID Ranges.

3. Apply.

The SID Number of the node has changed. In case the new SID Number is not unique within thescope of the current CDU version an error message is displayed and the user is asked to enter anew unique SID Number.

8.1.8.2 Update specific End Item detailed data

The detailed data of End Items differ essentially depending on their End Item Type. Thereforethe update of End Item detailed data will be described in an exemplary way in the following:

To Update specific End Item detailed data:

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–16


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


1. Select the specific End Item.

2. Select File–>Open–> or

position the cursor in the User Tree Nodes area and select Open–>. Move the cursor tothe right and choose one of the detailed data groupings, continue as described in the ex-amples.

The following examples start from the point where a specific End Item has been selected!

8.1.8.2.1 Example: Update End Item MDM_IO_BOARD

To update End Item MDM_IO_BOARD

1. Execute File–>Open–>MDM_IO_BOARD...

The ’MDM_IO_BOARD’ window will be displayed:

Figure 41. MDM_IO_BOARD

2. Enter an MDM Board Type or

select MDM Board Type ... for a list of all valid types, select one and Apply.

8.1.8.2.2 Example: Update End Item Support Information

To update End Item Support Information

1. Execute File–>Open–>Support Information... the ’Engineering Support Information’window will be displayed:

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–17


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 42. Engineering Support Information

2. Enter a Name, Version, Creating author, etc. and Apply.

8.1.8.2.3 Example: Update End Item Channel Description

To update End Item Channel Description

1. Execute File–>Open–>Channel Description...

The ’Channel Description’ window will be displayed:

Figure 43. Channel Description

The user may update or delete existing channel description entries or insert new ones.

To insert a new channel description entry:

2. Execute Insert–>Top to create an entry at the top of the entry list,

or

execute Insert–>Bottom to create an entry at the bottom of the entry list,

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–18


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


or

select an entry from the list and execute Insert–>Before to create an entry before theselected one in the entry list, or

select an entry from the list and execute Insert–>After to create an entry after the se-lected one in the entry list,

In each case the detailed ’Channel Description’ window is displayed:

Figure 44. Detailed Channel Description

3. Enter the Connector No. and Channel No. of the new entry.

4. Enter a signal type or

select Signal Type... for a list of all valid signal types, select one and Apply.

Figure 45. SIGNAL_TYPE list

5. Press Apply in the ’Channel Description’ window to make the entries persistent

The new entry is created as specified.

To update an existing channel description entry

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–19


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:




2. Select the desired Channel Description from the entry list and execute Open.

The detailed ’Channel Description’ window is displayed.

In this example it is only possible to update the signal type of a specific channel

3. Enter another signal type or

Select Signal Type... for a list of all valid signal types, select one and Apply

4. Apply in the ’Channel Description’ window to make the changes persistent

The entry is updated as specified.

To delete an existing channel description entry



2. Select the desired Channel Description from the entry list and execute Delete.

MDA will ask ’Do you really want to delete?’


The entry is deleted from the entry list.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–20


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8.2 CDU VERSION

In this section all operations on CDU Versions are described.

8.2.1 Consistency Checker

To perform a consistency check:

1. Select the specific CDU Version and execute Command–>Consistency Checker... .

The ’Consistency Checker’ window is displayed.

Figure 46. Consistency Checker

2. Please refer to the Consistency Checker section for more information on how to performconsistency checks.

8.2.2 Create

To create a new CDU Version the following preconditions have to be met:


� A CDU Root Node has already been defined.

� The user must work on the MDB instance which is associated to the father of the CDURoot Node (System Tree Node).

For all the ’... by copying ...’ operations, the CDU domain is copied automatically as part of thecontent. To update the CDU domain, please refer to the ’Update the CDU domain of a CDU Ver-sion’ operation.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–21


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8.2.2.1 Create an empty CDU Version

To Create an empty CDU Version:

1. Navigate to the desired CDU Root Node and select it

2. Execute File–>Show CDU Versions... or

Execute File–>Open or

position the cursor into the System Tree Nodes area, press the right mouse button and

select Open.

In all three cases the ’CDU Versions’ window is displayed listing all existing CDU Versions ofthe selected CDU Root Node.

Figure 47. CDU Versions

3. Execute Edit–>Create...

The ’Create CDU Version’ window is displayed.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–22


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 48. Create CDU Version

4. Select New Version.

5. Enter an owner

or

select Owner... for a list of all valid users, select one and Apply.

The Owner field is mandatory and has to be filled.

Figure 49. User List

6. Enter a short description of the new CDU Version (optional).

7. Enter a CDU domain or

select CDU domain... for a list of all valid domain values, select one and Apply.

The CDU Domain field is mandatory and has to be filled.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–23


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 50. CDU domain list help

8. Press Apply.

The new CDU Version is shown in the CDU Versions area. MDA automatically generates the nexthigher version number. The issue and revision number are set to zero as well as the status is setto ’DEVELOPMENT’.

Figure 51. CDU Versions area after creating an empty CDU Version

8.2.2.2 Create a CDU Version by copying an old CDU Version

Perform steps 1. to 6. of ’Create an empty CDU Version’.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–24


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Do not perform step 7,

instead do the following to Create a CDU Version by copying an old CDU Version:

7. Select Copy from CDU Version... for a list of all CDU (Test) Versions of the selected CDURoot Node and select a CDU Version.

Figure 52. CDU Version List

8. Press Apply to close the CDU Version list window.

9. Press Apply.

The copied CDU Version is shown in the CDU Versions area. MDA automatically generates thenext higher version number. The issue and revision number are set to zero as well as the statusis set to ’DEVELOPMENT’.

8.2.2.3 Create a CDU Version by copying a CDU Test Version

Perform steps 1. to 6. of ’Create an empty CDU Version’.,

Do not perform step 7

instead do the following to Create a CDU Version by copying a CDU Test Version:

7. Select Copy from CDU Version... for a list of all CDU (Test) Versions of the selected CDURoot Node and select a Test Version.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–25


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 53. CDU Version List


9. Press Apply.

The copied CDU Version is shown in the CDU Versions area. MDA automatically generates thenext higher version number. The issue and revision number are set to zero as well as the statusis set to ’DEVELOPMENT’.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–26


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 54. CDU Versions area after creating a new Version by copying a Test Version

8.2.2.4 Create an Issue of a CDU Version

Notice: MDA will only create a new issue if all other existing Versions of the CDU with the sameversion identifier are in status ’FROZEN’ (e.g. V2.0.0 FROZEN and V2.1.0 FROZEN andV2.1.1 FROZEN –> new issue created is V2.2.0 DEVELOPMENT).

To Create an Issue of a CDU Version

1. Navigate to desired CDU Root Node and select it



position the cursor into the System Tree Nodes area, press the right mouse button andselect Open.




4. Select New Issue.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–27


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


5. Enter an owner

or




7. Select Copy from CDU Version... for a list of all CDU (Test) Versions of the selectedCDU Root Node and select a CDU Version in status ’FROZEN’ .


9. Press Apply.

The copied CDU Issue is shown in the CDU Versions area. MDA automatically generates the nexthigher issue number and sets the revision number to zero. The version number is the same as theone from the copied CDU Version. The status is ’DEVELOPMENT’.

Figure 55. CDU Versions area after creating a new Issue of a CDU Version

8.2.2.5 Create an Issue of a CDU Version by copying a CDU Test Version

Notice: MDA will only create a new issue if all other existing Versions of the CDU with the sameversion identifier are in status ’FROZEN’ (e.g. V2.0.0 FROZEN and V2.1.0 FROZEN andV2.1.1 FROZEN –> new issue created is V2.2.0 DEVELOPMENT).

To Create an Issue of a CDU Version by copying a CDU Test Version

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–28


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:






select Open.





5. Enter an owner

or




7. Select Copy from CDU Version... for a list of all CDU (Test) Versions of the selectedCDU Root Node and select a CDU Test Version in status ’FROZEN’.

Notice :The initial Test Version V0.0.0 may not be used as the basis for creating a new issue.


9. Press Apply.

The copied CDU Issue is shown in the CDU Versions area. MDA automatically generates the nexthigher issue number and the revision number is set to zero. The version number is the same asthe one from the copied CDU Test Version. Automatically generated are also the actual MDBInstance as well as the Status ’DEVELOPMENT’.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–29


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 56. CDU Versions area after creating a new Issue by copying a Test Version

8.2.2.6 Create a Revision of a CDU Version

Notice: MDA will only create a new revision if all other existing Versions of the CDU with thesame version identifier are in status ’FROZEN’ (e.g. V2.0.0 FROZEN and V2.1.0 FROZEN andV2.2.1 FROZEN –> new revision created is V2.2.2. DEVELOPMENT).

To Create a Revision of a CDU Version:








4. Select New Revision.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–30


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


5. Enter an owner

or




7. Select Copy from CDU Version... for a list of all CDU (Test) Versions of the selectedCDU Root Node and select a CDU Version in status ’FROZEN’.


9. Press Apply.

The copied CDU Revision is shown in the CDU Versions area. The version and issue numbersare the same as the one from the copied CDU Version but MDA automatically generates the nexthigher revision number. The status is ’DEVELOPMENT’.

Figure 57. CDU Versions area after creating a Revision of a CDU Version

8.2.2.7 Create a Revision of a CDU Version by copying a CDU Test Version

Notice: MDA will only create a new revision if all other existing Test Versions of the CDU withthe same version identifier are in status ’FROZEN’ (e.g. V2.0.0 FROZEN and V2.1.0 FROZENand V2.2.1 FROZEN –> new revision created is V2.2.2. DEVELOPMENT).

To Create a Revision of a CDU Version by copying a CDU Test Version:


8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–31


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:









5. Enter an owner

or

select Owner... for a list of all valid users, select one and Apply.The Owner field is mandatory and has to be filled.


7. Select Copy from CDU Version... for a list of all CDU Versions of the selected CDURoot Node and select a Test Version in status ’FROZEN’.


9. Press Apply.

Notice :The initial Test Version V0.0.0 may not be used as the basis for creating a new revision.

The copied CDU Revision is shown in the CDU Versions area. The version and issue numbersare the same as the one from the copied CDU Test Version but MDA automatically generates thenext higher revision number. Automatically generated are also the actual MDB Instance and theStatus ’DEVELOPMENT’.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–32


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 58. CDU Versions area after creating a Revision by copying a Test Version

8.2.3 Delete a CDU Version

To delete a CDU Version the following preconditions have to be met:


� The CDU Version is in status DEVELOPMENT

� The CDU Version is not referenced by any CCU

� If the CDU Version is in status ’FROZEN’, it must have been archived before it can bedeleted.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–33


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To Delete a CDU Version:

1. Select the specific CDU Version and execute Edit–>Delete.

A confirmation window is displayed asking ’Do you really want to delete the CDU Version?’.

Figure 59. Confirmation window


The CDU Version is deleted from the ’CDU Versions’ window.

8.2.4 Open


8.2.5 Print

To obtain a print:

1. Select the specific CDU Version and executeCommand–> Tools –> Flexible MDB Reports

The ’Report Generator’ window is displayed.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–34


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 60. Report Generator

2. Please refer to the Flexible MDB Reports Generation section to specify the desired re-

port to be generated.



8.2.7 Data Distribution and Archiving


8.2.7.1 Distribute/Archive a CDU Version

The user can archive or distribute a CDU Version to the file system. The archiving stores the CDUVersion outside the MDB. Archived CDU Versions can be deleted by I_MDB even if they are fro-zen. Distributed CDU Versions can be imported by other MDB instances.

To perform the archive / distribution the following preconditions have to be met:

� The CDU Version has to have the status ’FROZEN’


To distribute/archive a CDU Version:

1. Navigate to the CDU Version window and select a version

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–35


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


2. Execute Command–>Export... to enter the ’Data Distribution / Data Archiving’ win-

dow.

Figure 61. CDU Version Data Distribution / Data Archiving window

3. Select Distribution or Archiving for the export type depending on the user choice.

Only the data archiving provides the configuration manager with the possibility to delete the CDUversion beyond the archiving.

ItemThe field contains the item from which the data distribution or data archiving will be performed.In this case it is the CDU Version.


Info FileThe field contains the information file name. It contains the same information as the ’Data Ar-chiving / Data Distribution’ window in ASCII format. The ’InfoFile’ filename has the same prefixas the export file name with the extension ’.info’.

4. Select the Export File field and enter the name of the export file.

The field is mandatory.

If no extension will be entered for the filename, the extension ’.dmp’ will be added automatically.Otherwise the user may add any extension he wants. The file will be stored in the user Home–Di-rectory.


8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–36


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


5. Select the Receiver field and enter the receive area.

The receive field is only active when the export type is distribution. Any name can be assignedand no check will be performed by I_MDB.

6. Select the Remark field and enter a comment to the export (optional).

The maximum number of allowed characters is 255.



8.2.7.2 Import/Restore a CDU Version

The user can import a CDU Version that has been exported by the distribution function fromanother MDB instance. The restore function imports a CDU Version that has been archived anddeleted via I_MDB.

To perform the import/restore, the following precondition has to be met:


To import/restore a CDU Version:



Figure 62. CDU Version Import / Restore Window

3. Import Type: Select Import for the import type if a distributed CDU Version shall be

loaded into the MDB or

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–37


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


select Restore for the import type if an archived CDU Version shall be loaded into the

MDB

4. Keep CCU Structure: Not needed for import of CDU Versions.

5. Confict behaviour: Only interesting in case of import of CDU Versions which comesfrom another MDB version.

If Conflict behaviour Abort is selected then the import aborts in case of any detectedconflicts.If Automatic is selected then the import shall solve all conflicts automatically (not yet

implemented).The Conflict behaviour is defaulted to Interactive. In this case the Import Conflicts

window pops up. This window lists all CDU versions imported including conflictclasses and actions for resolving these conflicts.

6. Select the Filename field and enter the name of the import/restore file.The field is mandatory.

Note: This file must be located in the user’s home directory.

7. Press Execute to start the import/restore.

In case the chosen conflict behaviour was interactive after some time the conflict window pops–up. This window lists the CDU version imported including conflict classes and actions for resolv-ing these conflicts (see section below). Only in case no conflicts were detected the import can becontinued by clicking on the ’ok’ button.


8.2.8 Show

8.2.8.1 Show CDU Versions

To Show CDU Versions:

1. Navigate within the ’System Tree Version’ scope within the Navigator window to a spe-cific CDU Node

2. Select the desired CDU

3. Execute File–>Show CDU Versions... or execute File–>Open or


8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–38


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



Pull the push pin in the upper left window corner to leave the window unchanged.

8.2.8.2 Show CDU Version Properties

To Show CDU Version Properties:

1. Navigate to the ’CDU Versions’ window as described in the previous section, step 1

2. Select a specific CDU Version and execute Edit–>Properties... .

The ’CDU Version Properties’ window is displayed listing all properties of the selected CDU Ver-sion.

Figure 63. CDU Version Properties

The Creation, Change, Review, and Frozen dates are set automatically by MDA. Consistency dateand status are set by the Consistency Checker. As long as the Consistency Checker has not runon the CDU Version, the Consistency status is ’NONE’.

The Restrictions button is enabled in case of restrictions which are attached on the CDU Version.Klick on Restrictions button to show a list of restricted item type – aggregate pairs ordered by ItemType or Aggregate. The attached CDU restrictions are only active if the CDU type is restricted.

The Ownership choice allows the CM user to set the owner which is shown in the ’Owner’ entryto the CDU version or to set the owner to the CDU version and its containing items.Since the CDU Version shown in the figure is still in status ’DEVELOPMENT’, there is no Re-view or Frozen date set.Pull the push pin in the upper left window corner to leave the window unchanged.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–39


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



The user can obtain information about all CDU version exports within the system tree versiondetermined by the navigation scope. This function is a part of the export/import informationbrowser which can be reached from the Navigator window of I_MDB. The pathname of the navi-gation point in the I_MDB Navigator window is used as the default value for the CDU pathnamefilter.

To show CDU version exports, the following precondition has to be met:

� Navigation scope is ’System Tree Version’

To show CDU Version exports:

1. Navigate to the ’System Tree Version’ scope within the Navigator window, no SystemTree Node is selected

2. Execute File –> Browse Exports –>CDU Versions... to enter the ’Show Exports’ win-

dow.

Figure 64. CDU version show exports window

Dedicated filters can be specified by the user in order to get information only from those versionsmatching the filter criteria. Within a filter field wildcards ’*’ can be used as a pattern for any char-acter. Leaving a filter field blank is equivalent to ’*’.

3. Select the CDU Path field and enter desired filter data

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–40


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Default is the navigation point of the I_MDB Navigator window. By confirming the default, onlyinformation from the CDU version within this subtree will be obtained.

4. Select the CDU version field and enter version, issue and revision

5. Press the Search button to obtain a list of all CDU version exports matching the speci-

fied filter criteria


Notice: In case no filter items are specified the user gets an export list of all existing exports ofthe default subtree.










The user can obtain information about all CDU version imports within the system tree versiondetermined by the navigation scope. This function is a part of the export/import informationbrowser which can be reached from the Navigator window of I_MDB. The pathname of the navi-gation point in the I_MDB Navigator window is used as the default value for the CDU pathnamefilter.

To show CDU version imports, the following precondition has to be met:


To show CDU Version imports:

1. Navigate to the ’System Tree Version’ scope within the Navigator window, no System

Tree Node is selected

2. Execute File –> Browse Imports –>CDU Versions... to enter the ’Show Imports’ win-dow.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–41


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 65. CDU show imports window


3. Select the CDU Path field and enter desired filter data

Default is the navigation point of the I_MDB Navigator window. By confirming the default onlyinformation from the CDU version within this subtree will be obtained.

4. Select the CDU Version field and enter version, issue and revision

5. Press the Search button to obtain a list of all CDU version imports matching the speci-



Notice: In case no filter items are specified the user gets an import list of all existing imports ofthe default subtree.





8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–42


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:









8.2.9 Update CDU Version Properties

The user is able to update a CDU Version if the following preconditions are met:


� The CDU Version is not in status ’FROZEN’.

8.2.9.1 Update the description of a CDU Version

To update the description of a CDU Version:

1. Select the specific CDU Version and execute Edit–>Props... .


2. Position the cursor on Description and click on the left mouse button.

3. Update the description and Apply.

8.2.9.2 Update/change the owner of a CDU Version

To update/change the owner of a CDU Version:



2. Enter an owner

or


8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–43


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



3. Press Apply

To create new users or delete existing ones from the User list, please refer to the MDA Installationand Administration Manual.

8.2.9.3 Update the status of a CDU Version to REVIEW

To update the status of a CDU Version to REVIEW:



2. Select the status REVIEW .

3. Press Apply.

The updated CDU Version status is shown in the CDU Versions area. MDA automatically gener-ates the Review date, which can be seen in the CDU Version Properties window.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–44


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 67. CDU Versions area after updating the status of a CDU Version to ’REVIEW’

8.2.9.4 Update the status of a CDU Version to FROZEN

Notice: The status of a CDU Version can only be updated to FROZEN, if the Consistency Check-er has run at least once on the CDU Version. If a CDU Version is set to ’FROZEN’ it can neverbe modified again.

To update the status of a CDU Version to FROZEN:



2. Select the status FROZEN.

3. Press Apply.

The updated CDU Version status is shown in the CDU Versions area. MDA automatically gener-ates the Frozen date, which can be seen in the CDU Version Properties window.

8.2.9.5 Update the CDU domain of a CDU Version

Notice: A CDU domain can only be updated if the CDU Version is in status ’DEVELOPMENT’and does not contain any End Items yet.

To update the CDU domain of a CDU Version:

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–45


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:







3. Press Apply

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–46


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8.3 CDU TEST VERSION

In this section all operations on CDU Test Versions are described.

In all cases where the operations on CDU Versions and CDU Test Versions are identical, only ref-erences to the corresponding CDU section will be given.


Please refer to the CDU Version ’Consistency Checker’ operation (see chapter 8.2.1, page 8–20).

8.3.2 Create

To create a new CDU Test Version the following preconditions have to be met:



For all the ’... by copying ...’ operations, the CDU domain is copied automatically as part of thecontent.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–47


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8.3.2.1 Create an empty CDU Test Version

To Create an empty CDU Test Version :

1. Navigate to the desired CDU Root Node and select it

2. Execute File–>Show CDU Versions... or File–>Open or




3. Execute Edit–>Create... .


8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–48


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



4. Select New Test Version.

5. Enter an owner or




6. Enter a short description of the new CDU Test Version (optional).



The CDU Domain field is mandatory and has to be filled.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–49


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



8. Press Apply.

The new CDU Test Version is shown in the CDU Versions area. MDA automatically generatesthe actual MDB Instance with the CDU Type ’T’ and the next higher # and the Status ’DE-VELOPMENT’. The CDU Test version, issue and revision numbers are set to zero:’0.0.0’.

Figure 73. CDU Versions area after creating an empty CDU Test Version

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–50


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8.3.2.2 Create a CDU Test Version by copying a CDU Version

To Create a CDU Test Version by copying a CDU Version:

Perform steps 1. to 6. of ’Create an empty CDU Test Version’.


instead do the following:

7. Select Copy from CDU Version... for a list of all CDU (Test) Versions of the selected CDURoot Node, select a CDU Version.

8. Press Apply to leave the CDU Version list window.

9. Press Apply.

The new CDU Test Version is shown in the CDU Versions area. The CDU Test version, issue andrevision numbers are the same as the ones from the copied CDU Version. MDA automaticallygenerates the Type ’T’ with # ’1’ and the actual MDB Instance as well as the Status ’DEVELOP-MENT’.

Figure 74. CDU Versions area after creating a Test Version by copying a CDU Version

8.3.2.3 Create a CDU Test Version by copying an old CDU Test Version

To Create a CDU Test Version by copying an old CDU Test Version

Perform steps 1. to 6. of ’Create an empty CDU Test Version’.



8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–51


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


7. Select Copy from CDU Version... for a list of all CDU (Test) Versions of the selected CDURoot Node, select a Test Version.


9. Press Apply.

The new CDU Test Version is shown in the CDU Versions area. The CDU Test version, issue andrevision numbers are the same as the ones from the copied Test Version. MDA automatically gen-erates the next higher # and the actual MDB Instance as well as the Status ’DEVELOPMENT’.

Figure 75. CDU Versions area after creating a Test Version by copying an old one

8.3.3 Delete a CDU Test Version

Please refer to the CDU Version ’Delete a CDU Version’ operation (see chapter 8.2.3, page 8–32).

8.3.4 Open


8.3.5 Print

Please refer to the CDU Version ’Print’ operation (see chapter 8.2.5, page 8–33).





8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–52


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8.3.8 Show

Please refer to the CDU Version ’Show’ operation (see chapter 8.2.8, page 8–37).

8.3.9 Update

Please refer to the CDU Version ’Update CDU Version Properties’ operation (see chapter 8.2.9,page 8–42).

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–53


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


8.4 RESTRICTED CDU VERSION

In this section all operations on Restricted CDU Versions are described.

In all cases where the operations on CDU Test Versions and Restricted CDU Versions are identi-cal, only references to the corresponding CDU section will be given.

8.4.1 Concept

With the previous CGS, users are not allowed to create local versions of foreign–owned CDUs.They may create Test Versions only which has the undesirable effect of providing unrestrictedaccess to the CDU contents. To remedy this shortcoming, the Restricted CDU Version concepthas been introduced. Like a Test Version, a Restricted CDU Version will be locally–owned. How-ever the user’s access will be limited to specific item type – aggregate combinations.

Default access restrictions (i.e. list of modifiable type aggregate combinations) will be definedby the installation of the MDB. The restrictions will apply to all designated foreign MDBinstances, i.e. instances not owning the CDU’s parent System Tree node.

The default restrictions are changeable by the Restrictions Administration Tool. This tool is in-vokable with I_MDB –> File –> CDU Restrictions Administration or by the CCU/CDU versionexport.

The CDU version export attaches the instance restrictions on the CDU version and the CCU ver-sion on each included CDU version.

The restrictions which are attached on a CDU version are copied by each copy process of thisCDU version.

The attached restrictions are only active in Restricted CDU Versions.

Figure 76. Concept of Restricted CDU Version

It is not possible to create an empty Restricted CDU Version.

It is not possible to create an item (Virtual and End Item) in a Restricted CDU Version.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–54


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The number ’#’ is unique in CDU for both: Test Versions and Restricted Versions.That means it must not exist a Test Version and a Restricted Version with the same ’#’ in the sameCDU.

8.4.2 CDU Version Restrictions Administration

To invoke the ’CDU Version Restrictions Administration’ tool:

Select File –> CDU Restrictions Administration.

Figure 77. CDU Version Restrictions Administration

To change CDU Restrictions:Select Restricted in the desired End Item Type – Aggregate row and enter ’N’ or ’Y’.Then klick on the Commit button or select Edit –> Commit.

Menue

� Exit button or select File –> Exit :Exit the program.

� Commit button or select Edit –> Commit:Save all changes in the database.

� Rollback button or select Edit –> Rollback:Undo all changes made since last commit.

� Export button:Not yet implemented.

� Import button:Not yet implemented.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–55


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� Select Options –> ToolbarShow button toolbar.

� Select Options –> BellNotify user by beeping.

� Select Options –> Hint logOn: Status field displays history of messagesOff: Status field displays last message

� Select Options –> Resume positionPosition the window properly on the screen.


Please refer to the CDU Version ’Consistency Checker’ operation (see chapter 8.2.1, page 8–20).

8.4.4 Create

To create a new CDU Test Version the following preconditions have to be met:



� ’Copy from CDU Version’ is mandatory.

For all the ’... by copying ...’ operations, the CDU domain is copied automatically as part of thecontent.

To Create a Restricted CDU Version by copying a CDU Version:

1. Navigate to the desired CDU Root Node and select it.


File–>Open or


select Open.


8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–56


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



3. Execute Edit–>Create... .



4. Select New Restricted Version.




8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–57


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



6. Enter a short description of the new CDU Test Version (optional).

7. Select Copy from CDU Version... for a list of all CDU (Test) Versions of the selected CDURoot Node, select a CDU Version.


9. Press Apply.

The new Restricted CDU Version is shown in the CDU Versions area. The Restricted CDU ver-sion, issue and revision numbers are the same as the ones from the copied CDU Version. MDAautomatically generates the Type ’R’ with # ’1’ and the actual MDB Instance as well as the Sta-tus ’DEVELOPMENT’.

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–58


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 81. CDU Versions area after creating a Restricted Version by copying a CDUVersion

8.4.5 Delete a Restricted CDU Version

Please refer to the CDU Version ’Delete a CDU Version’ operation (see chapter 8.2.3, page 8–32).

8.4.6 Open


8.4.7 Print






8.4.10 Show

Please refer to the CDU Version ’Show’ operation (see chapter 8.2.8, page 8–37).

8.4.11 Update

Please refer to the CDU Version ’Update CDU Version Properties’ operation (see chapter 8.2.9,page 8–42).

8–59

CGS–RIBRE–SUM–00032 03.07.2015– –8–59


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


9 CCU

For specific tests, simulations and application executions, specific User Tree (CDU) Versions must be con-figured which means that it has to be decided for each concerned User Tree (CDU) which Version/Issue/Re-vision to take for this specific purpose. As such a CCU is a composition of Configuration Data Units (CDUs),which are needed to represent a specific test environment or in general an applications execution environ-ment for e.g. simulation.

The development of Configuration Control Units down to atomic CDUs is determined by particular test andoperation purposes for mission specific element configuration needs on a more abstract level. Detailed enditem data is not relevant in this context in the sense that data is only logically grouped (configuration con-trolled) and checked for consistency and integrity, but not accessed. Nevertheless, MDA provides the possi-bility to navigate into a specific CCU Version and work on detailed data e.g. within one of its referencedCDUs, as if the user would navigate into the CDU Version directly through the Name Tree and would workfrom there.

A CCU may exist in several different versions and is always related to a node of a System Tree. A CCU Ver-sion contains clear references to other CCU– or CDU Versions. The scope of a CCU is the set of all referencedCCU– and CDU Versions. If all CCU Version references would be severed it would end up in a set of CDUVersion references. All CCU– and CDU Versions must clearly be referenced, i.e. MDA will always preventusers from referencing two different Versions of the same e.g. CCU.

Please remember that since each CCU is related to a System Tree Node and the System Tree is organizedhierarchically, a CCU referencing lower level ones (the subtree of this CCU), is too.

Each CCU Version is owned by one user.

The status of a CCU Version denotes whether it can still be modified (status ’DEVELOPMENT’) or if itscontents are frozen and can not be modified any longer (status ’FROZEN’).

Notice: MDA provides the possibility to navigate into a specific CCU Version and work on de-tailed data e.g. within one of its referenced CDUs, directly. This is possible because MDA doesresolve all references so that a user will see System Tree Nodes and CDU Nodes without any Sys-tem Tree or CDU Version information. All operations on these kind of nodes may be used as de-scribed in the corresponding sections of this Manual.

9.1 CCU (CCU NAME)

In this section all operations on CCUs are described.

9.1.1 Create

To create a new CCU the following preconditions have to be met:


� The corresponding System Tree Version is in status ’FROZEN’.

To Create a CCU:

1. Perform the operation ’Show CCU Versions’ described in section ’CCU Version’.

2. Move to the Edit button above the CCU Names area (left) and execute Edit–>Create...

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The ’Create CCU’ window is displayed.

3. Enter a Name for the CCU and Apply.

The Name of the new CCU is added to the list of CCU Names in the CCU Names area. If the newcreated CCU is selected, there are no existing Versions of it yet..

Figure 82. Create CCU

9.1.2 Delete

To delete a CCU the following preconditions have to be met:


� There are no existing Versions of the CCU

To Delete a CCU:

1. Perform the operation ’Show CCU Versions’ described in section ’CCU Version’.

2. Select the Name of the CCU to be deleted.

3. Move to the Edit button above the CCU Names area (left) and execute Edit–>Delete .

A confirmation window is displayed asking ’Do you really want to delete the CCU?’.


The CCU is deleted in the CCU Names area.

9.2 CCU VERSION

In this section all operations on CCU Versions are described.

9.2.1 Browse CCU Versions

To Browse CCU Versions:

1. Navigate into the System Tree Version in which you want to browse the CCU Versions.(Refer to the common operation ’Navigating through the Name Tree’.)

2. Execute File–>Browse All CCU Versions... .

The ’Browse CCU Version’ window is displayed listing all existing CCU Versions in the SystemTree Version.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



Each entry consists of the pathname of the System Tree Node to which a CCU is attached, as wellas the CCU Name and the CCU Version Identifier.


To perform a consistency check:

1. Perform the operation ’Show CCU Versions’ to enter the ’I_MDB:CCU Versions’ win-

dow.

2. Select the Name of the desired CCU.

3. Select the desired Version on which the consistency check shall be performed.

4. Move to the Command button above the CCU Versions area (right) and execute Com-mand–>Consistency Checker...

The ’Consistency Checker’ window is displayed.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 84. Consistency Checker

5. Please refer to the Consistency Checker section for more information on how to performconsistency checks.

9.2.3 Create

9.2.3.1 Create an empty CCU Version

To create an empty CCU Version the following preconditions have to be met:


� A CCU has already been defined.

To Create an empty CCU Version:

1. Perform the operation ’Show CCU Versions’ to enter the ’I_MDB:CCU Versions’ win-dow.

2. Select the Name of the CCU for which a new Version shall be created.

3. Move to the Edit button above the CCU Versions area (right) and execute

Edit–>Create...

The ’Create CCU Version’ window is displayed.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 85. Create CCU Version

4. Select New Version.

5. Enter an owner

or




7. Press Apply.

The new CCU Version is shown in the CCU Versions area. MDA automatically generates the nexthigher version number. The issue and revision number are set to zero, the status is set to ’DE-VELOPMENT’.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 86. Created CCU Version

9.2.3.2 Create a CCU Version by copying an old one

Perform steps 1. to 6. of ’Create an empty CCU Version’. Do not perform step 7,


7. Select Copy from CCU Version... for a list of all CCU Versions of the selected CCU, selectone and Apply.

After selection of a CCU version that shall be copied, the Including CDIs data entry field be-comes active. This data entry fields allows the user to define if the CDIs (for details about CDIsrefer to chapter 12) that were generated for the CCU version to be copied shall also be copied tothe new CCU version or not.

8. Position the cursor to the small Including CDIs square box and press the right mouse keyto select No or Yes (No is default) from the menu.

9. Press Apply.

The copied CCU Version is shown in the CCU Versions area. MDA automatically generates thenext higher version number. The issue and revision number are set to zero, the status is set to ’DE-VELOPMENT’. All references to CDU and CCU versions of the CCU version to be copied werecopied to the new CCU version. Depending on the Including CDIs option also the CDI of theold CCU version were copied or not.

9.2.3.3 Create an Issue of a CCU Version

Notice: MDA will only create a new issue if all other existing Versions of the CCU with the sameversion identifier are in status ’FROZEN’ (e.g. V2.0.0 FROZEN and V2.1.0 FROZEN andV2.1.1 FROZEN –> new issue created is V2.2.0 DEVELOPMENT).

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To Create an Issue of a CCU Version:

1. Perform the operation ’Show CCU Versions’.


3. Move to the Edit button above the CCU Versions area (right) and executeEdit–>Create...






7. Select Copy from CCU Version... for a list of all CCU Versions of the selected CCUand select one in status ’FROZEN’.

8. Press Apply to leave the CCU Version window.

After selection of a CCU version that shall be copied the Including CDIs data entry field becomesactive. This data entry fields allows the user to define if the CDIs (for details about CDIs referto chapter 12) that were generated for the CCU version to be copied shall also be copied to thenew CCU version or not.

9. Position the cursor to the small Including CDIs square box and press the right mouse

key to select No or Yes (No is default) from the menu.

10. Press Apply

The copied CCU Issue is shown in the CCU Versions area. MDA automatically generates the nexthigher issue number and the revision number is set to zero. The version number is the same asthe one from the copied CCU Version. The status is ’DEVELOPMENT’. All references to CDUand CCU versions of the CCU version to be copied were copied to the new CCU version. Depend-ing on the Including CDIs option also the CDI of the old CCU version were copied or not.

9.2.3.4 Create a Revision of a CCU Version

Notice: MDA will only create a new revision if all other existing Versions of the CCU with thesame version identifier are in status ’FROZEN’ (e.g. V2.0.0 FROZEN and V2.1.0 FROZEN andV2.2.1 FROZEN –> new revision created is V2.2.2. DEVELOPMENT).

To Create a Revision of a CCU Version:



9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3. Move to the Edit button above the CCU Versions area (right) and execute

Edit–>Create...






7. Select Copy from CCU Version... for a list of all CCU Versions of the selected CCU

and select one in status ’FROZEN’.

8. Press Apply to leave the CCU Version window.

After selection of a CCU version that shall be copied the Including CDIs data entry field becomesactive. This data entry fields allows the user to define if the CDIs (for details about CDIs referto chapter 12) that were generated for the CCU version to be copied shall also be copied to thenew CCU version or not.

9. Position the cursor to the small Including CDIs square box and press the right mouse

key to select No or Yes (No is default) from the menu.

10. Press Apply

The copied CCU Revision is shown in the CCU Versions area. The version and issue numbersare the same as the one from the copied CCU Version but MDA automatically generates the nexthigher revision number. The status is ’DEVELOPMENT’. All references to CDU and CCU ver-sions of the CCU version to be copied were copied to the new CCU version. Depending on theIncluding CDIs option also the CDI of the old CCU version were copied or not.

9.2.4 Delete a CCU Version

Notice: If the CCU Version is in status ’FROZEN’ it additionally must have been archived before.

To delete a CCU Version the following preconditions have to be met:


� The CCU Version is in status DEVELOPMENT.

� The CCU Version is not referenced by any other CCU Version.

To Delete a CCU Version:


2. Select the Name of the desired CCU from which a Version shall be deleted.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3. Select the Name of the desired CCU Version to be deleted.

4. Move to the Edit button above the CCU Versions area (right) and execute Edit–>Delete.

A confirmation window is displayed asking ’Do you really want to delete the CCU Version?’.


The CCU Version including all its CDIs is deleted from the CCU Versions area.

9.2.5 Open



This operation may be used on any kind of node within a CCU Version after having executedOpen of that specific CCU Version.

Please refer to the common operation ’Pathname & SID’ for more information.

9.2.7 Print

To obtain a Print:


2. Select the Name of the CCU for which the Version data shall be printed.

3. Move to the Command button above the CCU Versions area (right) and execute Com-mand–>Print...

The ’Report Generator’ window is displayed.

Figure 87. Report Generator

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


4. Please refer to the Report Generation section to specify the desired report to be gener-

ated.

9.2.8 References

In the following subsections all operations on references to CCU– and CDU (Test) Versions aredescribed.

9.2.8.1 Maintain References

To Maintain References:


2. Select the Name of the CCU for which Version references shall be maintained.

3. Move to the Command button above the CCU Versions area (right) and execute Com-mand–>Maintain References...

The ’Maintain References’ window is displayed.

Figure 88. Maintain References

The upper window part (CCU References area) lists all existing references to other CCU Versionsgiven by the pathname of their corresponding System Tree Node to which the CCU is attached,their CCU Name and CCU Version.

The lower window part (CDU References area) lists all existing references to other CDU Versionsgiven by the pathname of their CDU Root Nodes, their CDU Version. If the referenced CDU ver-sion is a Test Version, additionally their MDB Instance and Test# is listed.

Notice: The user may create or delete the references to other CCU– or CDU (Test) Versions withina specific CCU Version only if he is the owner of this CCU Version. The CCU Version must bein status ’DEVELOPMENT’.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


9.2.8.2 Create References to other CCU Versions

Notice: In order to avoid double references only those CCU Versions can be referenced:

- which’s scope is not in the scope of the current CCU Version and

- which’s scope is not in the scope of such CCU Versions referencing the current one and

- which do not reference any CDU Versions located outside the current CCUs subtree.

To create a new reference to another CCU Version, continue with:

4. Move to the Edit button above the CCU References area and execute Edit–>Create....

The ’Browse CCU Version’ window is displayed listing all existing CCU Versions belonging tothe same level and to the subtree of the current CCU Version.


5. Select the CCU Version to be referenced and Apply.

The selected CCU Version is added to the entries in the CCU Versions area of the ’Maintain Refer-ences’ window.

9.2.8.3 Create References to other CDU (Test) Versions

Notice:In order to avoid double references only those CDU Versions can be referenced:

- which are not in the scope of the current CCU Version and

- which are not in the scope of such CCU Versions referencing the current one and

- which are not outside the subtree of the current CCU Version but only in case that thiscurrent CCU Version is referenced by other CCU Versions.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To create a new reference to another CDU Version, continue with:

4. Move to the Edit button above the CDU References area and execute Edit–>Create...

The ’CDU Browser’ window is displayed listing all existing CDU (Test) Versions within the cur-rent System Tree Version.

Figure 90. CDU Browser

5. Select the CDU (Test) Version to be referenced and Apply.

The selected CDU (Test) Version is added to the entries in the CDU Versions area of the ’MaintainReferences’ window.

9.2.8.4 Delete References to other CCU Versions

To Delete References to other CCU Versions continue with:

4. In the CCU Versions area select the CCU Version entry to be deleted.

5. Move to the Edit button above the CCU Versions area and execute Edit–>Delete

A confirmation window is displayed asking ’Do you really want to delete the CCU Reference?’.


The CCU Version entry is deleted from the CCU Versions area.

9.2.8.5 Delete References to other CDU Versions

To Delete References to other CDU Versions continue with:

4. In the CDU Versions area select the CDU (Test) Version entry to be deleted.

5. Move to the Edit button above the CDU Versions area and execute Edit–>Delete

A confirmation window is displayed asking you if you really want to delete the CDU Reference.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



The CDU (Test) Version entry is deleted from the CDU Versions area.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


9.2.9 CU Version Manager

The CU version manager allows the creation of new CCU and CDU versions by copying old ver-sions in a given CCU scope. The new versions then replace the old ones in the scope. This is usefulif the user has a frozen CCU version and wants to have a new scope containing the same data,with some of the referenced CCU or CDU versions in status DEVELOPMENT.Additionally, the CU version manager provides functionality to add or remove references to CUsin the current scope and to delete CCU versions and CDU versions in the MDB.

The CU Version Manager can be started with flexible tool invocation on a selected CCU version.

9.2.9.1 The CU Version Manager tool modes

In order to make the user interface as simple as possible, the tool can operate in two differentmodes, each mode providing different buttons to perform different actions. The current operatingmode is displayed in the left part of the main menu and can be switched by pressing on the toolscope menu item.

- in CREATION mode, the user has the possibility to create new CU versions by copyingexisting ones as well as adding references to CCUs in the scope.

- in DELETION mode, the tool allows the deletion of references and CU versions in theMDB. Deletion of CU versions has to be confirmed before the items will actually be de-leted in the MDB.

9.2.9.2 The CU Version Manager main window

1

2 3

4

5

5.15.25.3

6

Description:

Figure 91. CU Version Manager main window showing CCU reference view in CREATION mode

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–15


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The figure above shows the different components of the CU Version Manager main window inCREATION mode:

1. The main menuFile–>Open new scope

Allows to open the tool on another CCU scope.

File–>QuitQuit the program.

View–>toggle tree viewToggles the tree view mode between CCU reference mode and System Tree

mode.

View–>CU InformationShows a submenu that allows the user to switch on/off the different CU proper–

ties in the CU information area (4).

View–>show reference from outside of scope warningsWhether or not a warning shall be displayed when a CCU in status development will be changed that is referenced by another CCU that is not part of the current

scope.

View–>show broken reference chain warningsWhether or not a warning shall be displayed when a new version of a CU will becreated that will not be part of the new scope. This can happen if the user re

moves a CCU from the action list (5) that has references to other CUs that are

still in the action list.Action–>copy CCU related tables

whether or not all related tables of a CCU shall be copied with the version itself.

Action–>reset minor version numbersWhether or not the minor version numbers are resetby copying CU versions.

example for reset is active, action V+, CCU version:

Set issue to 0 and set revision to 0

example for reset is active, action I+, CDU testversion on original instance:Set revision to 0 and reset testversion to 0.

Action–>set descriptions for new CU versionsOpens a window which sets the description default

when a new version of a CU will be created.“%d” is the default and means that the descriptions of source

and target CU version are identical.

All other text and the four identifiers %d, %t,%u and %v set

the description of the target CU version.Identifiers:

%d source description

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–16


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


%t date and time

%u user%v source CU version

Example:

“Copy from version %v by user %u on %t”

e.g. “Copy from version 3.2.1 by user OPS$CGSADMIN on

22–SEP–2004 14:23:32”

Action–>perform selected actions in MDBstart to perform all actions that are defined in the action list in the MDB.

Help–>AboutOpens a window with tool version information.

Help–>User ManualOpens the Acrobat Reader with this document.In order for this menu entry to work, you have to have the Acrobat Reader

executable acroread in you current search path.

2. The CCU tree (in CCU reference mode)

The tree displays all CUs in the scope as well as the references between the CUs. The

tree structure reflects the CCU reference structure of the current scope. CCUs can opennew subtrees provided they have references. The subtrees can be expanded and col-

lapsed by clicking on the + and – icons, or by using the popup menu. One or more CUs

can be selected in the tree structure before defining an action on the selected CUs withone of the action buttons (6). A popup menu allows the creation and removal of CU ref-

erences.

The CCU tree (in System Tree mode)The tree displays the System Tree Nodes and CU versions in the scope. The tree structurereflects the MDB System Tree structure. The subtrees can be expanded and collapsed byclicking on the + and – icons, or by using the popup menu. One or more CUs can be selectedin the tree structure before defining an action on the selected CUs with one of the action but-tons (6). A popup menu allows the creation and removal of CU references.

3. The status bar

provides information on currently ongoing operations.

4. The CU information area

provides information on the currently selected CCU or CDU. If more than one CU iscurrently selected, no information will be shown. The user then has the possibility to

view CU information on a specific CU by using the popup menu on the desired CU in

the CCU scope tree (2). How much information is displayed is configurable via the

View–>CU Information menu. Displayable properties are: Name, new Name, Path, new

Path, Version, Instance, Owner, Status, Creation Date, Change Date, Description and

Internal Version.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–17


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


If exact one CU version is currently selected in the CCU tree and no CU version is se-

lected in the action list and the status of the selected CU version is not FROZEN thenthe CU version description is editable with the Description button.

5. The action list

contains all CUs which have been selected for any operation in the current tool session.The list displays Type, Name, Version, Action and New Name of the CUs. The field New

Name will only be filled for CUs with Action C+ (5.3) . In DELETION mode, this col-

umn will be renamed to leave scope. By using the popup menu, it is possible to delete

one or more of the CUs from the action list or to highlight the selected CUs in the CCUscope tree (2). The popup menu contains an entry to enter new names for C+ CUs in the

list.

5.1 CDU CDI_DEFINITIONS selected for creation of a new Testversion5.2 CCU DMSS_HW_V600 selected for creation of a new Revision

5.3 CDU KM_DIFFREP_TEST with action C+, which result in the creation of a

new CCU.

6. The action buttons (in CREATION mode)

After having selected one or more CUs from the CCU scope tree (2) or the action list

(5), the desired action (creation of a new Version, Issue, Revision, Testversion or CU)

can be selected by clicking on the appropriate button. All selected CUs will then betransferred to the action list and deselected in the CCU scope tree.

The action buttons (in DELETION mode)In DELETION mode there are two buttons, namely D (Delete CU) and K (Keep in Scope).These allow the user to mark all currently select CU versions for deletion, or to be kept inscope.

9.2.9.3 CU version creation constraints

Depending on the CU type and action, the tool will check for several conditions:

- action T+ , type CCU:A warning message will appear saying that it is not possible to create testversions ofCCUs.

- action V+, I+ or R+, type CDU:In case the systemtree node to which the CDUs are attached has another MDB instancethan the current instance, a warning message will appear saying that it is only allowed tocreate testversions at the specified system tree node.

- all actions and types:In case one of the CCUs between the toplevel CCU and the CCU referencing the selecteditem is in status DEVELOPMENT and belongs to the current user, it is checked for refer-

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–18


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


ences from out of scope. This could possibly lead to a change of data that is not intendedby the user. A warning message will be displayed if not switched off via the main menu.

- action remove from list, all types:When an item is removed from the action list, it is checked that it does not reference itemsthat are still in the action list. This would lead to the creation of the referenced CUs with-out being able to reference them in the new scope. A warning message will be displayedif not switched off via the main menu.

- action C+, all types:When changing a CU name, it is checked that the new name does not already exist in thenew scope.When changing a CU path, it is checked that the new path does not violate the ’referencedCU out of subtree’ rule.

9.2.9.4 CU version deletion constraints

Depending on the CU type and action, the tool will check for several conditions:

- action D , type CCU:If there are items in the action list that are referenced by the selected CCU, and theseitems can no longer be kept in the scope, an error message will be generated.No out of scope references to the selected CUs are allowed.The toplevel CCU of the selected CUs must have either no father CCU or a father CCU instatus DEVELOPMENT.

- action K , all types:It is checked that the selected items are includable in the new scope. That means that therehas to exist a CCU in the reference path which will still exist in the new scope.All selected CUs have to be in status DEVELOPMENT.

9.2.9.5 how to create CU versions

The creation process can be divided in three to four steps, depending on the action you choosefor the creation of the new CU versions.

9.2.9.5.1 Select on or more CUs

Select the appropriate CUs from the CCU scope tree (or the action list if it already containsentries) by clicking on them. The selected items will be highlighted.

9.2.9.5.2 Assign an action to selected CUs

Click on the appropriate action button. The chosen action is the applied to all selected CUsand the CUs will be transferred to the action list, provided you did not violate any of the abovementioned constraints.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–19


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Additionally, CCUs that need to be created to be able to include the selected CUs in the newscope are transferred to the action list. They will have no action defined and you will not beable to create any new CU in the MDB as long as you don’t assign an appropriate action tothese CCUs.

9.2.9.5.3 Assign a new name or path to C+ CUs

In case you have any C+ CU in the action list, you have to define a new name for these CUsbefore being able to actually create the CU versions in the MDB. Open the action list popupmenu on a single C+ CU to assign a new name or path to this CU only, or open the popup menuon the action list background to either select all CUs and assign names to all selected C+ CUs,or assign names to unnamed C+ CUs only.A new window will pop up allowing the user to enter new names for the CU(s):

Figure 92. CU Version Manager new name assignment window

Enter a new name and or new path for the CU (or alternatively open a System Tree Nodebrowser by clicking on the path: button) and click OK. Provided you did not violate any ofthe above mentioned constraints, the window will disappear and the new names will be dis-played in the action list.If you want to copy the CU to another system tree node, you can click on the desired pathbutton to bring up a system tree node selection window.

9.2.9.5.4 create new CU versions in the MDB

Select Action–>perform selected actions in the MDB from the main menu to start the creationof all CUs displayed in the action list in the MDB. Before the actual creation is started, allitems in the action list are checked for correctness.

After completion of the creation of the CUs in the MDB, the CCU scope tree will be updated toshow the modified scope.

9.2.9.6 how to delete CU versions

The deletion process can be divided in three to four steps, depending on the action you choosefor the creation of the new CU versions.

9.2.9.6.1 Select on or more CUs

Select the appropriate CUs from the CCU scope tree (or the action list if it already containsentries) by clicking on them. The selected items will be highlighted.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–20


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


9.2.9.6.2 Press the action button D

The selected CUs will be transferred to the action list, provided you did not violate any ofthe above mentioned constraints.

As additional information, the column leave scope in the action list displays how many ofthe CUs in the subtree of the selected CCU will leave the scope.

9.2.9.6.3 delete CU versions in the MDB

Select Action–>perform selected actions in the MDB from the main menu to start the deletionof all CUs with action D displayed in the action list in the MDB. Before the actual deletionis started, all items in the action list are checked for correctness and a confirmation windowwill pop up showing all CU versions that will be deleted.

It is possible to archive CUs if they are in status FROZEN and they are not created in otherMDB instances (i.e. not imported). In this case a window “Do you want to archive frozen CUsbefore deleting?” pops up.

After completion of the deletion of the CUs in the MDB, the CCU scope tree will be updated toshow the modified scope. As an exception, the tool will quit if the toplevel CCU has been deleted.

9.2.9.7 Reference creation and removal

The user can add or remove CUs from the current scope by using the CCU tree(2) popup menu:

Description:

Figure 93. The CCU tree popup menu

Depending on the status and type of the node, the popup menu contains different active entries,giving the user different options on what to do:

- Add new reference (only available in CREATION mode)This option is only available for CCU versions in status DEVELOPMENT and allows to

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–21


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


add another reference from the currently selected CCU to a new CU version that has to beselected.

- Remove reference to this CCU (only available in CREATION mode)This option is only available for CCU versions which are referenced by a CCU in statusDEVELOPMENT (but not for the toplevel CCU). It permanently removes the selectedCCU from the current scope without deleting the CCU version itself in the MDB.

- Remove reference to this CDU (only available in CREATION mode)This option is only available for CDU versions which are referenced by a CCU in statusDEVELOPMENT. It permanently removes the selected CDU from the current scopewithout deleting the CDU version itself in the MDB.

When adding a CU version to the current scope, a CU version selection window will pop up,where you can move through the actual System Tree. Locate and select the desired CU versionand press the Select button to insert the reference to the current scope.

Figure 94. The CU version selection window

Before the reference is actually inserted into the current scope, it will be checked if the referenceviolates any existing CCU/CDU reference rule.

The CU version selection window will stay open as long as you do not press the Quit button andtherefore allows the fast creation of multiple references.

9.2.9.8 Log file

The CU version manager writes all actions to a log file, /tmp/CUVM.log by default. If you wantto change the name and or location of the log file, set the environment variable CUVM_LOG tothe absolute pathname of the desired file.If the file size exceeds 500k, the tool will automatically discard the first part of the logfile.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–22


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:




9.2.10.1 Distribute/Archive a CCU Version

The user can archive or distribute a CCU Version including all its CDIs to the file system. Thearchiving stores the CCU Version outside the MDB. Archived CCU Versions can be deleted byI_MDB even if they are frozen. Distributed CCU Versions can be imported by other MDBinstances.

To perform the archive / distribution the following preconditions have to be met:

� The CCU Version has to have the status ’FROZEN’


Notice: The Distribute/Archive function for CCU versions does always include the generatedCDIs.

To distribute/archive a CCU Version:

1. Navigate to the CCU Version window and select a version

2. Execute Command–>Export... to enter the ’Data Distribution / Data Archiving’ win-dow.

Figure 95. CCU Version Data Distribution / Data Archiving window

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–23


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3. Select Distribution or Archiving for the export type depending on the user choice.

Only the data archiving provides the configuration manager with the possiblity to delete the CCUversion beyond the archiving.

ItemThe field contains the item from which the data distribution or data archiving will be performed.In this case it is the CCU Version.


Info FileThe field contains the information file name. It contains the same information as the ’Data Ar-chiving / Data Distribution’ window in ASCII format. The ’InfoFile’ filename has the same prefixas the export file name with the extension ’.info’.

4. Select the Export File field and enter the name of the export file.

The field is mandatory.

The file must have an extension.and will be stored in the user Home–Directory.


5. Select the Receiver field and enter the receive area.

The receive field is only active when the export type is distribution. Any name can be assignedand no check will be performed by I_MDB. The field is mandatory.

6. Select the Remark field and enter a comment to the export (optional). The maximumnumber of allowed characters is 255.



9.2.10.2 Import/Restore a CCU Version

The user can import a CCU Version that has been exported by the distribution function fromanother MDB instance. The restore function imports a CCU Version that has been archived anddeleted via I_MDB.

To perform the import/restore, the following precondition has to be met:


To import/restore a CCU Version:



9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–24


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 96. CCU Version Import / Restore Window

3. Select Import for the import type if a distributed CCU Version shall be loaded into the

MDB

or

select Restore for the import type if an archived CCU Version shall be loaded into theMDB

4. Keep CCU Structure:Yes: hold original CCU structure

No: keep only one (top–level) CCU version

5. Confict behaviour: Only interesting in case of import of CCU Versions which comes

from another MDB version.If Conflict behaviour Abort is selected then the import aborts in case of any detected

conflicts.

If Automatic is selected then the import shall solve all conflicts automatically (not yet

implemented).The Conflict behaviour is defaulted to Interactive. In this case the Import Conflicts

window pops up. This window lists all CU versions imported including conflict classes

and actions for resolving these conflicts.

6. Select the Filename field and enter the name of the import/restore file. The field is

mandatory.

7. Press Execute to start the import/restore.



This operation may be used after Open of a specific CCU Version has been executed.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–25


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Please refer to the common operation ’Set Default Starting Point’ for more information.

9.2.12 Show

9.2.12.1 Show CCU Versions

Executing this operation the ’CCU Versions’ window will be displayed in which the user mayoperate on CCU definitions for a specific System Tree node.

To Show CCU Versions:

1. Navigate to the desired System Tree Node within the System Tree.

2. Select a System Tree Node within the System Tree area to operate on specific CCUs. or

Select the System Tree Root Node in the pathname area to show all CCUs of this Sys-

tem Tree Root Node. The selected node is displayed behind Pathname:

Figure 97. Selected System Tree Root Node within a specific System Tree Version

3. Execute File–>Show CCU Versions... .

The ’CCU Versions’ window is displayed listing all existing CCUs and their Versions attachedto the selected System Tree (Root) Node. If no CCUs exist the lists will be empty.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–26


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 98. CCU Versions

The ’CCU Versions’ window is divided into two separate parts. The one on the left shows theNames of all existing CCUs (CCU Names area) whereby the uppermost entry is marked for selec-tion by default. The other one on the right lists all existing CCU Versions belonging to the markedCCU Name.

To show the existing CCU Versions of a different CCU, move the cursor to its name and selectit. All existing CCU Versions of that CCU will be displayed.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–27


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 99. CCU Versions of another CCU

4. Quit the window (click on the pin) if you do not like to go on. Otherwise please refer to

the corresponding CCU (Version) operations.

9.2.12.2 Show CCU Version Properties

To Show CCU Version Properties:

1. Perform ’Show CCU Versions’ as described in the previous section.

2. Select the desired CCU Version.

3. Move to the Edit button above the CCU Versions area and execute Edit–>Props...

The ’CCU Version Properties’ window is displayed listing all properties of the selected CCU Ver-sion.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–28


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 100.CCU Version Properties

The Ownership choice allows the CM user to set the owner which is shown in the ’Owner’ entryto the CCU version or to set the owner to the CCU version and its containing items.

The Status choice allows the CM user to set the status to ’FROZEN’ of CCU version or to set thestatus to ’FROZEN’ of the CCU version and its containing items.

The Creation, Change and Frozen dates are set automatically by MDA. Consistency date and sta-tus are set by the Consistency Checker. As long as the Consistency Checker has not run on theCCU Version, the Consistency status is ’NONE’.


The user can obtain information about all CCU version exports within the system tree versiondetermined by the navigation scope. This function is a part of the export/import informationbrowser which can be reached from the Navigator window of I_MDB. The pathname of the navi-gation point in the I_MDB Navigator window is used as the default value for the CCU pathnamefilter.

To show CCU version exports, the following precondition has to be met:


To show exports:



2. Execute File –> Browse Exports –>CCU Versions... to enter the ’Show Exports’ win-

dow.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–29


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 101.CCU version show exports window

Dedicated filters can be specified by the user in order to get information only from those versionsmatching the filter criteria. Within a filter field wildcards ’*’ can be used as a pattern for any char-acter. Leaving a filter field blank is equivalent to ’*’.

3. Select the CCU Path field and enter desired filter data

Default is the navigation point of the I_MDB Navigator window. By confirming the default onlyinformation from the CDU version within this subtree will be obtained.

4. Select the CCU Name field and enter the desired CCU name

5. Select the CCU version field and enter version, issue and revision

6. Press the Search button to obtain a list of all CCU version exports matching the speci-



Notice: In case no filter items are specified the user gets an export list of all existing exports ofthe default subtree.




9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–30


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:








The user can obtain information about all CCU version imports within the system tree versiondetermined by the navigation scope. This function is a part of the export/import informationbrowser which can be reached from the Navigator window of I_MDB. The pathname of the navi-gation point in the I_MDB Navigator window is used as the default value for the CCU pathnamefilter.

To show CCU version imports, the following precondition has to be met:


To show imports:



2. Execute File –> Browse Imports –>CCU Versions... to enter the ’Show Imports’ win-

dow.

9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–31


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 102.CCU show imports window


3. Select the CCU Path field and enter desired filter data

Default is the navigation point of the I_MDB Navigator window. By confirming the default onlyinformation from the CCU version within this subtree will be obtained.

4. Select the CCU Name field and enter the desired CCU name

5. Select the CCU Version field and enter version, issue and revision

6. Press the Search button to obtain a list of all CCU version imports matching the speci-



Notice: In case no filter items are specified the user gets an import list of all existing imports ofthe default subtree.




9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–32


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:










9–33

CGS–RIBRE–SUM–00032 03.07.2015– –9–33


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



10–2

CGS–RIBRE–SUM–00032 03.07.2015– –10–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


10 REPORT GENERATION

N/A

10–2

CGS–RIBRE–SUM–00032 03.07.2015– –10–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11 MDA DATA APPLICATION PROGRAMMING INTERFACE (DATA–API)

11.1 GENERAL DESCRIPTION OF THE DATA–API

The Data–API is the Application Programmers Interface to the data stored in the MDB. The Data–API andits below described services together with the standard Oracle Ada / C embedded sql programming languageform the developers coding environment.

The API allows comfortable access to data stored in the MDB without having to know the detailed data orga-nisation within the MDB. The Data–API consists of the following parts:

� A PL/SQL Package (stored procedures), which provides procedures for database trans-action handling (Lock, Commit, Rollback) and for the definition of the data configura-tion scope, the CCU Version scope or the CDU Version scope including its end items(Config API).

� A PL/SQL Package (stored procedures), which provides procedures for operations onConfiguration Data Items (CDI).

� A PL/SQL Package (stored procedures), which provides procedures for operations onConfiguration Units (CU).

� Data End Item Views (meaning a logical data table presentation), to access data withinthe defined configuration scope.

� Data Aggregate Views (meaning a logical data table presentation), to access data withinthe defined configuration scope.

� Data Write Procedures to write aggregate information to the MDB.

� Aggregate Delete Procedures to delete single aggregates, multi record aggregates andspecific records of multi record aggregates.

� Common Views for Pathname SID translation, user tree navigation and mapping of userdefined end item types versus CGS standard end item types within the defined configu-ration scope.

� Create End Item Procedures to create und update end items into the MDB.

� Service Procedure to request several parameters and states of MDB, end items, etc.

The major advantage of using Oracle’s ”Stored Procedures” instead of ADA is that they are independentfrom any language. So it is possible to call them in any 3 GL supported by Oracle (Fortran, ADA, C, Coboletc..) and directly in SQL, PL/SQL.

The API components are shown in figure 103. It consists of different PL/SQL packages, views and write/ delete procedures. The API services provide the user with the capability to access the MDB from outside.The services are used for example when a mapping procedure or user defined consistency check shall beimplemented.

The API services related to CDI operations are explained in the next chapter.

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


MDB_API Package

MDB_API_WRITE Package

set configuration scope accept changesreset changesconvert CDU versionconvert CCU version

CDI_PROCS Package

lock end item

lock CCUcreate CDIdelete CDIinsert identifier for referenced end iteminsert code insert report or activity loginsert ASCII text

CDI Viewsgeneration inforeportcodetextcross reference list

End–Item ViewsAggregate Views

Write / Delete Proceduresinsert aggregatedelete single aggregatedelete multi record aggregatedelete specific record in multi record aggregate

API

Mapping

User DefinedConsistency Checks

Common Views

Create End Item Procedures

Service Proceduresread node descriptionexist nodeexist typeexist useris user configuration managerwho am i

create user nodecreate user node tmpupdate user node

Figure 103.API Components

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11.2 USING THE DATA–API

Before an application can access any data from the MDB a configuration scope (CDU / CCU version) hasto be set first.

This is performed by the Data–API procedure MDB_API.CONFIG_API.

The general sequence for the usage of the Data–API is given below:

� login to oracle

� set the configuration scope (CONFIG_API)

� access data (user written procedures and/or functions)

� accept/reset changes (COMMIT/ROLLBACK)

The PL/SQL package MDB_API is providing the following procedures:

� MDB_API.CONFIG_API

� CONVERT_CDU_VERSION

� CONVERT_CCU_VERSION

� MDB_API.COMMIT

� MDB_API.ROLLBACK

Procedure calls for the different application languages (ADA, C, SQL, ...) have to be executed accordingto the Oracle syntax for embedded SQL.

The host data types have to be chosen according the Pro* (ADA ,or C, or Fortran) Precompiler Language.

11.2.1 Description of the MDB_API Package

The MDB_API package contains procedures to set the configuration scope and to accept or reset changes.The following sections describe the parameter and procedures more in detail.

11.2.1.1 Procedure MDB_API.COMMIT

Description:

The procedure checks if the user is connected to the database. In case that no CCU or CDU version is config-ured an error is raised. The procedure commits the changes to the database. It is important, that not theORACLE commit is used at this point. If the commit procedure provided by Oracle is called directly, theconfiguration scope defined by the CONFIG_API procedures will be corrupted.

Parameter: None

Procedure call:MDB_API.COMMIT;

Exceptions:

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


In case of errors the following exceptions can be raised:

USE_ERROR – when connection status is wrong– when commit has been executed before config_api

MDB_ERROR – when other exceptions have occurredAPI_SET_STATUS_ERROR – when something went wrong during status exchange from any

scope to NONE. For all changed CDU’s and the CCU’s that refer– ence the CDU’s, the status will be changed.

Notice:When the commit procedure is executed after data modification, the consistency state is changedto NONE within each CDU where changes have been made. The consistency state of all CCU’sthat reference the CDU where changes have been made will also be changed to NONE.Additionally the change date will be changed when performing the commit.

11.2.1.2 Procedure MDB_API.ROLLBACK

Description:

The procedure checks if the user is connected to the database. In case that no CCU or CDU version is config-ured an error is raised. The procedure undo the changes to the database. It is important, that not the ORACLErollback is used at this point. If the rollback procedure provided by Oracle is called directly, the configurationscope defined by the CONFIG_API procedures will be corrupted.

Parameter: None

Procedure call:MDB_API.ROLLBACK;

Exceptions:


USE_ERROR – when connection status is wrong– when rollback has been executed before config_api

MDB_ERROR – when other exceptions have occurred

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11.2.1.3 Procedure MDB_API.CONFIG_API

Description:

The procedure sets the specific CCU/CDU version as the default CCU/CDU of the calling application. Forthe calling application an end item is identifiable only by its SID or pathname.

The procedure CONFIG_API can be called by the application with three different parameter lists. The defini-tions are explained below.

1. To set the specific CDU version as the default CDU version of the calling application the followingparameter list has to be used:

Parameter: Datatype:

ELEMENT_CONFIGURATION IN varchar2MISSION IN varchar2SYSTEMTREE_VERSION IN numberCDU_PATHNAME IN varchar2VERSION IN numberISSUE IN numberREVISION IN numberTESTVERSION IN numberMDB_INSTANCE IN varchar2TEST_IN IN varchar2

ELEMENT_CONFIGURATION : name of the element configurationMISSION : name of the missionSYSTEMTREE_VERSION : version number of the system treeCDU_PATHNAME : pathname of the CDU versionVERSION : version number of the CCU or CDUISSUE : issue number of the CCU or CDUREVISION : revision number of the CCU or CDUTESTVERSION : version number of the test version; number must be greater

than zero if TEST_IN flag has the value ’TRUE’TEST_IN : status flag indicating if this version is a test version or not

(value is TRUE or FALSE)MDB_INSTANCE : name of the MDB instance

For a test version the parameters VERSION, ISSUE and REVISION can have any value. The value of pa-rameter TESTVERSION has to be one or greater and the parameter TEST_IN must be TRUE.

Procedure call:MDB_API.CONFIG_API ( ELEMENT_CONFIGURATION, MISSION, SYSTEMTREE_VERSION, CDU_PATHNAME, VERSION,

ISSUE,REVISION ,TESTVERSION,

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


MDB_INSTANCE,TEST_IN );

2. To set the specific CCU version as the default CCU version of the calling application the following

parameter list has to be used:


ELEMENT_CONFIGURATION IN varchar2MISSION IN varchar2SYSTEMTREE_VERSION IN numberCCU_PATHNAME IN varchar2VERSION IN numberISSUE IN numberREVISION IN numberNAME IN varchar2

ELEMENT_CONFIGURATION : name of the element configurationMISSION : name of the missionSYSTEMTREE_VERSION : version number of the system treeCCU_PATHNAME : pathname of the CCU versionVERSION : version number of the CCU or CDUISSUE : issue number of the CCU or CDUREVISION : revision number of the CCU or CDUNAME : name of the CCU

Procedure call:MDB_API.CONFIG_API ( ELEMENT_CONFIGURATION, MISSION, SYSTEMTREE_VERSION, CCU_PATHNAME, VERSION,

ISSUE,REVISION ,NAME );

For the calling application an end item is then identifiable only by its SID number or pathname. Within onescope, the CDU scope or the CCU scope, the SID number is unique.

3. To set the specific CDU or CCU version as the default version of the calling application by the in-

ternal version number, the following parameter list has to be used:


INTERNAL_VERSION IN number SCOPE IN varchar2

INTERNAL_VERSION : internal version number of the CDU or CCU versionSCOPE : indication of a CCU or CDU scope

Procedure call:MDB_API.CONFIG_API ( INTERNAL_VERSION, SCOPE );

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Normally the config_api procedure will be executed with the CDU or CCU parameter list (long procedurecall) to configure the scope instead of the short call of config_api.

Exceptions:

For the three config_api calls the following exceptions can be raised:

PARAMETER_ERROR – when parameter scope in config_api is wrongAUTHORIZATION_ERROR– when the user has not the authorizationMDB_ERROR – when parameter test_in is wrong in config_api

– when a different error than the above mentioned has occurred

11.2.1.4 Procedure / Function MDB_API.CONVERT_CDU_VERSION

Description:

This procedure converts the CDU internal version to the external version identification element configura-tion, mission, system tree version, CDU pathname, version number, issue number, revision number, testver-sion number and MDB instance.

1. To convert an internal CDU version number the following parameter list has to be used:


CDU_INTERNAL_VERSION in numberELEMENT_CONFIGURATION OUT varchar2MISSION OUT varchar2SYSTEMTREE_VERSION OUT numberCDU_PATHNAME OUT varchar2VERSION OUT numberISSUE OUT numberREVISION OUT numberTESTVERSION OUT numberMDB_INSTANCE OUT varchar2

CDU_INTERNAL_VERSION CDU internal version numberELEMENT_CONFIGURATION : name of the element configurationMISSION : name of the missionSYSTEMTREE_VERSION : version number of the system treeCDU_PATHNAME : pathname of the CDU versionVERSION : version number of the CCU or CDUISSUE : issue number of the CCU or CDUREVISION : revision number of the CCU or CDUTESTVERSION : version number of the test version; number must be greater

than zero if TEST_IN flag has the value ’TRUE’MDB_INSTANCE : name of the MDB instance

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Procedure call:MDB_API.CONVERT_CDU_VERSION (CDU_INTERNAL_VERSION,

ELEMENT_CONFIGURATION,MISSION,SYSTEMTREE_VERSION,CDU_PATHNAME,VERSION,ISSUE,REVISION,TESTVERSION,MDB_INSTANCE)

2. To convert an external CDU version number the following parameter list has to be used: (in thiscase the function returns the internal version number)


ELEMENT_CONFIGURATION IN varchar2MISSION IN varchar2SYSTEMTREE_VERSION IN numberCDU_PATHNAME IN varchar2VERSION IN numberISSUE IN numberREVISION IN numberTESTVERSION IN numberMDB_INSTANCE IN varchar2

ELEMENT_CONFIGURATION : name of the element configurationMISSION : name of the missionSYSTEMTREE_VERSION : version number of the system treeCDU_PATHNAME : pathname of the CDU versionVERSION : version number of the CCU or CDUISSUE : issue number of the CCU or CDUREVISION : revision number of the CCU or CDUTESTVERSION : version number of the test version; number must be greater

than zero if TEST_IN flag has the value ’TRUE’MDB_INSTANCE : name of the MDB instance

Function call:

MDB_API.CONVERT_CDU_VERSION (ELEMENT_CONFIGURATION,MISSION,SYSTEMTREE_VERSION,CDU_PATHNAME,VERSION,ISSUE,REVISION,TESTVERSION,MDB_INSTANCE)

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Exceptions:

For the CONVERT_CDU_VERSION and CONVERT_CCU_VERSION calls the following exceptions canbe raised:

PARAMETER_ERROR – when one of the parameter is wrongMDB_ERROR – when an unexpected error occurrs

11.2.1.5 Procedure / Function MDB_API.CONVERT_CCU_VERSION

Description:

This procedure converts the CCU internal version to the external version identification element configura-tion, mission, system tree version, CCU pathname, version number, issue number, revision number, CCUname.

1. To convert an internal CCU version number the following parameter list has to be used:


CCU_INTERNAL_VERSION IN numberELEMENT_CONFIGURATION OUT varchar2MISSION OUT varchar2SYSTEMTREE_VERSION OUT numberCCU_PATHNAME OUT varchar2VERSION OUT numberISSUE OUT numberREVISION OUT numberNAME OUT varchar2

CCU_INTERNAL_VERSION CCU internal version numberELEMENT_CONFIGURATION : name of the element configurationMISSION : name of the missionSYSTEMTREE_VERSION : version number of the system treeCCU_PATHNAME : pathname of the CCU versionVERSION : version number of the CCU or CDUISSUE : issue number of the CCU or CDUREVISION : revision number of the CCU or CDUNAME : name of the CCU

Procedure call:

MDB_API.CONVERT_CCU_VERSION (CCU_INTERNAL_VERSION,ELEMENT_CONFIGURATION,MISSION,SYSTEMTREE_VERSION,CCU_PATHNAME,VERSION,ISSUE,REVISION,NAME)

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


2. To convert an external CCU version number the following parameter list has to be used: (in thiscase the function returns the CCU internal version number)


ELEMENT_CONFIGURATION IN varchar2MISSION IN varchar2SYSTEMTREE_VERSION IN numberCCU_PATHNAME IN varchar2VERSION IN numberISSUE IN numberREVISION IN numberNAME IN varchar2

ELEMENT_CONFIGURATION : name of the element configurationMISSION : name of the missionSYSTEMTREE_VERSION : version number of the system treeCCU_PATHNAME : pathname of the CCU versionVERSION : version number of the CCU or CDUISSUE : issue number of the CCU or CDUREVISION : revision number of the CCU or CDUNAME : name of the CCU

Function call:

MDB_API.CONVERT_CCU_VERSION (ELEMENT_CONFIGURATION,MISSION,SYSTEMTREE_VERSION,CCU_PATHNAME,VERSION,ISSUE,REVISION,NAME)

Exceptions:

For the CONVERT_CDU_VERSION and CONVERT_CCU_VERSION calls the following exceptions canbe raised:

PARAMETER_ERROR – when one of the parameter is wrongMDB_ERROR – when an unexpected error occurrs

11.2.2 API Exceptions

When using the API package in an application written in C or ADA, a file containing the exception numbershave to be included. These files contain the exception number definitions which may be raised by API proce-dures. For a C application the filename is USER_EXCEPTIONS_.h and for an ADA application the filename is

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


USER_EXCEPTIONS_.a.

The file content of user_exceptions.ads is:

PACKAGE user_exceptions IS

MDB_ERROR_NO :INTEGER := –20000;USE_ERROR_NO :INTEGER := –20001;AUTHORIZATION_ERROR_NO :INTEGER := –20002;PARAMETER_ERROR_NO :INTEGER := –20003;XREF_ERROR_NO :INTEGER := –20004;LOCK_ERROR_NO :INTEGER := –20005;API_SET_STATUS_ERROR_NO :INTEGER := –20006;FROZEN_ERROR_NO :INTEGER := –20007;PRIVILEGE_ERROR_NO :INTEGER := –20008;SID_RANGE_ERROR :INTEGER := –20009;

END;

The file content of user_exceptions.h is:

#define MDB_ERROR_NO –20000#define USE_ERROR_NO –20001#define AUTHORIZATION_ERROR_NO –20002#define PARAMETER_ERROR_NO –20003#define XREF_ERROR_NO –20004#define LOCK_ERROR_NO –20005#define API_SET_STATUS_ERROR_NO –20006#define FROZEN_ERROR_NO –20007#define PRIVILEGE_ERROR_NO –20008#define SID_RANGE_ERROR –20009

Program examples explaining the usage of the MDB API procedures are included in appendix D.

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11.2.3 Description of the MDB_API_WRITE Package

The MDB_API_WRITE package provides one procedure: the lock End–Item procedure.

Description:

The procedure tries to lock an End–Item, which is specified by the PATHNAME. When the End–Item hasbeen locked successfully, the return parameter LOCKED is TRUE (otherwise FALSE).

The procedure ensures data consistency. No other user is able to modify the End–Item when it is locked.


PATHNAME IN varchar2LOCKED IN OUT varchar2

PATHNAME : pathname of the referenced End–ItemLOCKED : status flag indicating if the item is locked or not.

Procedure call:

MDB_API_WRITE.LOCK_ITEM(PATHNAME, LOCKED);

Exceptions:


LOCK_ERROR – when the item is actually locked by a different userUSE_ERROR – when connection status is wrong (not connected to MDB)PARAMETER_ERROR – when the pathname is not visible in the selected scopeAUTORIZATION_ERROR – when the user is not the ownerFROZEN_ERROR – when the CDU status is Frozen. A lock is only allowed when

the CDU status is Development or Review. PRIVILEGE_ERROR – no privilege error will be raised when:

1) the status of selected CDU/CCU is review and the user has CM privilege2) the status of the selected CDU/CCU is development and the user is the owner.

– A privilege error will be raised in any other case.

The lock item procedure is used within the following sequence:

� Connect to MDB

� Set CCU or CDU configuration scope

� Lock End–Item

� Write data to MDB by using Write Procedures

� Commit the changes

The lock procedure is optional, but it is proposed to include it, to be sure that no other user modifies the dataat the same time.

It is also proposed to use the Write Procedures to modify data in the MDB. The Write Procedures are gener-ated by DADI–MA and the structure of those procedures is explained in chapter 11.2.6

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11.2.4 Description of End–Item Views

End–Item oriented views are generated by the Data Dictionary Tool on basis of the end–item definition.They are generated during the export to MDB within the Data Dictionary Tool.

The figure below displays the embedding of End–Item oriented views. In this figure the aggregate 1 and itsattributes are defined for two different End–Item types: STIMULUS and MEASUREMENT. To retrievedata from the MEASUREMENT end item view, the configuration scope has to be selected first.

AGG1 Attr 1 Attr 2

AGG2 Attr 1 Attr 2 Attr 3 Attr 4

AGG3 Attr 1 Attr 2 Attr 3

V1.0.1V1.0.0

AGG1 Attr 1 Attr 2

MEASUREMENTEnd–Item type

STIMULUSEnd–Item type

Configuration Scope

VIEW

Figure 104.End–Item View

The user can operate with the end item views by the select statement.

SELECT <list of end item attributes> FROM <end item type name> WHERE ....

The attribute names will be extended by a prefix when there is a name conflict. A conflict occurs, if one andthe same attribute name will be used within different aggregates of one end item. A definition like this ispossible during the Data Dictionary definition. In this case a prefix will be added automatically during theview generation. The prefix name can be found in the view file in the /dadi_export/api_views directory.

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The end–item views are implemented according to the following structure:

CREATE VIEW <end item type name>(<all end item type attribute field alias>,F_SID,F_CDU_INTERNAL_VERSION)

AS SELECT <all end item attribute fields>, UT.F_SID, UT.F_CDU_INTERNAL_VERSION

FROM <all other aggregate–tables>,T_USER_TREE_NODES UT

� select those end items that belong to the CCU/CDU configuration

scope

� set join conditions for all aggregates and join by SID and CDU

Version

� select the data for one specific end item type

Note:

� The view name will be <end item type name> .

� The <all end item attribute field alias> will be the column names of all at-tributes belonging to the end item type.

� Aggregates of the type MDA–Special usage ’VERY_LONG_RAW’ (aggregates storingsource–code, binary code or images) are not covered by End–Item Views. For these ag-gregates separate views (aggregate views) will be generated. The aggregate views areexplained in the next section.

� Duplicate Attributes will cause name conflicts in the views column list (view columnlist has to have unique names).

To use the End Item Views

Within the user program the end item views have to be used in the following way:

e.g.

SELECT <list of end item attributes> FROM <end item type name> WHERE ....;

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–15


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11.2.5 Description of Aggregate Views

Aggregate oriented Views are generated by the Data Dictionary Tool on the basis of the aggregate definitions.The Aggregate Views are created during the export to MDB within the Data Dictionary Tool. The followingdescribes how the views are implemented.

The user can operate with the aggregate views by the select statement.

SELECT <list of end item attributes> FROM <aggregate name> WHERE ....

The aggregate views also allow to access images and binary code, which are attributes of the type’VERY_LONG_RAW’.Attributes can either accessed with end item views or with aggregate views. It depends on the user choice.

The aggregate views are implemented according to the following structure:

CREATE VIEW V_<aggregate name>(F_CDU_INTERNAL_VERSION,F_SID,F_CHANGE_DATE,<all other fields alias>)

AS SELECT F_CDU_INTERNAL_VERSION, F_SID, F_CHANGE_DATE,<all other fields>FROM <name> A

� select those aggregates that belong to the CCU/CDU configuration scope

Note:

� The view name will be V_<aggregate name>. All aggregate view procedures start with V_ (View).

� The <all other fields alias> will be the column names of all attributes belonging to theaggregate.

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–16


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To use the Aggregate Views

Within the user program the aggregate views have to be used in the following way

e.g. SELECT <list of end item attributes> FROM <aggregate name> WHERE ....;

11.2.6 Description of Write Procedures

Aggregate oriented Write Procedures are generated by the Data Dictionary Tool on basis of the aggregatedefinitions. The Write Procedures are generated during the export to MDB within the Data Dictionary Tool.The following sections describe how the generation of write procedures has been implemented.

It is not necessary for a user to write a program for the definition of write procedures because this will bedone comfortable by the Data Dictionary Tool during the export. The write procedures enable user softwareto write aggregate information to the MDB.

The write procedures are implemented according to the following structure:

CREATE OR REPLACE PROCEDURE P_<aggregate name>(<all other fields alias>,PATHNAME IN VARCHAR2)

BEGIN

� check if the user is the owner;� check if the selected scope is locked;� check if the selected CDU/CCU has the status frozen or review;� insert values into MDB if all preconditions are correct;

END;

Note:

The write procedure name will be P_<aggregate name>. All write procedures start with P_ (P for Procedure).

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–17


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To use the Write Procedures

Within the user program the write procedures have to be used in the following way:

P_<aggregate name>(<all other field aliases>, pathname);

e.g.EXEC SQL EXECUTE

BEGIN P_EGSE_EQUIPMENT(:egse_description, :pathname); END;

END-EXEC ;

A program example, explaining how to use Write Procedures is included in appendix D.

11.2.7 Description of Aggregate Delete Procedures

Aggregate oriented Delete Procedures are generated by the Data Dictionary Tool on basis of the aggregatedefinition. The Delete Procedures are generated during the export to MDB by the Data Dictionary Tool. Thefollowing sections describe how the generation of delete procedures has been implemented. The delete pro-cedures enable user software to delete aggregate information in the MDB.

Two different delete procedures are implemented. One for the deletion of single aggregates and multi recordaggregates, and one for the deletion of one specific record within a multi record aggregate.

The general definition of a delete procedure for single aggregates and multi record aggregates is:

CREATE OR REPLACE PROCEDURE DA<aggregate name>(PATHNAME IN VARCHAR2)

BEGIN

� check if the user is the owner;� check if the selected scope is locked;� check if the selected CDU/CCU has the status frozen or review;� delete the aggregate in the MDB if all preconditions are correct;

END;

Note:

� All delete procedures for ’simple’ aggregates and multi record aggregates begin withDA (Delete All).

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–18


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


To use the Delete Procedures

Within the user program the delete procedures have to be used in the following way:

DA_<aggregate name>( pathname);


BEGIN DA_EGSE_EQUIPMENT(:pathname); END;

END-EXEC ;

The definition of a delete procedure for one specific record within a multi record aggregates is:

CREATE OR REPLACE PROCEDURE D_<aggregate name>(PATHNAME IN VARCHAR2,F_ENTRY_NUMBER IN NUMBER)

BEGIN

� check if the user is the owner;� check if the selected scope is locked;� check if the selected CDU/CCU has the status frozen or review;� delete the specific aggregate in the MDB if all preconditions are correct;

END;

Note:

� All delete procedures for a specific record within a multi record aggregates begin withD_ (Delete).

� The specific record to be deleted within the multi record aggregate has to be identifiedby the entry number in the parameter list.

To use the Delete Procedures for specific records

Within the user program the delete procedures have to be used in the following way:

D_<aggregate name>(pathname, :entry_number);


BEGIN D_IO_LIST_BUFFER_ADDRESS(:pathname, :entry_number); END;

END-EXEC ;

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–19


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11.2.8 Description of the Pathname–SID Relation View

Pathaname–SID relation view is a stored procedure provided with the MDA installation. The view selectsall pathnames and end item types in a specific CDU/CCU scope.In the following it will be described how the views have been implemented.

The user can operate with the Pathname–SID relation views by the select statement.

SELECT < parameter > FROM V_PATHNAME_SID_REL WHERE ....

Parameter for the select may be F_INTERNAL_VERSION , F_SID, F_TYPE and F_PATHNAME .

• F_INTERNAL_VERSION is the CDU internal version number.

• F_SID is the SID number.

• F_TYPE is the type of the user tree node, which may be Virtual or End–Item type.

• F_PATHNAME is the pathname of the virtual node or End–Item.

The Pathname–SID relation view is implemented according to the following structure:

CREATE VIEW V_PATHNAME_SID_REL(F_INTERNAL_VERSIONF_SID,F_TYPE,F_PATHNAME)

AS SELECT F_INTERNAL_VERSIONF_SID,F_TYPE,F_PATHNAME

FROM PATHNAME_SID_REL A

� select the CDU versions in the specified CCU/CDU configuration scope� select the pathnames and end item types that belongs to the user tree

The user can operate with the Pathname–SID relation views by the select statement:

SELECT < parameter > FROM V_PATHNAME_SID_REL WHERE ....

11.2.9 Description of the Foreign Key–SID Relation View

A Foreign Key is used for the identification of items in foreign databases. It can be used as a sort of crossreference between the MDB and other databases. Furthermore it can be used as an alternative access keywithin I_MDB.

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–20


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The Foreign Key–SID view selects all SID’s, Foreign Key Types and Foreign Keys in a specific CDU/CCUconfiguration scope.

Parameter for the select may be F_CDU_INTERNAL_VERSION, F_SID , KEY_TYPE and IDENTIFI-ER. The where condition has to contain two of the previous mentioned parameter.

• F_CDU_INTERNAL_VERSION is the CDU internal version number.


• KEY_TYPE is the type of the Foreign Key, which is equal to the foreign key aggregatename.

• IDENTIFIER is the value of the foreign key.

The Foreign Key–SID relation view is implemented according to the following structure:

CREATE view V_FOREIGNKEY_SID_REL(F_CDU_INTERNAL_VERSION,F_SID,KEY_TYPE,IDENTIFIER)

AS SELECT A.F_CDU_INTERNAL_VERSION,A.F_SID,A.KEY_TYPE,A.IDENTIFIER

FROM PATHNAME_SID_REL A

� select the CDU versions in the specified configuration scope� select the pathnames and end item types that belongs to the user tree

The user can operate with the FOREIGNKEY_SID_REL view by the select statement:

SELECT < parameter > FROM V_FOREIGNKEY_SID_REL WHERE ....

11.2.10 Description of the User Tree Nodes View

The V_USER_TREE_NODES view enables the user to navigate in the user tree and to retrieve node specificdata like F_NODE_NAME, F_TYPE, F_OWNER, F_CI_NUMBER etc. within the API Configurationscope.

Parameter for the select may be F_CDU_INTERNAL_VERSION, F_SID, F_FATHER_SID,F_NODE_NAME, F_TYPE, F_OWNER, F_CI_NUMBER, F_DESCRIPTION, F_CREATION_DATE,F_CHANGE_DATE.

• F_CDU_INTERNAL_VERSION is the CDU internal version number.


11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–21


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


• F_FATHER_SID is the SID number of the parent node.

• F_NODE_NAME is the node name of the node.

• F_TYPE is the item type name (e.g. VIRTUAL, EGSE_ANALOG_STIMULUS etc.).

• F_OWNER is the owner the the node.

• F_CI_NUMBER is the configuration item identifier of the node.

• F_DESCRIPTION is an information text for that node.

• F_CREATION_DATE provides the creation date of that node.

• F_CHANGE_DATE provides the last change date of that node.

Note:

� Using the oracle ’START WITH CONNECT BY’ clause for the columns F_SID andF_FATHER_SID the hierarchical name tree structure can be retrieved.

The User Tree Nodes view is implemented according to the following structure:

CREATE view V_USER_TREE_NODES(F_CDU_INTERNAL_VERSION,F_SID,F_FATHER_SID,F_NODE_NAME,F_TYPE,F_OWNER,F_CI_NUMBER,F_DESCRIPTION,F_CREATION_DATE,F_CHANGE_DATE)

AS SELECT A.F_CDU_INTERNAL_VERSION,A.F_SID,A.F_FATHER_SID,A.F_NODE_NAME,A.F_TYPE,A.F_OWNER,A.F_CI_NUMBER,A.F_DESCRIPTION,A.F_CREATION_DATE,A.F_CHANGE_DATE

from T_USER_TREE_NODES A

� select the CDU versions in the specified configuration scope� select attributes of an name tree node

The user can operate with the view by the select statement:

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–22


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


SELECT < parameter > FROM V_USER_TREE_NODES WHERE ....

11.2.11 Description of the V_ENT_EI_TYPE View

The V_ENT_EI_TYPE view is part of the MDB data dictionary and enables the user to retrieve the CGSstandard end item type to which a user defined end item type was mapped and vice versa.

• DD_VERSION is the MDB version to which the end item type belongs.

• TYPE_NAME is the end item type name.

• DESCRIPTION is an informational text.

• TYPE indicates whether the end item type is a user defined or CGS standard end item type.

• MAPPED_TO_TYPE contains the CGS standard end item type to which a user defined enditem type was mapped.

• F_CREATION_DATE provides the creation date of that type.

• F_CHANGE_DATE provides the last change date of that type.

The end item type view is implemented according to the following structure:

CREATE view V_ENT_EI_TYPE(DD_VERSION,TYPE_NAME,DESCRIPTION,TYPE,MAPPED_TO_TYPE,F_CREATION_DATE,F_CHANGE_DATE)

AS SELECT DD_VERSION,TYPE_NAME,DESCRIPTION,TYPE,MAPPED_TO_TYPE,CREATION_DATE,CHANGE_DATE

from ENT_EI_TYPE

� select attributes of an end item type

The user can operate with the view by the select statement:

SELECT < parameter > FROM V_ENT_EI_TYPE WHERE ....

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–23


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11.2.12 Description of CREATE_END_ITEM_API Package

The MDB_API_CEI package is an additional feature of the DATA–API of the MDA. It contains one proce-dure to insert a new user node (virtual node or end item), one procedure to insert a new user node temporary(virtual node or end item), one procedure to update a user node and several support procedures to read orto check specific information. The following sections describe the parameter and procedures in more detail.

11.2.12.1 Procedure MDB_API_CEI.CREATE_USER_NODE

Description:

The procedure checks if the user is connected to the database. In the case of successful connectionto the database the parameters are checked, i.e.

� if the father node exits, referred by path_name,

� if the node_name does not exist,

� if the node_type is allowed for the CDU domain,

� if the user of this procedure is a configuration manager and

� the CDU if it is not frozen.

In case of errors an exception is raised. Otherwise the procedure creates a new node as a child ofthe path_name node and returns the short identifier (SID). In the error case the SID is 0.


PATH_NAME IN varchar2NODE_NAME IN varchar2NODE_TYPE IN varchar2OWNER IN varchar2CI_NUMBER IN varchar2DESCRIPTION IN varchar2SID_NUMBER OUT number

PATH_NAME: path name of the father nodeNODE_NAME: name of the nodeNODE_TYPE: type of the nodeOWNER: owner of the nodeCI_NUMBER: configuration item numberDESCRIPTION: node descriptionSID_NUMBER: internal identification number of the node

Procedure call:

MDB_API_CEI.CREATE_USER_NODE( PATH_NAME,NODE_NAME,NODE_TYPE,OWNER,CI_NUMBER,DESCRIPTION,SID_NUMBER);

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–24


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Exceptions

In case of errors the following exceptions can be raised:USE_ERROR – when connection status is wrong or

– when node existPARAMETER_ERROR – when NODE_TYPE or PATH_NAME are empty or

– when OWNER not existPRIVILEGE_ERROR – when application user is not a cm–userFROZEN_ERROR – when CDU of the father node is frozenLOCK_ERROR – when it is not possible to lock the father node (i.e. locked

by a nother user)MDB_ERROR – when other exceptions have occurred

11.2.12.2 Procedure MDB_API_CEI.CREATE_USER_NODE_TMP

Description:

BDE_CEI (especially the BDE_CEI_LOAD procedure) requires a temporarary create node op-eration. After invocation of this operation a rollback is required in order to release the SIDs usedfor the temporary node creation which are taken by the system out of a special BDE range.. Acommit would store these SIDs permanently in the MDB and a later invocation of this procedurewould take the same SIDs and fail.

The procedure has the same interface description as MDB_API_CEI.CREATE_USER_NODE.

Use this function very carefully! Perform always a rollback afterwarts to release temporary SIDstaken out of a special BDE range (see also SID Range Tool Users and Operation Manual, 2.2.2)!

11.2.12.3 Procedure MDB_API_CEI.UPDATE_USER_NODE

Description:

The procedure checks if the user is connected to the database. In the case of successful connectionto the database the parameter are checked, i.e.


� if the node_name exists,

� if the owner exists,

� if the user of this procedure is a configuration

� if the CDU version it is not frozen.

In case of errors an exception is raised.Otherwise the procedure updates the existing node.


PATH_NAME IN varchar2NODE_NAME IN varchar2OWNER IN varchar2CI_NUMBER IN varchar2DESCRIPTION IN varchar2

PATH_NAME: path name of the father nodeNODE_NAME: name of the node

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–25


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


OWNER: owner of the node, if it is empty the old owner will still be usedCI_NUMBER: configuration item number, if it is equal ”–” the old ci_number

will still be usedDESCRIPTION: node description, if it is equal ”–” the old description will still

be used

Procedure call:

MDB_API_CEI.UPDATE_USER_NODE (PATH_NAME,NODE_NAME,OWNER,CI_NUMBER,DESCRIPTION);

Exceptions

In case of errors the following exceptions can be raised:USE_ERROR – when connection status is wrong or – when node not exist

– when trying update a CCU or CDU nodePARAMETER_ERROR – when NODE_NAME or PATH_NAME are empty or – when OWNER not existPRIVILEGE_ERROR – when application user is not a CM–userFROZEN_ERROR – when CDU of the node is frozenLOCK_ERROR – when it is not possible to lock the node (i.e. locked

by a nother user)MDB_ERROR – when other exceptions have occurred

11.2.12.4 Procedure MDB_API_CEI.READ_NODE_DESCRIPTION

Description:



� if the node_name exists.

In case of errors an exception is raised. Otherwise the procedure returns the parameters describingthe existing node.


PATH_NAME IN varchar2NODE_NAME IN varchar2SID_NUMBER OUT numberSCOPE OUT varchar2NODE_TYPE OUT varchar2OWNER OUT varchar2CDU_DOMAIN OUT varchar2CI_NUMBER OUT varchar2DESCRIPTION OUT varchar2

PATH_NAME: path name of the father nodeNAME_NAME: name of the node

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–26


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


SID_NUMBER: internal identification number of the nodeSCOPE: CCU/CDU/EINODE_TYPE: type of the nodeOWNER: owner of the nodeCDU_DOMAIN: domain name of the cdu of this node (if it exists)DESCRIPTION: node descriptionCI_NUMBER: configuration item numberSID_NUMBER: internal identification number of the node

Procedure call:

MDB_API_CEI.READ_NODE_DESCRIPTION( PATH_NAME,NODE_NAME,SID_NUMBER,NODE_TYPE,OWNER,SCOPE,CDU_DOMAIN,CI_NUMBER,DESCRIPTION);

Exceptions

In case of errors the following exceptions can be raised:USE_ERROR – when connection status is wrongPARAMETER_ERROR – when PATH_NAME is empty or node not existsMDB_ERROR – when other exceptions have occurred

11.2.12.5 Procedure MDB_API_CEI.EXIST_NODE

Description:

The procedure checks if the user is connected to the database. In the case of successful connectionto the database the parameters are checked. If the node (node_name) exists as child of father node,referred by path_name, the out–parameter EXIST will get the value ’TRUE’ assigned, otherwise’FALSE’. In case of errors an exception is raised.

Parameter: Datatype:PATH_NAME IN varchar2NODE_NAME IN varchar2EXIST OUT varchar2

PATH_NAME: path name of the father nodeNODE_NAME: name of the node; if it is empty, the path of PATH_NAME will

only be checkedEXIST: flag if the node exists (TRUE) or not (FALSE)

Procedure call:

MDB_API_CEI.EXIST_NODE( PATH_NAME,NODE_NAME,EXIST);

Exceptions

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–27


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


In case of errors the following exceptions can be raised:USE_ERROR – when connection status is wrongPARAMETER_ERROR – when PATH_NAME is emptyMDB_ERROR – when other exceptions have occurred

11.2.12.6 Procedure MDB_API_CEI.EXIST_USER

Description:

The procedure checks if the user is connected to the database. In the case of successful connectionto the database the parameters will be checked. If the user name exists the out–parameter EXISTwill get the value ’TRUE’ assigned, otherwise ’FALSE’. In case of errors an exception is raised.


USER_NAME IN varchar2EXIST OUT varchar2

USER_NAME: name of an userEXIST: flag if the user exists (TRUE) or not (FALSE)

Procedure call:

MDB_API_CEI.EXIST_USER (USER_NAME,EXIST);

Exceptions

In case of errors the following exceptions can be raised:USE_ERROR – when connection status is wrongPARAMETER_ERROR – when USER_NAME is emptyMDB_ERROR – when other exceptions have occurred

11.2.12.7 Procedure MDB_API_CEI.EXIST_TYPE

Description:

The procedure checks if the user is connected to the database. In case of successful connectionto the database the procedure checks if the type referred by the in–parameter TYPE_NAME existswithin the CDU domain referred by the in–parameter CDU_DOMAIN. If the type exists withinthe CDU domain, the out–parameter EXIST will get the value ’TRUE’ assigned, otherwise’FALSE’. In case of errors an exception is raised.


CDU_DOMAIN IN varchar2TYPE_NAME IN varchar2EXIST OUT varchar2

CDU_DOMAIN: path name of the father nodeTYPE_NAME: name of a node typeEXIST: flag if the type exists (TRUE) or not(FALSE)

Procedure call:

MDB_API_CEI.EXIST_TYPE( CDU_DOMAIN,TYPE_NAME,

EXIST);

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–28


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Exceptions

In case of errors the following exceptions can be raised:USE_ERROR – when connection status is wrongPARAMETER_ERROR – when CDU_DOMAIN or TYPE_NAME is emptyMDB_ERROR – when other exceptions have occurred

11.2.12.8 Procedure MDB_API_CEI.IS_CM_USER

Description:

The procedure checks if the user of this procedure is connected to the database. In the case of suc-cessful connection to the database the user name referred by OWNER is checked for CM privi-lege. If the user has CM privilege the out–parameter RESULT will get the value ’TRUE’ as-signed, otherwise ’FALSE’. In case of errors an exception is raised.

Parameter: Datatype:OWNER IN varchar2RESULT OUT varchar2

OWNER : name of a user, if it is empty the locked MDB–user will be checkedRESULT flag if the user is a configuration manager (TRUE) or not (FALSE)

Procedure call:

MDB_API_CEI.IS_CM_USER (OWNER,RESULT);

Exceptions

In case of errors the following exceptions can be raised:USE_ERROR – when connection status is wrongPARAMETER_ERROR – when OWNER specifies an unknown userMDB_ERROR – when other exceptions have occurred

11.2.12.9 Procedure MDB_API_CEI.WHO_AM_I

Description:

The procedure delete a user subtree .

Parameter: Datatype:USER_NAME OUT varchar2

USER_NAME: name of the actual ORACLE user

Procedure call:

MDB_API_CEI.WHO_AM_I(USER_NAME);

Exceptions:

MDB_ERROR – when any exceptions have occurred

11.2.12.10 Procedure MDB_API_CEI.DELETE_USER_SUBTREE

Description:


11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–29


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� if the father node exits, referred to by path_name,

� if the node_name does exist, referred to by node_name

� the CDU if it is not frozen.

� in case of a DEVELOPMENT CDU if the user is owner of the father node or has theCONFIGURATION_MANAGER privilege

� in case of a REVIEW CDU if the user has the CONFIGURATION_MANAGER privilege

In case of errors an exception is raised. Otherwise the procedure will delete the user subtree start-ing with the specified end item, including all detail data.


PATH_NAME IN varchar2NODE_NAME IN varchar2

PATH_NAME: path name of the father nodeNODE_NAME: name of the node

Procedure call:

MDB_API_CEI.DELETE_USER_SUBTREE( PATH_NAME,NODE_NAME);

Exceptions

In case of errors the following exceptions can be raised:USE_ERROR – when connection status is wrongPARAMETER_ERROR – when NODE_TYPE or PATH_NAME are empty or of invalid

lengthFROZEN_ERROR – when CDU of the father node is frozenLOCK_ERROR – when it is not possible to lock the father node (i.e. locked

by another user, does not exist, different owner)– when is is not possible to lock the node that starts the subtree (i.e.

locked by another user, does not exist, different owner)MDB_ERROR – when other exceptions have occurred

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–30


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11.2.13 MDB_API_CU – MDA Data Application Programming Interface (Data–API) toBDE_CU

BDE_CU provides in its SQL package MDB_API_CU database functions for creation or update of configu-ration units and procedures for creation and deletion of CCU references.

These functions can be used in other applications, for example user written applications.

It contains the following procedures and functions:

– procedure IS_CM_USER: checks the configuration management privilege of user

– procedure GET_SYSTEM_TREE_VERSION_STATUS: returns the status of a system treeversion

– procedure GET_MDB_INSTANCE: returns the current MDB instance

– procedure EXISTS_CDU: checks the existence of a CDU

– procedure CREATE_CDU: creates a CDU

– procedure EXISTS_CDU_VERSION: checks the existence of a CDU version

– procedure CREATE_CDU_VERSION: creates a CDU version

– procedure UPDATE_CDU_VERSION: updates the CDU domain, the owner and the descriptionof a existing CDU version in status DEVELOPMENT

– procedure EXISTS_CCU: checks the existence of a CCU

– procedure CREATE_CCU: creates a CCU

– procedure EXISTS_CCU_VERSION: checks the existence of a CCU version

– procedure CREATE_CCU_VERSION: creates a CCU version

– procedure UPDATE_CCU_VERSION: updates the owner and the description of a existing CCUversion in status DEVELOPMENT

– procedure DELETE_CCU_REFERENCES: deletes all CCU/CDU references for a CCU version

– procedure ADD_CCU_REFERENCE creates one CCU/CDU reference for a CCU version

The following two procedures are used internally by BDE_CU. Calling any of these procedures in user writ-ten applications is not recommended.

– procedure SWITCH_TO_LOAD: switches to load operation (internal version number is takenfrom the BDE special purpose range)

– procedure SWITCH_TO_STORE: switches to store operation (internal version number is takenfrom a internal MDA sequence)

11.2.13.1 Procedure MDB_API_CU.IS_CM_USER

Description:

This procedure checks the user’s MDB access privilege. If this privilege is CONFIGURATIONMANAGER it returns TRUE otherwise FALSE.


RESULT OUT varchar2

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–31


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


RESULT flag if the user is a Configuration Manager (’TRUE’) or not (’FALSE’)

Procedure call:

MDB_API_CU.IS_CM_USER(RESULT);

Exceptions:

MDB_ERROR: when other exceptions occurred; probably user was not correctly installed

11.2.13.2 Procedure MDB_API_CU.GET_SYSTEM_TREE_VERSION_STATUS

Description:

This procedure returns the status of a System Tree Version. The status can be ’FROZEN’ or ’DEVELOPMENT’.


ELEMENT_CONFIGURATION IN varchar2

ELEMENT_CONFIGURATION Element Configuration

MISSION IN varchar2

MISSION Mission

SYSTEM_TREE_VERSION IN number

SYSTEM_TREE_VERSION System Tree Version number

STATUS OUT varchar2

STATUS flag if the System Tree Version status is ’FROZEN’ or’DEVELOPMENT’

Procedure call:

MDB_API_CU.GET_SYSTEM_TREE_VERSION_STATUS(ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,STATUS);

Exceptions:

PARAMETER_ERROR when the Element Configuration, Mission or System TreeVersion does not exist

MDB_ERROR when other exceptions occurred

11.2.13.3 Procedure MDB_API_CU.GET_MDB_INSTANCE

Description:

This procedure returns the current MDB instance.


MDB_INSTANCE OUT varchar2

MDB_INSTANCE MDB instance

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–32


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Procedure call:

MDB_API_CU.GET_MDB_INSTANCE (MDB_INSTANCE);

Exceptions:


11.2.13.4 Procedure MDB_API_CU.SWITCH_TO_LOAD

Description:

This procedure switches to load operation (internal version number is taken from the BDE specialpurpose range)

Parameter Datatype:

no parameters

Procedure call:

MDB_API_CU.SWITCH_TO_LOAD;

Exceptions:

no exceptions

11.2.13.5 Procedure MDB_API_CU.SWITCH_TO_STORE

Description:

This procedure switches to store operation (internal version number is taken from the MDA se-quences)

Parameter Datatype:

no parameters

Procedure call:

MDB_API_CU.SWITCH_TO_STORE;

Exceptions:

no exceptions

11.2.13.6 Procedure MDB_API_CU.EXISTS_CDU

Description:

This procedure checks the existence of a CDU (CDU node, not a CDU version). If the CDU exists,the out parameter RESULT returns ’TRUE’ otherwise ’FALSE’.

Parameter Datatype:



MISSION IN varchar2

MISSION Mission

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–33


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:




CDU_PATH_NAME IN varchar2

CDU_PATH_NAME path name of the CDU

RESULT OUT varchar2

RESULT flag if the CDU exists ’TRUE’ otherwise ’FALSE’

Procedure call:

MDB_API_CU.EXISTS_CDU (ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,CDU_PATH_NAME,RESULT);

Exceptions:

PARAMETER_ERROR when the Element Configuration, Mission or System TreeVersion does not exists


11.2.13.7 Procedure MDB_API_CU.CREATE_CDU

Description:

This procedure creates a new CDU (empty CDU node, no CDU version). The user must have theConfiguration Manager privilege and the affected System Tree Version must be in status FRO-ZEN.

Parameter Datatype:



MISSION IN varchar2

MISSION Mission

SYSTEM_TREE_VERSION IN varchar2




Procedure call:

MDB_API_CU.CREATE_CDU (ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,CDU_PATH_NAME);

Exceptions:

AUTHORIZATION_ERROR when the user hasn’t the Configuration Manager privilege

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–34


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


PARAMETER_ERROR when the Mission, Element Configuration or System TreeVersion does not exist or the CDU path name is invalid

USE_ERROR when the CDU already exists or the System Tree Versionis not in status FROZEN


11.2.13.8 Procedure MDB_API_CU.EXISTS_CDU_VERSION

Description:

This procedure checks the existence of a CDU version. If the CDU version is not a test version,then the parameter TESTVERSION must be 0 and the parameter MDB_INSTANCE must be anempty string. If the CDU version exists, the out parameter RESULT returns ’TRUE’ otherwise’FALSE’.

Parameter Datatype:



MISSION IN varchar2

MISSION Mission





VERSION IN number

VERSION CDU version number

ISSUE IN number

ISSUE CDU issue number

REVISION IN number

REVISION CDU revision number

TESTVERSION IN number

TESTVERSION CDU testversion number= 0: CDU version is not a testversion> 0: CDU version is a testversion

MDB_INSTANCE IN varchar2

MDB_INSTANCE MDB instance of a CDU testversionempty string ’’ if CDU version is not a test version or whenthe MDB instance should be equal to the current MDB instance

RESULT OUT varchar2

RESULT ’TRUE’ if the CDU version exists otherwise ’FALSE’

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–35


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Procedure call:

MDB_API_CU.EXISTS_CDU_VERSION (ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,CDU_PATH_NAME,VERSION,ISSUE,REVISION,TESTVERSION,MDB_INSTANCE,RESULT);

Exceptions:

PARAMETER_ERROR when the Mission, Element Configuration or System TreeVersion does not exist


11.2.13.9 Procedure MDB_API_CU.CREATE_CDU_VERSION

Description:

This procedure creates a new empty CDU version. The user must have the Configuration Managerprivilege and the affected System Tree Version must be in status FROZEN.

Parameter Datatype:



MISSION IN varchar2

MISSION Mission





VERSION IN number

VERSION CDU version number, range: 1 .. 9999

ISSUE IN number

ISSUE CDU issue number, range: 0 .. 9999

REVISION IN number

REVISION CDU revision number, range: 0 .. 9999


TESTVERSION CDU testversion number, range: 0 .. 9999= 0: CDU version is not a testversion> 0: CDU version is a testversion

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–36


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


CDU_DOMAIN IN varchar2

CDU_DOMAIN CDU domain

OWNER IN varchar2

OWNER owner of the CDU version, if this parameter is an empty string, the current user will be inserted as owner

DESCRIPTION IN varchar2

DESCRIPTION description, this parameter can also be an empty string

Procedure call:

MDB_API_CU.CREATE_CDU_VERSION (ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,CDU_PATH_NAME,VERSION,ISSUE,REVISION,TESTVERSION,CDU_DOMAIN,OWNER,DESCRIPTION);

Exceptions:

AUTHORIZATION_ERROR when the user hasn’t the Configuration Manager privilegeor the MDB instance assigned to the system tree node below the CDU version (which isn’t a test version) does notcorrespond to the current MDB instance

PARAMETER_ERROR when the Element Configuration, Mission or System TreeVersion does not exist, the CDU path name is invalid, theversion is out of range 1 .. 9999 or the issue, revision or thetestversion is out of range 0 .. 9999 or when the domain isnot valid

USE_ERROR when the CDU already exists or the System Tree Versionis not in status FROZEN


11.2.13.10 Procedure MDB_API_CU.UPDATE_CDU_VERSION

Description:

This procedure updates the CDU domain, the owner and the description of an existing CDU ver-sion in status DEVELOPMENT or REVIEW. The user must have the Configuration Managerprivilege and the affected System Tree Version must be in status FROZEN.

Parameter Datatype:



11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–37


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


MISSION IN varchar2

MISSION Mission





VERSION IN number

VERSION CDU version number

ISSUE IN number

ISSUE CDU issue number

REVISION IN number

REVISION CDU revision number


TESTVERSION CDU testversion number= 0: CDU version is not a testversion> 0: CDU version is a testversion

CDU_DOMAIN IN varchar2

CDU_DOMAIN CDU domain, if this parameter a empty string, the CDUdomain will be not changed

OWNER IN varchar2

OWNER owner of the CDU version, if this parameter is an emptystring, the user won’t be changed


DESCRIPTION description, this parameter can also be a empty string

Procedure call:

MDB_API_CU.UPDATE_CDU_VERSION (ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,CDU_PATH_NAME,VERSION,ISSUE,REVISION,TESTVERSION,CDU_DOMAIN,OWNER,DESCRIPTION);

Exceptions:

AUTHORIZATION_ERROR when the user hasn’t the Configuration Manager privilegeor MDB instance assigned to the system tree node below

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–38


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


the CDU version (which isn’t a test version) does not correspond to the current MDB instance

PARAMETER_ERROR when the Element Configuration, Mission or System TreeVersion does not exist or when the CDU domain does notexist or is not conform to the end items existing in the CDUversion

USE_ERROR when the CDU not exists or is in status FROZEN


11.2.13.11 Procedure MDB_API_CU.EXISTS_CCU

Description:

This procedure checks the existence of a CCU (not a CCU version). If the CCU exists, the outparameter RESULT returns ’TRUE’ otherwise ’FALSE’.

Parameter Datatype:



MISSION IN varchar2

MISSION Mission



SYSTEM_TREE_PATH_NAME IN varchar2

SYSTEM_TREE_PATH_NAME system tree pathname

CCU_NAME IN varchar2

CCU_NAME name of the CCU

RESULT OUT varchar2

RESULT ’TRUE if the CCU exists otherwise ’FALSE’

Procedure call:

MDB_API_CU.EXISTS_CCU (ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,SYSTEM_TREE_PATH_NAME,CCU_NAME,RESULT);

Exceptions:

PARAMETER_ERROR when the Element Configuration, Mission or System TreeVersion or the System Tree Path Name not exists


11.2.13.12 Procedure MDB_API_CU.CREATE_CCU

Description:

This procedure creates a new CCU. The user must have the Configuration Manager privilege andthe affected System Tree Version must be in status FROZEN.

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–39


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Parameter Datatype:



MISSION IN varchar2

MISSION Mission




SYSTEM_TREE_PATH_NAME system tree pathname



Exceptions:

Procedure call:

MDB_API_CU.CREATE_CCU (ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,SYSTEM_TREE_PATH_NAME,CCU_NAME);


PARAMETER_ERROR when the Element Configuration, Mission, System TreeVersion or the System Tree Path Name does not exist or thesyntax of the CCU name is invalid

USE_ERROR when the CCU already exists or the System Tree Versionis not in status FROZEN


11.2.13.13 Procedure MDB_API_CU.EXISTS_CCU_VERSION

Description:

This procedure checks the existence of a CCU version. If the CCU version exists, the out parame-ter RESULT returns ’TRUE’ otherwise ’FALSE’.

Parameter Datatype:



MISSION IN varchar2

MISSION Mission



11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–40


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



SYSTEM_TREE_PATH_NAME system tree path_name



VERSION IN number

VERSION CCU version number

ISSUE IN number

ISSUE CCU issue number

REVISION IN number

REVISION CCU revision number

RESULT OUT varchar2

RESULT flag if the CCU exists ’TRUE’ otherwise ’FALSE’

Procedure call:

MDB_API_CU.EXISTS_CCU_VERSION (ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,SYSTEM_TREE_PATH_NAME,CCU_NAME,VERSION,ISSUE,REVISION,RESULT);

Exceptions:

PARAMETER_ERROR when the Element Configuration, Mission, System TreeVersion or the System Tree Path Name does not exist


11.2.13.14 Procedure MDB_API_CU.CREATE_CCU_VERSION

Description:

This procedure creates a new CCU version. The user must have the Configuration Manager privi-lege and the affected System Tree Version must be in status FROZEN.

Parameter Datatype:



MISSION IN varchar2

MISSION Mission



11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–41


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:






VERSION IN number


ISSUE IN number


REVISION IN number


OWNER IN varchar2

OWNER owner of the CDU version, if this parameter is an emptystring, the current user will be inserted as owner


DESCRIPTION description, this parameter can also be a empty string

Procedure call:

MDB_API_CU.CREATE_CCU_VERSION (ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,SYSTEM_TREE_PATH_NAME,CCU_NAME,VERSION,ISSUE,REVISION,OWNER,DESCRIPTION);

Exceptions:


PARAMETER_ERROR when the Element Configuration, Mission, System TreeVersion or the System Tree Path Name does not exist, the syntax of the CCU name is invalid,the version is out of range 1 .. 9999 orthe issue or/and revision is out of range 0 .. 9999

USE_ERROR when the CCU already exists or the System Tree Versionis not in status FROZEN


11.2.13.15 Procedure MDB_API_CU.UPDATE_CCU_VERSION

Description:

This procedure updates the owner and the description of an existing CCU version in status DE-VELOPMENT. The user must have the Configuration Manager privilege and the affected SystemTree Version must be in status FROZEN.

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–42


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Parameter Datatype:



MISSION IN varchar2

MISSION Mission







VERSION IN number


ISSUE IN number


REVISION IN number


OWNER IN varchar2

OWNER owner of the CCU version, if this parameter is an emptystring, the current user will be inserted as owner


DESCRIPTION description, this parameter can also be an empty string

Procedure call:

MDB_API_CU.UPDATE_CCU_VERSION (ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,SYSTEM_TREE_PATH_NAME,CCU_NAME,VERSION,ISSUE,REVISION,OWNER,DESCRIPTION);

Exceptions:


PARAMETER_ERROR when the Element Configuration, Mission or System TreeVersion does not exist,the System Tree Path Name does not exist,the syntax of the CCU_NAME is invalid,the version is out of range 1 .. 9999 orthe issue or/and revision is out of range 0 .. 9999

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–43


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


USE_ERROR when the CCU version not exists or is in status FROZEN


11.2.13.16 Procedure MDB_API_CU.DELETE_CCU_REFERENCES

Description:

This procedure deletes all existing CDU/CCU references for the given CCU version. The usermust be have the Configuration Manager privilege and the CCU version must be in status DE-VELOPMENT. The consistency status of all CCU versions which are a direct or indirect refer-ence to this CCU version and this CCU version are set to NONE.

Parameter Datatype:



MISSION IN varchar2

MISSION Mission







VERSION IN number


ISSUE IN number


REVISION IN number


Procedure call:

MDB_API_CU.DELETE_CCU_REFERENCES (ELEMENT_CONFIGURATION,MISSION,SYSTEM_TREE_VERSION,SYSTEM_TREE_PATH_NAME,CCU_NAME,VERSION,ISSUE,REVISION);

Exceptions:


PARAMETER_ERROR when the Element Configuration, Mission, System TreeVersion or the System Tree Path Name does not exist

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–44


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


USE_ERROR when the given CCU version not exists or is in statusFROZEN


11.2.13.17 Procedure MDB_API_CU.ADD_CCU_REFERENCE

Description:

This procedure creates a new CDU or CCU version reference.It checks the correctness of the reference. This procedure is overloaded.The user must be have the Configuration Manager privilege and the CCU version must be in statusDEVELOPMENT. The consistency status of all CCU versions which are a direct or indirect refer-ence to this CCU version and this CCU version are set to NONE when not both status are GLOB-AL_VALID. Also the consistency status of all CCU versions which are a direct or indirect refer-ence to the referenced CDU or CCU version and are set to NONE when not both (source anddestination) status are GLOBAL_VALID.

Parameter Datatype:



MISSION IN varchar2

MISSION Mission




SYSTEM_TREE_PATH_NAME system tree path name



VERSION IN number


ISSUE IN number


REVISION IN number


only for reference to a CDU version:

REF_CDU_PATH_NAME IN varchar2

REF_CDU_PATH_NAME path name of referenced CDU

REF_VERSION IN number

REF_VERSION version number of referenced CDU

REF_ISSUE IN number

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–45


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


REF_ISSUE issue number of referenced CDU

REF_REVISION IN number

REF_REVISION revision number of referenced CDU

REF_TESTVERSION IN number

REF_TESTVERSION testversion number of referenced CDU= 0: CDU version is not a testversion> 0: CDU version is a testversion

REF_MDB_INSTANCE IN varchar2

REF_MDB_INSTANCE MDB instance of referenced CDU testversionempty string ’’ if CDU version is not a test version or whenthe MDB instance should be equal to the current MDB instance

only for reference to a CCU version:

REF_SYSTEM_TREE_PATH_NAME IN varchar2

REF_SYSTEM_TREE_PATH_NAME system tree path name of referenced CCU

REF_CCU_NAME IN varchar2

REF_CCU_NAME name of the referenced CCU

REF_VERSION IN number

REF_VERSION version number of referenced CCU

REF_ISSUE IN number

REF_ISSUE issue number of referenced CCU

REF_REVISION IN number

REF_REVISION revision number of referenced CCU

for references to CCU or CDU versions:

RESULT OUT varchar2

RESULT flag

’OK’:

CCU/CDU version reference ok

’REFERENCE_NOT_EXISTS’:

referenced CDU/CCU version does not exist

’CCU_OUT_OF_TREE’:

if the referenced CCU version is not within thesubtree of the actual CCU version

’DOUBLE_REFERENCE_TO_CDU’:

a reference to another CDU version of the sameCDU already exists

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–46


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


’DOUBLE_REFERENCE_TO_CDU_VER’:

a reference to the same CDU version already exists

’DOUBLE_REFERENCE_TO_CCU’:

a reference to another version of the same CCU already exists

’DOUBLE_REFERENCE_TO_CCU_VER’:

a reference to the same CCU version already exists

’DOUBLE_REFERENCE_TO_SYS_NODE’:

a reference to an other CCU at the same system treenode already exists

’CCU_WITH_CDU_OUT_OF_TREE’:

the referenced CCU version contains references toCDU versions out of its subtree

Procedure call:

for a reference to a CDU version:MDB_API_CU.ADD_CCU_REFERENCES (ELEMENT_CONFIGURATION,

MISSION,SYSTEM_TREE_VERSION,SYSTEM_TREE_PATH_NAME,CCU_NAME,VERSION,ISSUE,REVISION,REF_CDU_PATH_NAME,REF_VERSION,REF_ISSUE,REF_REVISION,REF_TESTVERSION,REF_MDB_INSTANCE,RESULT);

for a reference to a CDU version:MDB_API_CU.ADD_CCU_REFERENCES (ELEMENT_CONFIGURATION,

MISSION,SYSTEM_TREE_VERSION,SYSTEM_TREE_PATH_NAME,CCU_NAME,VERSION,ISSUE,REVISION,REF_SYSTEM_TREE_PATH_NAME,REF_CCU_NAME,REF_VERSION,

11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–47


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


REF_ISSUE,REF_REVISION,RESULT);

Exceptions:


PARAMETER_ERROR when the Element Configuration, Mission, System TreeVersion or the system tree path name not exists

USE_ERROR when the given CCU version not exists or it is in statusFROZEN

LOCK_ERROR when the CCU versions referencing the current CCU version, the current CCU version itself or the referenced CCU/CDU version could not be locked


11–48

CGS–RIBRE–SUM–00032 03.07.2015– –11–48


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


12 CONFIGURATION DATA ITEM (CDI)

12.1 GENERAL DESCRIPTION OF THE CDI

A Configuration Data Item (CDI) refers to a configuration dependent MDB object which has beengenerated by application software and which is under MDA management. A CDI is not an enditem.

The CDIs are application generated data to be stored and managed in the MDB in dependenceto their configuration. A CDI is generated by an application software which is usually outsideMDA.For the CDI generation, different generation tools may be used which results in different contextand environment information, e.g. tool version, invocation parameter, etc. These configurationinformation must be recorded to allow reproducibility.

An example for the generation of CDIs is shown in the figure below. Specific data are extractedfrom the MDB and transformed by a tool in a spacecraft onboard calibration data table format.These generated objects are stored back as CDIs in the MDB in relation to the CCU.

ÀÀÀÀÀÀÀÀÀÀÀÀ

ÀÀÀÀÀÀÀÀÀ

ÀÀÀÀ

ÀÀÀÀÀÀ

ÀÀÀÀ

ÀÀÀÀ

ÀÀÀÀ


ÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀ

ƒcalibration data tablein onboard format

� � �

ÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀ

ÀÀÀÀÀÀÀÀÀÀ

ÀÀÀÀÀÀÀÀ

ÀÀÀÀÀÀanalog measurements definitions

transformation

MDBCCU

CDU CDU

ÀÀÀÀÀÀÀÀÀÀÀÀdata extraction

stored back

in the MDBas CDI

CDI x

Figure 105.CDI Generation Flow Example

Data used in the generation of a given CDI may be spread over several CDUs. The resulting CDIwill depend on a particular CDU version. A different CDI may result in a different configuration,which means a different CCU version.

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


A CDI is a special kind of MDB object with the following general structure:

� The Generation Information contains information about the generation process to allowreproducibility, e.g. tool identifier, invocation parameter, type of data used, etc.

� The CDI data block whose content is only known by the application. It is treated byMDA as an unstructured byte stream.

� The MDB Items Cross–Reference List which is used for integrity checks. It allows theidentification of CDIs that are effected by changes made on MDB end items.

The CDI and CCU structure is shown in the figure below.

ÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀ


ÀÀÀÀ

ÀÀÀÀ

ÀÀÀÀ

ÀÀÀÀ

ÂÂ

demo1 systest2ÀÀÀÀÀÀ

ÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀ

ÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀ

Generation info

ÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀÀ

CCUs

CDI body(treated by MDA

CDUs

as unstructured

MDB Items Xref List

CDI structure

demo2

A B X Y

byte stream)

ÀÀÀÀÀÀ

CDIs

Figure 106.CDI and CCU structure

There is a one–to–many relationship between CCU version and CDI. A CCU version may contain0, 1 or more CDIs, but a CDI belongs to one and only one CCU version.

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


12.2 USING THE CDI

The Application Programmers Interface (API) provides ”Stored Procedures” for loading config-uration dependent data (CDIs) into the MDB and views for read access. API services are used forthe CDI creation, retrieval and deletion.

The API allows comfortable access to data stored in the MDB without having to know the de-tailed data organisation within the MDB. The Data–API consists of two parts:

� An PL/SQL package, which provides procedures for database handling and for the def-inition the data configuration scope (CCU Version and CDU Version including its dataend items).

� Data end item Views (meaning a logical data table presentation), to access data withinthe defined configuration scope.

The user is able to view the CDI status and other properties like, size, generation date, etc.

A list of CDIs contained in a given CCU can be displayed and printed.

The user, running the application, must have CM privilege. It is necessary that the CCU has thestatus development, however the associated CDUs may have the status frozen.

When the CCU version will be deleted, all contained CDIs will be deleted. If there is any changeon the CCU version, all contained CDIs will be marked as invalid.

To access CDIs from the MDB the CCU has to be locked to prevent parallel write access fromother procedures.

The general sequence for a usage of the CDI is given below:

- configure the CCU scope (CONFIG_API)

- lock the CCU (LOCK_CCU)

- access data (CDI access via procedures, e.g. CREATE_CDI, INSERT_XREF, INSERT_REPORT, etc.)

- accept / reset changes (COMMIT / ROLLBACK)

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


12.2.1 Description of provided CDI Procedures for Write Access

All stored procedures for CDIs are provided by one package called CDI_PROCS. Only userswith privilege CONFIGURATION_MANAGER are able to use the procedures provided bythe package CDI_PROCS. To commit or undo changes in the MDB the procedures of theMDB_API package will be used.

Procedure calls for the different application languages (ADA, C, SQL, ...) have to be execut-ed according to the Oracle syntax for embedded SQL. The data types of the following proce-dure descriptions are valid for the PL/SQL language.The host data types have to be chosen according the Pro* (ADA ,or C, or Fortran) Precompil-er Language.

The CDI procedures do only work on the selected CCU Version.

12.2.1.1 Parameter Description

In this section there is a short description of the parameter used by the procedures within the pack-age CDI_PROCS.

NAME : name of the CDICDI_TYPE : type of the CDI (e.g. monitoring table)TARGET : target processor typeCRITICALITY : criticality of the softwareSC_IDENTIFIER : identifies the software name and version responsible for creating

the CDITOOL_IDENTIFIER : identifies the generation tool name and version responsible for

creating the CDIGENERATION_DATE : date when selected a ccu_version (calling CONFIG_API)GENERATION_STATUS : status of generated image (set by the generation tool)CODE_SIZE : size of codeREPORT_SIZE : size of reportTEXT_SIZE : size of textCODE_ENTRY_NO : entry number for code recordsCODE : binary codeREPORT_ENTRY_NO : entry number for report recordsREPORT : ASCII reportTEXT_ENTRY_NO : entry number for text recordsTEXT : ASCII textREF_SID : SID of referenced itemREF_PATHNAME : pathname of referenced itemLOCKED : status flag indicating if ccu is locked or not

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


12.2.1.2 Procedure COMMIT

Description:This procedure stores all data inserted since transaction begin (LOCK_CCU). It is a stored proce-dure from the MDB_API package.

Parameter: None

Procedure call:MDB_API.COMMIT;

In case of errors the following exceptions can be raised. USE_ERROR: – when CCU_VERSION is not locked

12.2.1.3 Procedure ROLLBACK

Description:This procedure revokes all data inserted since transaction begin (LOCK_CCU). It is a stored pro-cedure from the MDB_API package.

Parameter: None

Procedure call:MDB_API.ROLLBACK;

In case of errors the following exceptions can be raised. USE_ERROR: – when CCU_VERSION is not locked

12.2.1.4 Procedure LOCK_CCU

Description:This procedure tries to lock the selected CCU Version (via procedure API_CONFIG). When theCCU Version has been locked successfully the return parameter LOCKED is TRUE (otherwiseFALSE)

Parameter: Datatype:LOCKED IN OUT varchar2 (6)

Procedure call:CDI_PROCS.LOCK_CCU (LOCK_STATUS);

In case of errors the following exceptions can be raised: USE_ERROR: – when no valid CCU Version has been selected before

– when CCU_VERSION is already locked by current user processAUTHORIZATION_ERROR:

– when user is no CONFIGURATION_MANAGER– when selected CCU Version is not in status DEVELOPMENT

Constraints:It is not possible to change the CCU Version between LOCK_CCU and COMMIT / ROLLBACK.It is not possible to call LOCK_CCU twice.

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


12.2.1.5 Procedure CREATE_CDI

Description:This procedure creates a new CDI identified by its NAME. When already a CDI with this nameexists it will be deleted before.

Parameter: Datatype:NAME IN varchar2 (32)CDI_TYPE IN varchar2 (25)TARGET IN varchar2 (25)CRITICALITY IN varchar2 (25)SC_IDENTIFIER IN varchar2 (255)TOOL_IDENTIFIER IN varchar2 (255)

Procedure call:CDI_PROCS.CREATE_CDI ( NAME,

CDI_TYPE, TARGET, CRITICALITY, SC_IDENTIFIER, TOOL_IDENTIFIER, GENERATION_STATUS);

In case of errors the following exceptions can be raised:USE_ERROR: – when CCU Version not locked

12.2.1.6 Procedure DELETE_CDI

Description:This procedure deletes a CDI identified by NAME.

Parameter: Datatype:NAME IN varchar2 (32)

Procedure Call:CDI_PROCS.DELETE_CDI (NAME);

In case of errors the following exceptions can be raised: USE_ERROR: – when CCU Version not locked

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


12.2.1.7 Procedure INSERT_XREF

Description:This procedure inserts the identifiers (REF_SID, REF_PATHNAME) for one referenced (end)item in the CDI_CODE into the MDB. Due to the fact that the generated code can depend on sev-eral end items, each reference is identified by NAME and REF_ENTRY_NO.

Parameter: Datatype:NAME IN varchar2 (32)REF_ENTRY_NO IN number (10)REF_SID IN number (10)REF_PATHNAME IN varchar2 (255)

Procedure call:CDI_PROCS.INSERT_XREF ( NAME,

REF_ENTRY_NO, REF_SID, REF_PATHNAME);

In case of errors the following exceptions can be raised. USE_ERROR: – when CCU Version not locked

– when the procedure CREATE_CDI has not been called before or has raised an exception

XREF_ERROR: – when REF_SID or REF_PATHNAME doesn’t exist or invisible within the selected CCU version

12.2.1.8 Procedure INSERT_CODE

Description:This procedure inserts the generated code into the MDB. Using stored procedures it is impossibleto access code greater than 32760 bytes. So code greater than 32 KB has to be divided into severalpieces where each of them is identified by NAME and CODE_ENTRY_NO.

Parameter: Datatype:NAME IN varchar2 (32)CODE_ENTRY_NO IN number (10)CODE IN raw

Procedure Call:CDI_PROCS.INSERT_CODE ( NAME,

CODE_ENTRY_NO, CODE):

In case of errors the following exceptions can be raised: USE_ERROR: – when CCU Version not locked


12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


12.2.1.9 Procedure INSERT_REPORT

Description:This procedure inserts a report or activity log which gives information about the generated imageinto the MDB. Using stored procedures it is impossible to access ASCII text greater than 32760bytes. So code greater than 32 KB has to be divided into several pieces where each of them isidentified by NAME and REPORT_ENTRY_NO.

Parameter: Datatype:NAME IN varchar2 (32)REPORT_ENTRY_NO IN number (10)REPORT IN long

Procedure call:CDI_PROCS.INSERT_REPORT ( NAME,

REPORT_ENTRY_NO, REPORT):



12.2.1.10 Procedure INSERT_TEXT

Description:This procedure inserts an ASCII text into the MDB. Using stored procedures it is impossible toaccess code greater than 32760 bytes. So code greater than 32 KB has to be divided into severalpieces where each of them is identified by NAME and TEXT_ENTRY_NO.

Parameter: Datatype:NAME IN varchar2 (32)TEXT_ENTRY_NO IN number (10)TEXT IN long

Procedure call:CDI_PROCS.INSERT_TEXT ( NAME,

TEXT_ENTRY_NO, TEXT):



12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


12.2.2 Description of provided CDI Views for Read Access

The following views are provided for reading CDIs. All users, even the ”normal” ones, can retrieve CDIs.The CDI views do only work on the selected CCU Version.

View can be selected by the select command with statements like:

select * from <viewname> e.g. select * from CDI_GENERATION_INFO

12.2.2.1 View CDI_GENERATION_INFO

Parameter: Datatype:NAME varchar2 (32)CDI_TYPE varchar2 (25)TARGET varchar2 (25)CRITICALITY varchar2 (25)GENERATION_STATUS varchar2 (25)GENERATION_DATE dateCODE_SIZE number (10)REPORT_SIZE number (10)SC_IDENTIFIER varchar2 (255)TOOL_IDENTIFIER varchar2 (255)

12.2.2.2 View CDI_REPORT

Parameter: Datatype:NAME IN varchar2 (32)REPORT_ENTRY_NO IN number (10)REPORT IN long

12.2.2.3 View CDI_CODE

Parameter: Datatype:NAME IN varchar2 (32)CODE_ENTRY_NO IN number (10)CODE IN long raw

12.2.2.4 View CDI_TEXT

Parameter: Datatype:NAME IN varchar2 (32)TEXT_ENTRY_NO IN number (10)TEXT IN long

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


12.2.2.5 View CDI_XREF_LIST

Parameter: Datatype:NAME IN varchar2 (32)REF_ENTRY_NO IN number (10)REF_SID IN number (10)REF_PATHNAME IN varchar2 (255)

12.2.3 Program example for using CDI in ADA

The usage of the CDI procedures, provided by the package CDI_PROCS , will be explained in the followingexample. This program performs the following steps:

· Set the variables to be used with values

· Connection to MDB

· Set configuration scope for a CCU version

· Lock the CCU and check if lock was successful

· Create a new CDI

· Insert the identifiers for one referenced end item into the MDB

· Insert the generated code into the MDB

· Insert the generated report into the MDB

· Store all inserted data by commit

· Exception output

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– M A I N P R O G R A M NOM_CDI–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

with text_io; use text_io;with oracle_defs; use oracle_defs;WITH array_binds;WITH oracle_types;with user_exceptions;

procedure NOM_CDI is

DB_STRING : constant string := ””; � Declarationuser_id : constant string := ”/”;

CDI_NAME : oracle_defs.VARCHAR(32); CDI_TYPE : oracle_defs.VARCHAR(25); TARGET : oracle_defs.VARCHAR(25); CRITICALITY : oracle_defs.VARCHAR(25); SC_IDENTIFIER : oracle_defs.VARCHAR(255);TOOL_IDENTIFIER : oracle_defs.VARCHAR(255);GENERATION_STATUS : oracle_defs.VARCHAR(11);REF_ENTRY_NO : oracle_defs.integer := 1;REF_SID : oracle_defs.integer := –0815;REF_PATHNAME : oracle_defs.varchar(255);

CODE_ENTRY_NO : oracle_defs.integer := 1;CODE : oracle_defs.varchar(32760);REPORT_ENTRY_NO : oracle_defs.integer := 1;REPORT : oracle_defs.varchar(32760);

LOCK_STATUS : oracle_defs.varchar(5);

ELEMENT_CONFIGURATION : oracle_defs.varchar(16);MISSION : oracle_defs.varchar(16);SYSTEMTREE_VERSION : oracle_defs.integer;CCU_PATHNAME : oracle_defs.varchar(255);VERSION : oracle_defs.integer;ISSUE : oracle_defs.integer;REVISION : oracle_defs.integer;NAME : oracle_defs.varchar(30);

begin � InitializationCDI_NAME.buffer(1 .. 8) := ”CDI_NAME”;CDI_NAME.length := 8;CDI_TYPE.buffer(1 .. 16) := ”MONITORING TABLE”;CDI_TYPE.length := 16;TARGET.buffer(1 .. 5) := ”CDROM”;TARGET.length := 5;CRITICALITY.buffer(1 .. 6) := ”normal”;CRITICALITY.length := 6;SC_IDENTIFIER.buffer(1 .. 6) := ”source”;SC_IDENTIFIER.length := 6;TOOL_IDENTIFIER.buffer(1 .. 4) := ”tool”;TOOL_IDENTIFIER.length := 4;GENERATION_STATUS.buffer(1 .. 5):= ”VALID”;GENERATION_STATUS.length := 5;

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


REF_PATHNAME.buffer(1 .. 24) := ”/my/path/is/the/only/one”;REF_PATHNAME.length := 24;CODE.buffer(1 .. 12) := ”this is code”;CODE.length := 12;REPORT.buffer(1 .. 16) := ”this is a report”;REPORT.length := 16;

EXEC SQL CONNECT :user_id USING :DB_STRING; � Connect to MDB

� Configure the scope for the CCU version ELEMENT_CONFIGURATION.buffer(1..7) := ”CC_TEST”;ELEMENT_CONFIGURATION.length := 7;MISSION.buffer(1..13) := ”DUMMY_MISSION”;MISSION.length := 13;SYSTEMTREE_VERSION := 1;CCU_PATHNAME.buffer(1..20) := ”\CC_TEST\CC_TEST_GV1”;CCU_PATHNAME.length := 20;VERSION := 1;ISSUE := 0;REVISION := 0;NAME.buffer(1..11) := ”CC_TEST_GV1”;NAME.length := 11;

EXEC SQL EXECUTE BEGIN � Set new configuration scope MDB_API.CONFIG_API(:element_configuration,:mission,:systemtree_version,

:ccu_pathname,:version,:issue,:revision,:name); END;END–EXEC;

EXEC SQL EXECUTE � Lock the CCU version

BEGIN CDI_PROCS.LOCK_CCU(:LOCK_STATUS);

END; END–EXEC;

put_line (LOCK_STATUS.buffer);

if LOCK_STATUS.buffer(1 .. 4) = ”TRUE” then � Check if Lock was successful

EXEC SQL EXECUTE � Create the new CDI BEGIN CDI_PROCS.CREATE_CDI (:NAME, :CDI_TYPE, :TARGET, :CRITICALITY, :SC_IDENTIFIER, :TOOL_IDENTIFIER, :GENERATION_STATUS); END; END–EXEC;

EXEC SQL EXECUTE � Insert identifier for end item BEGIN CDI_PROCS.INSERT_XREF (:NAME, :REF_ENTRY_NO,

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


:REF_SID, :REF_PATHNAME); END; END–EXEC;

EXEC SQL EXECUTE � Insert identifier for code BEGIN CDI_PROCS.INSERT_CODE (:NAME, :CODE_ENTRY_NO, :HEXTORAW(:CODE)); END; END–EXEC;

EXEC SQL EXECUTE � Insert identifier for report BEGIN CDI_PROCS.INSERT_REPORT (:NAME, :REPORT_ENTRY_NO, :REPORT); END; END–EXEC;

EXEC SQL EXECUTE IMMEDIATE ”BEGIN MDB_API.COMMIT; END;”; � Commit CDI

else

put_line(” lock failed ”);

end if;

EXCEPTION � Error Message Output WHEN OTHERS =>

IF oracle_defs.sqlcode = user_exceptions.MDB_ERROR_NO THEN TEXT_IO.PUT_LINE(”MDB_ERROR_NO”); END IF;

IF oracle_defs.sqlcode = user_exceptions.USE_ERROR_NO THEN TEXT_IO.PUT_LINE(”USE_ERROR_NO”); END IF;

IF oracle_defs.sqlcode = user_exceptions.AUTHORIZATION_ERROR_NO THEN TEXT_IO.PUT_LINE(”AUTHORIZATION_ERROR_NO”); END IF;

IF oracle_defs.sqlcode = user_exceptions.PARAMETER_ERROR_NO THEN TEXT_IO.PUT_LINE(”PARAMETER_ERROR_NO”); END IF;

IF oracle_defs.sqlcode = user_exceptions.XREF_ERROR_NO THEN TEXT_IO.PUT_LINE(”XREF_ERROR_NO”); END IF;

TEXT_IO.PUT_LINE(”End of Program Exception Handler API/CDI–Test”);

end NOM_CDI;

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– E N D O F M A I N P R O G R A M –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


12.3 CDI MAINTENANCE IN I_MDB

A Configuration Data Item (CDI) refers to a configuration dependent MDB object which has beengenerated by application software and which is under MDA management. A CDI is not an enditem.

The CDIs are application generated data to be stored and managed in the MDB in dependenceto their configuration. A CDI is generated by an application software which is usually outsideMDA.For the CDI generation, different generation tools may be used which results in different contextand environment information, e.g. tool version, invocation parameter, etc. These configurationdependant data are stored in the MDB.

The CDI’s can be maintained within I_MDB. Information about all existing CDI‘s within a se-lected CCU version can be obtained.

To get the CDI maintenance information:

1. Navigate to the ‘I_MDB: CCU Versions window‘ and select the CCU version for which

you want to get the CDI information.

Figure 107.CDI Maintenance on a selected CCU version

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–15


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


2. Select Command –> Maintain CDI‘s... to pop up the ’Maintain CDI’s’ window.

Within this window the CDI names, types and their generation date are listed for the selectedCCU version.

Figure 108.Maintain CDI’s window

3. Pull the push pin in the upper left window corner to leave the ’Maintain CDI’s’ win-

dow.

12–16

CGS–RIBRE–SUM–00032 03.07.2015– –12–16


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


27


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13 CONSISTENCY CHECKER

13.1 OVERVIEW

In most cases, the MDA guarantees data integrity by checking during data entry time. But the possibility tomake data transparent and at the same time supporting the development of these data, implies that the MDAmust also offer possibilities to check data integrity not only at data entry time but at other points of time, andthat within single Versions of CDUs (User Trees) and CCUs even if these are still being developed.

For example, referencing an end item which has not been defined yet, will be a general need during develop-ment. Therefore it shall be possible to do so and to check the existence of the referenced end item at a laterpoint of time with the help of a Consistency Checker.

Because the MDA allows to violate such referential integrity constraints, it is absolutely necessary to beaware of the consistency status at any time. Therefore this status is attached to each Version as one maincharacteristic.

The consistency checks may be classified in selectable and non selectable checks. Non selectable consisten-cy checks are those that are executed in any case by the Consistency Checker. There is no influence by theuser in the definition of these checks. The following inconsistencies will be detected by the ConsistencyChecker:

� references to non–existing items or those which are out–of–scope, e.g. End Items withinEnd Item definitions,

� referential type incompatibilities

� circular references

� check if compilation status is TRUE

� check if foreign key aggregate is unique within the selected CCU or CDU scope (uniquecheck)

� double SIDs

� other Checks which are described in the CGS User Manual appendix N.

Selectable consistency checks are those that can be defined by the user. Within the definition of the data typesby the Data Dictionary Tool the user may specify and design consistency checks. The following user definedinconsistencies will be detected by the Consistency Checker:

� check if the data field, defined as mandatory field, is filled with a value (mandatorycheck)

� check if there is an aggregate for a defined end item type (mandatory check)

� check if attribute is unique within the selected CCU or CDU scope (unique check)

� check if attribute is unique in multi record aggregates (unique check)

� check if the data field, defined as range field, is filled with a value within the predefinedrange (range check)

� references that are out–of–date

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� minimum number of multi records for the aggregates

� user defined consistency checks

The resulting status reports give the End Item pathname, aggregate name, attribute name, and the text of theviolated consistency rules.

Notice: The Consistency Status is reset to ’NONE‘ each time data is updated in a specific Version.

The Consistency Checker Start–Up window provides in addition to the selection of the output devices allcapabilities to configure / limit the checks to be executed by selection of:

A) one or more of the following check categories

� Error

� Warning

� Caution

� Advisory

� TBD

Each single consistency check has a unique check category assigned. Possible check categories are configur-able by a special check category table. This allows easy extensions on check categories (table drivensee 13.6.2.1) without further implementation / coding effort.

Each check category gets a flag assigned defining if a failure of a check out of this category affects the consis-tency status of the CDU / CCU version (e.g. category Error: STATUS_EFFECTED = TRUE, catego-ry Advisory: STATUS_EFFECTED = FALSE).

B) one or more of the following check classes

� Mandatory checks (all mandatory aggregates / attributes filled)

� Referential Checks

· pathname references do not exist in scope

· pathname references exist in scope but point to wrong end item type

· Xref–Lists are out of date and need to be re–generated

· Xref–Lists build–up invalid cyclic dependencies (e.g. cyclic references ofAPs)

� Uniqueness checks

� Dependency Checks (checks within one or between two or more end items)

� TBD

Each single consistency check has a unique check class assigned. Possible check classes are configurableby a special check class table. This allows easy extensions on check classes (table driven) withoutfurther implementation / coding effort.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


C) one or more end item types

The Consistency Checker performs the checks of the selected check categories and check classes on the se-lected end item types.

The Consistency Checker Start–Up window allows the user to store and maintain his selections in ’user pro-files’. One profile can be defined as default profile and is automatically activated by start of the ConsistencyChecker Start–Up window. User profiles are stored in OS–Files and can be distributed among different users.

Important Constraints· All selected consistency checks are always executed within the whole configuration scope,

i.e. selected CCU or CDU version.

· The consistency status of CDU and CCU versions is only maintained in case the ConsistencyChecker performs a complete run (i.e. all checks affecting the consistency status of the se-lected CDU/CCU version). In all other cases the consistency status will not be modified.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.2 EXECUTING CONSISTENCY CHECKS

The Consistency Checker ( CC ) is a separate module which is called via I_MDB to check the consistencyof the end item data in the mission data base ( MDB ).

With I_MDB the user navigates through the name tree. Via flexible tool invocation (standard CGS/MDAcapability) the user is able to invoke the Consistency Checker Start–Up Window at the following places:

· ’I_MDB: CDU Versions’ window: Command––>Tools––>Consistency Checker

· ’I_MDB: CCU Versions’ window: Command––>Tools––>Consistency Checker

· ’I_MDB Navigator’, virtual user tree node, List Menu––>Tools––>Consistency Checker

· ’I_MDB Navigator’, end item node, List Menu––>Tools––>Consistency Checker

The user obtains here the possibility to configure the consistency check to his conception. He can store theparameters in profile files for future use. The Consistency Checker output can be directed to two output de-vices ( Screen, File ).

The following preconditions must be accomplished before the user can start the Consistency Checker:

– Scope selection

13.2.1 Consistency Checker Main Window

Figure 109.Consistency Checker Main Frame

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The window of the new Consistency Checker is divided into 3 areas:

· ConfigurationThis area displays the information of the CCU / CDU configuration:

� Path of the CCU / CDU

� The version of the CCU / CDU

� Start on: – Node: e.g.: ...\FLIGHT\ONBOARD\TCS\HEATINGor – End Item Type e.g.: [ EGSE_INTEGER_MEASUREMENT ]

· Output deviceThe user can select the desired output devices:

– ScreenThe Consistency Checker output will be displayed on the screen in a textedit window.

– Post ProcessorStarts a post processor tool.

– FileThe Consistency Checker output will be stored in the file which is given in the filenameinput area. A default filename ’untitled.rep’ is given in the filename box.

It is also possible to browse to a directory where the Consistency Checker output shall bestored. It shall be possible to assign a more meaningful name to be entered by the user,e.g. “DMSS_HW_V440_CCU_V100_1ST_CC_REP.txt” in a special directory.

· Check SelectionIn this area the user can select the desired check categories:

– Check CategoryThe user selects the needed check categories ( Error, Warning, Caution, Advisory ) whichare required for the consistency check.The check category which has impact to the consistency status is mark by the text ’’affectscc status’ in the check category list.

– Check ClassesThe user selects the needed check classes ( Dependency, Mandatory, Referential integrity,Uniqueness, ... ) which are required for the consistency check.

– End Item TypeThe user selects the needed end item types which are required for the consistency check.Only the end item types are visible which are used in the active scope.

· Execute ButtonStarts the consistency check with the selected conditions.When the user has not selected the complete entries which are necessary to determine the con-sistency status of the selected CDU / CCU version a warning message frame will pop up toinform the user.

· Reset ButtonSets the conditions back to the default conditions or to the beginning of the loaded profile file.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.2.2 Consistency Checker File Menu

The user has the possibility to store the selected conditions in a profile file in the file system to use these pro-files again.

Figure 110.Consistency checker file menu

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


· New Profile ...Generate a new profile file with a default adjustment.

Figure 111. Create a new profile file

· Open Profile ...Opens a generated profile file in the file system.

Figure 112.Open a profile file

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


· Save Profile ...Saves a generated profile file in the file system.

Figure 113.Save a profile file

· Save Profile As ...Saves a profile file in the file system under a new name.

Figure 114.Save As

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


· Delete Profile ...Deletes a generated profile file in the file system.

Figure 115.Save As

· Open PreProcessor File ...Open a post processor file. For detail description see chapter 13.2.3.

· EXITLeaves the Consistency Checker program.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.2.3 Post Processor Window

The post processor is a graphical user interface for the consistency checker ( CC ) output. If theuser has selected the output device ’Post Processor’ in the CC main window the CC generates ansemicolon separated ’.csv’ file. The ’.csv’ file contains two areas:

· Information Area:This area looks like:# Element configuration : <Element Configuration String># Mission : <Mission String># System tree version : <System Tree Version Number># CDU : <CCU/CDU pathname string># Start on : <Scope>

· Error Messages Area:For each error following information are available:

“<ErrorID: Error Message>”;“<Pathname>”;”<Aggregate Name>”;”<Attribute Name>”

13.2.3.1 Manual Post Processor Start

It is possible to open a ’*.csv’ file which was generated by a previous CC session. Therefore theuser has to open the ’*.csv’ ( ’Input File’ ) file in the post processor window. For later on selectederror informations a report file ( ’Report File’ ) must be inserted. Then the user has to press the’Load Input File’ button.

Figure 116.Post Processor Window

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.2.3.2 Automatic Post Processor Start

The post processor window opens automatically when the user has select the ’Post Processor’ but-ton in the output device area in the main CC window.

Figure 117.Post Processor Window

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.2.3.2.1 Post Processor Detail Data

Figure 118.Post Processor Detail Data Window

Figure 119.Post Processor Detail Data Window

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.3 CONSISTENCY CHECKER MESSAGES

Each message is constructed out of an unique identification (project abbreviation, category abbreviation,check number) and the message text.

The message text consists out of static and dynamic parts. Placeholders <%s> within the static part of themessage text will be substituted during check runtime by the actual values, e.g.

Identification Message Text

CGS ERR 111 Low Limit <%s> is higher than High Limit <%s>.

COL WRN 210 Reference out of scope

Within the report the messages look like:

CGS–ERR–111: Low Limit [100] is higher than High Limit [50].

COL–WRN–210: Reference out of scope

The identification of all CGS standard and end item type specific messages will start with ’CGS–’ followedby the category abbreviation and an integer number.

The identification of all user defined messages (e.g. Columbus specific) will start with e.g. ’COL–’ followedby the category abbreviation and an integer number.

Dynamic parts of the message will be surrounded by ’[’ ’]’.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4 CONSISTENCY STATUS

13.4.1 Consistency Status of a CDU (User Tree) Version

The Consistency Status of a CDU Version is ’NONE’ if the CDU Version has not been checked yet.

Its Consistency Status is ’GLOBAL_VALID ’ if the checked CDU Version fulfills all consistency rules andit does not contain references to external End Items (End Items defined in other CDU Versions).

Its Consistency Status is ’LOCAL_VALID ’ if the checked CDU Version fulfills all consistency rules butit does contain references to external End Items (which are not subject of the checking process though).

Its Consistency Status is ’LOCAL_INVALID ’ if the checked CDU Version does not fulfill all consistencyrules, e.g. it contains references to End Items which are assumed to exist within the checked CDU Version(internal references) but which do not exist.

13.4.2 Consistency Status of a CCU Version

The Consistency Status of a CCU Version is ’NONE’ if the CCU Version has not been checked yet.

Its Consistency Status is ’GLOBAL_VALID ’ if the checked CCU Version fulfills all consistency rules andit does not contain references to external CDU– or CCU Versions.

Its Consistency Status is ’LOCAL_VALID ’ if the checked CCU Version fulfills all consistency rules butit does contain references to external CDU– or CCU Versions (which are not subject of the checking processthough).

Its Consistency Status is ’LOCAL_INVALID ’ if the checked CCU Version does not fulfill all consistencyrules, e.g. it contains references to CDU– or CCU Versions which are assumed to exist in the scope of thechecked CCU Version (internal references) but which do not exist.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–15


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3 Consistency Status by different Error Cases

The scope for all examples for consistency status settings in this section is CCU D.

The consistency status is depended from the used report procedure and procedure parameters.

a) References to other end items are implemented with pathnames

see Chapter 13.4.3.1, 13.4.3.2 and 13.4.3.3

b) Abstract references to other end items are not implemented with pathnames (but with integers, enumera-tions or strings), minimum and/or maximum number of references are considered

see Chapter 13.4.3.4, 13.4.3.5, 13.4.3.6, 13.4.3.7 and 13.4.3.8

13.4.3.1 Error in End Item

Report procedure: CC_COMMON.REPORT_CHECK_IN_END_ITEM_NOK

CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1

ÇÇÇÇÇÇÇÇÇÇÇÇ

global valid

local valid

local invalid

Status

Agg1

Agg2

Figure 120. Check in end item is not ok

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–16


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.2 Error between End Items

Report procedure: CC_COMMON.REPORT_CHECK_BETWEEN_EIS_NOK

13.4.3.2.1 CDU Scope

CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1 End Item 2


global valid

local valid

local invalid

Status

wrong Item Type

Figure 121. Check between end items is not ok

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–17


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.2.2 CCU Scope

ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ

CCU A


CDU A

CCU B

CCU C

CCU D

CDU B CDU C


ÇÇÇÇÇÇÇÇ

global valid

local valid

local invalid

Status

Figure 122. Check between end items is not ok

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–18


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.3 Attribute or Foreign Key Aggregate is not unique in Scope

The end items to be checked must be from the same end item type.

Report procedure: CC_COMMON.REPORT_CHECK_UNIQUE_NOK

13.4.3.3.1 CCU Scope

CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C



global valid

local valid

local invalid

Status

Attr N = A Attr N = A

Figure 123. Attribute or Foreign Key Aggregate is not unique in CCU Scope

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–19


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.3.2 CDU Scope

CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C


ÇÇÇÇÇÇÇÇ

global valid

local valid

local invalid

Status

Attr N = A Attr N = A

Figure 124. Attribute or Foreign Key Aggregate is not unique in CDU Scope

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–20


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.4 Reference Out of Scope

Report procedure:

CC_COMMON.REPORT_CHECK_IN_SCOPE_NOK (pathname reference)

CC_COMMON.REPORT_MISSING_REFERENCE (abstract reference)


CCU A

ÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇÇ

CDU A


CCU B


CCU C


CCU D

CDU B CDU C


ÇÇÇÇÇÇÇÇÇ

global valid

local valid

local invalid

Status

ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ

CDU B

Figure 125. Reference out of Scope

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–21


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.5 Reference OK

No error will be reported – only for status setting.

Report procedure: CC_COMMON.REPORT_REFERENCE_OK (abstract reference)

If the reference a pathname then it is not recommended to execute the procedure REPORT_REF-ERENCE_OK. The correct status will be generated automatically by the Consistency Checker.


CCU A


CDU A

CCU B

CCU C

CCU D

CDU B CDU C


ÇÇÇÇÇÇÇÇ

global valid

local valid

local invalid

Status

Figure 126. Reference out of CDU

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–22


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.6 Too many References

Report procedure: CC_COMMON.REPORT_TOO_MANY_REFERENCES (abstract reference)

13.4.3.6.1 MINIMUM = 1, MAXIMUM = 1


CCU A


CDU A

CCU B

CCU C

CCU D

CDU B CDU C



global valid

local valid

local invalid

Status

End Item 3

Figure 127. Too many References (MINIMUM = 1, MAXIMUM = 1)

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–23


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1

End


global valid

local valid

local invalid

Status

End Item 3Item 2


CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1

ÇÇÇÇÇÇÇÇ

global valid

local valid

local invalid

Status

End Item 3EI 2


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–24


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



CCU A


CDU A

CCU B

CCU C

CCU D

CDU B CDU C



global valid

local valid

local invalid

Status


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–25


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.6.2 MINIMUM =1, MAXIMUM = 2


CCU A


CDU A

CCU B

CCU C

CCU D

CDU B CDU C


ÇÇÇÇÇÇÇÇ

global valid

local valid

local invalid

Status

End Item 3


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–26


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1

End


global valid

local valid

local invalid

Status

End Item 3Item 2 End Item 4


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–27


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.7 Error between End Items

Report procedure: CC_COMMON.REPORT_ERROR_BETWEEN_END_ITEMS (abstract reference)

CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1

ÇÇÇÇÇÇÇÇ

global valid

local valid

local invalid

Status

End Item 2

Figure 133. Error between End Items

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–28


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1


global valid

local valid

local invalid

Status

End Item 2


CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1

End


global valid

local valid

local invalid

Status

End Item 3Item 2


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–29


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1


global valid

local valid

local invalid

Status



CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1

ÇÇÇÇÇÇÇÇ

global valid

local valid

local invalid

Status

End Item 3EI 2


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–30


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.8 Uniqueness Violation

Report procedure: CC_COMMON.REPORT_UNIQUENESS_VIOLATION (abstract reference)

13.4.3.8.1 MAXIMUM = 1

CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1


global valid

local valid

local invalid

Status

End Item 2

Figure 138. Uniqueness Violation (MAXIMUM = 1)

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–31


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1


global valid

local valid

local invalid

Status

End Item 2


CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1


global valid

local valid

local invalid

Status



13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–32


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.4.3.8.2 MAXIMUM = 2

CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1

ÇÇÇÇÇÇÇÇ

global valid

local valid

local invalid

Status

End Item 2


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–33


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1


global valid

local valid

local invalid

Status



CCU A

CDU A

CCU B

CCU C

CCU D

CDU B CDU C

End Item 1

End

ÇÇÇÇÇÇÇÇ

global valid

local valid

local invalid

Status

End Item 3Item 2


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–34


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.5 PREDEFINED CONSISTENCY CHECKS

Quite a lot of consistency checks are performed on the CGS Standard End Item Types and their Aggregatesdefined in the document COL–RIBRE–TN 1206. The document contains all CGS Standard End item Types,Aggregates and the related Attributes. For most of the attributes a request for consistency check is defined.Also in the appendix N of the CGS Reference Manual all predefined consistency checks are listed.

The PL/SQL packages CC_CGS, CC_CGS_1, CC_CGS_2, CC_CGS_3 and CC_CGS_4 contain storedprocedures that perform checks on the CGS Standard End Item Types and Aggregates as defined in the abovementioned document.

When starting the Consistency Checker within I_MDB for a CDU scope or CCU scope, each End–Item thatcontains CGS Standard Aggregates, will be checked by the predefined checks.

A detailed description of detected predefined check errors will be displayed within the Consistency Checkerstatus report.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–35


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6 USER DEFINED CONSISTENCY CHECKS

13.6.1 User defined PL/SQL Procedures

User defined consistency checks are checks which extends the predefined checks as described before.

User defined PL/SQL Procedures are the mechanism to implement special checks on user defined end item’s.

Consistency check procedures may be written by the user in PL/SQL. A collection of procedures is calleda package. These packages are handled as stored procedures. They exist in the database and will be handledas API procedures. The packages have to be installed with the MDB account.

To enable these procedures it must executed a PL/SQL script which contains procedure calls from the PL/SQL package CC_SETUP. The procedures of this package store information about checks into ConsistencyChecker internal tables. After the start the Consistency Checker reads this internal tables and has the informa-tion for all checks.

Errors will be propagated via procedures which are part of the Consistency Checker PL/SQL packageCC_COMMON.

The user who has written the user defined consistency check procedure is responsible for the creation of mes-sages, indicating inconsistencies detected by the procedure.

The consistency checker not be aborted, when a run–time error is detected. This is a default setting and maynot be changed by the user.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–36


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.2 Check Categories and Check Classes

13.6.2.1 Table CC_CATEGORIES

This table contains all check categories.

Column Data type Description

CATEGORY_LONG_NAME VARCHAR2(40) Long name of category

CATEGORY VARCHAR2(3) Abreviation of long category name

STATUS_AFFECTED VARCHAR2(5) Boolean flag identifying if failure ofcheck affects the consistency statusof the CDU / CCU version or not.

Primary key is on column (CATEGORY).

Initial data records are:

· <MDB Version> Error ERR TRUE

· <MDB Version> Warning WRN FALSE

· <MDB Version> Caution CAU FALSE

· <MDB Version> Advisory ADV FALSE

· <MDB Version> others TBD TBD

13.6.2.2 Table CC_CLASSES

This table contains all check classes.

Column Data type Description

CLASS VARCHAR2(40) Name of the check class

Primary key is on column (CLASS).

Initial data records are:

· <MDB Version> Mandatory

· <MDB Version> Referential integrity

· <MDB Version> Uniqueness

· <MDB Version> Dependency (checks within one or between several end items)

· <MDB Version> others

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–37


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.3 Consistency Checker High Level Program Flow

For each execution mode (WITHIN_END_ITEM,

BETWEEN_END_ITEM,

UNIQUE_IN_SCOPE)

Execute procedure INIT_CC_END_ITEMS

For each check procedure

Execute initialisation procedure

For each query result of CC_FIXED_STATEMENT and CC_DYN_STATEMENT

execute check procedure

end loop

end loop

end loop

Execute finish procedure

Figure 144. Consistency Checker high level flow diagram

1. Loop: For each execution mode

For each execution mode (outer loop) the consistency checker executes the procedureINIT_CC_END_ITEMS. This procedure fills the table CC_END_ITEMS with those end items tobe checked depending on the execution mode, consistency status, selected subtree, check categoriesand check classes (refer to section NO TAG). The view V_CC_PATHNAME_SID_REL whichbased on this table is needed for the query statement retrieving CDU version, SID (and other optionalcolumns).

2. Loop: For each check procedure

For each check procedure to be executed its initialization procedure is started (if exists). This initializationprocedure mays fill the table CC_DYN_STATEMENTS with query statements for retrieval of SID,CDU internal version (and other columns) of those end items being candidate for this check proce-dure. This procedure cans also fill internal PL/SQL tables needed for check procedures.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–38


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


For each check procedure to be executed its finish procedure is started (if exists). This finish procedure maysdelete from (PL/SQL) tables which are filled by the initialization procedure.

3. Loop: For each query result of CC_FIXED_STATEMENTS, CC_DYN_STATEMENTS

First the query statements of CC_FIXED_STATEMEMENTS and second those of CC_DYN_STATE-MENTS are processed.

For each query result the result of the check procedure is taken by execution of the check procedure.

Each execution of the check procedure stores its results in the report table.

The check procedures shall not access the report tables directly but shall use library procedures to store thecheck results in the report table including the resulting consistency status (placeholders of messageare substituted by actual values).

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–39


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.4 Package CC_SETUP

13.6.4.1 Procedure REMOVE_ALL_CHECKS

Procedure interface:

REMOVE_ALL_CHECKS

Parameter description:

no parameters

Procedure description:

Use this procedure to remove all checks.

13.6.4.2 Procedure REMOVE_PROJECT_CHECKS


REMOVE_PROJECT_CHECKS (DEL_PROJECT)


Parameter: Datatype: Description:

DEL_PROJECT in varchar2 project abbreviation (up to 3 characters)


Use this procedure to remove all checks of the project DEL_PROJECT.

13.6.4.3 Procedure REMOVE_CHECK


REMOVE_CHECK (DEL_PROJECT,

DEL_CATEGORY,

DEL_CHECK_NUMBER)



DEL_PROJECT in varchar2 project abbreviation (up to 3 characters)

DEL_CATEGORY in varchar2 check category (see 13.6.2.1)

DEL_CHECK_NUMBER in number check number (integer)


Use this procedure to remove one check.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–40


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.4.4 Procedure INSERT_CHECK

This procedure is overloaded. Either use INSERT_CHECK’1 or use INSERT_CHECK’2,

ADD_MESSAGE_TEXT_TO_CHECK, ADD_TYPE_TO_CHECK and

ADD_FIXED_STATEMENT_TO_CHECK


INSERT_CHECK (PROJECT,

CATEGORY,

CHECK_NUMBER,

CLASS,

EXECUTION_MODE,

FORCED_EXECUTION,

PACKAGE_NAME,

PROCEDURE_NAME,

INIT_PACKAGE_NAME,

INIT_PROCEDURE_NAME,

FINISH_PACKAGE_NAME,

FINISH_PROCEDURE_NAME,

TYPES,

STATEMENT,

MESSAGE_TEXT)



PROJECT in varchar2 project abbreviation (up to 3 characters)

CATEGORY in varchar2 check category (see 13.6.2.1)

CHECK_NUMBER in number check number (integer)

CLASS in varchar2 check class (see 13.6.2.2)

EXECUTION_MODE in varchar2 enumeration

WITHIN_END_ITEM

BETWEEN_END_ITEM

UNIQUE_IN_SCOPE

FORCED_EXECUTION in varchar2 enumeration (obsolete)

TRUE

FALSE

PACKAGE_NAME in varchar2 Name of the PL/SQL package containing

the procedure implementation

PROCEDURE_NAME in varchar2 Name of the stored procedure implementing the check

INIT_PACKAGE_NAME in varchar2 Name of the PL/SQL package containing

the initialisation procedure implementation

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–41


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


INIT_PROCEDURE_NAMEin varchar2 Name of the initialisation stored procedure

(see 13.6.3)

FINISH_PACKAGE_NAME in varchar2 Name of the PL/SQL package containing

the finish procedure implementation

FINISH_PROCEDURE_NAME in varchar2 Name of the finish stored procedure (see 13.6.3)

TYPES in varchar2 type name can be:

– one end item type name

– a comma separated list of end item type names

– % (for all types)

STATEMENT in varchar2 Query statement retrieving CDU version, SID and

other optional columns

MESSAGE_TEXT in varchar2 message text (placeholders marked as <%s>)

The parameters PACKAGE_NAME, INIT_PACKAGE_NAME, INIT_PROCEDURE_NAME, FIN-ISH_PACKAGE_NAME or FINISH_PROCEDURE_NAME can be null.


Use this procedure to install a check.


INSERT_CHECK (PROJECT,

CATEGORY,

CHECK_NUMBER,

CLASS,

EXECUTION_MODE,

FORCED_EXECUTION,

PACKAGE_NAME,

PROCEDURE_NAME,

INIT_PACKAGE_NAME := null,

INIT_PROCEDURE_NAME := null,

FINISH_PACKAGE_NAME := null,

FINISH_PROCEDURE_NAME := null)






CLASS in varchar2 check class (see 13.6.2.2)

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–42


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


EXECUTION_MODE in varchar2 enumeration

WITHIN_END_ITEM

BETWEEN_END_ITEM

UNIQUE_IN_SCOPE

FORCED_EXECUTION in varchar2 enumeration (obsolete)

TRUE

FALSE

PACKAGE_NAME in varchar2 Name of the PL/SQL package containing

the procedure implementation

PROCEDURE_NAME in varchar2 Name of the stored procedure implementing the check

INIT_PACKAGE_NAME in varchar2 Name of the PL/SQL package containing

the initialisation procedure implementation

INIT_PROCEDURE_NAMEin varchar2 Name of the initialisation stored procedure

(see 13.6.3)

FINISH_PACKAGE_NAME in varchar2 Name of the PL/SQL package containing

the finish procedure implementation

FINISH_PROCEDURE_NAME in varchar2 Name of the finish stored procedure (see 13.6.3)

The parameters PACKAGE_NAME, INIT_PACKAGE_NAME, INIT_PROCEDURE_NAME, FIN-ISH_PACKAGE_NAME or FINISH_PROCEDURE_NAME can be null.


Use this procedure to install a check.

13.6.4.5 Procedure ADD_MESSAGE_TEXT_TO_CHECK


ADD_MESSAGE_TEXT_TO_CHECK (PROJECT,

CATEGORY,

CHECK_NUMBER,

MESSAGE_NUMBER,

MESSAGE_TEXT)







MESSAGE_NUMBER in number message number

MESSAGE_TEXT in varchar2 message text (placeholders marked as <%s>)


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–43


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.4.6 Procedure ADD_TYPE_TO_CHECK


ADD_TYPE_TO_CHECK (PROJECT,

CATEGORY,

CHECK_NUMBER,

TYPE_NAME)






TYPE_NAME in varchar2 type name can be:

– one end item type name

– a comma separated list of end item type names

– % (for all types)


Use this procedure to add an end item type to an existing check.

13.6.4.7 Procedure ADD_FIXED_STATEMENT_TO_CHECK


ADD_FIXED_STATEMENT_TO_CHECK (PROJECT,

CATEGORY,

CHECK_NUMBER,

STATEMENT_NUMBER,

STATEMENT)






STATEMENT_NUMBER in number statement number





13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–44


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.4.8 Procedure ADD_DYN_STATEMENT_TO_CHECK


ADD_DYN_STATEMENT_TO_CHECK (PROJECT,

CATEGORY,

CHECK_NUMBER,

STATEMENT_NUMBER,

STATEMENT)







STATEMENT_NUMBER in number statement number




13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–45


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.5 Error Reporting Procedures

The error reporting procedures are implemented in the PL/SQL package CC_COMMON.

The name of each error reporting procedure begins with REPORT_.

The following procedures should be used to propagate error to the Consistency Checker:

a) References to other end items are implemented with pathnames

REPORT_CHECK_IN_END_ITEM_NOK

REPORT_CHECK_BETWEEN_EIS_NOK

REPORT_CHECK_UNIQUE_NOK

REPORT_CHECK_IN_SCOPE_NOK

b) References to other end items are not implemented with pathnames (but with integers, enumerations orstrings), minimum and/or maximum number of references are considered

REPORT_ERROR_BETWEEN_END_ITEMS

REPORT_MISSING_REFERENCE

REPORT_TOO_MANY_REFERENCES

REPORT_REFERENCE_OK

REPORT_UNIQUENESS_VIOLATION

13.6.5.1 Procedure REPORT_CHECK_IN_END_ITEM_NOK

Use this procedure if checks between aggregates in one end item or between attributes in one aggregate areperformed to propagate an error message to the Consistency Checker.

Consistency status: see 13.4.3.1

ÀÀÀÀÀÀ

ÀÀÀÀ

ÀÀÀÀÀÀ

ÀÀÀÀÀÀÀÀÀ

ÀÀÀÀ

ÀÀÀÀÀÀ

End Item 1

Check between

Selected Scope

Agg1

Agg2

Figure 145. REPORT_CHECK_IN_END_ITEM_NOK

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–46


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


type MSG_PAR_TABLE_TYPE is table of varchar2(2000) index by binary_integer;

NO_MSG_PAR MSG_PAR_TABLE_TYPE;


REPORT_CHECK_IN_END_ITEM_NOK (SHORT_ID,

AGG_NAME := null,

ATT_NAME := null,

MSG_NBR := 1,

MSG_PARS := NO_MSG_PAR)




SHORT_ID in number Short ID of end item to be checked

AGG_NAME in varchar2 aggregate name

ATT_NAME in varchar2 attribute name

MSG_NBR in number message number

MSG_PARS in MSG_PAR_TABLE_TYPE message parameter table

This is the general form of REPORT_CHECK_IN_END_ITEM_NOK.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–47


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



REPORT_CHECK_IN_END_ITEM_NOK (SHORT_ID,

CDU,

AGG_NAME := null,

ATT_NAME := null,

MSG_NBR := 1,

MSG_PAR1 := null,

MSG_PAR2 := null,

MSG_PAR3 := null,

MSG_PAR4 := null,

MSG_PAR5 := null)





CDU in number CDU internal version

AGG_NAME in varchar2 Aggregate name

ATT_NAME in varchar2 Attribute name


MSG_PAR1 in varchar2 first message parameter

MSG_PAR2 in varchar2 second message parameter

MSG_PAR3 in varchar2 third message parameter

MSG_PAR4 in varchar2 forth message parameter

MSG_PAR5 in varchar2 fifth message parameter

This is a special form of REPORT_CHECK_IN_END_ITEM_NOK which is suitable for the most cases.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–48


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.5.2 Procedure REPORT_CHECK_BETWEEN_EIS_NOK

Use this procedure if checks between different end items (All end items are in scope and are existing) areperformed to propagate an error message to the Consistency Checker.


ÀÀÀÀÀÀÀÀÀ

ÀÀÀÀ

ÀÀÀÀÀÀ

ÀÀÀÀÀÀÀÀÀ

ÀÀÀÀ

ÀÀÀÀÀÀÀÀÀ


Check between

Selected Scope

Figure 146. REPORT_CHECK_BETWEEN_EIS_NOK

type SID_TABLE_TYPE is table of T_USER_TREE_NODES.F_SID%type index by binary_integer;


REPORT_CHECK_BETWEEN_EIS_NOK (SHORT_ID,

TO_SIDS,

AGG_NAME := null,

ATT_NAME := null,

MSG_NBR := 1,


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–49


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:






TO_SIDS in SID_TABLE_TYPE table of Short IDs of referenced end items





This is the general form of REPORT_CHECK_BETWEEN_EIS_NOK.



CDU,

TO_CDU,

AGG_NAME := null,

ATT_NAME := null,

MSG_NBR := 1,

MSG_PAR1 := null,

MSG_PAR2 := null,

MSG_PAR3 := null,

MSG_PAR4 := null,

MSG_PAR5 := null)





CDU in number CDU internal version of item to be checked

TO_CDU in number CDU internal version of referenced end item









This is a special form of REPORT_CHECK_BETWEEN_EIS_NOK which is suitable for checks betweentwo end items.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–50


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


type CDU_TABLE_TYPE is table of T_USER_TREE_NODES.F_CDU_INTERNAL_VERSION%typeindex by binary_integer;



CDU,

TO_CDUS,

AGG_NAME := null,

ATT_NAME := null,

MSG_NBR := 1,

MSG_PAR1 := null,

MSG_PAR2 := null,

MSG_PAR3 := null,

MSG_PAR4 := null,

MSG_PAR5 := null)






TO_CDUS in CDU_TABLE_TYPE table of CDU internal versions

of referenced end items









This is a special form of REPORT_CHECK_BETWEEN_EIS_NOK which is suitable for checks betweenmore as two end items.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–51


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.5.3 Procedure REPORT_CHECK_UNIQUE_NOK

Use this procedure if uniqueness checks between different end items (All end items are in scope and are exist-ing) are performed to propagate an error message to the Consistency Checker.

The uniqueness check of one attribute from the same aggregate in different end items is already implementedby the predefined consistency check CGS–ERR–3. The Uniqueness of one Attribute in scope is selectablewith the attribute editor of the DADIMA tool.

The uniqueness check of foreign key aggregates is already implemented by the predefined consistency checkCGS–ERR–5. In the aggregate editor of the DADIMA tool it is possible to define an aggregate as foreignkey aggregate.

All other uniqueness check cases must be defined by the user (check programmer).


ÀÀÀÀÀÀÀÀÀ

ÀÀÀÀ

ÀÀÀÀÀÀ

ÀÀÀÀÀÀÀÀÀ

ÀÀÀÀÀÀ

ÀÀÀÀÀÀÀÀÀ

End Item 1

Selected Scope

Agg1

Agg2

Agg1

Agg2

Checkbetween} }

End Item 2

Figure 147. REPORT_CHECK_UNIQUE_NOK


REPORT_CHECK_UNIQUE_NOK (SHORT_ID,

TO_SIDS,

AGG_NAME := null,

ATT_NAME := null,

MSG_NBR := 1,


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–52


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:






TO_SIDS in SID_TABLE_TYPE table of Short IDs of referenced end items





This is the general form of REPORT_CHECK_UNIQUE_NOK.


REPORT_CHECK_UNIQUE_NOK (SHORT_ID,

CDU,

TO_CDUS,

AGG_NAME := null,

ATT_NAME := null,

MSG_NBR := 1,

MSG_PAR1 := null,

MSG_PAR2 := null,

MSG_PAR3 := null,

MSG_PAR4 := null,

MSG_PAR5 := null)







of referenced end items









This is a special form of REPORT_CHECK_BETWEEN_EIS_NOK which is suitable for the most cases.

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–53


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.5.4 Procedure REPORT_CHECK_IN_SCOPE_NOK

Pathname reference must be exist in scope is a predefined check.

This procedure is not needed for user defined checks.

Use this procedure if the referenced end item is not in scope or does not exist to propagate an error messageto the Consistency Checker.


13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–54


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.5.5 Procedure REPORT_ERROR_BETWEEN_END_ITEMS

Use this procedure if checks between different end items (All end items are in scope and are existing) areperformed to propagate an error message to the Consistency Checker.

The references in the MDB are not implemented by pathnames but by other types of attributes (integer, enu-meration or string).



REPORT_ERROR_BETWEEN_END_ITEMS (SHORT_ID,

CDU,

TO_CDUS,

AGG_NAME := null,

ATT_NAME := null,

MSG_NBR := 1,








of referenced end items:

Index : CDU internal version of referenced

end item

Content: Number of this CDU internal version





13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–55


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.5.6 Procedure REPORT_MISSING_REFERENCE

Use this procedure if the referenced end items (TO_CDUS) are not in scope or are not existing to propagatean error message to the Consistency Checker.




REPORT_MISSING_REFERENCE (SHORT_ID,

CDU,

TO_CDUS := NO_TO_CDU,

AGG_NAME := null,

ATT_NAME := null,

MINIMUM := 1,

MSG_NBR := 1,










end item




MINIMUM in varchar2 minimum number of referenced end items



13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–56


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.5.7 Procedure REPORT_TOO_MANY_REFERENCES

Use this procedure if to many referenced end items (TO_CDUS) exist to propagate an error message to theConsistency Checker.




REPORT_TOO_MANY_REFERENCES (SHORT_ID,

CDU,

TO_CDUS,

AGG_NAME := null,

ATT_NAME := null,

MINIMUM := 1,

MAXIMUM := 1,

MSG_NBR := 1,










end item





MAXIMUM in varchar2 maximum number of referenced end items



13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–57


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.5.8 Procedure REPORT_REFERENCE_OK

Use this procedure if referenced end items (TO_CDUS) are out of CDU to propagate an information to theConsistency Checker. This information is only for the consistency status setting needed. No error messagewill be generated.




REPORT_REFERENCE_OK (SHORT_ID,

CDU,

TO_CDUS,

MINIMUM := 1)









end item



13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–58


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.5.9 Procedure REPORT_UNIQUENESS_VIOLATION

Use this procedure if uniqueness checks between different end items (All end items are in scope and are exist-ing) are performed to propagate an error message to the Consistency Checker.




REPORT_MISSING_REFERENCE (SHORT_ID,

CDU,

TO_CDUS,

AGG_NAME := null,

ATT_NAME := null,

MAXIMUM := 1,

MSG_NBR := 1,










end item




MAXIMUM in varchar2 maximum number of referenced end items



13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–59


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.6.6 Create Consistency Checks

The creation of consistency checks is divided in two parts

• insert check setup procedure calls into the consistency checker setup script

• insert check procedures in a PL/SQL stored procedure package

The first part stores information about checks into Consistency Checker internal tables. After the start theConsistency Checker reads this internal tables and has information for all checks.

The second part is the PL/SQL stored procedure package(s) which contain(s) the check procedures.

If the scripts for the both parts are located in the directory $MDA_HOME/config/mdb/install/user_de-fined_procedures then they will be executed from the script install_mdb automatically.

The order for the execution of both above mentioned parts must be:

1. PL/SQL stored procedure package (compilation of package)

2. consistency checker setup script

13.6.6.1 Consistency Checker Setup Script

13.6.6.1.1 Description of Procedure Parameters

see also 13.6.4

PROJECT: project abbreviation (any 3 characters)

CATEGORY: check category abbreviation (see 13.6.2.1)

recommended: ERR error status affected

WRN warning no status affected

CHECK_NUMBER: check number (any integer)

CLASS: check class (see 13.6.2.2)

EXECUTION_MODE:

WITHIN_END_ITEM check between attributes and/or aggregates in one end item

BETWEEN_END_ITEM check between end items

UNIQUE_IN_SCOPE check: a combination of attributes must be unique in scope

FORCED_EXECUTION: (obsolete)

TRUE

FALSE

INIT_PROCEDURE_NAME, FINISH_PROCEDURE_NAME:

see 13.6.3

TYPES: can be:

one end item type name

a comma separated list of end item type names

% (for all types)

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–60


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


STATEMENT: CC_FIXED_STATEMENTS in 13.6.3

examples:

select INTERNAL_VERSION,SID,END_ITEM_TYPE,MAPPED_TO_TYPE,PATHNAME

from V_CC_PATHNAME_SID_REL

where END_ITEM_TYPE in (’end_item_type_1’,’end_item_type_2’);

select INTERNAL_VERSION,SID

from V_CC_PATHNAME_SID_REL

where END_ITEM_TYPE = ’end_item_type_1’;

select INTERNAL_VERSION, SID, MAPPED_TO_TYPE

from (select TYPE_NAME

from CC_REL_TYPE_CHECKS

where PROJECT=’<project_name>’

and CATEGORY=’WITHIN_END_ITEM’

and CHECK_NUMBER=<check_number>), V_CC_PATHNAME_SID_REL

where MAPPED_TO_TYPE = TYPE_NAME’);

The table for the select statement must be V_CC_PATHNAME_SID_REL. A join with an other tableis possible. The columns INTERNAL_VERSION and SID must be selected, the others columns areoptional. The join with the table CC_REL_TYPE_CHECKS provide all end items with the types tobe checked (defined by CC_SETUP.INSERT_CHECK or CC_SETUP.ADD_TYPE_TO_CHECK).

INTERNAL_VERSION: CDU internal version

SID: short ID of the end item

END_ITEM_TYPE: end item type of the end item

MAPPED_TO_TYPE: if the end item type is mapped: mapped end item type

if the end item type is not mapped: END_ITEM_TYPE

PATHNAME: pathname of the end item

13.6.6.1.2 Simple Case

see 13.6.4.4

setup script:

declare PRJ varchar2(3) := ’<project_abbreviation>’; CAT varchar2(3); CNO number;begin

...

CNO := <check_number>;

CAT := ’<check_category_abbreviation>’; –– see 13.6.2.1

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–61


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


CC_SETUP.INSERT_CHECK

(PRJ,CAT,CNO,

’<check_class>’, –– see 13.6.2.2

’<execution_mode>’

’<forced_execution>’, –– obsolete

’<package_name>’,

’<procedure_name>’,

null, –– init package name

null, –– init procedure name

null, –– finish package name

null, –– finish procedure name

’<end_item_type_1>,<end_item_type_2> .. <end_item_type_n>’,

’<fixed_statement>’,

’<message_text>’);

...

end;/

example of setup script:

declare PRJ varchar2(3) := ’CGS’; CAT varchar2(3) := ’ERR’; CNO integer;begin

...

CNO := 991;


(PRO,CAT,CNO,

’WITHIN_END_ITEM’,’FALSE’,

’CGS_TEST’,’PROC’ || CNO,

null, null, null, null,

’EGSE_INTEGER_MEASUREMENT,UNSIGNED_INTEGER_MEASUREMENT’,

’select INTERNAL_VERSION, SID’ || ’ from V_CC_PATHNAME_SID_REL’ || ’ where MAPPED_TO_TYPE in ’ ||

’( ’’EGSE_INTEGER_MEASUREMENT’’,’’UNSIGNED_INTEGER_MEASUREMENT’’)’,

’Value 1 <%s> is greater than Value 2 <%s>’);

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–62


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


...

end;/

13.6.6.1.3 Complex Case

see 13.6.4.4, 13.6.4.5, 13.6.4.6, 13.6.4.7 and 13.6.4.8

setup script:

declare PRJ varchar2(3) := ’<project_abbreviation>’; CAT varchar2(3); CNO number;begin

...

CNO := <check_number>;

CAT := ’<check_category_abbreviation>’; –– see 13.6.2.1


(PRJ,CAT,CNO,

’<check_class>’, –– see 13.6.2.2

’<execution_mode>’

’<forced_execution>’, –– obsolete

’<package_name>’,

’<procedure_name>’,

’<init_package_name>’, –– init package name

’<init_procedure_name>’, –– init procedure name

’<finish_package_name>’, –– finish package name

’<finish_procedure_name>’); –– finish procedure name

CC_SETUP.ADD_TYPE_TO_CHECK(PRJ,CAT,CNO,’<end_item_type_1>’);

CC_SETUP.ADD_TYPE_TO_CHECK(PRJ,CAT,CNO,’<end_item_type_2>’);

..

CC_SETUP.ADD_TYPE_TO_CHECK(PRJ,CAT,CNO,’<end_item_type_n>’);

CC_SETUP.ADD_MESSAGE_TEXT_TO_CHECK(PRJ,CAT,CNO,1,’<message_text_1>’);

CC_SETUP.ADD_MESSAGE_TEXT_TO_CHECK(PRJ,CAT,CNO,2,’<message_text_2>’);

..

CC_SETUP.ADD_MESSAGE_TEXT_TO_CHECK(PRJ,CAT,CNO,n,’<message_text_n>’);

CC_SETUP.ADD_FIXED_STATEMENT_TO_CHECK(PRJ,CAT,CNO,1,’<fixed_stmt_1>’);

CC_SETUP.ADD_FIXED_STATEMENT_TO_CHECK(PRJ,CAT,CNO,2,’<fixed_stmt_2>’);

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–63


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


..

CC_SETUP.ADD_FIXED_STATEMENT_TO_CHECK(PRJ,CAT,CNO,n,’<fixed_stmt_n>’);

...

end;/

example of setup script:

declare PRJ varchar2(3) := ’CGS’; CAT varchar2(3); CNO number;begin

...

CNO := 992;

CAT := ’WRN’;


(PRJ,CAT,CNO,

’BETWEEN_END_ITEM’,’TRUE’,

’CGS_TEST’,’PROC’ || CNO,

’CGS_TEST’,’INI_PROC’ || CNO,

’CGS_TEST’,’FINISH_PROC’ || CNO,

CC_SETUP.ADD_TYPE_TO_CHECK(PRJ,CAT,CNO,

’EGSE_INTEGER_MEASUREMENT’);

CC_SETUP.ADD_TYPE_TO_CHECK(PRJ,CAT,CNO,

’UNSIGNED_INTEGER_MEASUREMENT’);

CC_SETUP.ADD_MESSAGE_TEXT_TO_CHECK(PRJ,CAT,CNO,1,

’Value 1 <%s> is greater than Value 2 <%s>’);

CC_SETUP.ADD_MESSAGE_TEXT_TO_CHECK(PRJ,CAT,CNO,2,

’Value 1 <%s> is equal Value 2 <%s>’);

CC_SETUP.ADD_FIXED_STATEMENT_TO_CHECK(PRJ,CAT,CNO,1,

’select INTERNAL_VERSION, SID’ ||

’ from V_CC_PATHNAME_SID_REL’ ||

’ where MAPPED_TO_TYPE = ’’EGSE_INTEGER_MEASUREMENT’’’);

CC_SETUP.ADD_FIXED_STATEMENT_TO_CHECK(PRJ,CAT,CNO,2,

’select INTERNAL_VERSION, SID’ ||

’ from V_CC_PATHNAME_SID_REL’ ||

’ where MAPPED_TO_TYPE = ’’UNSIGNED_INTEGER_MEASUREMENT’’’);

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–64


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


...

end;/

13.6.6.2 Check Procedure

The parameter (number and types) of a consistency check procedure must comply to the query results of thestatement (see 13.6.6.1.1).

Each check procedure checks exact one end item per procedure call.

Example passed to simple case in 13.6.6.1.2:

procedure PROC_SIMPLE (CDU integer,SID integer) is

VAL_1 : integer;

VAL_2 : integer;

begin

select <att_1>

from <agg_1>

into VAL_1

where F_CDU_INTERNAL_VERSION = CDU

and F_SID = SID;

select <att_2>

from <agg_2>

into VAL_2


and F_SID = SID;

if VAL_1 > VAL_2 then

CC_COMMON.REPORT_CHECK_IN_END_ITEM_NOK

(SID, CDU, ’<agg_1>’, ’<att_1>’, 1, VAL_1, VAL_2);

end if;

end PROC_SIMPLE;

Example passed to complex case in 13.6.6.1.3:

procedure PROC_COMPLEX (CDU integer,SID integer) is

VAL_1 : integer;

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–65


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


VAL_2 : integer;

PATH_1 : varchar2(255); –– a pathname

TO_CDU : integer;

begin

select <att_1>,<att_2> from <agg_1>

into VAL_1, PATH_1


and F_SID = SID;

select <att_3>, <agg_2>.F_CDU_INTERNAL_VERSION

from <agg_2>, V_PATHNAME_SID_REL

into VAL_2, TO_CDU

where V_PATHNAME_SID_REL.F_INTERNAL_VERSION=

<agg_2>.F_CDU_INTERNAL_VERSION=

and V_PATHNAME_SID_REL.F_INTERNAL_VERSION =

<agg_2>.F_CDU_INTERNAL_VERSION

and V_PATHNAME_SID_REL.F_SID = <agg_2>.F_SID

and V_PATHNAME_SID_REL.PATHNAME = PATH_1;

if VAL_1 > VAL_2 then

CC_COMMON.REPORT_CHECK_BETWEEN_EIS_NOK

(SID, CDU,TO_CDU, ’<agg_1>’, ’<att_1>’, 1, VAL_1, VAL_2);

elsif VAL_1 = VAL_2

CC_COMMON.REPORT_CHECK_BETWEEN_EIS_NOK

(SID, CDU, TO_CDU,’<agg_1>’, ’<att_1>’, 2, VAL_1, VAL_2);

end if;

end PROC_COMPLEX;

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–66


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


13.7 CONSISTENCY CHECKER IN BATCH MODE

It is possible to start the consistency checker in batch mode.

Usage: $MDA_HOME/bin/sun5/consistency_checker <parameter_file>

<parameter_file> and “FileName” must be inclusive directory path.

The parameter file is a textfile and must have the following structure:

# CONSISTENCY CHECKER Parameter:## WARNING: This file is automatically generated.# Any changes you make here will be lost!## –––––––––––––––––# Output Device# –––––––––––––––––Screen: <True|False>PostProcessor: <True|False>File: <True|False>FileName: [if “File: True” : consistency checker output filename]# –––––––––––––––––# Configuration# –––––––––––––––––ElementConfiguration: <element configuration name>Mission: <mission name>SystemTreeVersion: <system tree version number>1CCU/CDU: <CCU_system_tree_path CCU_name | CDU_path>Version: <version.issue.revision>SubTree/EndItem: ConsistencyDate: # –––––––––––––––––# Check Selection# –––––––––––––––––# –––––––––––––––––CheckCategory:# –––––––––––––––––AdvisoryCautionError Warning# –––––––––––––––––CheckClasses:# –––––––––––––––––DependencyMandatoryReferential integrityUniqueness# –––––––––––––––––EndItemTypes:

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–67


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


# –––––––––––––––––%ALL%

Example for a parameter file:

# CONSISTENCY CHECKER Parameter: PROBE_1.0.0_29May2001_12:18:37.pmf## WARNING: This file is automatically generated.# Any changes you make here will be lost!## –––––––––––––––––# Output Device# –––––––––––––––––Screen: TruePostProcessor: FalseFile: FalseFileName: # –––––––––––––––––# Configuration# –––––––––––––––––ElementConfiguration: CC_TESTMission: DUMMY_MISSIONSystemTreeVersion: 1CCU/CDU: \CC_TEST PROBEVersion: 1.0.0SubTree/EndItem: ConsistencyDate:# –––––––––––––––––# Check Selection# –––––––––––––––––# –––––––––––––––––CheckCategory:# –––––––––––––––––Error WarningCautionAdvisory# –––––––––––––––––CheckClasses:# –––––––––––––––––DependencyMandatoryReferential integrityUniqueness# –––––––––––––––––EndItemTypes:# –––––––––––––––––

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–68


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


%ALL%

Attention: After execution of checks the consistency checker ($MDA_HOME/bin/sun5/consisten-cy_checker) does remove the parameter file.

If this parameter file shall be reused then it permissions must be changed:

chmod –w <parameter_file>

13–69

CGS–RIBRE–SUM–00032 03.07.2015– –13–69


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



14–8

CGS–RIBRE–SUM–00032 03.07.2015– –14–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


14 MAPPING

14.1 CGS MAPPING

This section explains the CGS Mapping and the conjunction of the mapping to the Aggregate Views and theWrite Procedures.

The usage of the MDA/MDB in the ground avionics environment requires that specific End–Item–Typesneeds to be supported that are special to the Test & Checkout and Simulation Facility. Above mentioned End–Item–Types are called the CGS Standard End–Item–Types or CGS Standard Aggregates (which make–upthe End–item types).

When using above mentioned ground facilities for e.g. Onboard Equipment check–out or O/B Softwarequalification the application that performs for example o/b data monitoring needs to know the structure anddata definition of the data to be monitored. On the other hand the ground facilities are using their own datastructure definitions, the already mentioned Standard End–Item–Types or Standard Aggregates. This raisesthe problem that the monitoring function needs to know, how the onboard data can be acquired and inter-preted still using the applications known (standard) data definitions.

Two solutions are possible and supported by the DADI–MA.

� The usage of the standard end–item–type definitions and aggregates for end–item–typeconstruction.

� The mapping of end–item–types definitions to ground facility standard end–item–typesdefinitions.

The mapping mechanism provided with the MDB makes arbitrary defined data structures look like standardCGS data structures. In other words, the original user data are transferred and presented in a manner thatenables the CGS tools to perform their work as intended.

If the following operational scenario will be considered:

� The user defined types have arbitrary structures.

� CGS compliant data structures are generated by a user written software which shall becalled CGS mapper.

two representations may exist in the MDB, original and CGS representations. Both representations shall beaccessible through one and the same pathname.

Figure 148. displays a user defined End–Item–Type which is a mixture of user defined aggregates and CGSstandard aggregates. The user End–Item–Type consists of 2 CGS standard aggregates and 3 user defined ag-gregates.

To create a CGS compliant data structure, the user defined aggregates usr_A3, usr_A4 and usr_A5 must bemapped to the CGS aggregate cgs_A5.

14–8

CGS–RIBRE–SUM–00032 03.07.2015– –14–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


cgs_A3

cgs_A2 cgs_A2

cgs_A5

cgs_A3

Type structure expectedUser defined

to be generated

usr_A3

usr_A4

usr_A5

End–Item–Type by CGS

CGS standardaggregates

User definedaggregates

Figure 148.User defined End–Item–Types with mixed Aggregates

Figure 149.displays a second possible structure of a user defined End–Item–Type. It is a type containing onlyuser defined aggregates without CGS standard aggregates. The user defined End–Item–Type consists of 5user defined aggregates.

To create a CGS compliant data structure, the user defined aggregates usr_A1 to usr_A5 must be mappedto the CGS aggregate cgs_A3, cgs_A2 and cgs_A5.

Both cases illustrate, that a transformation of the user defined data structure content to the CGS data struc-ture, is necessary. When the transformation has been finished, the CGS view is according to figure 150. and151.

It is possible to perform the transformation by a user written software, the CGS mapper. This software hasto use the Aggregate View and Write Procedure services, provided by MDA. A possible operational scenariois shown in figure 152. The user defined data structures will be read from the MDB by the CGS mapper usingthe Aggregate View service. All transformations are then performed by the CGS mapper and the results arewritten back to the MDB by the Write Procedure service.

14–8

CGS–RIBRE–SUM–00032 03.07.2015– –14–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


cgs_A2

cgs_A5

cgs_A3

usr_A3

usr_A4

usr_A5

usr_A1

usr_A2

to be generated

Type structure expectedUser definedEnd–Item–Type by CGS

CGS standardaggregates

User definedaggregates

Figure 149.User defined End–Item–Type with User defined Aggregates

cgs_A3

cgs_A2 cgs_A2

cgs_A5

cgs_A3

User_EIT_1

F1(x)

transformationalgorithm

usr_A3

usr_A4

usr_A5

CGS view of User_EIT_1after generation of cgs_A5

Figure 150.Transformation of a mixed User defined Data Structure

14–8

CGS–RIBRE–SUM–00032 03.07.2015– –14–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


cgs_A2

cgs_A5

cgs_A3

User_EIT_2 CGS view of User_EIT_2

F1(x)

transformationalgorithms

F2(x)

F3(x)usr_A3

usr_A4

usr_A5

usr_A1

usr_A2

after generation of cgs_A3,2 & 5

Figure 151.Transformation of a single User defined Data Structure

MDB

Master Database(central repository)

user–providedtransformation

S/W

generated data structure

CGS view

CGS Mapper

Usage ofWrite Procedures

Usage ofAggregateViews

Figure 152.Operational Mapping Scenario

14–8

CGS–RIBRE–SUM–00032 03.07.2015– –14–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


14.2 USER DEFINED MAPPING

I_MDB allows to start user defined mapping procedures for End–Items of a specific type. The mapping pro-cedure assignment to a type has been defined with DADI–MA. The user is responsible for the generationand correctness of the mapping procedure.

The mapping may be executed for End–Items within a CDU scope, or for End–Items within a CCU scope.All End–Items within the selected scope, which are assigned to the mapping type, will be mapped by the userdefined mapping procedure.

14.2.1 Mapping in a CDU scope

To perform the CDU mapping the following precondition has to be met:


To perform a CDU Mapping:

1. Navigate to the CDU Version window and select a CDU Version.

2. Execute Command–>Tools–>Mapping Procedure... to start the mapping process.

Figure 153.Initiating the CDU mapping procedure

After releasing the mapping procedure button, a message will be displayed: ’Tool has been startedin batch mode’.

14–8

CGS–RIBRE–SUM–00032 03.07.2015– –14–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


3. Press OK and wait until a text editor pops up.

The text editor displays all defined mapping procedures within the selected scope in the followingway:

EXECUTE <Mapping Package Name>.<Mapping Procedure Name>

If the mapping procedure is defined by DADI–MA, but not available within the specified directo-ry, or if there is an error within the mapping procedure, an oracle error will be raised.

Messages generated during run–time execution of the mapping procedures are displayed betweenthe lines

Start execution of Mapping Procedures ...and

End execution of Mapping Procedures

4. Quit the text editor to return to the I_MDB: CDU Versions window.

14.2.2 Mapping in a CCU scope

To perform the CCU mapping the following precondition has to be met:


To perform a CCU Mapping:

1. Navigate to the CCU Version window and select a CCU Version

2. Execute Command–>Tools–>Mapping Procedure... to start the mapping process

Figure 154.Initiating the CCU mapping procedure

14–8

CGS–RIBRE–SUM–00032 03.07.2015– –14–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


After releasing the mapping procedure button, a message will be displayed: ’Tool has been startedin batch mode’.

3. Press OK and wait until a text editor pops up.

The text editor displays all defined mapping procedures within the selected scope in the followingway:

EXECUTE <Mapping Package Name>.<Mapping Procedure Name>

If the mapping procedure is defined by DADI–MA, but not available within the specified directo-ry, or if there is an error within the mapping procedure, an oracle error will be raised.

Messages generated during run–time execution of the mapping procedures are displayed betweenthe lines

Start execution of Mapping Procedures ...and

End execution of Mapping Procedures

4. Quit the text editor to return to the I_MDB: CDU Versions window.

14–8

CGS–RIBRE–SUM–00032 03.07.2015– –14–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


29


15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15 MDA BATCH DATA ENTRY FACILITY

The MDA Batch Data Entry facility (BDE) is a tool that provides the capability of populating theMDB in batch mode. In contrast to interactive data–entry tools which allow end items to be enteredone at a time, BDE is is primarily intended for loading multiple end items, even across multipleCDUs, in one single batch job. It is particularly well suited for the transfer of mass data from foreigndatabases into the MDB via ASCII files.

The overall BDE functionality comprises two different task:

1. Loading and storing of end item aggregate data (section 15.1)

2. Creation and maintenance of user tree / end item nodes (section NO TAG)

15.1 BATCH DATA ENTRY AGGREGATE LOADING

15.1.1 General Overview of Aggregate Loading

In contrast to interactive data–entry tools which allow end items to be entered one at a time, this partof BDE is aggregate oriented and is primarily intended for loading multiple aggregates of multipleend items, even across multiple CDUs, in one single batch job.

BDE aggregate loading provides three operations to the user:

– LOAD

– STORE

– RESET.

These operations are triggered by the bde_load, bde_store, and bde_resetcommands, respectively. They are described in the forthcoming sections. A simplified overview ofBDE is shown in the diagram below.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


MDB

Data Files

Config. File

BDE

Log files

bde_loadbde_storebde_reset

target CU,input files list, etc. data dictionary info

user data validated user data

Activity Log

Error Logs

Figure 155.Simplified Overview of BDE

15.1.1.1 BDE Provided Operations

15.1.1.1.1 BDE LOAD Operation

The LOAD operation is logically the first to be executed. Its purpose is to read and validate theuser–submitted input data and place it in a temporary Load Area (also referred to as the TempMDB) for subsequent transfer into the actual MDB (see BDE STORE operation below, section15.1.1.1.2).

A more detailed list of activities performed by the LOAD operation follows.

� Check user’s authorization (must have CM privilege).

� Lock the Load Area for exclusive use by BDE. If the Load Area is already in use, amessage is written to the error log and the run aborted.

� Process the BDE job Configuration File, i.e. extract and validate the runtime parameters

� Load contents of data files into the Load Area. This is done by invoking the SQL*Load-er for each specified input data file

� Perform validation checks of loaded data at the field and aggregate levels

� Delete all records containing invalid data.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� Generate the BDE–LOAD related reports.

15.1.1.1.2 BDE STORE Operation

The STORE operation essentially performs the transfer of data from the Load Area into the se-lected target Configuration Unit of the MDB. It executes as one single (atomic) transaction, i.e.should any error occur, all changes are rolled back. Steps performed are:

� Login / connect to MDB and check user’s authorization (must have CM privilege).

� Check that specified target CU hasn’t been modified since the most recent LOAD op-eration.

� Check that the Load Area has been filled by the previous corresponding LOAD opera-tion.

� Copy the contents of the Load Area into the MDB. In case of errors, roll back allchanges

� Read and store the binary large data (which cannot be loaded by the SQL*Loader)

� Release the Load Area (make it available to other jobs /users)

Only data that have been successfully loaded into the load area can be transferred into the MDB.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.1.1.1.3 BDE RESET Operation

The RESET operation deletes all tables in the Temp MDB and resets all parameters used by BDE.This operation is provided for explicitly freeing shared MDA resources in the event of BDE /system malfunctions or abnormal termination. It essentially releases the Load Area making itavailable to other jobs/ users.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.1.2 BDE Input Files

15.1.2.1 BDE Batch Configuration File

The Configuration File is basically used to identify:

� the data Source: i.e. the files containing the data to be loaded

� the data Destination:Target MDB configuration (CDU / CCU) in which the data shall be ultimately stored,and the individual aggregates to be populated.

The general layout of the Configuration File is illustrated below.

� � �

Config File Header

<file–name> <aggreg–name> <id–type> {<item–ident>}<file–name>

<file–name>

# MISSION:# SYSTEMTREE_VERSION:# CU_TYPE:# CU_NAME:# CU_VERSION:

<mission><systree version><CU Type><CU Name><CU Version>

Config File Body<aggreg–name> <id–type> {<item–ident>}

<aggreg–name> <id–type> {<item–ident>}

Figure 156. General Structure of BDE Configuration File

15.1.2.1.1 Configuration File Format

As can be seen from the general structure in Fig. 156., the Configuration File consists of two parts:(1) a header identifying the target CU and (2) a body specifying the files and aggregates involved.

15.1.2.1.1.1 Configuration File Header

The header part of the Configuration File uniquely identifies the target (or destination) Configu-ration Unit. It consists of the following entries:

� Mission:Name of the Mission. This is a string of up to 16 characters.

� System Tree Version:The system tree version number is an integer of up to 3 digits.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� CU Type:The type of Configuration Unit which the data shall be loaded into. The CU typemust be either ’CDU’ or ’CCU’. In the latter case data may be loaded into any CDUwithin the scope of that particular CCU.

� CU Name:The name of the respective Configuration Unit. If it’s a CDU, it must be identified bythe pathname of its CDU node. In case of a CCU, both the configuration name andthe pathname of the associated system tree node must be specified. The configurationname is a string of up to 16 characters.

� CU Version:This is the Configuration Unit’s version identifier in the usual MDA notation (i.e.Version.Issue.Revision). If the Configuration Unit is a CDU, the Test Version numberand the MDB instance identifier must be additionally specified. The latter may notexceed 16 characters.

# MISSION: <Mission Name># SYSTEMTREE_VERSION: <Version number># CU_TYPE: CDU# CU_NAME: <Pathname of CDU node># CU_VERSION: <Version.Issue.Revision.Testver-sion {MDB–Instance}>

Figure 157. Configuration File Header with CDU as target configuration

# MISSION: <Mission Name># SYSTEMTREE_VERSION: <Version number># CU_TYPE: CCU# CU_NAME: [<Configuration name>]<Pathname of Systreenode># CU_VERSION: <Version.Issue.Revision>

Figure 158. Configuration File Header with CCU as target configuration

All header lines begin with a ’#’ , followed by the appropriate keywords (MISSION, SYSTEM-TREE_VERSION, etc.). Blanks and tabs can be inserted anywhere between or at the beginningof each line to make the text readable.

Actual values of Mission Name, Systemtree–Version, CU–Type, CU–Name, and CU–Versionhave to follow the colon. Again, blanks and tabs can be inserted between colon and values.

The specified target Configuration Unit must exist and must have the CM status ’review’ or ’de-velopment’.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Commentary lines (which have to start with a ’#’ too) can be inserted anywhere between the head-er lines, but are not allowed to contain any of the keywords (MISSION, SYSTEMTREE_VER-SION, etc.).

15.1.2.1.1.2 Configuration File Body (File/Aggregate Identification)

The Configuration File body identifies the various files and aggregates involved in the BDE joband defines the association between them, i.e. indicates which file shall be loaded into which ag-gregate.

There must be one entry in the Configuration File body for each file to be loaded. Each entry shallconsist of:

� Filename:Name of the user data file. It must be the file’s basename (i.e. without the directorypathname and the ”.dat” suffix)

� Aggregate name:Name of the aggregate to be filled with data from the file denoted by Filenameabove. The aggregate name must be in UPPER CASE.

� ID–Type:This parameter indicates the type of identifier used as record key inside the data fileto identify the respective MDB end–items. The identification may be made

· by pathname,

· by SID,

· by any user–defined foreign key

Accordingly, the specified value shall be: PATHNAME, SID, or <name of foreign keyaggregate>

� Item Identifier:The end–item identifier MUST BE specified if, and only if, the file contains unfor-matted data (e.g. a byte stream) to be loaded into a so–called ”large” aggregate. (seeLoading of Unformatted Large Data in section 15.1.2.2.2.2 below). Depending on the ID–Type parameter above, either the end item’s pathname, SID orforeign key shall be specified.

� EntryIncluded:The flag EntryIncluded must be specified if, and only if, the file contains unformatted”large” attribute combined with other attribute types. In the simplest case this attrib-ute is only the entry number (see Unformatted Large Data combined with other at-tribute types in section 15.1.2.2.2.3 below).

FILENAME<TAB>AGGREGATENAME<TAB>ID–TYPE[<TAB>ITEM–IDENTIFIER[<TAB>EntryIncluded]<CR>

Figure 159. Format of File / Aggregate specification in Configuration File body

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The delimiter between Filename, Aggregatename, ID–Type and Item Identifier must be a<TAB>. The line must be terminated by carriage return (<CR>)

The following constraints apply for the filnames and aggregates in the Configuration File

– The filenames must be unique within one Configuration File.

– For all so called ”none large” aggregates the aggragate names must be unique within oneConfiguration File.

– For all so called ”large” aggregates the aggragate names must not be unique within oneConfiguration File.

– Specified input file must exist and must not be empty.

– Specified aggregate must exist in the MDB Data Dictionary. Furthermore it must be validwith respect to the type of end–items involved, i.e. the specified aggregate must be part ofthe respective end–item’s definition.

15.1.2.1.1.3 Configuration File Examples

Example 1:

In this example (fig. 160.) the target configuration is ’test version’ No. 1 of CDU V0.0.0 at node:\EURECA\EGSE\TEST\ONBOARD. Three input files are specified, all of them containing formatteddata records in which the end–items are identified by PATHNAME.

# MISSION: DUMMY_MISSION

# SYSTEMTREE_VERSION: 6

# CU_TYPE: CDU

# CU_NAME: \EURECA\EGSE\TEST\ONBOARD

# CU_VERSION: 000.000.000.001 CGS_V3_1

coeff_file T_ANA_CAL_COEFFICIENTS PATHNAME

n_limits_file T_FLOAT_NOMINAL_LIMITS PATHNAME

d_limits_file T_FLOAT_DANGER_LIMITS PATHNAME

Figure 160. Configuration File Example (1)

Example 2:

Here the target configuration is a CCU named QUAL_TEST_9 which is located at systree node\APM\CGS_TEST\FLIGHT. The first input file contains formatted data in which the end items areidentified by SID, whereas the second file contains unformatted ”large” data to be loaded into theUCL end item: \APM\CGS_TEST\FLIGHT\UCL_SYSLIB.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


# MISSION: DUMMY_MISSION

# SYSTEMTREE_VERSION: 2# CU_TYPE: CCU

# CU_NAME: [QUAL_TEST_9]\APM\CGS_TEST\FLIGHT# CU_VERSION: 003.000.000

cal_curve T_ANALOG_POINT_PAIRS SID

lib_file T_UCL_SPECIFICATION_SOURCES PATHNAME \APM\CGS_TEST\FLIGHT\UCL_SYSLIB

Figure 161. Configuration File Example (2)

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.1.2.2 User Data Files

15.1.2.2.1 General input file set-up for BDE jobs

User Data Files

Batch Config. Filefile_a aggreg_xfile_b aggreg_y

file_n aggreg_z

Mission:SysTree:CU Type:CU Name:CU Version:

...

...

...

...

...

file_a

file_b

file_n

�

�

�

Figure 162.General input files set-up

BDE expects all records within a given file to belong to one and only one aggregate, thereforethe file/aggregate combinations shown in figure 163. are invalid.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


File A

aggregate X

aggregate Y

File C

aggregate X

aggregate X

File D

(continued)

One aggregate spread over multiple files !(File contains several aggregates)

This is INVALID !

Figure 163.Invalid file / aggregate combinations

15.1.2.2.2 Data File Format / Record Structure

15.1.2.2.2.1 Formatted ASCII Data Files

� Data must be provided in sequential files organized into logical records.

� For non–repeating (’single’) aggregates, the record structure is as follows:

· Field 1: End Item Identifier (Pathname, SID or foreign key)

· Field 2 .. N: Data fields (of which at least one must be provided).

In this case, Field 1 is the unique record key.

� For repeating aggregates, the record structure must be as follows:

· Field 1: End Item Identifier (Pathname, SID or foreign key)

· Field 2: Sequence number (Entry Number)

· Field 3 .. N: Data fields (of which at least one must be provided).

Fields 1 and 2 taken together represent the record key which must be unique.

The general data record structure is shown below.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


IDENTIFIER<TAB>VALUE1<TAB>VALUE2<TAB>[... VA-LUEn]<CR>

IDENTIFIER<TAB>SEQNO<TAB>VALUE1<TAB>[... VA-LUEn]<CR>

a) Record structure for single aggregate:

a) Record structure for repeating aggregate:

Figure 164. Record Structure of BDE Input Data File

In the above figure, the meaning of the IDENTIFIER, SEQNO and VALUE fields is as follows:

– IDENTIFIER :This is the end item identifier. It must be either the Pathname, the SID or the item’s foreignkey (Requirement_PUI, Signal_PUI, etc. ). Further it must be unique within the specifiedConfiguration Unit. Its maximum length is 255 characters.

– SEQNO:This field applies to repeating aggregates only. This is the record’s sequence number withinthe particular repeating aggregate. Sequence numbers must be in 1–increment ascendingorder and must start with 1 (i.e. 1, 2, 3, ...)

– VALUE1 ..n:Actual data values.

Notes:

� Individual fields must be separated by a <TAB> character. The end of a record charactermust be a carriage return (<CR>). There must be no <TAB> between the last value andthe end–of–record character.

� Data fields must be in the same order as the corresponding attributes in the pertinentLoader Control File. To find out the right order, display or print the file correspondingto the aggregate of interest. BDE Loader Control Files have the extension ”.ctl” and canbe found in:

$MDA_HOME/config/mdb/install/dadi_export/bde_control_files

� String fields must be enclosed in double quotes unless the string consists of one wordand doesn’t contain any special character.

� Missing fields must be indicated by one <@> character. BDE will supply default valuesfor missing attribute values.

Note: Not all MDB aggregates may be loaded via BDE. Certain special–purpose aggregatesare reserved for MDA internal use and must be populated by other means. These aggregates are flagged as such in the MDB Data Dictionary (MDA_SPECIAL_USAGEflag)

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Loader Control File: T_FLOAT_NOMINAL_LIMITS.ctl

LOAD DATAREPLACEINTO TABLE T_FLOAT_NOMINAL_LIMITSFIELDS TERMINATED BY whitespace OPTIONALLY ENCLOSED BY ’”’TRAILING NULLCOLS (F_ID ,F_ENTRY_NUMBER ,F_NOMINAL_HIGH_LIMIT NULLIF( F_NOMINAL_HIGH_LIMIT =’@’) ,F_NOMINAL_HIGH_MESSAGE NULLIF( F_NOMINAL_HIGH_MESSAGE =’@’) ,F_NOMINAL_HIGH_ACTION NULLIF( F_NOMINAL_HIGH_ACTION =’@’) ,F_NOMINAL_LOW_LIMIT NULLIF( F_NOMINAL_LOW_LIMIT =’@’) ,F_NOMINAL_LOW_MESSAGE NULLIF( F_NOMINAL_LOW_MESSAGE =’@’) ,F_NOMINAL_LOW_ACTION NULLIF( F_NOMINAL_LOW_ACTION =’@’) ,F_NOMINAL_DELTA_LIMIT NULLIF( F_NOMINAL_DELTA_LIMIT =’@’) ,F_NOMINAL_DELTA_MESSAGE NULLIF( F_NOMINAL_DELTA_MESSAGE =’@’) ,F_NOMINAL_DELTA_ACTION NULLIF( F_NOMINAL_DELTA_ACTION =’@’) )

\AAA 1 100.0 \MSG1_H \ACTION1_H 5.0 \MSG1_L \ACTION1_L 2.0 \MSG1_D \ACTION1_D



\BBB 1 100.0 \MSG1_H \ACTION1_H 5.0 \MSG1_L \ACTION1_L 2.0 \MSG1_D \ACTION1_D



... ... ... ... ... ... ... ... ... ... ...

\NNN 1 100.0 \MSG1_H \ACTION1_H 5.0 \MSG1_L \ACTION1_L 2.0 \MSG1_D \ACTION1_D



Sample data file:

Item pathnameSeq–no

Data Fields

Figure 165.Loader Control File and corresponding data file (example)

15.1.2.2.2.2 Unformatted Large Data (Streams)

In the MDB, unformatted large data (ULD) are stored in special aggregates consisting of attrib-utes of type LONG CHAR or LONG RAW.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


ULD files may contain binary data (e.g. object code, bitmaps, libraries), text or both. Each ULDfile must be associated with one and only one MDB end–item; the association is defined throughthe Configuration File.

15.1.2.2.2.3 Unformatted Large Data combined with other attribute types

In special cases, like T_CSS_FB_IO_MDE_INFOS, the attribute of type ”LONG” or ”LONGRAW” is combined with attributes of other types, e.g. a SUBITEM_ID of type ”NUMBER”. Itis also allowed that the aggregate contains one large attribute and no attribute of a non large type.The size of the single MDB chunks may be less than 64 KB, i.e. the data of the chunks cannotbe appended. They have to be restored to the originally format. In this case the format of the aggre-gate file is as follows:

ENTRY NO.<TAB>VALUE1<TAB>[... VALUEm]<TAB>LENGTH OF

LONG DATA IN BYTES<CR>

BYTE1BYTE2...BYTEk<CR>

VALUEm+2<TAB>[... VALUEn]<CR>

a) Record structure for aggregates contraining long data as well as non–long data:

with n as the number all attributes, m<n-1 and k as the length of the long data in bytes

ENTRY NO.<TAB>LENGTH OF LONG DATA IN BYTES<CR>

BYTE1BYTE2...BYTEk<CR>

b) Record structure for aggregates contraining only long data with included entry no:

Please note that there may only be one attribute of type ”LONG” or ”LONG RAW” within onetable. This is a restriction of ORACLE.

15.1.2.2.3 MDA Data Types supported by BDE

User input data may include any MDA supported data type subject to the range and format restric-tions stated below.

MDA data type Format / Range Constraints

- STRING any sequence of ASCII characters, up to 255 chars long.

- INTEGER signed integer in range:–2147483648 to 2147483647

- SINGLE FLOAT Floating point number in the range:–3.40282E+38 to 3.40282E+38(precision: up to 6 digits after the decimal point)

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–15


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


- DOUBLE FLOAT Floating point number in the range:–1.79769313486231E+308 to 1.79769313486231E+308

(precision: up to 15 digits after the decimal point)

- BITSET 32–character string of 1 and 0.

- HEXADECIMAL String of hexadecimal characters (i.e. 0 .. 9, and A .. F)up to 255 chars long. Only upper–case characters allowed.

- ENUMERATION String constant taken from an attribute–specific list ofpredefined values

- PATHNAME Special kind of string (a sequence of MDB node names delimited by ”\”) used to identify an MDB item.

A node name may be any combination of letters, digits andunderscore characters. Only upper–case characters allowed.

- RAW byte stream (up to 255 bytes long)

- LONG CHAR character stream (up to 64KB bytes long).

- LONG RAW byte stream (up to 64KB bytes long)

- DATE character string with following format: ”DD–MON–YYYY HH:MI:SS”

Notes:

• All data types, except LONG RAW, must be loaded in character (ASCII) format. LONGRAW data must be loaded in binary (8–bit byte) format.

• FLOAT data may be provided in usual decimal form or in scientific (exponential) form.

15.1.3 BDE Output Files

15.1.3.1 BDE Reports

The reports (log files) generated by BDE are created in the directory $HOME/bde/reports .Those generated by the Oracle’s SQL*Loader utility (which is invoked by BDE when loadingformatted ASCII records) are located in the directory:$HOME/bde/reports/sqlloader

15.1.3.1.1 BDE Load Operation Report

The BDE Load Operation Report (activity log) contains information about:

– the BDE version, the BDE user, the date and time of invocation

– contents of the job’s Configuration File,

– job’s statistics (number of records processed, number of errors)

– a reference to the SQL*Loader log files.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–16


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


An example is included in appendix E.

15.1.3.1.2 BDE Load Error Report

The BDE Data Error Report contains detailed information about the data errors (if any) detectedby the BDE Data Checker during the Load operation. See example in appendix E.

15.1.3.1.3 BDE Store Operation Report

This report contains information about the outcome of the Store operation. An example is in-cluded in appendix E.

15.1.3.1.4 Oracle’s SQL*Loader Reports

As mentioned earlier, Oracle’s SQL*Loader log files are placed in the directory$HOME/bde/reports/sqlloader which is, in turn, divided into 3 subdirectories:log, dsc, and bad . Refer to section 15.1.4.1.2. For more information, consult theSQL*Loader Reference Guide, Oracle Part–No. 3606–v1.0.

Examples of these reports are also shown in appendix E.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–17


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.1.4 Using BDE

15.1.4.1 Prerequisites

15.1.4.1.1 BDE User Account

The BDE user must have the CONFIGURATION MANAGER privilege for the MDB he / sheis working on. Disk quotas, if assigned, must be large enough to accommodate the storage of alllog files generated during BDE execution.

15.1.4.1.2 BDE User’s Home Directory Structure

BDE expects the user’s home directory to be structured as described below.(Note: the required directories may be created ”manually” by the system administrator or by theuser – if not already done as part of the MDA installation)

user’s home directory

Used by SQL*Loader

$HOME

requireddirectories

Figure 166. Required Home Directory structure

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–18


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


As can be seen from the above figure, the BDE user’s home directory must contain a ”bde” subdi-rectory. The latter is further subdivided into 2 directories, one for input to BDE, and the other forthe generated output files. The following directories are therefore required under $HOME/bde:

� input

This directory must contain the Configuration File and the input data files.

� reports

This directory contains the log files generated during BDE execution, i.e.:

– the so–called activity logs (files bde_load_activity.log, bde_store_activity.log)

– the Data Error report (file bde_load_error.log )

– all files generated by the SQL*Loader utility. These are grouped into the ”sqlloader” subdirectory which, in turn, consists of thefollowing subdirectories:

· sqlloader/badThis directory is used by the SQL*Loader to report ”bad” data, i.e. datathat could not be loaded. The generated files have the same names as thecorresponding input files but with the extension ”.bad”.

· sqlloader/disThis directory is used by the SQL*Loader to report ”discarded” data. Thegenerated files have the same names as the corresponding input files butwith the extension ”.dsc”.

· sqlloader/log

This directory is used by the SQL*Loader to report general loader activi-ties. The generated files have the same names as the corresponding inputfiles but with the extension ”.log”.

15.1.4.1.3 BDE Runtime Options

BDE uses the following environment variables at runtime.

� Configuration File Variable

The current BDE Configuration File must be specified through the environment variableBDE_CFG. The default setting is:

BDE_CFG $HOME/bde/input/batch_config.dat.

It can be changed by entering

setenv BDE_CFG any_directory/name_of_batch_configuration_file

either interactively or in the user’s $HOME/.user/cshrc shell script. Due to the fact that datafileshave to reside in the same directory as the config file, a change of the directory does also affectthe location of the datafiles.

� Error Limit Variable

The desired maximum number of errors may be controlled via the environment variable BDE_ERROR_LIMIT. By default, it is set to:

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–19


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


BDE_ERROR_LIMIT 1000

This means that the BDE Data Checker will stop processing an input file in which more than thespecified number of errors are detected

The desired value can be entered using:

setenv BDE_ERROR_LIMIT max–number–of–errors

either interactively or in the user’s $HOME/.user/cshrc shell script.

15.1.4.2 BDE Job Preparation and Execution

15.1.4.2.1 Operational Phases

The overall process of loading data using BDE is typically performed in three phases:

� Preparation Phase

� Load & Validation Phase

� Final Storage Phase

These are summarized in figure 167. below.

Set up bde_load bde_store

Copy data into load directoryVerify format of data–file(s)Check existence of end–itemsCreate config file(s)

Issue bde_load commandCheck log files for errors

Issue bde_store commandCheck log files for errorsCheck loaded data in MDB

In case of errors return toPreparation Phase

Preparation Load & Validation Final Storage

Preparation PhaseIn case of errors return to

MDB & data files

Figure 167. BDE Operational Phases

Details of activities performed in each of these phases are given in figures 168., 169., and 170.,respectively.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–20


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


TapeDisc

Net-work

Is the file formatfor the data file

O.K.?

Modify format

Are all end itemsdefined and

O.K? (*)

(*)

aggregates are defined?End Items and associated

Clarify inconsistenciesbetween DADI definitionand loadable data

Are all end itemsdefined in the

MDB ?

Create end items for selected CCU/CDU

Create batchconfiguration file

of datafileNO

NO

NO

YES

YES

YES

Execute BDE_LOAD

Copy all data files to be loadedinto the BDE input directory.

Use

r D

ata

File

Ana

lysi

s

BD

E P

repa

ratio

n P

hase

Start

Figure 168.BDE Preparation Phase

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–21


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Execute BDE_LOAD

BDE LoadOperation

O.K?

NO

Check bde_load_activity.log

Check bde_load_errors.log

Is there

loaded into MDBany data to be

Execute BDE_RESET toclean up the load area

Modify the input files (data file,batch–config) to correct the error

Execute BDE_STORE

NO

YES

YES

BDEPreparation

Phase

BD

E L

oad

Pha

se

Check SQL*Loader Reports

Figure 169.BDE Load Phase

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–22


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Execute BDE_STORE

BDE STOREOperation

O.K?

NO

Check bde_store_activity.log

Copy BDE log files for

YES

archiving purposes

Print log files fordocumentation Purposes

Finish

Contact your local

Problem due toData Errors?

NO

BDE_LOAD

YES

System or Database Administrator

BD

E F

inal

Sto

rage

ExecuteBDE_RESET

Phase

Figure 170.BDE Storage Phase

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–23


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.1.4.2.2 BDE Execution Summary and Return Codes

As already mentioned, the following commands are available to the user at the Unix command–line level:

– bde_load This is logically the first command to be executed. It causes the contents of the all input datafiles (identified in the Configuration File) to be written into a temporary Load Area wherethey are checked for validity. Invalid data records are reported in log files and deleted(deletion ensures that only valid data is copied into the MDB by a subsequent bde_storeoperation)

– bde_store This command must be issued after bde_load. It transfers the contents of the Load Areainto the selected target Configuration Unit of the MDB. It executes as one single (atomic)transaction, i.e. should any error occur during the store operation, all entries or changes madeso far to the MDB are ”undone”, i.e. the transaction is rolled back.

– bde_reset Releases the Load Area making it available to other jobs/ users.

The full Unix pathnames for these commands are: $MDA_HOME/bin/common/bde_load,$MDA_HOME/bin/common/bde_store , and$MDA_HOME/bin/common/bde_reset , respectively.

Summarized execution flow

The context in which BDE commands are issued and the overall execution flow are summarizedbelow (also see Operational Phases in above section 15.1.4.2.1.).

• Verify BDE environment (input/output directories, environment variables); in partic-ular, set the environment variable BDE_CFG as the desired Configuration File.

• Create all required end–item nodes in the MDB

• Prepare / edit job input files (Configuration File and user data files)

• Issue bde_load command

• Check for possible errors in log files bde_load_activity.log andbde_load_errors.log if the exit status is not 0. In case of errors, repeat the abovesteps until the bde_load command completes successfully.

• Invoke bde_store

• Check file bde_store_activity.log for possible errors if the exit status is not0.. In case of errors, go back to ”Prepare / edit job input files”

• Invoke bde_reset

Upon successful completion (i.e. no errors detected), the BDE commands exit with a status codeof 0; otherwise a non–zero status code is returned to the caller (see table below)

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–24


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Return Code

0

2

3

4

42

Description

Returned by

BDE BDEStoreLoad

BDEReset

No error

SQL or data error

BDE environment error

BDE configuration file notfound or empty or erroneous

Exception error

X

X

X

X

X X X

X X

XX

Figure 171. BDE Return Codes

The following pages show two simple UNIX shell scripts illustrating the use of BDE commands.Sample BDE runs are provided in Appendix E.

15.1.4.2.3 BDE Usage Examples

#!/bin/sh # **********************************************************************# Unix shell script example showing multiple BDE jobs submissions# **********************************************************************# Set environment variable BDE_CFG for first job:setenv BDE_CFG $HOME/bde/input/config_1.dat# Issue bde_load command:$MDA_HOME/bin/common/bde_loadcase $? in # check bde_load return code

0) $MDA_HOME/bin/common/bde_store# Load was successful, issue store command to transfer # the data from the load area into the MDB

case $? in # check bde_store return code0) $MDA_HOME/bin/common/bde_reset# Store was successful, issue bde_reset to release and# clean up the load areacase $? in # check return code

0) exit;3) {write appropriate entry in log file} # Failure in BDE environment exit;42) {write appropriate entry in log file} exit;

esac;3) {write appropriate entry in log file} # Failure in BDE environment exit;

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–25


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


42) {write appropriate entry in log file} exit;

esac;2) {write appropriate entry in log file} # SQL or data error exit;3) {write appropriate entry in log fil e} # Failure in BDE environment exit;4) {write appropriate entry in log file} # Failure in BDE configuration file exit;42) {write appropriate entry in log file} exit;

esac;## Set environment variable BDE_CFG for next job:setenv BDE_CFG $HOME/bde/input/config_2.dat# start bde_load with new configuration file$MDA_HOME/bin/common/bde_load#check the return status case $? in........( same as for first load)esac;...# doneexit;

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–26


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


#!/bin/csh# **********************************************************************# A C–shell example# **********************************************************************

$MDA_HOME/bin/common/bde_loadset load_status = $statusif ($load_status == 0) then

echo ”BDE load performed successfully”

$MDA_HOME/bin/common/bde_storeset store_status = $statusif ($store_status == 0) then

echo ”BDE Store performed successfully”elseecho ”BDE store failed”

echo ” Status = $store_status ”echo ”Check bde_store_activity.log and/or bde_store_errors.log”

endifelse

echo ”BDE load failed”echo ” Status = $load_status”echo ”Check bde_load_activity.log and/or bde_load_errors.log”

endif

$MDA_HOME/bin/common/bde_resetif ($status != 0) echo ”BDE reset failed”

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–27


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.1.4.3 Summary of Constraints

The following general constraints apply to the Batch Data Entry facility:

Pathname References

When loading aggregates having pathname attributes, BDE does not check that the referencedend items actually exists in the specified MDB configuration.

Overwriting Data in MDB

The bde_store command overwrites previously existing end–item data without prior notifica-tion.

CU changes between LOAD and STORE

The bde_store command executes successfully only if the contents of the specified CU–ver-sion has not been changed since the previous bde_load command.

Privileges

Only user with MDB Configuration Manager privilege are allowed to use BDE.

Rounded values

When a float value is loaded into a field of type integer, the specified value is rounded to the near-est integer. For example, 3.4 becomes 3 and 3.6 becomes 4.

Case of Pathnames and Aggregate Names

Pathnames and aggregate names must be in UPPER CASE.

Maximum Number of Errors

– For the Oracle SQL–Loader, the max. number of errors is set to 50 per aggregate.

– For the BDE Load operation, the max. number of errors is set to 1000.

Filenames

– All BDE input files, including the job Configuration File, must have the extension ”.dat”. (Inside the Configuration File, however, file specifications must be without the ”.dat” suffix)

– The filenames may not contain any ”.” (dot) character, except the one used in the ”.dat”extension. For example, the file named: xxx . yyy . dat is an invalid BDE input file.

Maximum Number of Entries per Aggregate

The maximum numbers of entries in a repeating aggregate is limited to 9999.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–28


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.1.5 BDE Error Messages

15.1.5.1 Overview

System errors

Error–No Error–Category Error–Message

3001 SYSTEM_ERROR ”MDB_ERROR: Fatal MDA Error!”

3002 SYSTEM_ERROR ”ORACLE_ERROR: Fatal Oracle Error!”

3003 SYSTEM_ERROR ”AUTHORIZATION_ERROR: User has no oracle account”

3004 SYSTEM_ERROR ”AUTHORIZATION_ERROR: User is not registered as MDA user”

3005 SYSTEM_ERROR ”AUTHORIZATION_ERROR: CM privilege is necessary for BDE”

3006 SYSTEM_ERROR ”AUTHORIZATION_ERROR: Locked by another user”

3007 SYSTEM_ERROR ”MDB_ERROR: TEMP_MDB account not found”

3008 SYSTEM_ERROR ”MDB_ERROR: Invalid CU Type in LOCKED_FOR parameter”

3009 SYSTEM_ERROR ”MDB_ERROR: Invalid CU Type in LOCKED_BY parameter”

Usage errorsError–No Error–Category Error–Message

3102 USER_ERROR ”Invalid Header Format in Configuration File”

3103 USER_ERROR ”Invalid Identifier Type in Configuration File”

3104 USER_ERROR ”CU Version is FROZEN”

3105 USER_ERROR ”Invalid CU type”

3106 USER_ERROR ”Invalid Mission, Systemtree Version or Element Configuration”

3107 USER_ERROR ”Invalid CCU Version”

3108 USER_ERROR ”Invalid CDU Version”

3109 USER_ERROR ”Batch Configuration File not found”

3110 USER_ERROR ”No BDE_Load operation was performed before”

3111 USER_ERROR ”BDE_LOAD operation was performed by another user”

3112 USER_ERROR ”Locked by another tool”

3113 USER_ERROR ”CU Version has been changed after BDE_LOAD run”

3114 USER_ERROR ”File doesn’t exist”

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–29


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Data Errors


3201 DATA_ERROR ”INTEGER value out of range”

3202 DATA_ERROR ”SINGLE–FLOAT value out of range”

3203 DATA_ERROR ”DOUBLE–FLOAT value out of range”

3204 DATA_ERROR ”Invalid FLOAT format”

3205 DATA_ERROR ”Invalid HEXADECIMAL format”

3206 DATA_ERROR ”Invalid BITSET format”

3207 DATA_ERROR ”Invalid PATHNAME syntax”

3208 DATA_ERROR ”Invalid ENUMERATION value”

3209 DATA_ERROR ”Missing value”

3210 DATA_ERROR ”Invalid data type”

3211 DATA_ERROR ”String not properly terminated (or TAB in string)”

3212 DATA_ERROR ”Duplicate sequence number”

3213 DATA_ERROR “Aggregate contains only NULL values”

3214 DATA_ERROR “Invalid variant aggregate record”

3215 DATA_ERROR “Invalid foreign key”

Item Identifier Errors


3301 DATA_ERROR ”Entries out of sequence”

3302 DATA_ERROR ”Invalid Sequence Number (first entry must be #1)”

3303 DATA_ERROR ”Too few records in aggregate”

3304 DATA_ERROR ”Too many records in aggregate”

3305 DATA_ERROR ”Multiple occurrence of item key in SINGLE aggregate”

3306 DATA_ERROR ”End Item doesn’t exist in selected CU Version”

3307 DATA_ERROR ”End Item in frozen CDU Version”

3308 DATA_ERROR ”Multiple occurrence of Item Key in CU Version”

3309 DATA_ERROR ”Table (aggregate) not defined for this type of end item”

3310 DATA_ERROR ”Aggregate is restricted in CDU version”

15.1.5.2 System Errors

Errors belonging to that category are usually due to MDA–internal problems or system malfunc-tions that are not related to the user–submitted input data. These errors should be reported to theDBA or System Administrator.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–30


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.1.5.3 Usage Errors

These errors generally result from an incorrect use of BDE. The corresponding error messagesare, for the most part, self–explanatory. In the event of such an error:

– Check the Activity Log for details, and correct the error

– Rerun the job.

15.1.5.4 Data Errors / Item Identifier Errors

These errors are issued by the BDE Data Checker as a result of validation checks performed onthe user data. For each message, the error code and the message text are listed together with a briefexplanation. These error messages will appear in the Data Error Report generated at the end ofeach LOAD run (whenever errors have been detected). Note that error messages issued byOracle’s SQL*Loader – which can be found in separate log files – are documented in the Oracle’sUtilities User’s Guide. In all the cases listed below, the action to be taken by the user is the same:

– Check format, syntax, or range of the specified field in the specified input file (use the re-ported record key and column number as reference) and correct the error as necessary.

– Rerun the job.

Error messages and their explanations follow.

• Error code 3201: INTEGER value out of range

Value of the specified field (which is of type integer) is outside the range defined in the Data Dic-tionary.

• Error code 3202: SINGLE–FLOAT value out of range

Value of the specified field (which is of type single float) is outside the range defined in the DataDictionary.

• Error code 3203: DOUBLE–FLOAT value out of range

Value of the specified field (which is of type double float) is outside the range defined in the DataDictionary.

• Error code 3204: Invalid FLOAT format

Specified field doesn’t fulfil MDA’s float format specifications.

• Error code 3205: Invalid HEXADECIMAL format

Specified field doesn’t fulfil MDA’s hexadecimal format specifications.

• Error code 3206: Invalid BITSET format

• Specified field doesn’t fulfil MDA’s bitset format specifications.

• Error code 3207: Invalid PATHNAME syntax

Specified field doesn’t fulfil MDA’s pathname syntax specifications.

• Error code 3208: Invalid ENUMERATION value

Value of the specified field (which is of type enumeration) was not found in the list of allowedvalues for that particular field.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–31


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


• Error code 3209: Missing value

A value for one of the attributes is missing in the datafile

• Error code 3210: Invalid data type

A value supplied by the datafile is of type STRING where an attribute type other than string isrequested.

• Error code 3211: String not properly terminated (or TAB in string)

A STRING value supplied by the datafile has no closing quotation marks of contains a TAB.

• Error code 3212: Duplicate sequence number

The datafile contains more than onde entry with the same sequence number.

• Error code 3213: Aggregate contains only NULL values

The Aggregate contains only NULL values.

• Error code 3214: Invalid variant aggregate record

The variant aggregate record is invalid in composite aggregate.

• Error code 3215: Invalid foreign key

The foreign key aggregate record is invalid in composite aggregate.

• Error code 3301: Entries out of sequence

The records in the specified repeating aggregate are not in the proper sequence(sequence numbers must be in ascending order and with a sequence step of 1)

• Error code 3302: Invalid ENTRY NUMBER (first entry must be #1)

The first record in the specified repeating aggregate must have the sequence number 1.

• Error code 3303: Too few records in aggregate

The number of records that were loaded is less than the required minimum for the specified re-peating aggregate.

• Error code 3304: Too many records in aggregate

The required maximum number of records for the specified repeating aggregate has been exceed-ed.

• Error code 3305: Multiple occurrence of item key in SINGLE aggregate

Two or more records associated with the specified non–repeating aggregate have the same recordkey (pathname identifier).

• Error code 3309: Table (aggregate) not defined for this type of end item

The type definition of the end item indicated in the user data file does not contain the aggregatespecified in the Configuration File.

• Error code 3310: Aggregate is restricted in CDU version

The aggregate is restricted for the specified item type in restricted CDU version.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–32


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.1.5.5 Other Errors (system / programming errors, exceptions, etc.)

Error messages of this kind refer to abnormal conditions, internal problems or inconsistencieswhich result in the run being aborted. These error messages will appear in the Activity Log. Theyshould be reported, depending on the case, to either the Database or SW Maintenance personnel.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–33


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.2 BATCH DATA ENTRY CREATE END ITEM

15.2.1 General Description of the BDE_CEI

BDE_CEI is a tool that provides operations for loading the type specific data of an end item intothe mission database. A functional overview of BDE_CEI is best given by describing the threeoperations it provides to the user, namely:

� LOAD

� STORE

� RESET.

These operations are triggered by the

� bde_cei_load,

� bde_cei_store,

� bde_cei_reset

commands, respectively. A detailed description of bde_cei_load, bde_cei_store and bde_cei_re-set is provided in the following sections of this manual. A simplified overview of BDE_CEI isgiven in figure NO TAG

MDB

Data File

Config. File

BDE_

Log files

bde_cei_loadbde_cei_storebde_cei_reset

target CU,input files list, etc. data dictionary info


Activity Log

Error Logs

CEI

Figure 172. Simplified Overview of BDE_CEI

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–34


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.2.2 BDE_CEI Provided Operations

15.2.2.1 BDE_CEI_LOAD

The bde_cei_load operation is logically the first to be executed. Its purpose is to read and validatethe user–submitted CEI activities and place it in a temporary Load Area (also referred to as the.result–file) for the subsequent commit of the End Item Creation within the actual MDB (see op-eration bde_cei_store, section NO TAG).

A more detailed list of activities performed by the LOAD operation follows.

� Check user’s authorization (must have CM privilege).

� Lock the Load Area file for exclusive use by BDE_CEI. If the Load Area file is alreadyin use, a message is written to the error log and the run aborted.

� Process the BDE_CEI Configuration File, i.e. extract and validate the runtime parameters

� Perform validation checks of loaded data at the field and aggregate levels

� Generate the bde_cei_load related reports containing in particular the activities of CEI.

The BDE_CEI_LOAD works with his own sid–range in the temporary database field.

15.2.2.2 BDE_CEI_STORE

This operation essentially performs the end item creation and update within selected target Con-figuration Unit of the MDB. It executes as one transaction. If any error occurs, all changes arerolled back. Steps performed are:

� Login / connect to MDB and check user’s authorization (must have CM privilege).

� Check that the Load Area has been filled by the previous corresponding LOAD operation.

� Creation and update of end items. In case of errors, roll back all changes.

15.2.2.3 BDE_CEI_RESET

bde_cei_reset deletes all log files and the Load Area File and resets all parameters used byBDE_CEI.

This operation explicitly frees shared (MDA) resources and the bde_cei_report–files in case theresults of the bde_cei_load operation (listed in the bde_cei_load_activity.log file) are not the ex-pected and not acceptable. In addition this operation can be used in case of BDE_CEI / systemmalfunctions or abnormal termination. It essentially releases the Load Area making it availableto other jobs/ users.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–35


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.2.3 BDE_CEI Input Files

15.2.4 BDE_CEI Batch Configuration File

The BDE_CEI uses the standard BDE batch config file.

Note, that only the Data Destination, i.e. the target CU identification is used for BDE_CEI. Pleaserefer to the section of the BDE Batch Config File for aggregate loading (section 15.1.2.1).

15.2.5 User Data Files

15.2.5.1 General input file set-up for BDE_CEI jobs

The input files which have to be available for BDE_CEI are:

• the BDE config file

• the BDE_CEI data file

The BDE config file is used as the BDE_CEI config file.

Batch Config. File

� � �

<file–name> <aggreg–name><file–name> <aggreg–name>

<file–name> <aggreg–name>

Mission:SysTree:CU Type:CU Name:CU Version:

One End Item $BDE_CFG.cei

$BDE_CFG

Figure 173.General input file set-up

The BDE_CEI data file contains all end items to be created and updated within the MDB. Thefile name is specified by the environment variable $BDE_CFG plus the extension <.cei>.

Each end item is represented in three lines of the file with the following structure:

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–36


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


• Line 1: pathname

• Line 2: type <tab> owner <tab> CI–number

• Line 3: description

That composition of and end item is mandatory, but the attributes of line 2 can be skipped(<tab><tab>).

Data Type Format /Range Constraint

pathname string up to 255 char long

type string up to 40 char long

owner string up to 30 char long

CI–number string up to 10 char long

description string up to 80 char long

An example is given below:

\EURECA\EGSE\TEST\BDE_CEI_TEST\DEPLOY_ENABLED

EGSE_INTEGER_SW_VARIABLE OPS$THPAETZ 123

create EI with only new end item; Type with single and multi record

15.2.6 BDE_CEI Output Files

15.2.6.1 BDE_CEI Reports

15.2.6.1.1 BDE_CEI Load Operation Report

• The BDE_CEI Load Operation Report (activity log) contains information about:

– the BDE_CEI version, the BDE_CEI user, the date and time of invocation

– the batch configuration file,

– the number of created / updated / rejected end items.

The report is placed in the report directory $HOME/bde/reports as bde_cei_load_activity.log.

• The BDE_CEI Load Area File (result) as the output of the load operation and the input forthe store operation contains information for each end item if

– it already exists, i.e. it shall be updated, or it can be created

– all parameter for end item creation as input of the bde_cei_store.

The report is placed in the report directory $HOME/bde/reports as .bde_cei_load_result. The filecan be used for low level debugging however, the user may not alter this file.

15.2.6.1.2 BDE_CEI Load Error Report

The BDE_CEI Load Error Report contains detailed information about the errors occurred duringbde_cei_load operation in particular:

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–37


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


• MDB connection privilege errors,

• the pathname of the rejected end item and

• the related error message.

The report is placed in the report directory $HOME/bde/reports as bde_cei_load_error.log.

15.2.6.1.3 BDE_CEI Store Operation Report

The BDE_CEI Store Operation Report, or so called activity report, contains information about

• the BDE_CEI version, the BDE_CEI user, the date and time of invocation,

• the error messages in case store errors occur (the pathname of the rejected end item and therelated error message),

• the number of created / updated end items.

The report is placed in the report directory $HOME/bde/reports as bde_cei_store_activity.log.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–38


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.2.7 Using BDE_CEI

15.2.7.1 Prerequisites

15.2.7.1.1 BDE_CEI User account attributes

The user using BDE_CEI, must have the CONFIGURATION MANAGER privilege for theMDB he is working on.

If disk quotas are set for the computer system where MDA is installed, the user using BDE_CEImust have sufficient disk quotas.

15.2.7.1.2 Configure the users directory structure

The BDE_CEI user’s home directory must have the following structure. This must be set up afterinstalling the BDE_CEI software by the system administrator or by the user.

This structure is the same as the normal BDE directory structure.

users home directory

BDE_CEI required directory structure

Figure 174.Required BDE_CEI directory structure

15.2.7.1.2.1 Directory ”input”

It’s recommended but not necessary that this directory contains the batch configuration andthe data files.

15.2.7.1.2.2 Directory ”report”

In this directory the following reports are stored after invocation of BDE_CEI:

� BDE_CEI reports which contains the all activities during loading data with BDE_CEI(so called activity–log),

� BDE_CEI error file which contains the description of possible data–errors.

15.2.7.1.3 BDE_CEI Runtime Options

BDE_CEI uses the BDE environment variables as runtime options. If these variables are not set,BDE_CEI uses default values.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–39


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.2.7.1.3.1 BDE_CEI Batch Configuration File Specification

The value of the environment variable is set per default to

BDE_CFG $HOME/bde/input/batch_config.dat.


setenv BDE_CFG $HOME/bde/input/name_of_batch_configuration_file

either interactively or in the user’s $HOME/.user/cshrc shell script. The BDE_CFG environmentvariable specifies also the BDE_CEI data file as follows “$BDE_CEI.cei”.

15.2.7.1.3.2 BDE_CEI Error Limit

The value of the environment variable is set per default to

BDE_ERROR_LIMIT 1000Up to this limit the data–checker will report any error which is found in the set of loadabledata. If this limit is exceeded, the data–checker will stop (with an appropriate message).


setenv BDE_ERROR_LIMIT users_new_error_limit

either interactively or in the user’s $HOME/.user/cshrc shell script.

15.2.7.2 BDE_CEI Invocation

The BDE_CEI invocation applies the same methodology as BDE invocation. The BDE_CEI pro-cess consists of the following logical phases:

• preparation

• load

• final storage

• execution of reset

For more detailed information please refer the similar chapter of BDE invocation.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–40


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


BDEPreparation Load Data Store Data

Copy data into load directoryVerify format of data–file(s)Create config file(s)

Invocation of BDE_CEI_LOADCheck reports

Invocation of BDE_CEI_STORECheck reportsCheck loaded data in MDB

In case of load errors return toBDE Preparation Phase

In case of store errors return toBDE Preparation Phase

BDE_CEI Preparation BDE_CEI Load BDE_CEI Storage BDE_CEI Reset

Reset

Invocation of BDE_CEI_RESETDeletetion of activityand report log files

15.2.7.2.1 Invocation of BDE_CEI

The BDE_CEI commands to execute BDE_CEI in background are:

• bde_cei_load

• bde_cei_store

• bde_cei_reset

The execution of BDE_CEI shall be carried out by the following main steps:

• define end–items to be created,

• prepare user data files according defined end–items,

• preparation of batch configuration files,

• invoke bde_cei_load,

• check bde_cei_load_activity.log/error.logIn case of errors check also in associated log–files and start again with preparation of data–files and/or database definition after BDE_CEI reset,

• invoke bde_cei_store

• check bde_cei_store_activity.log/error.logIn case of errors check also in associated log–files and start again with preparation of data–files and/or database definition.

• invoke bde_cei_reset to delete activity.log/error.logs.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–41


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The BDE_CEI shall be used directly by user commanding or by usage of a shell script. An exam-ple of a shell script is explained in the section of BDE invocation – the BDE commands have tobe replaced by BDE_CEI commands as described in this section.

BDE_CEI is providing return codes, which can be used if BDE_CEI is invoked from a shell script.The provided return codes of these commands are given in following table:

ReturnCode

0

2

3

4

42

Description of Return Code Used by

BDE BDEStoreLoad

BDEReset

No error

SQL or Data file error


BDE configuration file notfound or empty

Exception error (Request data error)

X

X

X

X

X X

X

X X

XX

Figure 175.BDE_CEI Foreground Return Codes

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–42


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.2.7.3 BDE_CEI General Constraints

The following constraints are applicable for BDE_CEI:

Overwriting Data in MDB

The function bde_cei_store overwrites previously existing data in the MDB without informationto the user. The MDB – Update are performed as listed in the load report unless an error occurs.

CU changes between LOAD and STORE

bde_cei_store inserts all detailed data into the MDB only if the CU status and path nodes are un-changed between bde_cei_load and bde_cei_store.

Privileges

Only users with the privilege Configuration–Manager are able to load data via BDE_CEI into theMDB.

Provided Identifier

Loading of foreign key is supported in the DATA API by standard aggregate store operations.

Pathname Syntax Check

Leading underscores in the pathname and lower case characters are not allowed in pathnames.

Numbers of Enditem Nodes

The number of end items to be created are limited. The limitation is driven by the SID ranges forthe actual MDB instance and its special BDE–purpose range. These ranges can be defined andextended using the SID–Range Tool.

Error Limits

There are the following error limits:

� The default max. number of bde_cei_load errors is set to 1000.

� The max. number of bde_cei_store errors is set to 1.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–43


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.2.8 BDE_CEI Error Messages

15.2.8.1 Error Overview

Error codes due to system/user errors


3001 SYSTEM_ERROR ”MDB_ERROR: Fatal MDA Error!”

3002 SYSTEM_ERROR ”ORACLE_ERROR: Fatal Oracle Error!”

3003 SYSTEM_ERROR ”AUTHORIZATION_ERROR: User has no oracle account”

3004 SYSTEM_ERROR ”AUTHORIZATION_ERROR: User is not registered as MDA user”

3005 SYSTEM_ERROR ”AUTHORIZATION_ERROR: CM privilege is necessary for BDE”

3010 SYSTEM_ERROR ”CONNECT_ERROR”

3011 SYSTEM_ERROR ”environment variable TWO_TASK is absent”

3012 SYSTEM_ERROR ”environment variable ORACLE_HOME is absent”

3013 SYSTEM_ERROR ”environment variable ORACLE_SID is absent”

3014 SYSTEM ERROR “unix error: $HOME or $USER was absent or global environmentparameter error”


3101 USER_ERROR “CDU version is restricted”

3102 USER_ERROR ”Invalid Header Format in Configuration File”

3104 USER_ERROR ”CU Version is FROZEN”


3109 USER_ERROR ”impossible to access to the config or data file”

3110 USER_ERROR ”No BDE_CEI_Load operation was performed before”

3111 USER_ERROR ”BDE_CEI_LOAD operation was performed by another user”

3112 USER_ERROR ”Locked by another tool or user”

3113 USER_ERROR ”SID range error”

3116 USER_ERROR ”impossible to create report or output files”

3117 USER ERROR “Invalid MISSION name syntax in Configuration File”

3118 USER ERROR “Invalid SYSTEMTREE_version syntax in Configuration File”

3119 USER ERROR “Invalid CU name syntax in Configuration File”

3120 USER ERROR “Invalid CU version syntax in Configuration File”

3121 USER ERROR “unexpected end of file”

3122 USER ERROR “an old BDE_CEI_LOAD session exist”

3123 USER ERROR “one of the configurations parameter is out of order”

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–44


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Error codes due to data errors


3207 DATA_ERROR ”Invalid PATHNAME syntax or length (empty or more than 255characters)”

3209 DATA_ERROR ”incompatibility TYPE of update node”

3210 DATA_ERROR ”Invalid PATH Name (empty or more than 80 characters)”

3211 DATA_ERROR ”Invalid TYPE or TYPE Name (empty or more than 40 characters)”

3212 DATA_ERROR ”Invalid OWNER Name length (max 30 characters)”

3213 DATA_ERROR ”Invalid CI–NUMBER length (max 10 characters)”

3214 DATA_ERROR ”Invalid DESCRIPTION length (max 80 characters)”

3291 DATA_ERROR “one of the request parameters is out of order”

15.2.8.2 User Data Errors

The Errors listed in the table system/user errors prepares an direct break of the work of theBDE_CEI operations. During the work of the bde_cei_load operation the errors 3104, 3112 andall data errors will only listed in the report files, the request will be skipped and the work goeson with the next request. In all error cases the same user actions will be necessary:

• Check format, syntax, or range of the specified field in the specified input file (use reportedrecord key and column number as reference) and correct the error as necessary.

• Start the bde_cei_reset.

• Rerun the job.

In the following the unexactly error messages shall be described in detail

• Error code 3209: incompatibility TYPE of update node

The request to update a node must have the same node–type like the existing node.

For example : the existing node has the node–type VIRTUAL and the request tries to update thenode with EGSE_INTEGER_SW_VARIABLE as node–type.

• Error code 3291: one of the request parameters is out of order

In the second line in the requestfile (requestnumber is printed in the errorfile) is an error occurred.This line contains the following sequence: node_type, owner and the ci_number. One or more ofthese parameters are wrong or the line is empty.

• Error code 3207: Invalid PATHNAME syntax or length (empty or more than 255characters)

The first line of the requestfile (requestnumber is printed in the errorfile) contains an error. Butoften this failure will be also displayed, if the pathname is not valid in the scope determined bythe bde_configuration file.

15.2.8.3 Other Errors (system / programming errors, Database problems, etc.)

Error messages of this kind refer to abnormal conditions, internal problems or inconsistencieswhich usually result in the run being aborted. These error messages will appear in the Activity

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–45


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Log. They should be reported, depending on the case, to either the Database or SW Maintenancepersonnel. For example the MDB Fatal Error of the bde_cei_load operation can have the reasonin the limited number of temporary created enditem. This limitation can be changed by redifini-tions of the MDB instance ranges using the SID–Range Tool.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–46


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.3 BATCH DATA ENTRY CREATE CONFIGURATION UNIT FACILITY

15.3.1 General Description

Batch Data Entry Create Config Unit (BDE_CU) is the extension of the tools Batch Data Entry (BDE) andBatch Data Entry Create End Item (BDE_CEI).

All these tools provide operations for loading data or data structures from ASCII files into the mission data-base:

BDE – aggregate related data of an end item (e.g. limited sets, physical address)BDE_CEI – user tree structureBDE_CU – empty CDUs

– empty CDU versions– empty CCUs– empty CCU versions– CCU references

The BDE_CU is thus a tool which provides operations for loading the configuration unit specific data in themission database.

BDE_CU is functional divided into tree parts, namely:

– the load operation bde_cu_load

– the store operation bde_cu_store

– the reset operation bde_cu_reset

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–47


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.3.2 Provided Operations

MDB

Data File

Config. File

BDE–

Log files

bde_cu_loadbde_cu_storebde_cu_reset

element configuration,mission and data dictionary info


Activity Log

Error Logs

CU

system tree version

Figure 176. Simplified Overview of BDE_CU

15.3.2.1 Load operation

The bde_cu_load operation is logically the first to be executed. Its purpose is to read and validate the userrelated CU activities (create CDU, create CDU version, create CCU, create CCU version and create CCUreference) from the Data File and place it in a load result file (.bde_cu_load_result). This file contains thecommands for the bde_cu_store operation. For the validation of the configuration unit data this data is tem-porary stored in the MDB.

The following activities are performed by the load operation:

· Check user’s authorization (must have Configuration Manager privilege)

· Connect to MDB.

· Parse the BDE_CU configuration file, i.e. extract and validate runtime parameters.

· Parse the BDE_CU data file, perform validation checks and store the data temporary in theMDB.

· Generate the load result file and the activity and error logfile for the load operation.

During the load operation the program uses a ”BDE range” which has to be configured in sizeand range with the SID Range Tool.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–48


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.3.2.2 Store operation

The bde_cu_store operation performs the CDU node, CDU version, CCU, CCU version and CCU referencecreation in the specified system tree version.

In case a version already exists an update is performed.

If any error occurs, all changes are discarded.

The following activities are performed by the store operation:

· Connect to MDB

· Check user’s authorization (must have Configuration Manager privilege)

· Check that the load area has been filled by the previous corresponding load operation.

· Creation of CDUs and/orcreation of CCUs and/orcreation of CDU versions and/orupdate of CDU versions and/orcreation of CCU versions and/orupdate of CCU versions and/orcreation of CCU references (to other CCU versions and/or to other CDU versions)

· In case of errors, discard all changes.

15.3.2.3 Reset operation

The bde_cu_reset operation deletes all log files and the load area file.

This operation can be used in case of BDE_CU or system malfunctions. It essentially releases the load areaand makes it available for new jobs.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–49


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.3.3 BDE_CU Input Files

15.3.3.1 BDE_CU Batch Configuration File

BDE_CU does not use the standard BDE batch config file format. Since the information for CDU/CCU ver-sions are part of the data file (see section 15.3.3.2) this data needs not to be defined here. Instead the ElementConfiguration name, mission and system tree version needs to be defined here.

The order of the three parameter lines can be any. The number of blanks and tabs is also any.

The name of the BDE_CU configuration file must be set by the environment variable BDE_CFG. If the set-ting of BDE_CFG is not performed, the default batch config file $HOME/bde/input/batch_config.dat is tak-en.

# ELEMENT_CONFIGURATION: Element Configu-ration Name# MISSION: Mission Name# SYSTEMTREE_VERSION: System Tree VersionNumber

Figure 177. Description of the BDE_CU batch configuration file

15.3.3.2 User Data File

The name of the BDE_CU data file is $BDE_CFG.cu, i.e. name of data file = name of config file + extension”.cu”. If $BDE_CFG is not defined then the data file name is $HOME/bde/input/batch_config.dat.cu.

The BDE_CU data file contains creation commands and their parameters. The creation commands in eachLine 1 in the data file must be identical to the description (bold/italic) below. All parameters (Line 2 andgreater) must be defined by user. The parameters in brackets ([..]) are optional. The number of blanks and/ortabs between parameters are not relevant. By a missing owner BDE_CU inserts the actual owner. By missingdescription, the description is empty. Testversion and MDB instance are only needed for CDU testversions.The last line of each command block bust be empty.

Data Type Format/Range Constraint

pathname string up to 255 characters

version number between 0 and 9999 (0 is only allowed in testversion 0.0.0.1)

issue, revision number between 0 and 9999

testversion number between 0 and 9999

MDB instance string up to 16 characters

CDU domain string up to 16 characters

description string up to 80 characters

CCU name string up to 30 characters

15.3.3.2.1 Create CDU without Version

Line 1: CREATE CDU

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–50


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Line 2: CDU pathname

Line 3: <empty>

15.3.3.2.2 Create CDU Version

Line 1: CREATE CDU VERSION

Line 2: CDU pathname

Line 3: version.issue.revision[.testversion]

Line 4: CDU domain [owner]

Line 5: [description]

Line 6: <empty>

15.3.3.2.3 Create CCU without Version

Line 1: CREATE CCU

Line 2: system tree pathname

Line 3: CCU name

Line 4: <empty>

15.3.3.2.4 Create CCU Version

Line 1: CREATE CCU VERSION


Line 3: CCU name version.issue.revision [owner]

Line 4: [description]

Line 5: <empty>

15.3.3.2.5 Create CCU references

Line 1: CREATE CCU REFERENCES


Line 3: CCU name version.issue.revision

...

Line m: system tree pathname

Line m+1:...Line n: CDU pathname

Line n+1;

}

}

only for CCUreferences

only for CDUreferences

CCU name version.issue.revision

version.issue.revision[.testversion MDB Instance]

...

last Line: <empty>

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–51


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.3.4 BDE_CU Output Files

The directory for the location of the BDE_CU report files is $HOME/bde/reports.

15.3.4.1 Load Activity Report

The BDE_CU load activity report (file: bde_cu_load_activity.log) contains information about:

– the BDE_CU version

– the BDE_CU user

– the date and time of invocation

– the batch configuration file

– the full pathname of data file

– the BDE error limit

– the creation / update commands and/or rejected commands

– the number of created, updated and rejected CDUs / CDU versions / CCUs / CCU versions /CCU references

– the number of errors

– the date and time of end of job

15.3.4.2 Load Area File

The BDE_CU load area file (.bde_cu_load_result) as the output of the load operation and the input for thestore operation contains information for each valid command (CREATE CDU, CREATE CDU VERSION,CREATE CCU, CREATE CCU VERSION, CREATE CCU REFERENCES):

– if the CDU, CDU version, CCU, CCU version or the CCU references already exist, then theyshall be updated, else they shall be created

– all parameters for creation or update as input of bde_cu_store

15.3.4.3 Load Error Report

The BDE_CU load error report (file: bde_cu_load_error.log) contains detailed information about the errorsoccurred during the load operation:

– MDB connection privilege errors

– the pathname, name, version etc. of the rejected item (CDU, CDU version, CCU, CCU version,maintain CCU reference)

– the related error message

15.3.4.4 Store Activity Report

The BDE_CU store activity report (file: bde_cu_store_activity.log) contains information about:


– the BDE_CU user

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–52


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



– the batch configuration file

– the full pathname of data file

– the BDE error limit

– the creation / update commands

– the number of created, updated and rejected CDUs / CDU versions / CCUs / CCU versions /CCU references



15.3.4.5 Store Error Report

The BDE_CU store activity report (file: bde_cu_store_error.log) contains information about:


– the BDE_CU user



– the related error message


15.3.4.6 Reset Activity Report

The BDE_CU reset activity report (file: bde_cu_reset_activity.log) contains information about:


– the BDE_CU user


– the deleted files


15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–53


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.3.5 Using BDE_CU

15.3.5.1 User Privilege

The user running BDE_CU must have the CONFIGURATION MANAGER privilege for the MDB he isworking on.

15.3.5.2 User Directory Structure

If the directory structure needed for BDE_CU does not exist, then bde_cu_load creates this structure auto-matically.

The directory structure is the same as the normal BDE directory structure.

users home directory

BDE_CU required directory structure

Figure 178. Required BDE_CU directory structure

The use of the directory input is recommended but not required. It is allowed to store data and configurationfiles in another directory, but then the environment variable BDE_CFG has to point to the appropriate configfile. If the environment variable is undefined, then the default batch config file batch_config.dat and the datafile batch_config.dat.cu are expected in the input directory.

In the directory reports the reports are stored after invocation of bde_cu_load, bde_cu_store or bde_cu_reset.Also the load area file (.bde_cu_load_result) is stored in this directory.

15.3.5.3 Runtime Options

BDE_CU uses the BDE environment variables as runtime options. If these variables are not defined,BDE_CU uses default values.

15.3.5.3.1 BDE Configuration File Specification

The environment variable BDE_CFG defines the name with the full pathname of the batch configurationfile.

If this environment variable is undefined, then the batch configuration file name is $HOME/bde/input/batch_config.dat.

15.3.5.3.2 BDE Error Limit

The environment variable BDE_ERROR_LIMIT sets the number of maximal errors reported by the datachecker. If this limit is exceeded, the data checker will stop with an appropriate message.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–54


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


If this environment variable is undefined, then the error limit will be set to 1000.

15.3.5.4 BDE_CU Invocation

The BDE_CU invocation follows the same methodology as BDE and BDE_CEI. The BDE_CU process con-sists of the following logical phases:

– preparation

– load operation

– store operation

– reset operation

BDEPreparation Load Data Store Data

Copy data into load directoryVerify format of data–file(s)Create config file(s)

Invocation of bde_cu_load Invocation of bde_cu_storeCheck reportsCheck loaded data in MDB

In case of load errors perform In case of store errors perform”Reset” and return to BDE

BDE–CU Preparation BDE–CU Load BDE–CU Store BDE–CU Reset

Reset

Invocation of bde_cu_resetDeletetion of activityand report log files

Sets the BDE_CFG variable

Check reports

in case oferrors

in case oferrors

Preparation phase”Reset” and return to BDEPreparation phase

Figure 179. BDE_CU Process

The execution of BDE_CU is carried out by the following steps:

– write the create commands of CDU, CDU version, CCU, CCU version and/or CCU referencesand the affected parameters in an ASCII file

– preparation of batch configuration file

– copy the batch configuration file and the data file into the BDE input directory

– setenv BDE_CFG input_directory_pathname/batch_configuration_filename

– invoke bde_cu_load

– check bde_cu_load_activity.log and bde_cu_load_error.logIn case of too many errors (user decision) check the log–files and start again with preparation ofbatch configuration and/or data file after bde_cu_reset command

– invoke bde_cu_store

– check bde_cu_store_activity.log and bde_cu_store_error.logIn case of errors check the log–files and start again with preparation of batch configurationand/or data file after bde_cu_reset command

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–55


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Invocation of bde_cu_reset is necessary in case of:

– user will start again with preparation of batch configuration and/or data file direct after ainvocation of bde_cu_load (the number of errors is not relevant; no bde_cu_store was performed)

– bde_cu_store returns with an error

BDE_CU is providing return codes. The provided return codes of these commands are given in the followingtable:

ReturnCode

0

2

3

4

42

Description of Return Code Used by

BDE BDEStoreLoad

BDEReset

No error

SQL or Data file error


Exception error (Request data error)

X

X

X

X

X X

X

X X

XX

BDE configuration file hasmissing parameters

Figure 180. BDE_CU Foreground Return Codes

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–56


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.3.6 BDE_CU Constraints

15.3.6.1 BDE_CU General Constraints

The following constraints are applicable in BDE_CU:

– The user must have the Configuration Manager privilege.

– The affected system tree version must be in status FROZEN.

– The operation bde_cu_store overwrites previously existing data in the MDB without informationto the user. The update of MDB is performed as listed in the load activity report if the status ofthe affected CDU/CCU version is DEVELOPMENT or REVIEW.

– bde_cu_store updates all data in the MDB only if the CDU/CCU status are unchanged betweenbde_cu_load and bde_cu_store.

– The number of CDUs, CDU versions and CCU versions to be created during one execution islimited. The amount of version, that can be created during one execution, is configurable with theSID – Range Tool (special purpose range of BDE).

– The default maximal number of reported bde_cu_load errors is set to 1000 (user definable byenvironment variable BDE_ERROR_LIMIT).

– If by the execution of bde_cu_store an error occurs, the program is terminated.This one error will be reported.

– Each user can only start one operation (i.e. load, store or reset) at a time.

15.3.6.2 Create CDUs in batch mode

– This function creates empty CDU nodes. CDU versions have to be created with the create CDUversion function.

– The system tree paths, below which the CDU nodes shall be created, have to exist.

15.3.6.3 Create CDU versions in batch mode

– This function creates empty CDU versions in status DEVELOPMENT. User tree nodes and enditem detail data have to be created with separate BDE operations.

– The system tree path, below which the CDU versions shall be created, has to exist.

– In the case that no testversion shall be created, the system tree node, below which the CDUversion shall be created, must have the actual MDB instance assigned (must be responsible MDBinstance for this node).

– In opposite to I_MDB the user can freely choose the version, issue, revision and test versionnumber of the CDU version.

15.3.6.4 Create CCUs in batch mode

– This function creates empty CCUs. CCU versions and CCU references have to be created withthe create CCU version and the create CCU references function.

– The system tree paths, to which the CCUs shall be attached, have to exist.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–57


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.3.6.5 Create CCU versions in batch mode

– This function creates empty CCU versions in status DEVELOPMENT. References to CDUversions and /or CCU versions have to be created with the create CCU maintain referencesfunction. User tree nodes and end item detail data have to be created with separate BDEoperations.

– The system tree paths, to which the CCU versions shall be attached, have to exist.

– In difference to I_MDB the user can freely choose the version, issue and revision number of theCCU version.

15.3.6.6 Create CCU references in batch mode

– The CCU version has to exist

– It is not allowed to have more than one direct or indirect reference from a CDU version to a CDUversion.

CCU X V(l,m,n)

CCU Y V(o,p,q)

only two of these threereferences are allowed!

=>

CDU Z

or

orV(s,t,u)

Figure 181. Double referenced CDU version

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–58


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


– It is not allowed to have a double referenced CDU node (i.e. the CCU has references to morethan one version of the same CDU node)

CCU X V(l,m,n)

only one of these tworeferences is allowed!

=>

CDU Z V(u,s,t)

or


=>

CDU Z V(r,s,t)

CCU X V(l,m,n)

CDU Z V(u,s,t)

or

CDU Z V(r,s,t)

CCU X V(l,m,n)

or

Figure 182. Double referenced CDU node

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–59


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


– The system tree node of a referenced CCU version must be in the same subtree as the system treenode of the source CCU version. The referenced CCU version must be attached under the sourceCCU version in the system tree.

CCU Y V(o,p,q)

CCU X V(l,m,n)

Figure 183. CCU reference to same system tree node

CCU X V(l,m,n) CCU Y V(o,p,q)

CCU Y V(o,p,q)

CCU X V(l,m,n)

Figure 184. CCU reference out of subtree

– It is not allowed to have more than one direct or indirect reference from a CCU version to a CCUversion.

CCU X V(l,m,n)

CCU Y V(o,p,q)

CCU Z V(r,s,t)

or

or


=>

Figure 185. Double referenced CCU version

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–60


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


– It is not allowed to have more then one direct or indirect reference to CCU versions (even ofdifferent CCUs) at the same system tree node.

CCU Z V(r,s,t)

CCU Y V(o,p,q)

CCU X V(l,m,n)

CCU Z V(r,s,t)

CCU Y V(o,p,q)

CCU X V(l,m,n)

CCU Z V(l,m,n)

=> only one of these two references is allowed!

=> only two of theses three references is allowed!

Figure 186. Double referenced system tree node

– It is not allowed to have a double referenced CCU (i.e. the CCU has references to more than oneversion of the same CCU)

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–61


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


CCU X V(l,m,n)

oronly one of these tworeferences is allowed!

=>


=>

CCU Y V(r,s,t)

CCU Y V(u,s,t)

CCU X V(l,m,n)

or

CCU Z V(r,s,t)

CCU Z V(u,s,t)

CCU X V(l,m,n)

Figure 187. Double referenced CCU

– It is allowed to reference a CDU version out of scope of the system subtree of a CCU version, butthis CCU version may not be referenced by an other CCU version.

CCU X V(l,m,n)

CCU Y V(o,p,q)

CDU Z V(s,t,u)

allowed

Figure 188. Reference to a CCU version with a CDU version reference out of subtree

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–62


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.3.7 BDE_CU Error Messages

15.3.7.1 Overview

The following errors are divided into different classes: system and user errors, respectivelydata file errors, which are further divided into data and API errors. System and user errorsand the error messages belonging to them are nearly identical in bde_cu_load andbde_cu_store when not mentioned otherwise (error messages of the store moduloes are ap-pended to the load messages with a trailing ’/’).



3001 SYSTEM_ERROR ”fatal MDB error”

3002 SYSTEM_ERROR ”user has no oracle account”

3003 SYSTEM_ERROR ”user is no registered MDA user”

3004 SYSTEM_ERROR ”CM privilege is necessary”


3006 SYSTEM_ERROR ”environment variable TWO_TASK is absent”

3007 SYSTEM ERROR “environment variable HOME is absent”

3101 SYSTEM ERROR ”error creating report or output file <filename>”

3102 SYSTEM_ERROR ”not enough memory”

3103 USER_ERROR ”an old bde_cu_load session exists”

3104 USER ERROR “error accessing the data file <filename>” / ”load result file does notexist”

3105 USER ERROR ”error accessing the config file <filename>”

Error codes due to syntactical errors in the data file

2001 DATA ERROR ”command <command> has missing parameters”

2002 DATA_ERROR ”command <command> has too many parameters”

2003 DATA_ERROR ”<pathname> is not a valid CDU_PATHNAME string”

2004 DATA_ERROR ”<instance> is not a valid MDB_INSTANCE string”

2005 DATA_ERROR ”<domain> is not a valid CDU_DOMAIN string”

2006 DATA_ERROR ”<owner> is not a valid OWNER string”

2007 DATA_ERROR ”<description> is not a valid DESCRIPTION string (too long)”

2008 DATA ERROR “<pathname> is not a valid SYSTEM_TREE_PATHNAME”

2009 DATA ERROR “<name> is not a valid CCU_NAME string”

2010 DATA ERROR “VERSION, ISSUE, REVISION or TESTVERSION invalid ormissing”

2011 DATA ERROR “no testversion allowed in <command> command”

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–63


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


2012 DATA ERROR “unknown command: <command>”

4001 DATA_ERROR ”# MISSION is missing in config file”

4002 DATA_ERROR ”# SYSTEMTREE_VERSION is missing in config file”

4003 DATA_ERROR ”# SYSTEMTREE_VERSION is not a number in config file”

4004 DATA_ERROR ”# ELEMENT_CONFIGURATION is missing in config file”

Error codes due to other errors in the data file

The following errors are detected by the BDE_CU API procedures and therefore identicalin bde_cu_load and bde_cu_store:

2100 API_ERROR a database object is not found. An specific error message will begenerated by the API.

2101 API_ERROR the API had problems handling the request. An specific error messagewill be generated by the API.

2102 API_ERROR ”database resources temporarily unavailable”an additional error message will be created by the API stating whichdatabase object caused the error

2103 API_ERROR ”reference could not be created”an additional error message will be created by the API stating why theproblem occurred

2104 API_ERROR “systemtree version is not FROZEN”



15.3.7.3 Usage Errors

These errors generally result from an incorrect use of BDE. The corresponding error messagesare, for the most part, self–explanatory. In the event of such an error:

– Check the Activity Log for details, and correct the error

– Rerun the job.

15.3.7.4 Data Errors

These errors are issued by the BDE_CU Data Checker as a result of syntactical checks performedon the user data. Depending on the time of occurence (either after bde_cu_load or bde_cu_store),different actions have to taken to eliminate these errors:

– occurence after bde_cu_load:Check the error log file for details, and correct the errorRerun the job

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–64


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


– occurence after bde_cu_store:Something was changed in the database after the last run of bde_cu_load,therefore run bde_cu_reset and bde_cu_load again.

15.3.7.5 API errors

These errors are detected by the BDE_CU API Stored Procedures. Most likely, these are no syn-tactical data errors (otherwise they would have been detected by the BDE_CU Data Checker),but errors detected by ORACLE (e.g. items locked by another user, non–existing database ob-jects...). These errors have to be eliminated the same way as Data Errors.


Error messages of this kind refer to abnormal conditions, internal problems or inconsistencieswhich result in the run being aborted. These error messages will appear in the Activity Log. Theyshould be reported, depending on the case, to either the Database or SW Maintenance personnel.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–65


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.4 CREATE_BDE_FILES

15.4.1 General Description

The Batch Data Entry (BDE) CREATE_BDE_FILES tool represents the counterpart to the Batch Data Entry(BDE) tool, the Batch Data Entry Create Config Unit (BDE_CU) and Batch Data Entry Create End Item(BDE_CEI). These tools provide operations for loading data or data structures from ASCII files into the mis-sion database (MDB):

BDE – aggregate related data of an end item (e.g. limited sets, physical address)BDE_CEI – user tree structureBDE_CU – empty CDUs

– empty CDU versions– empty CCUs– empty CCU versions– CCU references

Thus, CREATE_BDE_FILES is a tool which combines the operations to create the input files for the a. m.tools by reading data from the MDB. The files can be modified by the user and may either be used directlyto overwrite the database contents, or to create new data entries within another MDB version or instance.

15.4.2 Provided Operations

15.4.2.1 General

CREATE_BDE_FILES combines two operations:

· Store CCU

· Store CDU

The operations are selected via the menu items provided by I_MDB (Interactive MDB). They can be execut-ed by all users. Special privileges like Configuration Manager privilege as are necessary for BDE, BDE_CEor BDE_CU are not required. Nevertheless, in case the status of the user is not ”Configuration Manager”he/she will not be able to store the data again.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–66


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


MDB

CREATE

via I_MDB

data dictionary info

element configurationBDE

missionsystem tree versionuser tree data

Config. file (Ext.: .dat)

..

BDE input file 1

BDE_CU input file

BDE_CEI input file (Ext.: .dat.cei)

(Ext.: _cu.dat.cu)

(aggregate data file)

BDE input file n (aggregate data file)

BDE_CU config file (Ext.: _cu.dat)

FILES

Figure 189. Overview of CREATE_BDE_FILES

15.4.2.2 CREATE_BDE_FILES Store CCU

The purpose of this function is to store all data related to the selected CCU. The generated files are writtento the directory as specified by the user.

They will contain all necessary information to create – the selected CCU, – the CCU version, – CCU references, – CDU references– CDU versions– CDU data (user trees, aggregate files)

15.4.2.3 CREATE_BDE_FILES Store CDU

The purpose of this function is to store all data related to the selected CDU. The generated files are writtento the directory as specified by the user.

They will contain all necessary information to create – the selected CDU,

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–67


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


– the CDU version, – CDU data (user trees, aggregate files)

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–68


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.4.3 CREATE_BDE_FILES Output Files

15.4.3.1 BDE Configuration File

This file is used to identify the target configuration unit (either CDU or CCU version) and the related aggre-gate data files. The file, thus, consists of two parts:

· the file header containingmission, system tree version, CU type, name and version

and

· the file body containingdata filename, aggregate name, ID type (i.e. PATHNAME or SID or name of foreign key aggregate) and item identifier (i.e. in case of large aggregates oftype LONG or LONG_RAW the values of the ID type is specified)

For a detailed description of this file refer to section 15 of this document, MDA Batch Data Entry Facility.

The basename of the file normally is provided by the user. In case no name has been specified by the userthe name ”batch_config” will be selected. The name of the file is derived from this basename appended by”_”, the MDB internal version of the CDU or CCU and the extension ”.dat”. The internal version is used inorder to avoid overwriting of the file by another call of CREATE_BDE_FILES.

# MISSION:# SYSTEM-TREE_VER-SION: # CU_TYPE:# CU_NAME:# CU_VER-SION:

<Mission Name><System Tree Ver-sion Number>”CDU” | ”CCU”<CU Name><CU Version>Figure 190. BDE Configuration File Header

<file_name><tab><aggregate_name><tab><ID–type>{<tab><item–id>}<CR><file_name><tab><aggregate_name><tab><ID–type>{<tab><item–id>}<CR>

<file_name><tab><aggregate_name><tab><ID–type>{<tab><item–id>}<CR>

<file_name><tab><aggregate_name><tab><ID–type>{<tab><item–id>}<CR>

:

Figure 191. BDE Configuration File Body

15.4.3.2 BDE_CEI Input Data File

The BDE_CEI tool reuses the header information provided via the BDE configuration file. Additionally, adata file is needed containing the information about all end items to be created or updated within the MDB.

Each end item is represented by three lines of the file with the following structure:

· Line 1:pathname

· Line 2: type <tab> owner <tab> CI–number

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–69


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


· Line 3:description (optional)

Please refer to section 15.2 of this document, BATCH DATA ENTRY CREATE END ITEM, for a detaileddescription of BDE_CEI.

The name of the file is derived from the BDE configuration filename appended by the extension ”.dat.cei”,e.g. batch_config.dat.cei.

15.4.3.3 BDE_CU Batch Configuration File

BDE_CU does not use the standard BDE batch config file format. It uses an own configuration file instead,containing the Element Configuration name, mission and system tree version.

The name of the BDE_CU configuration file is derived from the BDE configuration filename appended by”_cu.” and the extension ”.dat”, e.g. batch_config_cu.dat.

# ELE-MENT_CON-FIGURATION:# MISSION:# SYSTEM-TREE_VERSION:

<element configu-ration><mission name><system tree ver-sion>

Figure 192. BDE_CU batch configuration file

15.4.3.4 BDE_CU User Data File

The BDE_CU data file contains the commands and their parameters to create CDU’s, CCU’s, CDU versions,CCU versions and CCU references. The name of this file is derived from the BDE configuration filenameappended by ”_cu.” and the extension ”.dat.cu”, e.g. batch_config_cu.dat.cu.

The BDE_CU data file contains creation commands and their parameters. The following commands areused:

· CREATE CDU

· CREATE CDU VERSION

· CREATE CCU

· CREATE CCU VERSION

· CREATE CCU REFERENCES

Please refer to the section 15 of this document, BATCH DATA ENTRY CREATE CONFIGURATION UNIT FACILITY ,for a detailed description of files, file formats and commands used by BDE_CU.

Note: CREATE_BDE_FILES can be started using the switches ”SID”,”PATHNAME” or the name of aFOREIGN_KEY. In case of SID or FOREIGN_KEY the mentioned values have to exist prior to usingBDE_CU. SID’s are assigned automatically by the system during creation of CDU’s/CCU’s. Therefore,commands like ”CREATE SID” or ”CREATE FOREIGN KEY” are not available.

15.4.3.5 BDE Aggregate Data Files

An aggregate file contains all records related to a certain aggregate, i.e there is only one file for each aggre-gate. Nevertheless – no rule without exception – for aggregates containing the data types ”LONG” or ”LONGRAW” there will be one file for each record. In this case the BDE config file contains the item identifier,

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–70


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


i.e. Pathname, SID or foreign key, together with the referred filename. For a detailed description of this file and the file formats refer to section 15, MDA BATCH DATA ENTRYFACILITY.

Up to 4 filetypes are maintained:

· the ”single record” case:the file contains the record values of a standard aggregate, the structure for a single recordis as follows:

identifier<tab>VALUE1<tab>VALUE2[...<tab>VALUEn]<CR>

· the ”multi record” case:the file contains the record values of a standard aggregate together with a sequence number,the structure for a single record is as follows:

identifier<tab>Entry_Number<tab>VALUE1<tab>VALUE2[...<tab>VALUEn]<CR>

· unformatted large data:there is only one attribute of type ”LONG” or ”LONG RAW”. The entries within the MDBare separated by chunks of up to 64 KB size. All these chunks are written to one aggregatefile. The BDE_Load procedure will divide the contents of the file into 64 KB chunks againduring loading of the data.

· unformatted large data combined with other attribute types:in special cases, like T_CSS_FB_IO_MDE_INFOS, the attribute of type ”LONG” or”LONG RAW” is combined with attributes of other types, e.g. a SUBITEM_ID of type”NUMBER”. The size of the single MDB chunks may be less than 64 KB, i.e. the data of thechunks cannot be appended. They have to be restored to the originally format. In this casethe format of the aggregate file is as follows:

<Entry No. 1><tab>VAL1<tab>[...VALn<tab>]<Length of data in Bytes><CR><Byte1><Byte2>...<Byte Length of data in Bytes><CR>:<Entry No. n><tab>VAL1<tab>[...VALn<tab>]<Length of data in Bytes><CR><Byte1><Byte2>...<Byte Length of data in Bytes><CR>

Please note that there may only be one attribute of type ”LONG” or ”LONG RAW” withinone table. This is a restriction of ORACLE.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–71


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.4.4 Using CREATE_BDE_FILES

15.4.4.1 CREATE_BDE_FILES Invocation

CREATE_BDE_FILES can be started on every work–station running the SOLARIS operating system. It canbe invoked via I_MDB or via command line.

All output files of CREATE_BDE_FILES will be written to the directory ~/bde/input, by default. A scriptfile is generated containing all necessary commands to re–create the retrieved database contents viaBDE_CU, BDU_CEI and BDE. This file, named batch_config.com by default, can be executed from thecommand line.

15.4.4.1.1 Invocation via I_MDB

CREATE_BDE_FILES normally will be called using the so–called ”Flexible Tool Invocation” of the Inter-active MDB (I_MDB):

Select a CDU version or CCU version via I_MDBSelect item ”Tools –> Create BDE Files” from menu ”Command” via the right mouse button

15.4.4.1.2 Invocation via C–Shell

CREATE_BDE_FILES may be called manually. In that case the parameters have to be provided by the user.The profile is as follows:

$MDA_HOME/bin/sun5/create_bde_files<blank>\<CU_TYPE> <internal version> <KEY>[ <output directory>[ <configfile> [commandfile]]][–i | –f <parameterfile>]

where CU_TYPE (CDU | CCU) CU_VERSION CCU or CDU MDB internal version [KEY PATHNAME | SID | <name of foreign key>

default: PATHNAME [Output directory default: ~/bde/input [data file prefix default: batch_config_<CU_VERSION>

[Name of command file default: batchconfig.com[–i | –f <parameter file name>]]]]]

Additional parameters can be specified in a parameter file (if the –f flag is used), or on standard input (if the–i flag is specified). In both cases, no GUI will come up, and the program will completely run in batch mode.

Options that can be specified in the parameter file are (keywords are printed bold, default values in italics):BDE_CU: complete | skipBDE_CEI: complete | skip | customTypes[end item type list, one type on each row, may only be specified when using customTypes]BDE: complete | skip | customTypes | customAggregates[aggregate list, one aggregate on each row, may only be specified when using customAggregates]

Blanks may be filled in everywhere between the words to improve readability. For a detailed description ofthe above parameters, refer to the next chapter.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–72


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.4.4.2 The CREATE_BDE_FILES main window

When the program is started with the flexible tool invocation, or on the command line without the parameters–i and –f, CREATE_BDE_FILES starts up with the following GUI:

Figure 193. The CREATE_BDE_FILES main window

The top part lets you choose global parameters concerning all three types of data generated, BDE_CU,BDE_CEI and BDE data. These parameters can as well be specified as command line parameters and havethe following meaning:

Output directory The directory where all output files will be stored.

Output data prefix A prefix for all generated output file names. This might come in handy if youdecide to create more than one set of files in the same directory and don’t wantto overwrite the previous set.

Output command name The file name of the shell script that allows the loading of all generated databack into the MDB

Output key The key used as identifier for the end items when loading back the data intothe MDB.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–73


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The bottom part is divided into three parts, one part for each of the BDE components. Here you can restrictthe amount of data that will be generated be CREATE_BDE_FILES. All the selection that can be made inthe lower part of the main window can as well be specified by using the –i or –f option on the command line.

BDE_CU completegenerate the ouput files that contain information about all CCUs, CDUs and CCU references in the current scope.

skipskip the generation of BDE_CU data files.

BDE_CEI completegenerate the ouput files that contain information about the creation of all end items in the current scope.

skipskip the generation of BDE_CEI data files.

custom end item type listgenerate output only for the creation of end items of the selected enditem types.

BDE completegenerate the ouput files that contain information about the detailed data of all end items in the current scope.

selected EIsdo only generate detailed data files for the end item types selected inthe BDE_CEI custom end item type list.

skipskip the generation of BDE data files.

custom aggregate listgenerate output only for the selected aggregates.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–74


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.4.5 CREATE_BDE_FILES Constraints

The following constraints are applicable to CREATE_BDE_FILES:

– only the type specific data of an end item can be stored by CREATE_BDE_FILES

– no subitem data can be stored by CREATE_BDE_FILES

– tables may only have one attribute of type ”LONG” or ”LONG RAW”, due to Oracle restrictions.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–75


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


15.4.6 CREATE_BDE_FILES Error Messages

15.4.6.1 Overview

The following errors may occur in case CREATE_BDE_FILES has been started manually.If started via I_MDB these errors normally will not appear:



3001 SYSTEM_ERROR ”fatal MDB error”

3002 SYSTEM_ERROR ”user has no oracle account”

3003 SYSTEM_ERROR ”user is no registered MDA user”

3004 SYSTEM_ERROR ”CM privilege is necessary”


3011 SYSTEM_ERROR ”environment variable TWO_TASK is missing”





Error messages of this kind refer to abnormal conditions, internal problems or inconsistencieswhich result in the run being aborted. They should be reported, depending on the case, to eitherthe Database or SW Maintenance personnel.

15–76

CGS–RIBRE–SUM–00032 03.07.2015– –15–76


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


30


16–3

CGS–RIBRE–SUM–00032 03.07.2015– –16–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


16 CSS DATA AND INTERFACE HANDLING

The Columbus Software Simulator (CSS) integration functions provided in I_MDB allows tostart the CSS tool. This functions can only be invoked when the user is within a CCU scope.

The CSS function in I_MDB is attached to Items which are defined by the type TOPLEVEL_COMPOSITE_FB. This Item–Type has been defined with DADI–MA. It is neces-sary to define the Items in a CDU scope.

The next section explains how to start the CSS tool from I_MDB.

16.1 CSS Start

It is prerequisite that an Item with the type TOPLEVEL_COMPOSITE_FB has been defined ina CDU scope.

To start the CSS tool:

1. Navigate to the Item of the type TOPLEVEL_COMPOSITE_FB in the related CCUscope.

2. Select the Item and press the right mouse button to pop up the command menu.

Figure 194.Entering the CSS

3. Select Tools –> CSS Start... from this list.

The ’CSS Scope Check’ window comes up.

16–3

CGS–RIBRE–SUM–00032 03.07.2015– –16–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 195.CSS Tools start via the ’CSS Scope Check’ Window

From this window it is possible to start the CSS Editor (MDE) or the CSS Control System(MOCS). When entering this window, I_MDB automatically performs a comparison between theCDU’s of the actual CCU loaded in I_MDB and the CDU’s in the Reference Library List.

Any Differences will be presented in the text window below Differences:. This information aboutthe difference check are stored in the file CSS_SCOPE_CHECK.LOG in the user Home Directo-ry.

If there are no differences, MDE or MOCS can be started immediately.

If any differences are found, information of the CCU version, MDB instance and CDU referencepath will be displayed, that the user can decide if the differences are decisive to stop the CSS call.If the differences are unimportant for the CSS call, the user can continue.

4. If the user decides not to continue the CSS call due to important differences, press Quitto leave the ’CSS Scope Check’ window.

5. Select the CSS Editor MDE or the CSS Control System MOCS depending on user

choice.

6. Start the tool with Start CSS.

The CSS Editor Tool will be entered where the user can continue on preparation his simulationmodel. When the work is finished he has to exit the CSS tool and will return to the ’I_MDB Navi-gator’ window.

The CSS Start program is a unix process which remains when the program execution has beenfinished. The process can be iconised and it can be stopped by the Quit command.

16–3

CGS–RIBRE–SUM–00032 03.07.2015– –16–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


31


17–6

CGS–RIBRE–SUM–00032 03.07.2015– –17–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


17 ADVANCED OPERATIONS

17.1 FOREIGN KEY SUPPORT

A foreign key is used for the identification of items in foreign databases. It can be used as a sortof cross reference between the MDB and other non MDB databases. Furthermore it can be usedas an alternative access key within I_MDB.

Each foreign key must be defined as an aggregate of end items. An aggregate is a detail data tableconsisting of one or more fields defined with the data dictionary tool of MDA. Not necessarilyall end items have to have this aggregate assigned. Through this approach the MDA keeps selfadapting (table–driven) and the data entry of the foreign keys can be performed with the alreadyexisting S/W (I_MDB). Syntax checks are performed by I_MDB according to the field defini-tions of the foreign key e.g. validation of integer ranges or values of enumeration types. The se-mantic correctness of the foreign key value can be defined through customer requirements. Theverification will be performed by a special consistency check executed by the consistency check-er. Also the uniqueness of the key values in a CCU or CDU version has to be verified by the consis-tency checker. There are two reasons for that. Through the definition of a CCU version the keysmay be no longer unique. This can also happen through a copy subtree because the keys cannotbe changed automatically as for SIDs. This is why I_MDB cannot guarantee the uniqueness ofthe foreign key values in a configuration.

The interactive end item access via a foreign key will be covered by the ’direct end item access’function, therefore please refer to the common operation ’direct end item access’.

17.2 FLEXIBLE TOOL INVOCATION

The flexible tool invocation function allows the integration of tools to be started from I_MDB.These tools can be integrated from the customer himself in order to fulfil special demands. Userapplication tools may be attached to CDU versions, CCU versions and End Items so that they canbe started from that specific scope.

The scopes in which a tool shall be available in I_MDB can be defined. A tool can be availablefor CCU versions and / or CDU versions ( configuration units ), so that whenever a configurationunit is selected in the configuration unit window, the tool appears in the command menu and isexecutable from there.

A tool can also be available for a specific End Item Type within a CCU and / or CDU navigationscope of the I_MDB navigator window.

All tools are invoked by I_MDB. In four different windows a tool menu is available with thenames of all tools which can be started in the current scope.

- for a CDU version the tool appears in the CDU version window

- for a CCU version the tool appears in the CCU version window

- for an end item the tool appears in the I_MDB navigator window

- for an end item the tool appears in the direct end item access window

17–6

CGS–RIBRE–SUM–00032 03.07.2015– –17–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 196.Tool start via CCU Version window

Perform the following steps if the tool is attached and shall be started from a CCU orCDU scope:

1. Navigate to the ‘I_MDB: CCU Versions window‘

or

‘I_MDB: CDU Versions window’

depending where the tool has been attached to.

2. Select Command –> Tools to get the tool menu.

If different tool attachments have been defined within DADIMA, the user will get this list oftools.

3. Select the tool to be started.

If no customer defined parameters exist, the tool will be started immediately with the standardversion identification parameters.

4. If customer defined parameters exist, the ’Tool Invocation window’ for the parameter

data entry is generated.

Enter the actual values for the parameter fields and start the tool execution with Exe-cute.

The tool is called with the standard version identification parameters and the added values of theentered parameter values.

17–6

CGS–RIBRE–SUM–00032 03.07.2015– –17–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 197.Tool Parameter Entry

To start the tool from an end item:

1. Navigate to the end item within the ’I_MDB navigator window’

or

Navigate to the end item within the ‘Direct End Item Access window‘.

In the case of an end item it is important which navigation scope has been selected. The navigationscope is shown in the right bottom corner of the I_MDB navigator window. The navigation scopecan be CCU version or CDU version depending on the kind of configuration unit which has beenselected.

2. Select the specific end item

3. Select File–>Tools if the current window is the ’Navigator’ window

or

select Search&Edit–>Tools if the current window is the ’Direct End Item Access’ win-

dow

to get the tool menu.

4. Select the tool to be started.

If no customer defined parameters exist, the tool will be started immediately with the standardversion identification parameters.

5. If customer defined parameters exist, the ’Tool Invocation window’ for the parameter

data entry is generated.

Enter the actual values for the parameter fields and start the tool execution with Exe-cute.

The tool is called with the standard version identification parameters and the added values of theentered parameter values.

17–6

CGS–RIBRE–SUM–00032 03.07.2015– –17–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


17.3 CLS INTERFACE HANDLING

An Automated Procedure (AP) is a computer program or program component, performing a se-quence of operations that would otherwise be executed by a human operator. In general APs arewritten in the User Control Language (CLS/UCL). CLS is a dedicated test and operation languagefor monitoring and control of a system.

A set of CLS commands and instructions can be predefined and stored in user libraries and systemlibraries.

For the implementation of APs, user libraries and system libraries, CGS provides the CLS Editorand Compiler.

The CLS Editor and Compiler integration functions provided in I_MDB allows to start the CLSEditor and Compiler.

The CLS functions are attached in I_MDB to End–Items which are defined by the type

� UCL_AUTOMATED_PROCEDURE

� UCL_USER_LIBRARY

� UCL_SYSTEM_LIBRARY

� All end items having formal parameters (e.g. Stimuli, Predefined Telecommands etc.)

These Item–Types have been defined with DADI–MA.

17.3.1 CLS in Manual Mode

APs, user libraries and system libraries can be generated for a single End–Item. To start the CLSEditor and Compiler from I_MDB for a single End–Item, it is prerequisite that the End–Item iscomposed of one of the above mentioned types.

To start the CLS Editor and Compiler tool:

1. Navigate to the Item of the desired type UCL_AUTOMATED_PROCEDURE,

UCL_USER_LIBRARY or UCL_SYSTEM_LIBRARY in the related CDU or CCU

scope.


3. Select Tools –> CLS Editor... from this list.

The message ’Tool has been started in batch mode’ appears in the I_MDB navigator message lineand after a while the CLS Editor and Compiler window comes up.

The window pre–settings depend on the selected type where the tool has been started from. Theuser can continue on preparation the automated procedures, system libraries or user libraries.When the work is finished the user can exit the CLS tool and can continue the work in I_MDB.

The CLS tool is a unix process which remains when the program execution has been finished.The process can be iconised and it can be stopped by the Quit command.

17–6

CGS–RIBRE–SUM–00032 03.07.2015– –17–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


17.3.2 CLS in Batch Mode

The function CLS in batch mode allows to compile all CLS end items (e.g. APs, user libraries,system libraries, items with parameters etc.) within a selected CDU scope or CCU scope. Thissaves time when the source code has been changed and it ensures compilation consistency.

To start the CLS Compiler in Batch Mode:

1. Navigate to the desired I_MDB: CCU Version or I_MDB: CDU Version window.

2. Select Command –> Tools –> CLS Batch Compiler... from the pop up menu.

The window ’Tool Invocation’ popps up.

3. Enter a value for Forced Compilation (y/n). The default values is ’n’.

’y’ ––> enforce compilation for all CLS end items’n’ ––> use CLS make facility

4. Press the botton Execute. A message ’... has been started in batch mode’ appears in theI_MDB navigator message line.

After a while the textedit tool comes up containing the result of the batch compilation process.In case a compilation unit has failed, the error listing for each failed unit is displayed in the report.

17–6

CGS–RIBRE–SUM–00032 03.07.2015– –17–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


32


18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


18 DETAIL DATA EDITOR

The Detail Data Editor (DDED) is a tool to edit the detailed data for End–Items. Single aggregateand composite aggregate data may be entered by the DDED. The DDED can be used instead or in parallel to the standard data editor, which is accessible viathe File–>Open–>... operation. It depends on the users choice to use the standard data editor orthe DDED. It is not possible to edit composite aggregates with the standard editor, only the singleaggregate may be edited.

The next section explains how to start the DDED tool within I_MDB.

18.1 DDED START

It is prerequisite, that the DDED is attached to the End–Item type. This attachment has to becreated during the data structure definition with DADIMA.

The DDED integration has been created by the user who is responsible for the data structure defi-nition, so that the I_MDB user is able to work with the DDED.

To start the DDED tool:

1. Navigate to the desired Item within the user tree.


Figure 198.Starting the Detail Data Editor

3. Select Tools –> Detail Data Editor... from this list.

The message window ’Tool has been started in batch mode’ comes up.

The DDED main window displays the message ”Please wait a moment –– I’m reading the enditem data structure”.

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


4. Wait until the above mentioned message disappears. The user can then work with the

DDED on the desired end item which is described in the next sections.

18.2 DDED MAIN WINDOW

When the DDED has been started, at first the main window is popped up. Global commands onan End–Item can be executed from this window.

A

B

C

D

EF

Figure 199.DDED Main Window

A Menu bar

The menu bar contains two menus, one to open and save an end item, and one to set some of theDDEDs properties.

File –> Open end item

Open another End–Item. Before opening the new end item, the program asks wether you wantto save any changes you made to the current end item.

File –> Save end item

Saves all changes you made to the current end item.

File –> Quit

Quit the DDED. Beforethe program is closed, it asks wether you want to save any changes youmade to the current end item.

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Properties –> Edit Mode

The user may select between two different edit modes: read only or edit.By choosing edit, you are allowed to actually change end item data. This is only allowed as longas you are the owner of the end item and the containing CDU is not in status frozen.Mode Read only prohibits the changing of end item data. The DDED will start automatically inthis mode if you are not owner, or if the containing CDU is in status frozen.

Properties –> Logfile Level

It may be selected if only errors, all messages or debug information shall be written to a log file.The Logfile will be used for failure analysis and is not relevant for the normal user. The files arestored in the $MDA_HOME/bin/sun4/MESS directory.

Properties –>Check Level

Selection of the level for mandatory check. The following 3 levels are supported:without Mandatory Check

the DDED will not make a mandatory check.only changed Aggregates

the mandatory check will only be done on changed aggregates (default)Full Check

the mandatory check will be done on all aggregates of the end item

Properties –> Tab position

You can select the position at which the aggregate tabs will be placed.

Help –> About

Displays genreal information about the DDED.

B Info area

The information area contains the Pathname and Creation Date of the end item that is currentlydisplayed in the main window.

C Aggregate tabs

The aggregate tab area contains a tab for every aggregate of the end item. By selecting a tab, theaggregate content area (D) will be updated to show the contents of the currently selected aggre-gate.

D Aggregate contents

The aggregate contents area show the end item data of the currently selected aggregate.

E Comand area

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The command area contains two buttons. By selecting the button Reset end item, the values ofthe end item will be reset to the database values. Any changes you made after you last saved theend item will be lost.The button Save end item saves all uncomitted changes to the database.

F Message bar

Messages as response to user actions will be displayed in this part of the window.

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


18.3 DATA ENTERING FOR NON–COMPOSITE AGGREGATES

Non–composite aggregates are aggregates containing only single record or multi record data.This chapter describes how to enter data into these types of aggregates.

18.3.1 Single Record Aggregate data editing

When you have selected a single–record aggregate by pressing on the aggregate tab, the aggregatecontent area will be showing the aggregate contents.

Figure 200.DDED window showing a single–record aggregate

To fill Single Record Aggregates with data

1. If the attribute type is not enumeration, simply select the desired data field in the aggre-

gate content area and enter the attribute value.

Otherwise click on the button on the right of the attribute field to open the drop downmenu containing the valid values for this enumeration. Then select a value from the list.

Attributes of type pathname can as well be filled by clicking on the label of the attibute.

This will open the PNS tool where you can select the desired pathname.

2. Pressing the Return key will have the attribute value checked for type conformance.

This will not work for enumeration type attributes, which can only contain values ofcorrect type.

If the consistency checker detects an error, a message will appear in the message bar.

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The Tab key and the Shift+Tab key may be used to switch forward and backward between thedata entry records.

The Save operation has to be used to permanently store the data in the database.

18.3.2 Multi Record Aggregate data editing

Multi record aggregates are aggregates containing more than one record of data. When selectinga multi record aggregate from the aggregate tab area, the aggregate contents will be updated toshow the contents of the selected aggregate:

A

B

C

Figure 201.DDED window showing a single–record aggregate

Data Definition Area Explanation

The data definition area for a multi record aggregate is more complex than the one of a singleaggregate. An explanation of the definition area follows now.

A Multi Record Aggregate List

The number of lists shown depends on the number of attributes defined for the multi record aggre-gate. A maximum number of three attribute lists may be displayed.

B Data Value Entry Fields

New attribute values for one record of the multi record aggregate can be entered in the data entryfields at the bottom of the lists. The currently selected records values will be displayed here.

C Pull Down Menus

The pull–down menus below the scroll lists provide operations on the multi record aggregate re-cords like insertion, deletion, etc. The different commands are explained below.

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Copy

The copy operation copies the actually selected record into the copy buffer. Afterwards the recordmay be inserted with the paste operation.

Paste

Insertion of a record from the copy buffer into the list of records. The place of insertion can bedefined by selecting one of the following menu items: first, before, after and last.

Insert

Insertion of a new empty record on the first scroll list position, before the actually selected record,after the actually selected record, or at the last scroll list position.

Delete

Deletion of the actually selected record.

Focus –> Get

Displays the position number of the actually selected record.

Focus –> Set

Selects and displays the record of the given position number

Focus –> Total

Displays the number of records which are currently defined for the multi record aggregate.

The Numbers on the left and right side within the pull–down menu area indicate the minimumand maximum number of definable records. If the maximum number is equal to zero, the maxi-mum number of records is unlimited.

To create a new row for a Multi Record Aggregate

1. Move the mouse pointer to the scroll lists and select the desired record if the new record

shall be inserted before or after an existing record (skip this step if there are no recordsdefined).

2. Select one option from the Insert menu, depending on the insert position within the

scroll list.

3. Select the related data field(s) in the data definition area at the bottom of the pull down

menu and enter the attribute value(s). Attribute data of multi–record aggregates can be

entered in alomost the same manner as attribute data for single–record aggregates.The only difference is, that by pressing the Enter button, the attribute data will not only

be checked for type conormance, but as well be inserted in the list, assuming that no er-

rors are found.

4. Select the highlighted record within the list to fill in the entered data into the list (if the

record has not already been updated).

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


5. Repeat step 3 to step 4, if several records shall be created.


18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


18.4 DATA ENTERING FOR COMPOSITE AGGREGATES

A so called composite aggregate is an aggregate on higher level consisting of more than one sim-ple aggregates.

Relationships and dependencies between the aggregates of a composite aggregate may be definedby the variant part and the foreign key reference.

For a subset of the aggregates of a composite aggregate a variant part can be defined which issimilar to a variant record in ADA. One special attribute of an aggregate represents the discrimi-nant. Within the DDED Composite Aggregate window the attribute which represents the discriminant,is marked by the identifier +. Depending on the value of this attribute other simple aggregatesof this composite aggregates become valid (so called variant aggregates).

A foreign key attribute is a reference to one or more other aggregates within the composite aggre-gate (i.e. other aggregates of this composite aggregate have the same attribute). The name of thisforeign key attribute is the same in all referenced aggregates.

Within the DDED Composite Aggregate window the attribute which represents the foreign key,is marked by the identifier * .

All foreign key attributes of the same composite aggregate for one end item have the same value.The user needs to enter the value only once, DDED automatically updates all foreign key attrib-utes of the composte aggregate, when the user enters a vaule for this attribute.

How to enter data into screen forms of composite aggregates having variant aggreagtes and for-eign key attributes is described in detail in the following parts.

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Foreign Key Identifier Discriminant Identifier

A

B

DC

Figure 202.DDED window showing a composite aggregate with Foreign Key and Dirs-criminant Identifier

A Menu bar

See the description for single record aggregates, section 18.3.1.

B Data definition area

Area where the attribute data values of the multi record aggregates will be defined. It containsfields for data entering and displays the related attribute data types, e.g Raw value Type. The han-dling of data entry is equal to the one of ’Multi Record Aggregate Data Entry’ described in section18.3.2.

C Command area

See the description for single record aggregates, section 18.3.1.

D Message bar

Messages as response on user actions are displayed in the area at the bottom of the window.

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Define Data for a Composite Aggregate with a Variant Part

1. Select or create an end item of type EGSE_FLOAT_MEASUREMENT and start theDDED.

2. Select View–>[composite aggregate to be modified] (e.g. Analog Calibration) from

the DDED main window.

The aggregate content part shows the selected aggregates attributes. The attribute which repre-sents the discriminant is marked by the identifier +.

3. Open the pull–down menu by pressing on the button on the right side of the text entry

field. The menu shows the valid enumeration values, e.g. IDENTICAL, POINT_PAIRS,

POLYNOM.

Figure 203.DDED window showing a composite aggregate with discriminant

4. Select one item from the selection list.

After the selection has been made, the aggregate contents will be updated showing the new attrib-utes thet belong to the selected discriminant value. Each enumeration type has its own descriptionand therefore its own data entry fields.

Figure 204. displays an example of an aggregate with a discriminant. When the enumerationPOINT_PAIRS has been selected, the data definition area changes as it is shown. The compositeaggregate is composed of a multi record aggregate called ’Analog Point Pairs’.

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 204.DDED window showing composite aggregate after discriminant selection

5. Insert the attribute values of the simple aggregates and/or multi record aggregates as ex-

plained in the sections above.


18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Define Data for a Composite Aggregate with a Foreign Key Attribute

1. Select or create an end item of type EGSE_PREDEFINED_TC and start the DDED.

2. Select View–>[composite aggregate to be modified] (e.g. Parameter Raw Value de-scription) from the DDED main window.

The aggregate content part is updated to show the selected aggregates attributes. The attributewhich represents the Foreign Key is marked by the identifier * .

1. Move the mouse pointer to the scroll lists and select the desired record if the new record

shall be inserted before or after an existing record (skip this step if there are no records

defined).

2. Select one option from the Insert menu, depending on the insert position within the

scroll list.

3. Select the related data field(s) in the data definition area at the bottom of the pull down

menu and enter the attribute value(s). Attribute data of multi–record aggregates can be

entered in alomost the same manner as attribute data for single–record aggregates.The only difference is, that by pressing the Enter button, the attribute data will not only

be checked for type conormance, but as well be inserted in the list, assuming that no er-

rors are found.

4. Select the highlighted record within the list to fill in the entered data into the list (if the

record has not already been updated).

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


By inserting the composite aggregate record, the window is extended by the aggregates contain-ing variant records and foreign key attributes. An example is shown in figure 205. (use the scroll-bar on the right of the DDED window to make the aggregates visible).

Foreign Key Reference

Attributes of the aggregate containing a Foreign Key attribute

Figure 205.DDED window showing a composite aggregate with a Foreign Key

5. Insert the attribute values into the aggregates referenced by the foreign key. The data

entering can be performed as explained in section 18.3.2. The foreign key attribute field

will be filled automatically.

6. Repeat step 2. to step 5. if several composite aggregate records shall be created.


18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


18.5 PATHNAME SUPPORT (PNS)

The data entering of attribute values of type pathname is supported by the Pathname Support(PNS) window. It is a comfortable way to enter the pathname related information. The PNS maybe used by different applications running on one workstation. Whenever pathnames have to beentered, the PNS window will pop up.

A

B

C

D

E

Figure 206.Pathname Support Window

A Information area

The information area displays the tool that has invoked the PNS. In case PNS has been called bythe DDED further information about the end item name, aggregate and attribute for which a path-name reference shall be defined is displayed.

Application

Contains the name of the tool which has started the PNS (e.g. DDED, CLS etc.).

Pathname

Contains the pathname of an end item.

Aggregate

Contains the MDB aggregate name for which the PNS is called.

Attribute

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Contains the MDB attribute name for which the PNS has been called.

Help Button

The help button displays help information about the PNS window.

B Mode area

The Mode area allows to show the actual end item pathname (pathname mode), or to switch toanother CDU version (CDU version mode). These two modes have different selection lists. TheFilter and Goto fields will be changed when switching to another mode.

CDU

With the CDU button the CDU version mode may be selected. The field behind the button dis-plays the actual selected CDU/CCU version.

Pathname

With the Pathname button the pathname mode may be selected. The field behind the button dis-plays the actual selected pathname.

Filter

The filter button and fields are for the preparation and displaying of the actual filter. Wildcards(* and ?) may be used within the filter specification.

The Filter–>Actual button applies the strings inside the filter text fields as the actual filter. Thefilter apply is also done by pressing the return key inside one of the filter text fields.

The Default/All button use the default filter to update the selection list elements.

The last 9 defined filters are added to the filter selection list.

Goto

With the Goto function the first element marching the criterion specified in the goto entry field-will be select in the selection list.

The Goto menu operations are the same as for the Filter operations.

C Selection lists

Dependant on the actual mode the displayed items will be:

� in pathname mode the actual accessible end items with their pathname and typeare displayed.

� in CDU version mode the actual accessible CDU versions with their relatedpathname, version and MDB instance are displayed.

D Command area

The command area contains three buttons to perform operations on the selected pathname:

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Quit

Quits the PNS without returning a pathname.

Apply

Send the selected pathname to the calling application. Thereafter the PNS window is iconized.

Reject

Cancel the PNS operations without returning a pathname. Thereafter the PNS window is ico-nized.

E Message bar

Messages in response to user actions are displayed here.

To use the PNS

It is prerequisite that the PNS has been started from an application.

In the mode area, the CDU / CCU version is displayed and the selection list displays the pathnamesthat may be referenced.

If the required pathname reference is not in the actual configuration scope, execute step 1., other-wise continue with step 4.

1. Select the CDU button to switch to the CDU version mode.

The selection list is changed and the possible CDU selections are shown.

2. Select the desired CDU version, so that it becomes highlighted.

3. Select the Pathname button to switch to the pathname mode.

4. If required, use the Filter and/or the Goto functions to restrict the pathnames in the

selection list to a subset.

5. Select the desired pathname reference, so that it becomes highlighted.

6. Select the Apply button to transfer the pathname reference to the application.

The PNS window will be iconized, and the communication to the calling application is finished.The application will remain iconized until being called by another application.

7. If the PNS is no longer required, the Quit button has to be pressed.

18–4

CGS–RIBRE–SUM–00032 03.07.2015– –18–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


33


19–4

CGS–RIBRE–SUM–00032 03.07.2015– –19–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


19 CUSTOMER SPECIFIC IMPLEMENTATIONS

19.1 MISSION BUILT FACILITY – MBF

19.1.1 MBF Identifier Support

The MBF identifier is the Program Unique Signal Data Identifier (PUI) as defined in the NASASSPS document. The PUI has a length of 13 characters. A part of the PUI corresponds to the path-name of the end item. Each end item is identified by a PUI therefore all end items have to havethe aggregate representing the PUI. The MBF identifier should be handled as an instance of a for-eign key.

The Signal PUI has been defined within DADI–MA so that the direct end item access via the for-eign key Signal PUI is possible in I_MDB. The window for signal PUI parameter data entry isshown in figure 207.

Figure 207.Direct end item access via Signal PUI

19.1.2 Foreign Key Support

Please refer to the common operation ’Foreign Key Support’, section NO TAG of this document.

19.1.3 Consistency Checker – MBF related special checks

MDA provides special checks for the MBF related end–items. For more information about theconsistency checker please refer to the section 13 of this document.

19.1.4 Batch Data Entry

The Batch Data Entry concept and mechanisms are described in the section 15 of this document.

19–4

CGS–RIBRE–SUM–00032 03.07.2015– –19–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


19.2 MATRIX–X INTEGRATION

The Matrix–X integration functions provided in I_MDB allows to start the Matrix–X tool. Ma-trix–X is integrated into the MDB via the flexible tool mechanism.

The Matrix–X functions in I_MDB are attached to Items which are assigned to the typeMX_MODEL. This Item–Type has been defined with DADI–MA. In DADI–MA the Matrix–Xtool has been attached to the MX_MODEL type within a CDU scope and CCU scope.

Figure 208.MX_MODEL definition in DADI–MA

To start the Matrix–X tool, it is prerequisite that an Item with the type MX_MODEL has beendefined in a CDU and/or CCU scope.

To start the Matrix–X tool:

1. Navigate to the Item of the type MX_MODEL in the related CDU or CCU scope.

2. Select the Item of the type MX_MODEL.

3. Within the user tree node area, press the right mouse button to pop up the command

menu.

4. Select Tools–>MATRIXx Editor... to start and enter the Matrix–X tool.

19–4

CGS–RIBRE–SUM–00032 03.07.2015– –19–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 209.Matrix–X Editor start

The Matrix–X Tool will be entered where the user can continue on preparation his simulationmodel. When the work is finished he has to exit the Matrix–X tool and will return to the ’I_MDBNavigator’ window.

The Matrix–X Start program is a unix process which remains when the program execution hasbeen finished. The process can be iconised and it can be stopped by the Quit command.

19–4

CGS–RIBRE–SUM–00032 03.07.2015– –19–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


34


20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


20 ADD SYSTEM TREE VERSION

The Add System tree Version (ASV) is a tool to copy CDU versions (or a whole CCU versionscope) from one system tree version to another, but it allows to copy items only within the samesystem tree. The destination system tree has to be in status FROZEN in order to be able to startthe ASV.

The next section explains how to start the ASV tool within I_MDB.

20.1 START THE ADDITION OF CCU/CDU VERSION

This function is activated within the existing ’IMDB: System Tree Version’ window. Within this windowthe user selects the destination system tree version. After the choice select the menu item ’Add System TreeVersions...’ in the ’Command’ menu of the ’IMDB: System Tree Versions’ window, which is only active forsystem tree versions in status ’FROZEN’. The ’IMDB: CCU/CDU Version Browser’ window pops up.

Figure 210. (I_MDB: System Tree Versions)

20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


20.2 SYSTEM TREE VERSION WINDOW

Before the user can add any CDU/CCU Versions to the destination system tree, the source system tree versionhas to be selected. It must be different from the destination system tree version, but has to be of thesame element configuration and mission. If the source system tree version is identical with the des-tination version the error message ’Source and destination system tree cannot be identical!’ will bedisplayed.

Figure 211. (IMDB: System Tree Version)

After a correct selection the following information will be displayed in the headline of the main window:

’IMDB: CCU/CDU Version Browser, <Element Configuration>, <Mission>, from System TreeVersion <X> to <Y>’

<Element Configuration>: The actual element configuration name<Mission>: The actual mission name<X>: The source system tree version<Y>: The destination system tree version

The system tree version window disappears from the screen and the ’IMDB: CCU/CDU Version Browser’becomes active. This window offers two modes, i.e. ’Collect CCU version’ mode and ’Collect CDU

20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


version’ mode. The user can switch between these modes via the menu options ’Command–>CollectCCU incl. CDUs’ and ’Command–>Collect CDUs’ ( see.: section 20.3.3 ). The CCU mode is thedefault mode and it will be displayed in the lower right corner. In case of CCU mode all CCU items ( System Tree Path, CCU Name ) will be displayed in the list.Initially no list item is selected and the version list is empty.In case of CDU mode all CDU items ( CDU Path ) will be displayed in the list. Initially no list itemis selected and the version list is empty.

20.3 CCU/CDU VERSION BROWSER

The CCU/CDU Version Browser provides mechanism to collect those CCU and CDU versions, that shallbe copied from the source system tree version to the destination system tree version. The collectedversions are marked in the browser and are also displayed in the ’IMDB: CCU/CDU Version Collec-tion’ window.The browser operates in two modes. In the ’Collect CCU incl. CDUs’ ( see Figure 212. ) the usercan collect all CCU versions that shall be added to the destination system tree version, in ’CollectCDUs’ ( see Figure 213. ) mode respectively all CDU versions.In both modes the browser displays two lists. Depending on the selected mode on the left side the’System Tree Path’ or ’CDU Path’ list is displayed and on the right side the corresponding versionlist.The version list enables to collect single CCU or CDU version whereas the ’CDU – system tree path’list allows to collect complete CCUs or CDUs containing all corresponding versions.

Figure 212. (CCU/CDU Version Browser, main window in CCU version mode)

20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 213. (CCU/CDU Version Browser, main window in CDU version mode)

20.3.1 Single/Multi Selection on ’System Tree Path’ or ’CDU Path’ list

These lists are multi selection list. If one CCU or CDU is selected the corresponding versions are displayedin the versions list.If more than one list item is selected all not existing CCU/CDU versions in the destination system tree versionare chosen for collection. In the version list a string ’–––––– All ––––––’ will be displayed.After selection of the desired CCU/CDU versions press the ’Collect’ button to transfer the selections to the

’IMDB: CCU/CDU Version Collection’ window ( see section 20.4 ) The collected list items will be markedwith a checked box. The collection window contains all CCU/CDU versions being candidates for the addoperations. The selection of CCU/CDU versions and the add operation can be performed several times.

Interpretation of list icons:

· Empty BoxNo CCU/CDU version exists in the destination system tree version yet.No CCU/CDU version is collected for the add operation to the destination system tree ver-sion.

· Half filled BoxSome CCU/CDU versions already exist in the destination system tree version.

· Full filled BoxAll CCU/CDU versions exist in the destination system tree version.

· Checked BoxOne or more versions are collected for the add operation to destination system tree version.

20.3.2 Single/Multi Selection on Version(s) list

This list is a multi selection list. If only one list item in ’System Tree Path’ or ’CDU Path’ list is selectedthe versions of this CCU/CDU are displayed in the version list.

20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


After selection of all desired CCU/CDU versions press the ’Collect’ button to transfer the selections to the

’IMDB: CCU/CDU Version Collection’ window ( see section 20.4 )Only the versions with an empty box will be transfered to the ’IMDB: CCU/CDU Version Collection’ win-dow. The items will be check marked. Full filled boxed items will be ignored because they are already exist-ing in the destination system tree version.

Interpretation of list icons:

· Empty BoxVersion does not exist in the destination system tree version and is not collected.

· Full filled BoxThis version already exists in the destination system tree version

· Checked BoxThis version is collected for the add operation to the destination system tree version.

20.3.3 Command Menu

Figure 214. (Command Menu)

· Select System Tree Version...This menu allows to select/change the source system tree version.Since the ’IMDB: CCU/CDU Collection’ window may only contain items of one system tree

20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


version, the window must be empty for this operation.In case it contains some items the system asks for discarding these items prior to system treeversion change.

· Collect CCU incl. CDUsThis menu item allows to switch to the CCU incl. CDU versions collection for the samesource system tree version.Since only one mode i.e. ’Collect CCU incl. CDUs’ or ’Collect CDUs’ can be active at a time,the ’IMDB: CCU/CDU version Collection’ must be empty. In case it contains some items thesystem asks for discarding these items prior to mode change.

· Collect CDUsThis menu item allows the user to switch to the CDU versions collection for the same sourcesystem tree version.Since only one mode i.e. ’Collect CCU incl. CDUs’ or ’Collect CDUs’ can be active at a time,the ’IMDB: CCU/CDU version Collection’ must be empty. In case it contains some items thesystem asks for discarding these items prior to mode change.

20.3.4 Edit Menu

Figure 215. (Edit Menu)

20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


· Filter...Activate the filter mechanism for ’System Tree Path’ or ’CDU Path’. A filter window ( seesection 20.6 ) pops up.

· Show CCU/CDU Collections...Activate the ’IMDB: CCU/CDU Version Collection’ window, if it was dismissed before.

· Select AllSet all items of the ’System Tree Path’ or ’CDU Path’ list to selected status.

· Deselect AllSet all items of the ’System Tree Path’ or ’CDU Path’ list to deselected status.

· CollectTransfer all selected item of the ’System Tree Path’ or ’CDU Path’ list to the ’IMDB: CCU/CDU Version Collection’ window.

· RemoveRemove all selected items of the ’System Tree Path’ or ’CDU Path’ list from the ’IMDB:CCU/CDU Version Collection’ window, which were transfered with the ’Collect’ commandbefore.

20.3.5 Version List Menu

Figure 216. (Version List Menu)

· Select AllSet all items of the ’Version(s)’ list to selected status.

20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


· Deselect AllSet all items of the ’Version(s)’ list to deselected status.

· CollectTransfer all selected items of the ’Version(s)’ list to the ’IMDB: CCU/CDU Version Collec-tion’ window.

· RemoveRemove all selected items of the ’Version(s)’ list from the ’IMDB: CCU/CDU VersionCollection’ window. which are transfered with the ’Collect’ command before.

20.4 CCU/CDU VERSION COLLECTION

Figure 217. (CCU Version Collection)

Figure 218. (CDU Version Collection)

The window contains all collected CCU/CDU versions which were selected in the ’IMDB: CCU/CDU Ver-sion Browser’ window before the ’Collect’ command.

· ApplyWith the ’Apply’ button the addition of the CCU/CDU versions from the source system treeversion into the destination system tree version will be started.For user information a progress window pops up ( see section 20.5 )

· RemoveRemove all selected list items of the ’IMDB: CCU/CDU Version Collection’ window whichare transfered with the ’Collect’ command before.

20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


20.4.1 Collected List Menu

· Select AllSet all list items of the ’IMDB: CCU/CDU Version Collection’ window to selected status.

· Deselect AllSet all list items of the ’IMDB: CCU/CDU Version Collection’ window to deselected status.

· RemoveRemove all selected list items of the ’IMDB: CCU/CDU Version Collection’ window whichare transfered with the ’Collect’ command before.

20.5 PROGRESS WINDOW

After execution of the ’Apply’ button in the ’IMDB: CCU/CDU Version Collection’ window, the progresswindow pops up.

Figure 219. (Progress window)

· AbortAbort the current operation. All changes performed until the ’Abort’ button was pressed aretaken back.

20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


20.6 CCU AND CDU VERSION BROWSER FILTER

The ’IMDB: CCU/CDU Version Browser Filter’ is activated via the menu ’Edit–>Filter...’ of the Browserwindow. The appearance depends on the selected mode. The following figure shows the Browser windowin CCU incl. CDUs mode.

Figure 220. (Browser Filter window in CCU incl. CDUs mode)

The filter options allows the user to limit the CCUs displayed in the browser to the following filter options:

· CCU Path

Selected all CCUs matching CCU path

eg.: ”\FR*SE\*”

· CCU Name

Select all CCUs matching the CCU name.

eg.: ”CC*_FIRS*”

· CCU Version

Select all CCUs matching version, issue, revision.

eg.: ”1.*.3”

· ApplyThe ’Apply’ button refreshes the list of ’System Tree Path’ or ’CDU Path’ in the ’IMDB:CCU/CDU Version Browser’ window with the settings of the filter options.

20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 221. (Browser Filter window in CDU mode)

The filter options allows the user to limit the CCUs displayed in the browser to the following filter options:

· CDU Path

Selected all CDUs matching the CDU path.

eg.: ”\FR*SE\*”

· CDU Version

Select all CDUs matching version, issue, revision, testversion

eg.: ”1.*.7.*”

· ApplyThe ’Apply’ button refreshes the list of ’System Tree Path’ or ’CDU Path’ in the ’IMDB:CCU/CDU Version Browser’ window with the settings of the filter options.

20–12

CGS–RIBRE–SUM–00032 03.07.2015– –20–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


35


21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


21 EXCELMDB

ExcelMDB allows the editing of attribute values in the MDB with Excel on a PC. It uses BDE andCREATE_BDE_FILES for data transfer to and from the MDB and converts the files to Excel format.

The next section gives an overview about ExcelMDB functionality

21.1 OVERVIEW

ExcelMDB enables the user to read/write Enditem data of the Mission Data Base (MDB) into/from an Excelspreadsheet.

The Enditem data, identified by their pathnames, consist of tables called aggregates. The items of one aggre-gate are called attributes. There are two kinds of aggregates in the MDB: Single record aggregates, whichcontain one aggregate entry and multi record aggregates containing multiple aggregate entries. Each Endi-tem belongs to one Enditem type.

To read/store MDB data in/from Excel the structure of an Enditem must be represented in an Excel spread-sheet. This is done in the following way:

· Each row of an Excel spreadsheet contains one Enditem identified by his pathname.

· Each column contains one attribute value of one aggregate belonging to this Enditem.

Because of the two kinds of aggregates there are two kinds of spreadsheets to represent the Enditem data:

· a so called Mixed spreadsheet containing singlerecord and/or multirecord aggregates with one rowper enditem, different Entry Numbers are placed in different columns, and

· a Multirecord spreadsheet containing one multi record aggregate of one Enditem type, having one rowper Entry Number

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


21.1.1 Structure of a Mixed Spreadsheet

Figure 222.An ExcelMDB spreadsheet of type MIXED

The header consists of the first four rows, where only Cell A1 should be modified by the user.

· The first row can be filled out by the user with free choosable text, but it has to end with the character>. ExcelMDB adds information about the Configuration Unit and date/time in this row after reading/writing data from/to MDB.

· The second row is reserved for the aggregate names. The first column of this row contains the keywordAggregate the second column the key word Enditem Type, both used by ExcelMDB. In the followingcolumns the aggregate names are listed

· The third row is reserved for the attribute names. The first column of this row contains the key wordAttribute, the second column is empty. In the following columns the attribute names are listed.

· The fourth row is reserved for the Entry Numbers. The first column of this row contains the key wordEntry Number, the second column is empty. In the following columns the Entry Numbers of the aggre-gates are listed.

· The following rows contain the data of the Enditems. Each row begins in the first column with theEnditem pathname followed in the second column by the Enditem type of this Enditem. The followingcolumns contain the data of the Enditem.

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


21.1.2 Structure of a Multirecord Spreadsheet

Figure 223.An ExcelMDB spreadsheet of type MULTIRECORD

Again, the header consists of the first four rows, where only Cell A1 should be modified by the user.

· The first row can be filled out by the user with free choosable text, but it has to end with the character>. ExcelMDB adds information about the Configuration Unit and date/time in this row after reading/writing data from/to MDB.

· The second row is reserved for the aggregate names. The first column of this row contains the keywordAggregate used by ExcelMDB. In the following columns the aggregate names are listed

· The third row is reserved for the attribute names. The first column of this row contains the keywordAttribute, the second column is empty. In the following columns the attribute names are listed.

· The fourth row is reserved contains in the first column the keyword Enditem Type: followed by theEnditem type of the listed Enditems below.

· The following rows contain the data of the Enditems. Each row begins in the first column with theEnditem pathname followed in the second column by the entry number. The following columns con-tain the data of the Enditem.

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


21.2 GETTING STARTED

21.2.1 Client installation (Windows PC)

Using FTP, transfer the tar file located in $MDA_HOME/util/excel_mdb/x86 from your CGS unix worksta-tion. Create a directory and unpack the tar file using Winzip or any other packer able to handle tar files.

21.2.2 Server installation

Due to the fact that ExcelMDB can either use SSH/SFTP or REXEC/FTP as connection method to communi-cate with the server, you either have to configure SSH and SFTP or REXEC and FTP daemons on the server.

Most Linux installations install a SSH server by default, so using SSH to connect to a Linux server shoulddo without further server configuration.The same applies to REXEC/FTP on Solaris servers.

21.2.2.1 REXEC/FTP

In case you want to use REXEC/FTP connections to a Linux server, configure the server that the followingdaemons are running:

· FTP (a daemon doing real ASCII transfers is required)

· RLogin

· RExec

· RSh

The step above may be skipped if the server is running Solaris, since Solaris has all necessary daemons en-abled by default.

On the server, make an entry in the users ~/.rhosts file that does only contain the IP address of the PC on anew line. If the file does not exist, create it. After that, make sure that the command rsh <servername>“source .login;ls” does not abort before showing the directory contents.

You also have to make sure that the client PC is visible on the server by using ypcat hosts.

21.2.2.2 SSH/SFTP

In case you want to use SSH/SFTP connections to a Solaris server, configure the server that a SSH daemonis running.

The step above may be skipped if the server is running Linux, since Linux has the SSH daemon enabled bydefault.

21.2.2.3 JAVA installation

The server part of ExcelMDB requires a JRE 1.4 or higher installed in one of the following directories

· $GSAF_TOOLS/jre–1_4

· /tools/jre–1_4

· $GSAF_HOME/tools/jre–1_4

In order to have maximum ExcelMDB performance, the directory containing the JRE should not be mountedover the network, but should reside on a local disk.

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


21.2.3 ExcelMDB Client Configuration

The ExcelMDB client configuration is handled by the login window. It contains the login and oracle informa-tion that is neccessary for ExcelMDB. The login dialog pops up every time a connection to the MDB is re-quired. This gives the user the possibility to add a new connection or modify existing connections at runtime.

The login dialog furthermore asks for the server and oracle passwords and stores these passwords as longas Excel is still running.

Figure 224. ExcelMDB Login Window

21.2.3.1 Connection Groups

New Group: Add a new group to the connection list.Delete Group: Delete the selected group.Copy Group: Performs a copy of the selected connection group and appends it to the

connection list.Move Up: Moves the selected group in the connection list one row position up.Move Down: Moves the selected group in the connection list one row position down.Import: Imports old configuration files (config.txt).

21.2.3.2 Connection Details

The configuration looks like: Item Example Description– Group: cgsadmin/tf1–dbs Free choosable (not empty) text as header for the following

information. It will be displayed in the Login window.– User: cgsadmin Username to be used for CGS server account

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


– CGS Host Name: tf1–dbs Name of the CGS server– CGS Host IP: 149.243.228.141 IP address of the CGS server– Connection Type: REXEC/FTP The connection type to use to connect the CGS server– Oracle Host Name: tf1–dbs Name of oracle server– Oracle Host IP: 149.243.228.141 IP address of the oracle server– Oracle SID: cgs5 Oracle SID of the database to which to connect– Oracle Port: 1521 Port address where oracle communication takes place

Using different hosts as CGS Host and Oracle Host, or a user home directory that is mounted overa network may reduce performance dramatically.

21.2.4 Start ExcelMDB

Use the windows explorer to navigate to the directory where the tool has been installed and start ex-celmdb.bat via double–click. The Excel main window comes up asking wether macros should be enabled.Enable the macros to have ExcelMDB functionality within Excel. Excel now contains a MDB Activitiesmenu entry.

21.3 EXCELMDB FUNCTIONALITY

21.3.1 Open MDB Browser

Press menu item Open MDB Browser in the pop up menu MDB Activities of the Excel main menu. The Loginwindow appears. To log on to the database, select the desired group from the Group combo box, provide allnecessary passwords and press the Connect button. This opens the MDB Browser window.

Figure 225.The MDB Browser window

The MDB browser window can be handled like a file manager. The left–sided part of the window (MDBNavigation Tree) displays the nodes (Virtual Nodes, CDUs, User Tree Nodes etc.) that are part of MDB. A

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


single click on a node actualizes the right part of the window. The upper component of the right part containsthe description of the selected node (Node Information). Below that are the following components in verticalorder:

· The System Tree Version. If a system tree in the MDB Navigation Tree is selected, the system tree canbe changed. All depending data will be updated. If there is no system tree in the MDB Navigation Treeselected the combo box is disabled.

· The CCUs. If a node in the MDB Navigation Tree is selected which contains CCUs, it can be selectedin the combo box, otherwise the combo box is disabled.

· The CCU versions. In case of a CCU is selected by the user a CCU version can be selected in the combobox. A control message appears displaying the selected scope including the CCU internal version. Alsothe Continue button will be enabled.

· The CDU versions. In case of the selected node in the MDB Navigation Tree is of type CDU the useris enabled to select a CDU version. A control message appears displaying the selected scope includingthe CDU internal version. Also the Continue button will be enabled.

· The Continue with CU found in SpreadSheet Header, Continue and Cancel buttons. The first but-ton is only visible in case an operation has been started on an ExcelMDB Spreadsheet containing CUinformation in the Cell A1, all three buttons are only visible in case the Browser has been started auto-matically during a Read or Write action.

The login and Browser windows are needed for nearly all ExcelMDB operations.

In case of the user has selected a CCU or CDU version, the menu item Open Configuration in the menuConfiguration becomes enabled. So the user is enable to navigate down to user tree level.

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


21.3.2 Create Excel spreadsheet header

This feature enables the user to create an Excel spreadsheet header that represents the MDB data structurein an Excel spreadsheet. After selection of menu item Create Excel spreadsheet header from the MDB Activ-ities menu and database logon the ExcelMDB Spreadsheet Header Creator pops up.

Figure 226. The ExcelMDB Spreadsheet Header Creator window

At startup, the left part shows a tree containing all Enditem Types. Each type has one or more aggregatesand each of the aggregates has one or more attributes.

Mandatory Aggregates are represented using a bold font, multirecord aggregates are denoted by a trailing(multirecord) behind the aggregate name.

Attribute names are followed by the MDA data type of the particular attribute.

Selecting a checkbox adds the Attribute (or all Attributes of an Aggregate or Enditem Type) to the PreviewPane, unselecting a checkbox removes the Attribute(s) from the Preview again. The preview pane shows howthe spreadsheet is going to look like once it has been saved and loaded into Excel.

In case an ExcelMDB spreadsheet of type MIXED is created (this can be changed by selecting the appropriatecheckbox in the Spreadsheet Type area), a column is added for every Entry Number that is currently dis-played in the Multirecord Aggregates area. Naturally, this does only apply for multirecord aggregates.

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


The checkbox Show full spreadsheet preview can be used to show/hide the rows and columns of the spread-sheet preview that do only contain keywords.

21.3.3 Modify Excel Spreadsheet Header

This menu item enables the user to modify the header of the currently opened ExcelMDB spreadsheet. Modi-fication of headers is only allowed for empty ExcelMDB sheets.

21.3.4 Update Excel Spreadsheet

This menu item enables the user to update the data of an existing Excel spreadsheet. Only the Enditems dis-played in the loaded spreadsheet will be updated.

Press menu item Update Excel Spreadsheet in the pop up menu MDB Activities of the Excel command menubar and login to the database. In case a CU in the correct syntax is found in the Cell A1 of the spreadsheet,the ExcelMDB sheet is updated with data from this CCU/CDU. Otherwise a CCU/CDU has to be selectedin the Browser window. After pressing the Continue button of the browser window the Message Windowcomes up informing about the operation progress.After a while (depending on the size of the data to retrieve) it disappears and the User is asked wether hewants to highlight changed data. Depending on the answer an extra spreadsheet is added to the current workbook containing the retrieved val-ues. All values that have been changed are highlighted.

Note: For Enditems of the Excel spreadsheet that are out of scope no values will be displayed.

21.3.5 Read Enditems from CCU/CDU

This menu item enables the user to read data from MDB for an existing Excel spreadsheet header The Endi-tem types to be loaded are selectable by the user. Also a restriction in the pathname of the Enditems the userwill retrieve is possible.

Press menu item Read Enditems from CCU/CDU in the pop up menu MDB Activities of the Excel commandmenu bar, login to the database and select either a CCU or CDU. After pressing the Continue button of thebrowser window the Select Enditem Types and Pathname window comes up allowing to select the EnditemTypes to read and to make a restriction on the Enditem pathnames.

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Figure 227. The Enditem Type and Pathname selection window

In case of Multi record spreadsheets, the button >> is disabled and only one Enditem Type is selectable.

Make your selection and press the Continue button. The Message Window comes up informing about theoperation progress.After a while (depending on the size of the data to retrieve) it disappears and the User is asked wether hewants to overwrite the current file.

21.3.6 Write Worksheet Data Into MDB

This menu item enables the user to store the data of the actual loaded Excel spreadsheet in MDB. As resulteither 4 or 6 files are created:

· The input file. This file is the original file loaded into MDB. The tool creates the filename <filename–INP.xls> from the original filename <filename.xls>

· A file that contains the data of the Enditems before loading the input data file into MDB. The toolcreates the filename <filename–WAS.xls> from the original filename <filename.xls>

· A file that contains the data of the Enditems after loading the input data file into MDB. The tool createsthe filename <filename–IS.xls> from the original filename <filename.xls>

· A file that contains the CDU versions of the Enditems which are affected when loading the input datafile into MDB. The tool creates the filename <filename–CDU.xls> from the original filename <file-name.xls>

The next two files are only written if the user selects to create DIFF files:

· A file that contains the data of the Enditems after loading the input data file into MDB. The changeddata in compare to the Was–File are highlighted. The tool creates the filename <filename–DIFF.xls>from the original filename <filename.xls>

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


· A file that contains the data of the Enditems which are changed after loading the input data file intoMDB. The tool creates the filename <filename–DIFF–LIST.xls> from the original filename <file-name.xls>

For each write process a <directory_selected_by_the_user\filename\Ri> directory is created, where i is aninteger value 1 .. n which will be added if the write process for this excel file will be done multiple times.The 6 files will be stored in this directory.

Press menu item Write Worksheet Data to MDB in the pop up menu MDB Activities of the Excel commandmenu bar, login to the database and select either a CCU or CDU. After pressing the Continue button of thebrowser, a confirmation window pops up asking wether you really want to write data to the MDB.

Figure 228. The Write Confirmation window

The confirmation window contains 3 checkboxes that can change the behaviour of the write process:

· delete additional entriesThis checkbox is only available for multirecord spreadsheets. If the box is checked, the write processdeletes all records from the aggregate that are not part of the spreadsheet. If you remove rows withEntry Numbers from the spreadsheet and check this box, then the rows deleted from the spreadsheetwill be deleted in the MDB.

· write empty cells to MDBBy default, empty cells are not written to the MDB. In order to remove an Attribute value, you eitherhave to insert @ into the cell, or you have to check this box. If it is checked, all empty cells are writtenas empty Attribute values to the MDB.

· create DIFF filesWhen this option is checked, ExcelMDB creates the two additional DIFF files mentioned above. Olderversions of ExcelMDB did not give this choice to the user but created DIFF files for every write pro-cess.

When the Yes button is pressed, the Message Window comes up informing about the operation progress.After a while (depending on the size of the data to store), the message Quit window to return to Excel orQuit window to create difference files appears in the message window. You can now close the window tostart the difference file creation process. After a while the already stored difference file appears as Excelspreadsheet.

Each transfer of Excel data to MDB produces files in the Unix directory ~user/Batch_Data/. These files canbe used for troubleshooting. They are not be deleted by the tool, so the directory must be cleared sometimes.

If there are Enditems in the spreadsheet that are out of scope the tool will try to create them. In this case thetool terminates with an error message.

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Multiple usages of identical pathnames in one mixed spreadsheet are not allowed and cause the tool to anerror message.

21.3.7 Write Workbook Data Into MDB

The function of this menu item is similar to menu item Write Worksheet Data Into MDB.

This menu item enables the user to store the data of the actual loaded Excel workbook (all spreadsheets inactual workbook) in MDB.

21.3.8 Extract CDU Versions

This menu item enables the user to retrieve the CDU versions of the Enditems of the actual loaded Excelspreadsheet data from MDB. As result a file containing the affected CDU versions are listed. Enditems notbelonging to a CDU version are extra listed.

Press menu item Extract CDU Versions in the pop up menu MDB Activities of the Excel command menubar and login to the database. The browser window comes up.

In case you select a system tree, the latest existing CDU versions having Enditems in the spreadsheet willbe shown. If the CDU version is in status FROZEN, then also the latest DEVELOPMENT version will beshown.In case you select a CCU version, the CDU versions in the selected CCU scope having Enditems in thespreadsheet will be shown.

After having pressed the Continue button, the Message window appears. After process completion (this maytake a while), the window is automatically closed and Excel show the CDU list spreadsheet.

21.3.9 Create Difference File (Pathname by Pathname)

This menu item enables the user to display the difference in the data of 2 Excel spreadsheets containing dataretrieved from MDB. 2 files will be created:

· A file containing the spreadsheet data where the difference data will be gray highlighted. In case ofmissing pathnames in the spreadsheets they are marked as ?deleted? at the end of the spreadsheet con-taining the differences.

· A file containing only the data that are different. The pathname, Enditem type, position of the data inthe spreadsheet, old and new value are displayed.

Press menu item Create Difference File (Pathname by Pathname) in the pop up menu MDB Activities ofthe Excel command menu bar. A filename selection dialog pops up. Select or enter the filenames and pressthe Start button to create the difference files. A confirmation window pops up.

After a while (depending on the size of the data) the difference Excel spreadsheet and the file containing onlythe difference data (filename ends with –LIST) appear.

21.3.10 Create Difference File (Cell by Cell)

This menu item enables the user to display the difference in the data of 2 Excel spreadsheets. The size ofcolumns and rows must be equal. The difference data will be gray highlighted.

Press menu item Create Difference File (Cell by Cell) in the pop up menu MDB Activities of the Excel com-mand menu bar. A filename selection dialog pops up. Select or enter the filenames and press the Start buttonto create the difference files. A confirmation window pops up.

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


After a while (depending on the size of the data) the difference Excel spreadsheet appears.

21.3.11 Convert .txt –> .xls (MDB Template)

This menu item enables the user to add the default template to a raw MDB file (a tab delimited textfile).

Press menu item Convert .txt –> .xls (MDB Template) in the pop up menu MDB Activities of the Excelcommand menu bar. A filename selection dialog appears. After pressing the Open button Excel displays theimported spreadsheet.

Note that it is not possible to import arbitrary text files into ExcelMDB spreadsheets. The text files muststrictly conform to the ExcelMDB internal text file structure.

21.4 BATCHMODE

The ExcelMDB batchmode allows to separate job definition and job execution. It provides a GUI to defineExcelMDB actions to be executed one after another and therefore makes it possible to create ExcelMDBspreadsheets and defining the jobs during the day, and to execute them during the night to minimize perfor-mance bottlenecks during the working hours.

21.4.1 Starting the ExcelMDB batchmode

Once you have correctly adapted the ExcelMDB configuration file as described in 21.2.3, you can start thebatchmode GUI by navigating to the ExcelMDB home directory with the Windows Explorer and by double–clicking on file batchmode.bat.

This batchfile can as well be used to start an already defined project without further user interaction. In orderto start an already defined project, the following arguments can be applied on the MS–DOS prompt com-mand line:

batchmode.bat [–<group n> <unix pw n> [<mdb pw n>]] [–run] [project filename]

All parameters are optional, not specifying any parameter has the same effect as double–clicking on thebatchmode.bat file in the Explorer.

The meaning of the parameters is as follows:–<group> is the name of a group from the configuration file and has always to be combined with

the unix password (or both passwords). Note that the group name is preceded by a – sign.<unix pw> is the unix password of the group specified in the previous argument<mdb pw> is the MDB password of the group specified before–run invokes the batchmode in run–mode and only opens and runs the specified project

file. No further user interaction is needed. This has to be the last argument before theproject file name.

<project file> the name of an already existing ExcelMDB batchmode project file. The project filename has to end with .bprj and has to be the last argument.

It is also possible to specify passwords for more than one group on the command line. In order to do this,just repeatedly specify the arguments [–<group n> <unix pw n> [<mdb pw n>]].

21.4.2 The ExcelMDB batchmode GUI

The batchmode GUI consists of a main menu, a toolbar, the job table and the status bar. The main menu holdsmenu entries for all available actions, whereas the toolbar only holds the most commonly used actions. The

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


job table holds all information about the current project and contains one line per job. Each line holds allthe information needed to execute the job. The status bar gives information about currently active processes,errors or information messages.

21.4.2.1 The main menu

The main menu contains the following menus and entries:File–>New Discards the actual project and opens a new, empty and untitled projectFile–>Open Opens an existing projectFile–>Save Saves the current projectFile–>Save As Saves the current project under a new nameFile–>Save Copy As Saves a copy of the current project under a specifiable nameFile–>Quit Terminates the batchmodeEdit–>Copy Copies the content of the currently selected table cellEdit–>Paste Pastes the value from the clipboard to the currently selected table cellEdit–>Cut Cuts the contents from the currently selected table cellEdit–>Insert row before Inserts a new, empty job before the currently selected row, or at the beginning

of the project if no row is selectedEdit–>Insert row after Inserts a new, empty job after the currently selected row, or at the end

of the project if no row is selectedEdit–>Delete row Deletes the currently selected rowEdit–>View job details Opens a window showing all parameters belonging to the selected jobHelp–>About Displays tool version information

21.4.2.2 The toolbar

In addition to the main menu, most functionality is available in the toolbar. Besides the main menu function-ality, there are two more buttons.

The run button (the second rightmost toolbar button) starts the execution of all defined jobs immediately aftera confirmation has been issued.

The run at button (the rightmost toolbar button) starts the execution of the project at the time specified inthe time widget in the toolbar. If the time specified there lies in the past, then the project is executed immedi-ately. In the meantime, before the execution begins, the tool is minimized to the system tray. The system traymenu allows the cancelling of the job prior to execution time as well as the termination of the batchmode.

21.4.2.3 The job table

Every single row of the job table visualizes one ExcelMDB action. It consists of the following columns:No The number of the job. This is not used by ExcelMDB but is only available

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–15


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


to identify a single job easily.Group The group known from ExcelMDBUnix Password The unix password (similar to ExcelMDB)MDB Password The MDB password (similar to ExcelMDB)Action What to do with the specified Excel file. This field can have the following

values:Read read all enditems (see 21.3.5)Write write the spreadsheet contents to the MDB without

creating any missing enditems (see 21.3.6)Write/Create write the spreadsheet contents to the MDB with

creating any missing enditems (see 21.3.6)Update update spreadsheet values (see 21.3.3)

Depends on If specified, makes execution of this job depending on a successful executionof the job specified here

Excel file The name of the Excel fileScope The configuration scope in the MDB (as specified by the browser window

when using ExcelMDB)WAS–IS–INP directory The directory where ExcelMDB will place the WAS–, IS– and INP– files

(similar to ExcelMDB).This parameter is only valid for Actions Write and Write/Create.

Enditem types The Enditem types for which data is to be retrieved(similar to ExcelMDB).This parameter is only valid for Action Read.

Pathname mask The pattern to apply to the retrieved Enditems. This is useful for further re–stricting the Enditems to be read.(similar to ExcelMDB).This parameter is only valid for Action Read.

Delete additional rows Wether to remove multirecord entries from an aggregate when it is not specified in the spreadsheet.(similar to ExcelMDB).

Write empty cells Wether to store empty cells into the MDB.(similar to ExcelMDB).

Some of the values can be filled in by either entering text into the appropriate fields or by pressing the buttonat the left of the column to bring up a dialog.

21.4.3 Project execution

After project execution has been initialized (either by specifying the appropriate command line argumentsor by pressing one of the run buttons), first of all the program checks for missing passwords and tries to com-plete them. This can only be done if you defined more than one job with the same group and have only speci-fied the password for one of the jobs.

Second, the tool checks for missing and invalid parameters.

It then starts one job after another, resolving and using any defined dependencies. The progress is shown ina Project Output window (very similar to normal ExcelMDB operation) and is as well logged to a logfile.This logfile resides in the same directory the project file is in and has the same name, but with extension .loginstead of .bprj

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–16


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


When project execution is finished, the end time is displayed in the message window. The window stays openand has to be closed by hand unless the tool has been started with the –run option.

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–17


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


A typical Project Output window looks like this:

Figure 229.The Project Output window showing a finished Read Job

21.5 REQUIREMENTS

In order to run ExcelMDB properly, you need a– Compaq Professional Workstation AP 400 or compatible PC running

Windows XPMicrosoft Office XP

21.6 LIMITATIONS

ExcelMDB can not handle Aggregates containing Attributes of LONG datatypes, and does only allow selec-tion of Aggregates that have at least one Attribute with the IMDB Display Flag set to ’SHOW ON SCREEN’.

21–18

CGS–RIBRE–SUM–00032 03.07.2015– –21–18


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


36


22–5

CGS–RIBRE–SUM–00032 03.07.2015– –22–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


22 FILE LOADER/EXTRACTOR

22.1 OVERVIEW

These tools provide operations for loading and extracting of complete files or directories into and from theMDB (mission database).

The contents of loaded files are stored in end items of type EXTERNAL_FILE.

The operations are selectable via the menu items provided by I_MDB (Interactive MDB) in CDU or CCUscope:

Tool Name Invocation of Tool on Privilege

File Loader Enditem of Type EXTERNAL_FILE in CCUScope

NORMAL_USER

Enditem of Type EXTERNAL_FILE in CDUScope

NORMAL_USER

CCU Version CONFIGURATION_MANAGER

CDU Version CONFIGURATION_MANAGER

File Extractor Enditem of Type EXTERNAL_FILE in CCUScope

NORMAL_USER

Enditem of Type EXTERNAL_FILE in CCUScope

NORMAL_USER

CCU Version NORMAL_USER

CDU Version NORMAL_USER

22.2 FILE LOADER

22.2.1 Pre–conditions

The source files must exist.

The user must have the read permission for source files of type BINARY, ASCII and DIRECTORY.

For source files of type DIRECTORY the user must also have the executable permission.

22.2.2 Start on Enditem of Type EXTERNAL_FILE

The purpose is to store the content of one file or one directory into one MDB enditem of type EXTER-NAL_FILE. The information about this file must exist in aggregate File Specification. For Loading of a filethe attributes Source File Directory and Source File Name are mandatory. For a directory only Source FileDirectory is needed. The Loader does archive directories with the Unix tar before storing into MDB. Theattribute Description is optional. It is for information only. The Source File Type field is filled by the fileloader . If the attribute Target File Access is empty then the loader does insert the value RWX for executablefiles and SYSTEM_DEFAULT for all other files.

After the start of this tool a window File Loader Tool V3.0 appears. The progress and the success of the execu-tion is shown in this window. The File Loader does check the permissions of the file or directory before load-ing. Errors are reported into the same window.

22–5

CGS–RIBRE–SUM–00032 03.07.2015– –22–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


22.2.3 Start on CCU or CDU Version

It exists two modi for the File Loader on CCU or CDU version:

· Without Loader Info FileThe load information is taken from the aggregate File Specification.

· Use of Loader Info FileThe load information is taken from a Loader Info File.This mode is obsolete and it is not recommended.It exists because of backward compatibility.

The button Use Loader Info File can used for the toggle between the two modi. This button is located in theOptions menu. The menu File –> Save Options makes the change permanent.

22.2.3.1 Without Loader Info File

The purpose is to store the contents of files and directories into all MDB enditems of type EXTERNAL_FILEin CDU or CCU version scope. The information about the files must exist in all aggregates File Specification.For Loading of a file the attributes Source File Directory and Source File Name are mandatory. For a directo-ry only Source File Directory is needed. The Loader does archive directories with the Unix tar before storinginto MDB. The attribute Description is optional. It is for information only. The Source File Type field is filledby the file loader . If the attribute Target File Access is empty then the loader does insert the value RWX forexecutable files and SYSTEM_DEFAULT for all other files.

After the start of this tool a window File Loader Tool V3.0 appears. The progress and the success of the execu-tion is shown in this window. The File Loader does check the permissions of each file or directory beforeloading. Errors are reported into the same window.

22.2.4 Use of Loader Info File (obsolete)

In case of start the loader on a CCU or CDU version it is possible to store all files and/or directories givenby a loader info file into the MDB. The advantage is that the user mustn’t start the file loader on each EXTER-NAL_FILE enditem.

Before the start of file loader it is necessary to create a loader info file.

The structure of loader info file is:

# Loader Info File# <enditem pathname>,<source file>,<destination directory>,[<destination file>]# the source file must be relative to the Loader Info File# the destination file is only needed if destination basename isn’t equal source file basename

<enditem pathname>,<source file>,<destination directory>,[<destination file>]<enditem pathname>,<source file>,<destination directory>,[<destination file>]...

The ’#’ character on the first position of a line is a flag for a command line.The enditem pathname points to an enditem of type EXTERNAL_FILE to be created or updated by the load-er tool. The pathname must be allowed in the CCU or CDU scope.The source file must be relative to the loader info file.The destination file is only needed if destination basename isn’t equal source file basename.Unix environment variables are allowed in the destination directory name.

22–5

CGS–RIBRE–SUM–00032 03.07.2015– –22–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Example for a loader info file:

# Loader Info File for CCU FILE_IO # <enditem pathname>,<source file>,<destination directory>,[<destination file>]\APM\FILE_IO\LOADER_INFO,LOADER_INFO_FILE_IO,$HOME/file_io/out,\APM\FILE_IO\FILE_1,in/FILE_LOADER.tcl,$HOME/file_io/out,\APM\FILE_IO\FILE_2,in/FILE_EXTRACTOR.tcl,$HOME/file_io/out,FILE_EXTRACTOR2.tcl\APM\FILE_IO\FILE_3,in/whatami,$HOME/file_io/out,\APM\FILE_IO\FILE_4,in/directory_1,$HOME/file_io/out,\APM\FILE_IO\FILE_5,in/directory_2,$HOME/file_io/out,dir_2

After the start of this tool the user must choose the loader info file via a file browser. The progress and the success of the execution is shown in the File Loader Tool window. The File Loader does check the permissions of each file before loading. Errors are reported in tool window.

22.3 FILE EXTRACTOR

22.3.1 Start on Enditem of Type EXTERNAL_FILE

The purpose of this tool is to extract the file content contained in one enditem of type EXTERNAL_FILEinto the Unix filesystem.

22.3.2 Start on CCU or CDU Version

The purpose of this tool is to extract the file or directory contents contained in all enditems of type EXTER-NAL_FILE in CCU or CDU version scope into the Unix filesystem.

22.3.3 Common

The user must have the necessary write permissions for the creation of files or directories.

The attributes Source File Directory, Source File Name, Target File Directory and Target File Name locatedin aggregate File Specification may be influence of the location of target file or directory.

Source FileType

Source FileDirectory

Source FileName

Target FileDirectory

Target FileName

Target File Location

DIRECTORY filled empty filled empty Target File Directory

DIRECTORY filled empty empty empty Source File Directory

ASCII orBINARY

filled filled filled filled Target File Directory/Target File Name

ASCII orBINARY

filled filled empty empty Source File Directory/Source File Name

ASCII orBINARY

filled filled filled empty Target File Directory/Source File Name

After the start of this tool a window File Extractor Tool V3.0 appears. The progress and the success of theexecution is shown in this window. The File Extractor does check the permissions of each destination directo-ry before extracting. Errors are reported in the same window.

22–5

CGS–RIBRE–SUM–00032 03.07.2015– –22–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


22.3.4 Batch Mode

It is also possible to start the file extractor in batch mode.

Invocation:

$MDA_HOME/util/file_io/file_extractor_if <parameter_1> .. <Parameter_n>

Parameters :

Parameter Number CCU CDU

1 Element Configuration Element Configuration

2 Mission Mission

3 Systemtree Version Number Systemtree Version Number

4 CCU CDU

5 Systemtree Node Pathname CDU Pathname

6 CCU Name Version

7 Version Issue

8 Issue Revision

9 Revision Testversion

10 [Item Pathname] MDB instance

11 [Item Pathname]

The last parameter called Item Pathname is optional. If this parameter is given then the extractor does extractonly this item and not all items in CCU or CDU version scope.

All parameters of type pathname (Systemtree Node Pathname, CDU Pathname and Item Pathname) mustbe enclosed in single or double quotes.

If a CDU version is a “normal” version (i.e. no testversion) then:Testversion: 0MDB instance: “”

Examples:

$MDA_HOME/util/file_io/file_extractor_if APM MASTER 12 CDU “\APM\COL_CC\MCS_OPS\OB” 10 0 0 “” “\APM\COL_CC\MCS_OPS\OB\HAZARD_CMDS\RULE_FILE”

$MDA_HOME/util/file_io/file_extractor_if APM MASTER 12 CCU “\APM” MCS_AIV 8.7.0

22–5

CGS–RIBRE–SUM–00032 03.07.2015– –22–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


37


A-1

CGS–RIBRE–SUM–00032 03.07.2015– –A-1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


A ACRONYMS

AP Automated Procedure

API Application Programmable Interface

APM Attached Pressurized Module

BDE Batch Data Entry

CCU Configuration Control Unit

CDU Configuration Data Unit

CM Configuration Management

CU Configuration Unit

DADI Data Dictonary

DMS Data Management Subsystem

EGSE Electrical Ground Support Equipment

EOR End of Record

ID Identifier

ICD Interface Control Document

MDA Mission Database Application

MDB Mission DataBase

SID Short Identifier

SSMB Space Station Manned Base

TCS Thermal Control Subsystem

B-6

CGS–RIBRE–SUM–00032 03.07.2015– –B-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.

Action Actions are high–level commands which provide for a flight configurationcontrol at higher levels than elementary commands and AutomatedProcedures (AP). They are pre–planned, goal–oriented operations ofeither Payload Elements or Subsystems. An Action may be linked tolower–level actions reflecting the hierarchical decomposition of theon–board operation. On Action level, all necessary pre–checks are carriedout to ensure a safe implementation of an automated operation consistentwith the actual mission phase and flight element configuration.

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

Archive Refers to the process of relegating obsolete data to external backingstorage. The reverse operation (copying archived data back to activestorage) is known as restore.

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.

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

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 configurationmanagement purposes.CUs are of two kinds: (a) Configuration Data Units (CDU), which contain the actual data(b) Configuration Control Units (CCU), which contain referenceinformation (CU name, version number, etc.) about other CUs, just like adirectory in a file system.

B-6

CGS–RIBRE–SUM–00032 03.07.2015– –B-2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Configuration Control Unit (CCU)A Configuration Control Unit is a Configuration Unit used to define andcontrol other Configuration Units. It identifies which specificcombinations of CDU instances make up a particular configuration. AConfiguration Control Unit may, in turn, point to lower–level controlunits, thus leading to a hierarchical configuration tree whose topmost(root) component corresponds to an entire Columbus FlightConfiguration.

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

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

Consistency state LOCAL VALID,LOCAL INVALIDGLOBAL VALID

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 andmanipulation 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 thedatabase. 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).

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.

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

B-6

CGS–RIBRE–SUM–00032 03.07.2015– –B-3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


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

E

End–Item see MDB item

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

G

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

Hierarchical Name Tree see Name Tree

I

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.

Issue see Version

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

J

K

L

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.

M

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

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

B-6

CGS–RIBRE–SUM–00032 03.07.2015– –B-4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


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 GroundSupport Equipment. Access to the MDB is controlled and managed byMPS.

N

Nametree Hierarchical (tree) structure within the MDB which portrays thehierarchical decomposition of Columbus Flight Configurations intosystems, subsystems, equipment, etc. The topmost node of the nametree(called the root node) designates the Flight Configuration, whereasterminal nodes (leaf nodes) 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 thesuccession of nodes to be traversed to reach that particular item in theNametree.

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

O

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

P

Parent In a hierarchical structure, denotes an immediate ancestor of a givencomponent.

Pathname see Nametree

Q

R

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

B-6

CGS–RIBRE–SUM–00032 03.07.2015– –B-5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Report In the context of this document, a report may be defined as anyhuman–readable description of one or more MDB items. It is an assortedcollection of information usually presented to the user in form of a tableor itemized list (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 areexecuted, and the resulting output routed either to the workstation’s screen(on–screen report), to the printer or to a user–selected file.

Revision see Version

S

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

T

U

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

User Throughout this document the term User refers to any person usingMDA–provided services. Users are grouped into different classes orcategories and will be assigned different privileges based on the task theyperform.

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 orinstances (CU occurrences) commonly referred to as versions, e.g. DMSVersion 3.2.1.

In the Configuration Management (CM) context, however, the various CUoccurrences. 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 newversion– 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.

B-6

CGS–RIBRE–SUM–00032 03.07.2015– –B-6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


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

W

X

Y

Z

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


C EXAMPLES OF MDA REPORTS

Content:

- C–1: CCU Version References Report

- C–2: CDU Difference Report

- C–3: CCU Version Report

- C–4: CDU Detail Report

- C–5: CDU Name Tree Report

- C–6: System Tree Difference Report

- C–7: CCU Cross References Report

- C–8: CCU End Item Xref Report

C-1 CCU Version References Report

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11–JUL–94 14:28:21 CCU VERSION REFERENCES REPORTPAGE 1

Element: [SSMB] Mission: [DUMMY_MISSION] [V1]Owner: [OPS$WERKMAN]Description: [descr.]Status: [FROZEN] Created: [15.01.1993 12:00:00]Frozen: [15.01.1993 12:00:00]

[\SSMB]CCU name: [CONFIGURATION] [V4.0.0]Owner: [OPS$MITSCHDO]Status: [DEVELOPMENT] Created: [11.07.1994 11:28:43]Changed: [11.07.1994 11:28:43] Frozen: [NULL]Consistency status: [NONE] Consistency date: [11.07.1994 11:28:43]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


C-2 CDU Difference Report

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11–JUL–94 14:10:14 CDU DIFFERENCE REPORTPAGE 1

CDU DIFFERENCE REPORT


1. User tree version:[\SSMB\THERMAL\WATERLOOP][V1.0.0] MDB instance: [MPS_DEVELOPMENT] CDU domain: [DMS]Owner: [OPS$GRUNWALD]Status: [FROZEN] Created: [05.04.1994 12:21:38]Changed: [14.06.1994 08:46:35] Review: [NULL]Frozen: [14.06.1994 08:46:35]Consistency status: [LOCAL_INVALID] Consistency date: [13.04.1994 06:19:36]

2. User tree version:[\SSMB\THERMAL\WATERLOOP][V5.0.1] MDB instance: [MPS_DEVELOPMENT] CDU domain: [DMS]Owner: [OPS$MITSCHDO]Status: [DEVELOPMENT] Created: [05.07.1994 02:24:54]Changed: [05.07.1994 02:24:54] Review: [NULL]Frozen: [NULL]Consistency status: [NONE] Consistency date: [05.07.1994 02:24:54]

Nodes are different:3 [\SSMB\THERMAL\WATERLOOP]

Type: [CDU] CI–number: [NULL]Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:21:39]Changed: [05.04.1994 12:21:39]

3 [\SSMB\THERMAL\WATERLOOP]Type: [CDU] CI–number: [NULL]Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54]Changed: [05.07.1994 02:24:54]

4 [\SSMB\THERMAL\WATERLOOP\PUMP]Type: [VIRTUAL] CI–number: [NULL]Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00]Changed: [05.04.1994 12:00:00]

4 [\SSMB\THERMAL\WATERLOOP\PUMP]Type: [VIRTUAL] CI–number: [NULL]Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54]Changed: [05.07.1994 02:24:54]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:




End item node with different details:

End item of first user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\MODE]Type: [SOFTWARE_ENUMERATION_DATA] SW access class: [READ_WRITE]SW type: [STATE_CODE_TYPE] Owner: [OPS$GRUNWALD]Description: [Status of the pumps]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

End item of second user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\MODE]Type: [SOFTWARE_ENUMERATION_DATA] SW access class: [READ_WRITE]SW type: [STATE_CODE_TYPE] Owner: [OPS$MITSCHDO]Description: [Status of the pumps]Created: [05.07.1994 02:24:54] Changed: [05.07.1994 02:24:54]


End item of first user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRESSURE_IN]Type: [STAU_ANALOG_MEASUREMENT] SW access class: [READ]SW type: [REAL_TYPE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

End item of second user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRESSURE_IN]Type: [STAU_ANALOG_MEASUREMENT] SW access class: [READ]SW type: [REAL_TYPE] Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54] Changed: [05.07.1994 02:24:54]


End item of first user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRESSURE_OUT]Type: [STAU_ANALOG_MEASUREMENT] SW access class: [READ]SW type: [REAL_TYPE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

End item of second user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRESSURE_OUT]Type: [STAU_ANALOG_MEASUREMENT] SW access class: [READ]SW type: [REAL_TYPE] Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54] Changed: [05.07.1994 02:24:54]

5 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY]Type: [VIRTUAL] CI–number: [NULL]Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00]Changed: [05.04.1994 12:00:00]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:




5 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY]Type: [VIRTUAL] CI–number: [NULL]Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54]Changed: [05.07.1994 02:24:54]


End item of first user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\ACTIVATE]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]SW type: [NONE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [11.04.1994 05:38:11]

End item of second user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\ACTIVATE]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]SW type: [NONE] Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54] Changed: [05.07.1994 02:24:54]

Table differences:1. User tree version:AP Source

AP Source : [procedure activate;

function f (x: real): real;begin

return x ** 2 – 1.0;end f;

constant d: real := 1.0 / 16.0; –– 16 lines for interval [x, x+1]

constant s: real := 32.0; –– 32 character widths for interval [y, y+1]

constant h1: integer := 40; –– character position of x–axisconstant h2: integer := 80; –– line widthconstant lim: integer := 32;

variable k: integer;variable n: integer;variable x: real;variable y: real;variable a: string (h2);

beginfor j := 1 to h2 do a(j) := ’ ’; end for;for i := –lim to lim do

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:




x := d * real (i); y := f(x);a(h1) := ’:’; n := integer (s * y) + h1;if n < h2 then a(n) := ’*’; else n := 0; end if;if n < h1 then k := h1; else k := n; end if;for j := 1 to k do

–– \is_io_library.put_char (a(j));end for;

–– \is_io_library.new_line;if n <> 0 then a(n) := ’ ’; end if;\SSMB\THERMAL\FREONLOOP\PUUMP\MODE := $O

N;end for;

end activate;]

2. User tree version:AP Source

AP Source : [procedure activate;




constant s: real := 32.0; –– 32 character widths for interval [y, y+1]

constant h1: integer := 40; –– character position of x–axisconstant h2: integer := 80; –– line widthconstant lim: integer := 32;


beginfor j := 1 to h2 do a(j) := ’ ’; end for;for i := –lim to lim do

x := d * real (i); y := f(x);a(h1) := ’:’; n := integer (s * y) + h1;if n < h2 then a(n) := ’*’; else n := 0; end if;if n < h1 then k := h1; else k := n; end if;for j := 1 to k do


–– \is_io_library.new_line;if n <> 0 then a(n) := ’ ’; end if;\SSMB\THERMAL\FREONLOOP\PUUMP\MODE := $O

N;end for;

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:




end activate;]

Non printable table contents:


End item of first user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\DELTA_PRESSURE]Type: [STAU_ANALOG_MEASUREMENT] SW access class: [READ]SW type: [REAL_TYPE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

End item of second user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\DELTA_PRESSURE]Type: [STAU_ANALOG_MEASUREMENT] SW access class: [READ]SW type: [REAL_TYPE] Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54] Changed: [05.07.1994 02:24:54]


End item of first user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\DE_ACTIVATE]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]SW type: [NONE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

End item of second user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\DE_ACTIVATE]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]SW type: [NONE] Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54] Changed: [05.07.1994 02:24:54]

6 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\MOTOR]Type: [VIRTUAL] CI–number: [NULL]Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00]Changed: [05.04.1994 12:00:00]

6 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\MOTOR]Type: [VIRTUAL] CI–number: [NULL]Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54]Changed: [05.07.1994 02:24:54]


End item of first user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\STATUS]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:




Type: [SOFTWARE_BOOLEAN_DATA] SW access class: [READ_WRITE]SW type: [BOOLEAN_TYPE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

End item of second user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\STATUS]Type: [SOFTWARE_BOOLEAN_DATA] SW access class: [READ_WRITE]SW type: [BOOLEAN_TYPE] Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54] Changed: [05.07.1994 02:24:54]

6 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\VALVE]Type: [VIRTUAL] CI–number: [NULL]Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00]Changed: [05.04.1994 12:00:00]

6 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\VALVE]Type: [VIRTUAL] CI–number: [NULL]Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54]Changed: [05.07.1994 02:24:54]


End item of first user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\VALVE\OFF]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]SW type: [NONE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

End item of second user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\VALVE\OFF]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]SW type: [NONE] Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54] Changed: [05.07.1994 02:24:54]


End item of first user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\VALVE\ON]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]SW type: [NONE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

End item of second user tree:[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\VALVE\ON]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:




SW type: [NONE] Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54] Changed: [05.07.1994 02:24:54]

5 [\SSMB\THERMAL\WATERLOOP\PUMP\REDUNDANT]Type: [VIRTUAL] CI–number: [NULL]Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00]Changed: [05.04.1994 12:00:00]

5 [\SSMB\THERMAL\WATERLOOP\PUMP\REDUNDANT]Type: [VIRTUAL] CI–number: [NULL]Owner: [OPS$MITSCHDO]Description: [NULL]Created: [05.07.1994 02:24:54]Changed: [05.07.1994 02:24:54]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


C-3 CCU Version Report

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11–JUL–94 14:29:39 CCU VERSIONS REPORTPAGE 1


[\SSMB]CCU name: [CONFIGURATION] [V4.0.0]Owner: [OPS$MITSCHDO]Status: [DEVELOPMENT] Created: [11.07.1994 11:28:43]Changed: [11.07.1994 11:28:43] Frozen: [NULL]Consistency status: [NONE] Consistency date: [11.07.1994 11:28:43]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


C-4 CDU Detail Report

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11–JUL–94 14:03:09 CDU DETAIL REPORTPAGE 1

CDU DETAIL REPORT


[\SSMB\THERMAL\WATERLOOP][V1.0.0] MDB instance: [MPS_DEVELOPMENT] CDU domain: [DMS]Owner: [OPS$GRUNWALD]Status: [FROZEN] Created: [05.04.1994 12:21:38]Changed: [14.06.1994 08:46:35] Review: [NULL]Frozen: [14.06.1994 08:46:35]Consistency status: [LOCAL_INVALID] Consistency date: [13.04.1994 06:19:36]

[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\STATUS]Type: [SOFTWARE_BOOLEAN_DATA] SW access class: [READ_WRITE]SW type: [BOOLEAN_TYPE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

DMS Discrete Limit SetsExpected state : [NULL] Enable flag : [NULL]

SW Boolean DataDescription : [NULL] Initial value : [NULL] Producer : [NULL]

STAU Discrete CalibrationState Code Low : [OK] State Code High : [NOK]

[\SSMB\THERMAL\WATERLOOP\PUMP\MODE]Type: [SOFTWARE_ENUMERATION_DATA] SW access class: [READ_WRITE]SW type: [STATE_CODE_TYPE] Owner: [OPS$GRUNWALD]Description: [Status of the pumps]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

DMS Discrete Limit SetsExpected state : [NULL] Enable flag : [NULL]

DMS Group Discrete CalibrationState Code Text : [PRIM_ON] State Code Number : [1]

State Code Text : [RED_ON] State Code Number : [2]

State Code Text : [BOTH_OFF] State Code Number : [3]

SW Enumeration DataDescription : [This value is set by an Automated procedure.]Initial value : [NULL] Producer : [NULL]

[\SSMB\THERMAL\WATERLOOP\PUMP\PRESSURE_IN]Type: [STAU_ANALOG_MEASUREMENT] SW access class: [READ]SW type: [REAL_TYPE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-15


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



CDU DETAIL REPORT

STAU Analog MeasurementDescription : [NULL] Redundant Measurement : [NULL]

Analog Limit SetsHigh limit : [NULL] Delta limit : [NULL] Low limit : [NULL]Enable flag : [NULL] Danger limit flag : [NULL]

DMS Analog CalibrationCoefficient 0 : [NULL] Coefficient 1 : [NULL] Coefficient 2 : [NULL]Coefficient 3 : [NULL] Coefficient 4 : [NULL] Range Low : [NULL]Range High : [NULL] Engineering Unit : [NULL]

DMS Equipment AddressEquipment : [NULL] Connector : [NULL] PIN : [NULL]

[\SSMB\THERMAL\WATERLOOP\PUMP\PRESSURE_OUT]Type: [STAU_ANALOG_MEASUREMENT] SW access class: [READ]SW type: [REAL_TYPE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]





[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\DELTA_PRESSURE]Type: [STAU_ANALOG_MEASUREMENT] SW access class: [READ]SW type: [REAL_TYPE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]




C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-16


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



CDU DETAIL REPORT


[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\ACTIVATE]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]SW type: [NONE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [11.04.1994 05:38:11]

Automated ProcedureOnboard Flag : [TRUE] Priority : [LOW]

Cross Reference ListPathname : [NULL] SID : [NULL]

Default ValueIndex : [NULL] Integer : [NULL] Real : [NULL] Boolean : [NULL]Character : [NULL] Word : [NULL] Bitset : [NULL] Pathname : [NULL]State Code : [NULL] Year : [NULL] Month : [NULL] Day : [NULL]Seconds : [NULL] Completion Code : [NULL] Unsigned Integer : [NULL]Long Real : [NULL] UCL String : [NULL]

Formal ParameterName : [NULL] List : [NULL] Mode In : [NULL] Mode Out : [NULL]Optional : [NULL] Software Type : [NULL]

AP SourceAP Source : [procedure activate;




constant s: real := 32.0; –– 32 character widths for interval [y, y+1]constant h1: integer := 40; –– character position of x–axisconstant h2: integer := 80; –– line widthconstant lim: integer := 32;


beginfor j := 1 to h2 do a(j) := ’ ’; end for;

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-17


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



CDU DETAIL REPORT

for i := –lim to lim dox := d * real (i); y := f(x);a(h1) := ’:’; n := integer (s * y) + h1;if n < h2 then a(n) := ’*’; else n := 0; end if;if n < h1 then k := h1; else k := n; end if;for j := 1 to k do


–– \is_io_library.new_line;if n <> 0 then a(n) := ’ ’; end if;\SSMB\THERMAL\FREONLOOP\PUUMP\MODE := $ON;

end for;end activate;]

Compilation DateCompilation Date : []

[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\DE_ACTIVATE]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]SW type: [NONE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]

Automated ProcedureOnboard Flag : [NULL] Priority : [NULL]




AP SourceAP Source : [NULL]

Compilation DateCompilation Date : [NULL]

[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\VALVE\OFF]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]SW type: [NONE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]


C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-18


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



CDU DETAIL REPORT






[\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\VALVE\ON]Type: [UCL_AUTOMATED_PROCEDURE] SW access class: [EXECUTE]SW type: [NONE] Owner: [OPS$GRUNWALD]Description: [NULL]Created: [05.04.1994 12:00:00] Changed: [05.04.1994 12:00:00]







C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-19


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


C-5 CDU Name Tree Report

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-20


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11–JUL–94 14:14:02 CDU NAME TREE REPORTPAGE 1

CDU NAME TREE REPORT


[\SSMB\THERMAL\WATERLOOP][V1.0.0] MDB instance: [MPS_DEVELOPMENT] CDU domain: [DMS]Owner: [OPS$GRUNWALD]Status: [FROZEN] Created: [05.04.1994 12:21:38]Changed: [14.06.1994 08:46:35] Review: [NULL]Frozen: [14.06.1994 08:46:35]Consistency status: [LOCAL_INVALID] Consistency date: [13.04.1994 06:19:36]

3 [\SSMB\THERMAL\WATERLOOP]Type: [CDU]

4 [\SSMB\THERMAL\WATERLOOP\PUMP]Type: [VIRTUAL]

5 [\SSMB\THERMAL\WATERLOOP\PUMP\MODE]Type: [SOFTWARE_ENUMERATION_DATA]

5 [\SSMB\THERMAL\WATERLOOP\PUMP\PRESSURE_IN]Type: [STAU_ANALOG_MEASUREMENT]

5 [\SSMB\THERMAL\WATERLOOP\PUMP\PRESSURE_OUT]Type: [STAU_ANALOG_MEASUREMENT]

5 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY]Type: [VIRTUAL]

6 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\ACTIVATE]Type: [UCL_AUTOMATED_PROCEDURE]

6 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\DELTA_PRESSURE]Type: [STAU_ANALOG_MEASUREMENT]

6 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\DE_ACTIVATE]Type: [UCL_AUTOMATED_PROCEDURE]

6 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\MOTOR]Type: [VIRTUAL]

6 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\STATUS]Type: [SOFTWARE_BOOLEAN_DATA]

6 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\VALVE]Type: [VIRTUAL]

7 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\VALVE\OFF]Type: [UCL_AUTOMATED_PROCEDURE]

7 [\SSMB\THERMAL\WATERLOOP\PUMP\PRIMARY\VALVE\ON]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-21


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


11–JUL–94 14:14:02 CDU NAME TREE REPORTPAGE 2

CDU NAME TREE REPORT

Type: [UCL_AUTOMATED_PROCEDURE]

5 [\SSMB\THERMAL\WATERLOOP\PUMP\REDUNDANT]Type: [VIRTUAL]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-22


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


C-6 System Tree Difference Report

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-23


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


21–JUL–95 08:59:04 SYS-TEM TREE DIFFERENCEREPORT PAGE 1

1. System tree version: Element: [SSMB] Mission:[DUMMY_MISSION] [V1] Owner: [OPS$HERR-MANN] Description: [descr.] Status: [FROZEN] Created:[10.11.1994 12:00:00] Frozen: [10.11.199412:00:00]

2. System tree version: Element: [SSMB] Mission:[DUMMY_MISSION] [V4] Owner: [OPS$HOPP-MANN] Description: [new systemtree V3] Status: [FROZEN] Created:[11.05.1995 04:34:19] Frozen: [11.05.199505:00:23]

Nodes are different: 1 [\SSMB] MDB instance: [MPS_DE-VELOPMENT] Owner: [OPS$HERR-MANN] Description: [descr.] Created: [10.11.199412:00:00] Changed: [10.11.199412:00:00]

1 [\SSMB] MDB instance: [MPS_DE-VELOPMENT] Owner: [OPS$HOPP-MANN]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-24


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Nodes are different: 3 [\SSMB\C_DH\COM-PUTER] MDB instance:[MPS_AIV] Owner: [OPS$HERR-MANN] Description: [descr.] Created: [10.11.199412:00:00] Changed: [10.11.199412:00:00]

3 [\SSMB\C_DH\COM-PUTER] MDB instance:[MPS_DEVELOPMENT] Owner: [OPS$HOPP-MANN]

SYSTEM TREEDIFFERENCE REPORT £ 21–JUL–95 08:59:04SYSTEM TREE DIFFER-ENCE REPORT PAGE 2

Description: [descr.] Created: [11.05.199504:34:20] Changed: [11.05.199504:34:20]

Nodes are different: 3 [\SSMB\C_DH\MDM] MDB instance:[MPS_AIV] Owner: [OPS$HERR-MANN] Description: [descr.] Created: [10.11.199412:00:00] Changed: [10.11.1994

2 [\SSMB\GNC] MDB instance: [MPS_DE-VELOPMENT] Owner: [OPS$HOPP-MANN] Description: [descr.] Created: [11.05.199504:34:20] Changed: [11.05.199504:34:20]

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-25


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Nodes are different: 2 [\SSMB\LIFE_SUP-PORT] MDB instance:[MPS_AIV] Owner: [OPS$HERR-MANN] Description: [descr.] Created: [10.11.199412:00:00] Changed: [10.11.199412:00:00]

2 [\SSMB\LIFE_SUP-PORT] MDB instance: [MPS_DE-VELOPMENT] Owner: [OPS$HOPP-MANN] Description: [descr.] Created: [11.05.199504:34:20] Changed: [11.05.199504:34:20]

Nodes are different: 2 [\SSMB\POWER] MDB instance:[MPS_AIV] Owner: [OPS$HERR-MANN] Description: [descr.] Created: [10.11.199412:00:00]

SYSTEM TREEDIFFERENCE REPORT £ 21–JUL–95 08:59:04SYSTEM TREE DIFFER-ENCE REPORT PAGE 3

Changed: [10.11.1994

2 [\SSMB\THERMAL] MDB instance: [MPS_DE-VELOPMENT] Owner: [OPS$HOPP-MANN] Description: [descr.] Created: [11.05.199504:34:20] Changed: [11.05.199504:34:20]

SYSTEM TREE

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-26


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


C-7 CCU Cross Reference Report

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-27


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-28


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


C-8 CCU End Item Xref Report

C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-29


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


C-30

CGS–RIBRE–SUM–00032 03.07.2015– –C-30


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



D–9

CGS–RIBRE–SUM–00032 03.07.2015– –D–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


D EXAMPLES OF MDA API PROCEDURES

D-1 Data Access Procedure

This example descibes the MDB access with standard oracle functions.

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––WITH oracle_defs;WITH TEXT_IO; USE TEXT_IO;

PACKAGE BODY API_ACCESS IS

PACKAGE int_io IS NEW INTEGER_IO(oracle_defs.integer);USEINT_IO;

EXEC SQL DECLARE MDB DATABASE;–– Important definition EXEC SQL WHENEVER SQLERROR RAISE oracle_error;

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

PROCEDURE select_data_from_API–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

IS

f_sid, F_CDU_INTERNAL_VERSION, F_ENTRY_NUMBER:

oracle_defs.integer := 0; str32:

oracle_defs.varchar(32); found:

BOOLEAN := TRUE;

sql_select_statement: CONSTANT STRING := ”SELECT F_CDU_INTERNAL_VER-

SION,F_SID,F_ENTRY_NUMBER,F_ENG_NAME FROM MDM_04”;

EXEC SQL AT MDB DECLARE s STATEMENT; EXEC SQL DECLARE c CURSOR FOR s;

BEGIN EXEC SQL PREPARE s FROM :sql_select_statement; EXEC SQL OPEN c;

D–9

CGS–RIBRE–SUM–00032 03.07.2015– –D–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


WHILE found LOOP

EXEC SQL FETCH c INTO:F_CDU_INTERNAL_VERSION,:F_SID,:F_ENTRY_NUMBER,:str32;

found := NOT oracle.error.if_not_found ;

IF NOT found THEN EXIT; END IF;

put(F_CDU_INTERNAL_VERSION); put(F_SID); put(F_ENTRY_NUMBER); put(’ ’); put_line(str32.buffer(1 .. INTEGER(str32.LENGTH)));

END LOOP; EXEC SQL CLOSE c;END;

END; –– Package

D-2 Usage of MDB_API Procedures

The usage of the MDB_API procedures provided by the Data–API, will be explained in the fol-lowing example. This program performs the following steps:


· Set configuration for a CCU scope by using the internal version number

· Display of CCU and CDU versions in the CCU scope

· Set configuration for a CDU scope by using the internal version number


· Set configuration for a CCU scope by using the long parameter list (element_configuration,mission, systemtree_version, etc.).


· Set configuration for a CDU test version scope by using the long parameter list (element_con-figuration, mission, systemtree_version, etc.).


· Exception output

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– M A I N P R O G R A M API DEMO

D–9

CGS–RIBRE–SUM–00032 03.07.2015– –D–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


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

WITH ORACLE_DEFS;WITH USER_EXCEPTIONS; � Exeception Numbers used in MDB_APIWITH TEXT_IO; USE TEXT_IO;

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––PROCEDURE api_demo IS––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– EXEC SQL WHENEVER SQLERROR RAISE oracle_error;

oracle_error : EXCEPTION; � Declarations

user_id : constant string := ”mda_test/mda_test”;internal_version : integer;scope : string(1..3); –– ”CCU” or ”CDU”element_configuration : oracle.varchar(16);mission : oracle.varchar(16);systemtree_version: integer;ccu_pathname : oracle.varchar(255);cdu_pathname : oracle.varchar(255);version : integer;issue : integer;revision : integer;testversion : integer;name : oracle.varchar(30);mdb_instance : oracle.varchar(16);test_in : oracle.varchar(5);

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––PROCEDURE select_T_CONFIG_API � Procedure for listing of CDU versions

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––IS i : integer := 0;found : BOOLEAN := TRUE; sql_select_statement : CONSTANT STRING := ”SELECT * FROM T_API_CONFIG”;

EXEC SQL DECLARE s STATEMENT;EXEC SQL DECLARE c CURSOR FOR s;BEGIN EXEC SQL PREPARE s FROM :sql_select_statement; EXEC SQL OPEN c; TEXT_IO.PUT_LINE(”table T_API_CONFIG:”); WHILE found LOOP

EXEC SQL FETCH c INTO:internal_version; found := NOT oracle.error.if_not_found;IF found THEN

INTEGER_IO.put(internal_version);END IF;IF (i mod 5 = 4 OR NOT found) AND i>0 THEN

TEXT_IO.NEW_LINE;END IF; i := i+1;

END LOOP; IF i = 1 THEN

TEXT_IO.PUT_LINE(” No selection”);

D–9

CGS–RIBRE–SUM–00032 03.07.2015– –D–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


END IF; EXEC SQL CLOSE c;END;

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––PROCEDURE select_CONFIG_API � Procedure for listing of CCU versions

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––IS internal_version: integer :=0;scope: string(1..3) := ” ”;date: string(1..9) := ” ”;

BEGIN TEXT_IO.PUT_LINE(”table API_CONFIG:”); EXEC SQL SELECT INTERNAL_VERSION,SCOPE,CONFIG_DATE INTO :internal_version,:scope,:date FROM API_CONFIG; INTEGER_IO.PUT(internal_version); TEXT_IO.PUT(” ” & scope & ” ”); TEXT_IO.PUT_LINE(date);END;

BEGIN

EXEC SQL CONNECT :user_id; � Connect to MDB

TEXT_IO.NEW_LINE;TEXT_IO.PUT_LINE(”Configure API for a CCU version – short call version”);internal_version:=470002;scope:=”CCU”; � Configure the scope for a CCUEXEC SQL EXECUTE BEGIN MDB_API.CONFIG_API(:internal_version,:scope); END;

END–EXEC;

select_CONFIG_API; � Listing of all CDU versions in the scopeselect_T_CONFIG_API; � Listing of all CCU versions in the scope

TEXT_IO.PUT_LINE(”Rollback”); � Undo the changes to the MDBEXEC SQL EXECUTE IMMEDIATE ”BEGIN MDB_API.ROLLBACK; END;”;

TEXT_IO.PUT_LINE(”Commit”); � Commit the changes to the MDBEXEC SQL EXECUTE IMMEDIATE ”BEGIN MDB_API.COMMIT; END;”;

TEXT_IO.NEW_LINE;TEXT_IO.PUT_LINE(”Configure API for a CDU version – short call version”);internal_version:=470003;scope:=”CDU”; � Configure the scope for a CDU the short call version EXEC SQL EXECUTE BEGIN MDB_API.CONFIG_API(:internal_version,:scope); END;

END–EXEC;




D–9

CGS–RIBRE–SUM–00032 03.07.2015– –D–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


TEXT_IO.NEW_LINE; � Configure the scope for a CCU with the long call version TEXT_IO.PUT_LINE(”Configure API for a CCU version – long call version”);

element_configuration.buffer(1..7) := ”CC_TEST”;element_configuration.length := 7;mission.buffer(1..13) := ”DUMMY_MISSION”;mission.length := 13;systemtree_version := 1;ccu_pathname.buffer(1..20) := ”\CC_TEST\CC_TEST_GV1”;ccu_pathname.length := 20;version := 1;issue := 0;revision := 0;name.buffer(1..11) := ”CC_TEST_GV1”;name.length := 11;


:ccu_pathname,:version,:issue,:revision,:name); END;END–EXEC;




TEXT_IO.NEW_LINE; � Configure the scope for a CDU test version with the long call version

TEXT_IO.PUT_LINE(”Configure API for a CDU test version – long call version”);

element_configuration.buffer(1..7) := ”CC_TEST”;element_configuration.length := 7;mission.buffer(1..13) := ”DUMMY_MISSION”;mission.length := 13;systemtree_version := 1;cdu_pathname.buffer(1..32) := ”\CC_TEST\CC_TEST_LI1\CC_TEST_LI4”;cdu_pathname.length := 32;version := 0;issue := 0;revision := 0;testversion := 1;mdb_instance.buffer(1..8) := ”MDA_TEST”;mdb_instance.length := 8;test_in.buffer(1..4) := ”TRUE”;test_in.length := 4;


:cdu_pathname,:version,:issue,:revision, :testversion,:mdb_instance,:test_in);

END;

D–9

CGS–RIBRE–SUM–00032 03.07.2015– –D–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


END–EXEC;




––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Exceptions –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

EXCEPTION � Exception output

WHEN oracle_error => IF oracle_defs.sqlcode = user_exceptions.MDB_ERROR_NO THEN TEXT_IO.PUT_LINE(”MDB_ERROR”);ELSIF oracle_defs.sqlcode = user_exceptions.USE_ERROR_NO THEN TEXT_IO.PUT_LINE(”USE_ERROR”);ELSIF oracle_defs.sqlcode = user_exceptions.AUTHORIZATION_ERROR_NO THEN TEXT_IO.PUT_LINE(”AUTHORIZATION_ERROR”);ELSIF oracle_defs.sqlcode = user_exceptions.PARAMETER_ERROR_NO THEN TEXT_IO.PUT_LINE(”PARAMETER_ERROR”);ELSE TEXT_IO.PUT_LINE(oracle.error.message);END IF;

END api_demo;––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– E N D O F M A I N P R O G R A M –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

D–9

CGS–RIBRE–SUM–00032 03.07.2015– –D–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


D-3 Using Write Procedures with the Data–API

The usage of the MDB_API procedures provided by the Data–API in conjunction with the WriteProcedures, will be explained by the following example. This program performs the followingsteps:


· Set configuration for a CCU scope by using the internal version number

· Call Write Procedure

· Commit the changes made

· Exception output

––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– M A I N P R O G R A M API WRITE DEMO–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

WITH ORACLE_DEFS;WITH USER_EXCEPTIONS; � Exeception Numbers used in MDB_APIWITH TEXT_IO; USE TEXT_IO;

–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––PROCEDURE api_write_demo IS––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– EXEC SQL WHENEVER SQLERROR RAISE oracle_error;

oracle_error : EXCEPTION; � DeclarationsDB_STRING : constant string := ””;

USER_ID : constant string := ”/”;INTERNAL_VERSION : INTEGER := 601; –– CCU or CDU scopeSCOPE : oracle_defs.varchar(3) := (LENGTH => 3, BUFFER => ”CCU”, n => 3);egse_description :oracle_defs.varchar(7) := (LENGTH => 7, BUFFER =>

”HP3852A”, n => 7);pathname : oracle_defs.varchar(34) := (LENGTH => 34, BUFFER =>

”\GSRF\DMSRF\ONGROUND\EGSE\DATA_ACQ”, n => 34);

BEGIN

TEXT_IO.PUT_LINE(”Start of Program API–Write Demo”);EXEC SQL CONNECT :USER_ID USING :DB_STRING; � Connect to MDB

� Configure the scope for a CCU EXEC SQL EXECUTE BEGIN MDB_API.CONFIG_API(:INTERNAL_VERSION,:SCOPE); END; END–EXEC;

� Call Write ProcedureEXEC SQL EXECUTE BEGIN P_EGSE_EQUIPMENT(:egse_description,:pathname); END; END–EXEC;

TEXT_IO.PUT_LINE(”Commit”); � Commit the changes to the MDBEXEC SQL EXECUTE IMMEDIATE ”BEGIN MDB_API.COMMIT; END;”;TEXT_IO.PUT_LINE(”End of Program API–Write Demo”);

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

D–9

CGS–RIBRE–SUM–00032 03.07.2015– –D–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


–– Exceptions –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

EXCEPTION � Exception output

WHEN oracle_error => IF oracle_defs.sqlcode = user_exceptions.MDB_ERROR_NO THEN TEXT_IO.PUT_LINE(”MDB_ERROR”);ELSIF oracle_defs.sqlcode = user_exceptions.USE_ERROR_NO THEN TEXT_IO.PUT_LINE(”USE_ERROR”);ELSIF oracle_defs.sqlcode = user_exceptions.AUTHORIZATION_ERROR_NO THEN TEXT_IO.PUT_LINE(”AUTHORIZATION_ERROR”);ELSIF oracle_defs.sqlcode = user_exceptions.PARAMETER_ERROR_NO THEN TEXT_IO.PUT_LINE(”PARAMETER_ERROR”);ELSE TEXT_IO.PUT_LINE(oracle.error.message);END IF;

END api_write_demo;––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– E N D O F M A I N P R O G R A M –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

EGSE_EQUIPMENT is an aggregate with the attribute Description, defined with DADI–MA.The Write Procedure P_EGSE_EQUIPMENT, which is called within the main program has beengenerated automatically during the export within DADI–MA. The Write Procedure which hasbeen created for this demo, contains the following statements:

CREATE OR REPLACE PROCEDURE P_EGSE_EQUIPMENT(F_DESCRIPTION IN VARCHAR2,pathname IN VARCHAR2)

AS sid NUMBER;cdu_internal_number NUMBER;

BEGINMDB_API_WRITE.check_write_request(

pathname,’EGSE_EQUIPMENT’, sid,cdu_internal_version);

DELETE FROM EGSE_EQUIPMENT WHERE F_SID=sid AND F_CDU_INTERNAL_VERSION=cdu_internal_version;

INSERT INTO EGSE_EQUIPMENT VALUES(cdu_internal_version,sid,SYSDATE,F_DESCRIPTION);

END;

D–9

CGS–RIBRE–SUM–00032 03.07.2015– –D–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–1


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


E EXAMPLE OF BDE SESSIONS

This appendix describes two BDE sample runs. The first case shows ”nominal” operation, i.e. allthree steps (load, store and reset) perform successfully. In the second case, various errors are detectedand reported in the log files.

For both cases, the respective set of input files (job configuration file and data files) is shown, together with the resulting log (report) files.

E-1 Batch Configuration Files

The following batch configuration files are used:

• for nominal BDE Operation:

# MISSION: DUMMY_MISSION# SYSTEMTREE_VERSION: 2# CU_TYPE: CCU# CU_NAME: [CCU_DEV]\SSMB# CU_VERSION: 001.000.000nom_test_single TEST_SINGLE PATHNAMEnom_test_multi TEST_MULTI PATHNAMEt_large_char TEST_LARGE_CHAR PATHNAME \SSMB\CDU_DEV\BDE_TEST\NODE1t_large_raw TEST_LARGE_RAW PATHNAME \SSMB\CDU_DEV\BDE_TEST\NODE3

• for non–nominal BDE Operation:

# MISSION: DUMMY_MISSION# SYSTEMTREE_VERSION: 2# CU_TYPE: CDU# CU_NAME: \SSMB\CDU_DEV# CU_VERSION: 001.000.000.000 MDB_INSTANCEnn_3_test_single TEST_SINGLE PATHNAMEnn_3_test_multi TEST_MULTI PATHNAME

The contents of the associated data files:

– nom_test_single.dat

– nom_test_multi.dat

– nn_3_test_single.dat

– nn_3_test_multi.dat

are listed on the next pages.

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–2


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


E-2 Input Data Files

� File nom_test_single.dat

\SSMB\CDU_DEV\BDE_TEST\NODE1 string1___123456789012345678901234567890

1.123456 1.123456789012345 2147483647

0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABC-

DEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABC-

DEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDE

00011001111111111111000000000101 \WELCOME\TO\THE\PATHNAME\TEST1\WELCOME\TO\THE\PATHNAME\TEST1\WEL-

COME\TO\THE\PATHNAME\TEST1\WELCOME\TO\THE\PATHNAME\TEST1\WELCOME\TO\THE\PATHNAME\TEST1\WEL-

COME\TO\THE\PATHNAME\TEST1\WELCOME\TO\THE\PATHNAME\TEST1\WELCOME\TO\THE\PATHNAME\TEST1\PATH-

NAME\TEST1 AMPERE

\SSMB\CDU_DEV\BDE_TEST\NODE2 @

@ @ @ @

@ @ @

\SSMB\CDU_DEV\BDE_TEST\NODE3 ”string3 with blanks”

1.999993 1.99992 1 0909009A1

00011001111111111111000000000101 \PATH\PATHNAME

AMPERE

\SSMB\CDU_DEV\BDE_TEST\NODE4 ”string4 ””String4”” with blanks”

1.999994 1.99977792 10099 0909009ABCDEF10

00011001111111111111000000000101 \VALID\PATH

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–3


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


OHM

\SSMB\CDU_DEV\BDE_TEST\NODE5 string5

1.999995 1.99977792 –10099.1 0909009ABCDEF10

00011001111111111111000000000101 \VALID\PATH

OHM


1.999996 1.99977792 10099 0909009ABCDEF10

00011001111111111111000000000101 \VALID\PATH

OHM


1.999997 1.99977792 10099 0909009ABCDEF10

00011001111111111111000000000101 \VALID\PATH

OHM


1.999998 1.99977792 10099 0909009ABCDEF10

00011001111111111111000000000101 \VALID\PATH

OHM


1.999999 1.99977792 10099 0909009ABCDEF10

00011001111111111111000000000101 \VALID\PATH

OHM

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–4


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� File nom_test_multi.dat

\SSMB\CDU_DEV\BDE_TEST\NODE1 1

string1.1 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string1.2 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string1.3 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string1.4 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string1.5 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–5


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



string2.1 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string2.2 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string2.3 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string2.4 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string2.5 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string3.1 1.999 1.99992 5

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–6


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string3.2 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string3.3 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string3.4 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string3.5 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string4.1 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–7


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



string4.2 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string4.3 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string4.4 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string4.5 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string5.1 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string5.2 1.999 1.99992 5

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–8


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string5.3 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string5.4 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string5.5 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string6.1 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string6.2 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–9


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



string6.3 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string6.4 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string6.5 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string7.1 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string7.2 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string7.3 1.999 1.99992 5

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–10


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string7.4 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string7.5 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string8.1 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string8.2 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string8.3 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–11


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



string8.4 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string8.5 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string9.1 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string9.2 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string9.3 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string9.4 1.999 1.99992 5

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–12


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string9.5 1.999 1.99992 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–13


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� File nn_3_test_single.dat


1.123456 1.123456789012345678901234567890

2147483647 0123456789ABCDEF01 00011001111111111111000000000101

\WELCOME\TO\THE\PATHNAME\TEST1

AMPERE


000000000000000000000000001.999

000000000000000000000000001.999 2147483647

0123456789ABCDEF01 00011001111111111111000000000101

\WELCOME\TO\THE\PATHNAME\TEST1

AMPERE


0001.999 0001.99977792E6 @

@ @ @ @

@

\SSMB\CDU_DEV\BDE_TEST\NODE3 ”string3 with blanks”

1.999993 1.99992 +–0 0909009A1

00011001111111111111000000000101 \PATH\PATHNAME

AMPERE

\SSMB\CDU_DEV\BDE_TEST\NODE4 ”string4 ””String4”” with blanks”

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–14


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


1.999994 1.99977792 10099 0909009ABCDEF10

000110011111111111110000000001010101 \VALID\PATH

OHM


1.999995 1.99977792 –10099.1 0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABC-

DEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABC-

DEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF

00011001111111111111000000000101 \VALID\PATH

OHM

\SSMB\CDU_DEV\BDE_TEST\NODE6 ”string6 exceed range of COL_STRING (40) but not 255”

1.999996 1.99977792 10099 0909009ABCDEF10

00011001111111111111000000000101 \VALID\PATH

OHM

\SSMB\CDU_DEV\BDE_TEST\NODE7 ”string7 enclosed in double quotes is too long string7 enclosed in double quotes is too long string7

enclosed in double quotes is too long string7 enclosed in double quotes is too long string7 enclosed in double quotes is too long string7 enclosed in

double quotes is too long” 1.999997 1.99977792

10099 0909009ABCDEF10 00011001111111111111000000000101

\VALID\PATHOHM

\SSMB\CDU_DEV\BDE_TEST\NODE8 ”string8 is a string

1.999998 1.99977792 10099 0909009ABCDEF10

00011001111111111111000000000101 \VALID\PATH

OHM

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–15


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



1.999999 1.99977792 10099 0909009ABCDEF10

00011001111111111111000000000101 \VALID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VAL-

ID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VAL-

ID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VAL-

ID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG

OHM

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–16


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� File nn_3_test_multi.dat


string0.1 1.000001 1.000000000000001

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH Bue


string0.2 1.000002 1.000000000000002

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH INVALID


string0.3 –4.000003 1.000000000000003

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string0.4 1.000004 2.000000000000004

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string0.5 1.000005 1.000000000000005

4 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–17


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



string1.1 –3 1.000000000000002

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string1.2 1.000004 2 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string1.3 1.0123456 1.0123456789123456

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string1.4 3.41E38 1.000000000000008

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string1.5 1.000010 1.8E308 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string2.1 1.000003 1.000000000000003

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–18


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


5.123 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string2.2 1.000006 1.000000000000006

5.98765432109876 0123456789ABCDEF10

00011001111111111111000000000101 \PATH\PATH

BLUE


string2.3 1.000009 1.000000000000009

0000000000000000000000000005 0123456789ABCDEF10

00011001111111111111000000000101 \PATH\PATH

BLUE


string2.4 1.000012 1.000000000000012

5 0123456789ABCDEF10 00110

\PATH\PATH BLUE


string2.5 1.000015 1.000000000000015

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string3.1 1.999e6 1.000000000000004

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–19


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string3.2 1.000008 1.99992F7 5

0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string3.3 1.000012 1.000000000000012

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string3.4 1.000016 1.000000000000016

5 0123456789ABCDEF10 02011001111111111111000000000101

\PATH\PATH BLUE


string3.5 1.000020 1.000000000000020

5 0123456789ABCDEF10 0#011001111111111111000000000101

\PATH\PATH BLUE


string4.1 1.000005 1.000000000000005

5 G0123456789ABCDEF0 00011001111111111111000000000101

\PATH\PATH BLUE

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–20


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



string4.2 1.000010 1.000000000000010

5 f0123456789ABCDEF0 00011001111111111111000000000101

\PATH\PATH BLUE


string4.3 1.000015 1.000000000000015

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH/NAME#NOT%OK BLUE


string4.4 1.000020 1.000000000000020

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\name BLUE


string4.5 1.000025 1.000000000000025

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string5.1 1.000006 1.000000000000006

5 0123456789ABCDEF10 00011001111111111111000000000101

\012345\67890\4711\0815 BLUE


string5.2 1.000012 1.000000000000012

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–21


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


5 0123456789ABCDEF10 00011001111111111111000000000101

\_WITH_LEADING\UNDERSCORE BLUE


string5.3 1.000018 1.000000000000018

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string5.4 1.000024 1.000000000000024

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string5.5 1.000030 1.000000000000030

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string6.1 1.000007 1.000000000000007

5F99 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string6.2 1.000014 1.000000000000014

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–22


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



string6.3 1.000021 1.000000000000021

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string6.4 1.000028 1.000000000000028

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string6.5 1.000035 1.000000000000035

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string7.1 1.000008 1.000000000000008

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string7.2 1.000016 1.000000000000016

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string7.3 1.000024 1.000000000000024

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–23


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string7.4 1.000032 1.000000000000032

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string7.5 1.000040 1.000000000000040

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string8.1 1.000009 1.000000000000009

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string8.2 1.000018 1.000000000000018

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string8.3 1.000027 1.000000000000027

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–24


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



string8.4 1.000036 1.000000000000036

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string8.5 1.000045 1.000000000000045

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string9.1 1.000010 1.000000000000010

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string9.2 1.000020 1.000000000000020

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string9.3 1.000030 1.000000000000030

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string9.4 1.000040 1.000000000000040

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–25


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE


string9.5 1.000050 1.000000000000050

5 0123456789ABCDEF10 00011001111111111111000000000101

\PATH\PATH BLUE

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–26


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


E-3 BDE Execution / Sample runs

� Case 1: Nominal BDE operation

First, the environment variable BDE_CFG is set, then the three BDE operations invoked successively.The following commands are used at the Unix command–line level(actual user input shown in boldface letters):mps_1{proebst}33: setenv BDE_CFG $HOME/bde/input/nom_2_config.dat

mps_1{proebst}34: $MDA_HOME/bin/common/bde_load

mps_1{proebst}35: $MDA_HOME/bin/common/bde_store

mps_1{proebst}35: $MDA_HOME/bin/common/bde_reset

As a result, the following log files (reports) are created in the directory $HOME/bde/reports

• bde_load_activity.log

• bde_load_errors.log

• bde_store_activity.log

Additional information is provided by the SQL*Loader in the following log files(directory $HOME/bde/reports/sqlloader/log):

• nom_2_config.log

• nom_test_single.log

• nom_test_multi.log

Log files contents are shown at the end of this appendix.

� Case 2: Non–nominal BDE operation

For this second case, the BDE_CFG environment variable must be reset accordingly. BDE invocation is thesame as before. So the command sequence is:mps_1{proebst}33: setenv BDE_CFG $HOME/bde/input/nn_3_config.dat

mps_1{proebst}34: $MDA_HOME/bin/common/bde_load

mps_1{proebst}35: $MDA_HOME/bin/common/bde_store

mps_1{proebst}35: $MDA_HOME/bin/common/bde_reset

This results in the following log files being created (directory $HOME/bde/reports):

• bde_load_activity.log

• bde_load_errors.log

• bde_store_activity.log

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–27


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Similarly the following files are created by the SQL*Loader in the directories

(a) in the directory $HOME/bde/reports/sqlloader/log

• nn_3_config.log

• nn_3_test_single.log

• nn_3_test_multi.log

(b) in the directory $HOME/bde/reports/sqlloader/bad

• nn_3_test_single.bad

• nn_3_test_multi.bad

Log files contents are shown at the end of this appendix.

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–28


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


E-4 BDE Log Files for Case 1: Nominal Operation

� File bde_load_activity.log******************************************************************

MDA Batch Data Entry Facility V1.0.0 BDE LOAD Operation Report

User: proebst

Job started on Tue Feb 7 14:56:58 MET 1995******************************************************************

––– Job Configuration Parameters ––– ––––––––––––––––––––––––––––––––––––––––

# MISSION: DUMMY_MISSION# SYSTEMTREE_VERSION: 2

# CU_TYPE: CCU# CU_NAME: [CCU_DEV]\SSMB

# CU_VERSION: 001.000.000

nom_test_single TEST_SINGLE PATHNAMEnom_test_multi TEST_MULTI PATHNAME

t_large_char TEST_LARGE_CHAR PATHNAME \SSMB\CDU_DEV\BDE_TEST\NODE1t_large_raw TEST_LARGE_RAW PATHNAME \SSMB\CDU_DEV\BDE_TEST\NODE3

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

Error limit: 1000 per file

Data Checks results

* Input File nom_test_single:

Records processed: 9 Data errors: 0

* Input File nom_test_multi:

Records processed: 45 Data errors: 0

Total files processed: 2

Total records processed: 54Total errors detected: 0

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–29


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


***** BDE_LOAD finished *****

No errors reported by SQL*Loader

No data errors reported by BDE Checker

Issue BDE_STORE command to post loaded data into the MDB

or BDE_RESET command to clear the Load Area.

Job ended on Tue Feb 7 14:59:05 MET 1995

� File bde_store_activity.log****************************************************************** MDA Batch Data Entry Facility V1.0.0

BDE STORE Operation Report

User: proebst Job started on Tue Feb 7 14:59:57 MET 1995

******************************************************************

***** BDE_STORE successfully terminated *****


� File nom_2_config.log

SQL*Loader: Version 1.1.9.0.1 – Production on Tue Feb 7 14:57:56 1995

Copyright (c) Oracle Corporation 1979, 1992. All rights reserved.

Control File: /usr/columbus/users30/proebst/mda_v3/config/mdb/install/dadi_export/bde_control_files/batch_config.ctl

Data File: /usr/columbus/users30/proebst/bde/input/nom_2_config.dat Bad File: /usr/columbus/users30/proebst/bde/reports/sqlloader/bad/nom_2_config.bad

Discard File: /usr/columbus/users30/proebst/bde/reports/sqlloader/dis/nom_2_config.dsc (Allow all discards)

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–30


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Number to load: ALL

Number to skip: 0Errors allowed: 50

Bind array: 64 rows, maximum of 65536 bytesContinuation: none specified

Path used: ConventionalSilent options: FEEDBACK

Table T_BDE_BATCH_CONFIGS, loaded when 1:1 != 0X23(character ’#’)Insert option in effect for this table: REPLACE

TRAILING NULLCOLS option in effect

Column Name Position Len Term Encl Datatype

–––––––––––––––––––––––––––––– –––––––––– ––––– –––– –––– –––––––––––––––––––––F_FILE_NAME FIRST * WHT O(”) CHARACTER

F_TABLE NEXT * WHT O(”) CHARACTER F_ID_TYPE NEXT * WHT O(”) CHARACTER

F_ID NEXT * WHT O(”) CHARACTER

Record 1: Discarded – failed all WHEN clauses.

Record 2: Discarded – failed all WHEN clauses.Record 3: Discarded – failed all WHEN clauses.


Record 6: Discarded – all columns null.

Table T_BDE_BATCH_CONFIGS:

4 Rows successfully loaded. 0 Rows not loaded due to data errors.

5 Rows not loaded because all WHEN clauses were failed. 1 Row not loaded because all fields were null.

Space allocated for bind array: 65520 bytes(63 rows)Space allocated for memory besides bind array: 98668 bytes

Total logical records skipped: 0Total logical records read: 10

Total logical records rejected: 0Total logical records discarded: 5

Run began on Tue Feb 7 14:57:55 1995Run ended on Tue Feb 7 14:57:57 1995

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–31


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Elapsed time was: 00:00:02.41

CPU time was: 00:00:00.51 (May not include ORACLE CPU time)

� File nom_test_single.log



Control File: /usr/columbus/users30/proebst/mda_v3/config/mdb/install/dadi_export/bde_control_files/TEST_SINGLE.ctl

Data File: /usr/columbus/users30/proebst/bde/input/nom_test_single.dat Bad File: /usr/columbus/users30/proebst/bde/reports/sqlloader/bad/nom_test_single.bad

Discard File: /usr/columbus/users30/proebst/bde/reports/sqlloader/dis/nom_test_single.dsc (Allow all discards)

Number to load: ALL




Table TEST_SINGLE, loaded from every logical record.

Insert option in effect for this table: REPLACETRAILING NULLCOLS option in effect


–––––––––––––––––––––––––––––– –––––––––– ––––– –––– –––– –––––––––––––––––––––F_ID FIRST * WHT O(”) CHARACTER

COL_STRING NEXT * WHT O(”) CHARACTER COL_SINGLE_FLOAT NEXT * WHT O(”) CHARACTER

COL_DOUBLE_FLOAT NEXT * WHT O(”) CHARACTER COL_INTEGER NEXT * WHT O(”) CHARACTER

COL_HEX NEXT * WHT O(”) CHARACTER COL_BITSET NEXT * WHT O(”) CHARACTER

COL_PATHNAME NEXT * WHT O(”) CHARACTER COL_ENUM NEXT * WHT O(”) CHARACTER

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–32


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Column COL_STRING is NULL if COL_STRING = 0X40(character ’@’)

Column COL_SINGLE_FLOAT is NULL if COL_SINGLE_FLOAT = 0X40(character ’@’)Column COL_DOUBLE_FLOAT is NULL if COL_DOUBLE_FLOAT = 0X40(character ’@’)

Column COL_INTEGER is NULL if COL_INTEGER = 0X40(character ’@’)Column COL_HEX is NULL if COL_HEX = 0X40(character ’@’)

Column COL_BITSET is NULL if COL_BITSET = 0X40(character ’@’)Column COL_PATHNAME is NULL if COL_PATHNAME = 0X40(character ’@’)

Column COL_ENUM is NULL if COL_ENUM = 0X40(character ’@’)

Table TEST_SINGLE:


0 Rows not loaded because all WHEN clauses were failed. 0 Rows not loaded because all fields were null.

Space allocated for bind array: 65520 bytes(28 rows)

Space allocated for memory besides bind array: 104620 bytes

Total logical records skipped: 0

Total logical records read: 9Total logical records rejected: 0

Total logical records discarded: 0


Elapsed time was: 00:00:02.48CPU time was: 00:00:00.52 (May not include ORACLE CPU time)

� File nom_test_multi.log



Control File: /usr/columbus/users30/proebst/mda_v3/config/mdb/install/dadi_export/bde_control_files/TEST_MULTI.ctl

Data File: /usr/columbus/users30/proebst/bde/input/nom_test_multi.dat Bad File: /usr/columbus/users30/proebst/bde/reports/sqlloader/bad/nom_test_multi.bad

Discard File: /usr/columbus/users30/proebst/bde/reports/sqlloader/dis/nom_test_multi.dsc (Allow all discards)

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–33


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Number to load: ALL




Table TEST_MULTI, loaded from every logical record.


Column Name Position Len Term Encl Datatype–––––––––––––––––––––––––––––– –––––––––– ––––– –––– –––– –––––––––––––––––––––

F_ID FIRST * WHT O(”) CHARACTER F_ENTRY_NUMBER NEXT * WHT O(”) CHARACTER










Table TEST_MULTI: 45 Rows successfully loaded.

0 Rows not loaded due to data errors. 0 Rows not loaded because all WHEN clauses were failed.

0 Rows not loaded because all fields were null.


E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–34


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:








E-5 BDE Log Files for Case 2: Non–Nominal Operation

� File bde_load_activity.log****************************************************************** MDA Batch Data Entry Facility V1.0.0

BDE LOAD Operation Report


******************************************************************

––– Job Configuration Parameters –––

–––––––––––––––––––––––––––––––––––––––– # MISSION: DUMMY_MISSION

# SYSTEMTREE_VERSION: 2# CU_TYPE: CDU

# CU_NAME: \SSMB\CDU_DEV# CU_VERSION: 001.000.000.000 MDB_INSTANCE

nn_3_test_single TEST_SINGLE PATHNAME

nn_3_test_multi TEST_MULTI PATHNAME––––––––––––––––––––––––––––––––––––––––

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–35


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Error limit: 1000 per file

Data Checks results

* Input File nn_3_test_single: Records processed: 1

Data errors: 0

* Input File nn_3_test_multi: Records processed: 49

Data errors: 23

Total files processed: 2Total records processed: 50

Total errors detected: 23

***** BDE_LOAD finished *****

SQL*Loader errors reported in file(s): ––> nn_3_test_multi.log

––> nn_3_test_single.log

BDE data errors reported in file: ––> bde_load_errors.log

Issue BDE_STORE command to post loaded data into the MDB

or BDE_RESET command to clear the Load Area.


E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–36


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� File bde_load_errors.log

MDA Batch Data Entry Facility V1.0.0 BDE LOAD Error Report for PROEBST on 07–FEB–1995 14:36:51 £User: PROEBST MDA Batch Data Entry Facility V1.0.0 Date: 07–FEB–1995 14:36:51 BDE LOAD Error Report Item data rejected due to identifier errors Input Data File: nn_3_test_multi Error Item Identifier No. Error Message –––––––––––––––––––––––––––––––––––––––––––––––––– ––––– –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– \SSMB\CDU_DEV\BDE_TEST\NODE6 3301 Entries out of sequence 3302 Invalid Sequence Number (first entry must be #1) £User: PROEBST MDA Batch Data Entry Facility V1.0.0 Date: 07–FEB–1995 14:36:51 BDE LOAD Error Report Records rejected due to data errors Input Data File: nn_3_test_multi Entry Col Error Item Identifier No. Field name No. No. Error Message –––––––––––––––––––––––––––––––––––––––––––––––––– ––––– –––––––––––––––––––––––––––––– –––– ––––– ––––––––––––––––––––––– ––––––––––––––––––––––––––––––––––––– \SSMB\CDU_DEV\BDE_TEST\NODE0 1 COL_ENUM 10 3208 Invalid ENUMERATION val ue 2 COL_ENUM 10 3208 Invalid ENUMERATION val ue 3 COL_SINGLE_FLOAT 4 3202 SINGLE–FLOAT value out of range 4 COL_DOUBLE_FLOAT 5 3203 DOUBLE–FLOAT value out of range 5 COL_INTEGER 6 3201 INTEGER value out of ra nge \SSMB\CDU_DEV\BDE_TEST\NODE1 1 COL_SINGLE_FLOAT 4 3204 Invalid FLOAT format 2 COL_DOUBLE_FLOAT 5 3204 Invalid FLOAT format 3 COL_SINGLE_FLOAT 4 3204 Invalid FLOAT format COL_DOUBLE_FLOAT 5 3204 Invalid FLOAT format 4 COL_SINGLE_FLOAT 4 3204 Invalid FLOAT format 5 COL_DOUBLE_FLOAT 5 3204 Invalid FLOAT format \SSMB\CDU_DEV\BDE_TEST\NODE3 1 COL_SINGLE_FLOAT 4 3204 Invalid FLOAT format 2 COL_DOUBLE_FLOAT 5 3204 Invalid FLOAT format 4 COL_BITSET 8 3206 Invalid BITSET format 5 COL_BITSET 8 3206 Invalid BITSET format \SSMB\CDU_DEV\BDE_TEST\NODE4 1 COL_HEX 7 3205 Invalid HEXADECIMAL for mat 2 COL_HEX 7 3205 Invalid HEXADECIMAL for mat 3 COL_PATHNAME 9 3207 Invalid PATHNAME syntax 4 COL_PATHNAME 9 3207 Invalid PATHNAME syntax

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–37


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� File bde_store_activity.log******************************************************************

MDA Batch Data Entry Facility V1.0.0 BDE STORE Operation Report


******************************************************************

***** BDE_STORE successfully terminated *****


� File nn_3_test_single.log



Control File: /usr/columbus/users30/proebst/mda_v3/config/mdb/install/dadi_export/bde_control_files/TEST_SINGLE.ctl

Data File: /usr/columbus/users30/proebst/bde/input/nn_3_test_single.dat Bad File: /usr/columbus/users30/proebst/bde/reports/sqlloader/bad/nn_3_test_single.bad

Discard File: /usr/columbus/users30/proebst/bde/reports/sqlloader/dis/nn_3_test_single.dsc (Allow all discards)

Number to load: ALLNumber to skip: 0

Errors allowed: 50Bind array: 64 rows, maximum of 65536 bytes

Continuation: none specifiedPath used: Conventional

Silent options: FEEDBACK

Table TEST_SINGLE, loaded from every logical record.


E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–38


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



–––––––––––––––––––––––––––––– –––––––––– ––––– –––– –––– –––––––––––––––––––––F_ID FIRST * WHT O(”) CHARACTER





Column COL_STRING is NULL if COL_STRING = 0X40(character ’@’)Column COL_SINGLE_FLOAT is NULL if COL_SINGLE_FLOAT = 0X40(character ’@’)

Column COL_DOUBLE_FLOAT is NULL if COL_DOUBLE_FLOAT = 0X40(character ’@’)Column COL_INTEGER is NULL if COL_INTEGER = 0X40(character ’@’)

Column COL_HEX is NULL if COL_HEX = 0X40(character ’@’)Column COL_BITSET is NULL if COL_BITSET = 0X40(character ’@’)

Column COL_PATHNAME is NULL if COL_PATHNAME = 0X40(character ’@’)Column COL_ENUM is NULL if COL_ENUM = 0X40(character ’@’)

Record 8: Rejected – Error on table TEST_SINGLE, column COL_STRING.

Field in data file exceeded maximum specified lengthRecord 9: Rejected – Error on table TEST_SINGLE, column COL_STRING.

Logical record ended – second enclosure character not presentRecord 10: Rejected – Error on table TEST_SINGLE, column COL_PATHNAME.

Field in data file exceeded maximum specified lengthRecord 1: Rejected – Error on table TEST_SINGLE.

ORA–01401: inserted value too large for column

Record 2: Rejected – Error on table TEST_SINGLE.


Record 4: Rejected – Error on table TEST_SINGLE, column COL_INTEGER.

ORA–01722: invalid number

Record 5: Rejected – Error on table TEST_SINGLE.ORA–01401: inserted value too large for column

Record 6: Rejected – Error on table TEST_SINGLE.ORA–01461: can bind a LONG value only for insert into a LONG column

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–39


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Record 7: Rejected – Error on table TEST_SINGLE.


Table TEST_SINGLE: 1 Row successfully loaded.

9 Rows not loaded due to data errors. 0 Rows not loaded because all WHEN clauses were failed.

0 Rows not loaded because all fields were null.

Space allocated for bind array: 65520 bytes(28 rows)

Space allocated for memory besides bind array: 104635 bytes






� File nn_3_config.log



Control File: /usr/columbus/users30/proebst/mda_v3/config/mdb/install/dadi_export/bde_control_files/batch_config.ctl

Data File: /usr/columbus/users30/proebst/bde/input/nn_3_config.dat Bad File: /usr/columbus/users30/proebst/bde/reports/sqlloader/bad/nn_3_config.bad

Discard File: /usr/columbus/users30/proebst/bde/reports/sqlloader/dis/nn_3_config.dsc (Allow all discards)



E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–40


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


Continuation: none specified


Table T_BDE_BATCH_CONFIGS, loaded when 1:1 != 0X23(character ’#’)Insert option in effect for this table: REPLACE



F_FILE_NAME FIRST * WHT O(”) CHARACTER F_TABLE NEXT * WHT O(”) CHARACTER

F_ID_TYPE NEXT * WHT O(”) CHARACTER F_ID NEXT * WHT O(”) CHARACTER



Record 5: Discarded – failed all WHEN clauses.Record 6: Discarded – all columns null.

Table T_BDE_BATCH_CONFIGS:


5 Rows not loaded because all WHEN clauses were failed. 1 Row not loaded because all fields were null.





Run began on Tue Feb 7 14:35:54 1995

Run ended on Tue Feb 7 14:35:56 1995


E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–41


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� File nn_3_test_single.bad\SSMB\CDU_DEV\BDE_TEST\NODE7 ”string7 enclosed in double quotes is too long string7 enclosed in double quotes is too long string 7 enclosed in double quotes is too long string7 enclosed in double quotes is toolong string7 enclosed in double quotes is too long string7 enclosed in double quotes is too long” 1.999997 1.99977792 10099 0909009 ABCDEF10 00011001111111111111000000000101 \VALID\PATH OHM\SSMB\CDU_DEV\BDE_TEST\NODE8 ”string8 is a string 1.999998 1.99977792 10099 0909009ABCDEF10 00011001111111111111000000000101 \VALID\PA TH OHM\SSMB\CDU_DEV\BDE_TEST\NODE9 string9 1.999999 1.99977792 10099 0909009ABCDEF10 00011001111111111111000000000101 \VALID\PATH\IS\TOO\LON G\VAL-ID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VALID\PATH\IS\T OO\LONG\VALID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG\VAL-ID\PATH\IS\TOO\LONG\VALID\PATH\IS\TOO\LONG OHM\SSMB\CDU_DEV\BDE_TEST\NODE0 string0 1.123456 1.123456789012345678901234567890 2147483647 0123456789ABCDEF01 000110011111111111110000 00000101 \WEL-COME\TO\THE\PATHNAME\TEST1 AMPERE\SSMB\CDU_DEV\BDE_TEST\NODE1 string1 000000000000000000000000001.999 000000000000000000000000001.999 2147483647 0123456789ABCDEF01 00 011001111111111111000000000101 \WELCOME\TO\THE\PATHNAME\TEST1 AMPERE\SSMB\CDU_DEV\BDE_TEST\NODE3 ”string3 with blanks” 1.999993 1.99992 +–0 0909009A1 00011001111111111111000000000101 \PATH\PATHNAME AMPER E\SSMB\CDU_DEV\BDE_TEST\NODE4 ”string4 ””String4”” with blanks” 1.999994 1.99977792 10099 0909009ABCDEF10 0001100111111111111100000000 01010101 \VALID\PATHOHM\SSMB\CDU_DEV\BDE_TEST\NODE5 string5 1.999995 1.99977792 –10099.1 0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF01 23456789ABCDEF0123456789ABCDEF0123456789ABC-DEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123456789ABCDEF 00011001111111111111000000000101 \VALID\PATHOHM\SSMB\CDU_DEV\BDE_TEST\NODE6 ”string6 exceed range of COL_STRING (40) but not 255” 1.999996 1.99977792 10099 0909009ABCDEF10 00011001 111111111111000000000101\VALID\PATH OHM

� File nn_3_test_multi.log



Control File: /usr/columbus/users30/proebst/mda_v3/config/mdb/install/dadi_export/bde_control_files/TEST_MULTI.ctlData File: /usr/columbus/users30/proebst/bde/input/nn_3_test_multi.dat

Bad File: /usr/columbus/users30/proebst/bde/reports/sqlloader/bad/nn_3_test_multi.bad Discard File: /usr/columbus/users30/proebst/bde/reports/sqlloader/dis/nn_3_test_multi.dsc

(Allow all discards)



Continuation: none specifiedPath used: Conventional

Silent options: FEEDBACK

Table TEST_MULTI, loaded from every logical record.Insert option in effect for this table: REPLACE



E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–42


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


F_ID FIRST * WHT O(”) CHARACTER

F_ENTRY_NUMBER NEXT * WHT O(”) CHARACTER COL_STRING NEXT * WHT O(”) CHARACTER

COL_SINGLE_FLOAT NEXT * WHT O(”) CHARACTER COL_DOUBLE_FLOAT NEXT * WHT O(”) CHARACTER

COL_INTEGER NEXT * WHT O(”) CHARACTER COL_HEX NEXT * WHT O(”) CHARACTER

COL_BITSET NEXT * WHT O(”) CHARACTER COL_PATHNAME NEXT * WHT O(”) CHARACTER

COL_ENUM NEXT * WHT O(”) CHARACTER






Record 31: Rejected – Error on table TEST_MULTI, column COL_INTEGER.

ORA–01722: invalid number

Table TEST_MULTI:

49 Rows successfully loaded. 1 Row not loaded due to data errors.

0 Rows not loaded because all WHEN clauses were failed. 0 Rows not loaded because all fields were null.






E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–43


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:


� File nn_3_test_multi.bad\SSMB\CDU_DEV\BDE_TEST\NODE6 1 string6.1 1.000007 1.000000000000007 5F99 0123456789ABCDEF10 00011001111111111111000000000101 \PATH\PATHBLUE

E–44

CGS–RIBRE–SUM–00032 03.07.2015– –E–44


Datumvon

/Issue:/Rev.:

/Page:/Date:

/of:

Datum/Date:



mda reference manual cgs–ribre–sum–0003 8–qa 03.07

Documents