integrated information support system li12 … · 'a-r191 955 integrated information support...

'A-R191 955 INTEGRATED INFORMATION SUPPORT SYSTEM (I ISS) YOLUME 5 LI12COhhMO DATA MODEL S.. (U) GENERAL ELECTRIC COSCHENECTADY NY PRODUCTION RESOURCES CONSU..

UNCASSFIE J ALHOF ETAL. 91 NOV 85 UM-6291411SS F/O 12/5 N

mosoEEmhhholh

iliu LM32 2

11W11

MICROCOPY RESOLUTION TEST CHARTNATIONAL BURAUJ Of STANDARDS 1963-A

mi-mi in lnal0a

AD-181955AFVAL-TR-86-4005Vol V I Part 7

INTERATED INFORMATIONSUPPORT SYSTEM (IISS)volume V - Common Data Model SubsystemPart 7 - NDDL User's Guide

DTICGeneral Electric Company ELECTE

Production Resources Consulting JUL 0 6 8One River RoadSchenectady, New York 12345 D~D

Final Report for Period 22 September 1980 - 31 July 1985

November 1985

Approved for public release; distribution is unlimited.

MATERIALS LABORATORYAIR FORCE WRIGHT AERONAUTICAL LABORATORIESAIR FORCE SYSTEMS COMMANDWRIGHT-PATTERSON AFB, OH 45433-6533

L-

NOTICE

When Government drawings specifications. or other data are used for any purpose other thanin connection with a definitely related Government procurement operation, the United StatesGovernment thereby incurs no responsibility nor any obligation whatsoever, and the fact that thegovernment may have tormulated- furnished, or in any way supplied the said drawingsspecifications or other data. is not to be regarded by implication or otherwise as in anymanner licensing the holder or any other person or corporation, or conveying any rights orpermission to manufacture. use. or sell any patented invention that may in any way be relatedthereto

This report has been reviewed by the Office of Public Affairs (ASD/PA) and is releasable to theNational Technical Information Service (NTIS) At NTIS. it will be available to the generalpublic, including foreign nations.

This technical repo has been reviewed and is approved for publication.

ND L./J PROJECT MANAGER DATEA FINA L./ML TC

W IGHT PA ERSON AFB OH 45433

FOR THE COMMANDER.-

• (E0ALD C. SHUMAKER, BRANCH CHIEF DATEAFWAL/MLTCWRIGHT PATTERSON AFB OH 45433

'if your address has changed, if you wish to be removed from our mailing list, or if theaddressee is no longer employed by your organization please notify AFWAL/MLTC, W.PAFB. OH45433 to help us maintain a current mailing fist.'

Copies of this report should not be returned unless return is required by secuntry c',',"ra,-'tcontractual obligations, or notice on a specibc document

smeum'?.V C6&se.cA?1O'. of ?a$$ Past

REPOR DOCUMENTATION PAGE '4/1~I~j~Unclassified,

11g SICUm.'vr C1.9,g@ite05uf A&IU@MRh? 3 Of73ete5:Vs~~bS M&P@R7

Approved for public release;lb OC&.h~s~~at~b,~wb0A~e.S S~ssu&Sdi stributi on Is unlimited.

4. f,6M65.6ft @UG&A7.05.IC WiORT "W"61106 6. 6s05tTaifS @bGAifa5AYO. 90 ftweASS 5ugAisi

AFVAL-TR-6-4006 Vol V,* Part '7

G&. I&SANR 0 PU0s OWues ORGAseZAT1?,W opic @596(19 %S~I Aug Of M051 @AmOR ORnGA10061080

Production Resources C onsult lag AVLNft. &books" IC4W,. #u a i ZP Ca) fbt A005555 (tii.5 u51 mp S Cow$i

a River Road AF 0344353Sohoeeta61y WT 123465 WA2 N44363

ateFrcel labsoraoyn OA A1'VAL'iNLTC 733610-C-9155Ai a orow Ceas. Cmand USAFsOSud 55w~w O

MOGSAII "J C? TWASK *@mIE USI?Wight-PAutrsom An. Ohio 45433 INKNONoN.01.

(see Reverse)II

12-fSMG8OeA4-AUW@1W6bW AlthoffJ. Apicella.h. bernier.M. Dradley.W. Singh.S. Thompson.D.Rgan.J. Leifeste.B. ___

13a, tVVI of Asporn? 138. TOWE covefSo 16. SaTE of WORT Cyr.. Mo.. Sint is. face COUNTSfinalI 1eehaleal saipers 1 2 SePt So60 31 hy JiN mS$ 1985 November I ISO

IS. uPPAEMESAMY OTAT@Sbe computer software contained herein are theoretical and/orICANProect rieity 201 references that In ao way reflect Air Force-owned or -developedSCAMProjct riortT 601computer software.

605*,, (0015 14.11JSC? T&US rCenar on imr - f Vmesumss ae saf t 6f at" nmmior

is. ABTRA&CY ccme~ do soup if mWef 40 alits ft OWs avower#

The Common Data Model Processor (CDMP) is a mechanism by which applicationprograms can retrieve and update data without knowing where or how the dataare stored. The CDMP relies on three types of schemas (conceptual. external.and internal) and on two types of schema mappings (conceptual -to-external andconceptual -to- internal ). A schema Is a description of data from a particularviewpoint. A mapping Is a description of the correspondence between elementsof one schema and those of another. The schemas and mappings are stored in adatabase, called the Common Data Model (CDM). where they are available to the

4 CD9(P software. The Neutral Data Definition Language (WWI,) Is the means forstoring and maintaining the schemas and mappings In the CDN database. Thismanual explains the syntax and semantics of each NDDL consizd.

6ftc6^1811120"O~WITIm~ D *ME as WTv. r g warnU ms Unclassified

David 16. J"Asea Waedv As, Caer O.IATL ftv $15-255-0"

DO FORM 1473. g APR b9oof Of I~a "o n tosso10Ai. Unclassified8

MCtum,?, Cia5IPeCA1O#Ef O T044 PAG

11. Title

Integrated information Support System (OISS)Vol V - Common Data Model SubsystemPart 7 - NDDL User's Guide

A 8 D 86 147717 Jul 1988

I ea

Accesion For

NTIS CRA&IDTIC TAB 0Uiannourced 1Ju ,titfi.ca~n . ........... .

By ......... ... ......Dist; ibution I

Availability Ccdies

oil t ,, cial

LA 4'I j %

UK 620141100

1 November 1985

PREFACE

This user's manual covers the work performed under AirForce Contract F3361-80-C-5155 (ICAM Project 6201). Thiscontract is sponsored by the Materials Laboratory, Air ForceSystems Command, Wright-Patterson Air Force Base, Ohio. It wasadministered under the technical direction of hr. Gerald C.Shumaker, ICAM Program Manager, Manufacturing TeohnologyDivision. through Project Manager, Mr. David Judson. The PrimeContractor was Production Resources Consulting of the GeneralElectric Company, Schenectady, New York, under the direction ofMr. Alan Rubenstein. The General Electric Project Manager wasMr. Myron Hurlbut of Industrial Automation Systems Department,Albany, New York.

Certain work aimed at improving Test Bed Technology hasbeen performed by other contracts with Project 6201 performingintegrating functions. This work consisted of enhancements toTest Bed software and establishment and operation of Test Bedhardware and communications for developers and other users.Documentation relating to the Test Bed from all of thesecontractors and projects have been integrated under Project 6201for publication and treatment as an integrated set of documents.The particular contributors to each document are noted on theReport Documentation Page (DD1473). A listing and descriptionof the entire project documentation system and how they arerelated is contained in document FTR620100001, Project Overview.

The subcontractors and their contributing activities wereas follows:

TASK 4.2

Subcontractors Role

Boeing Military Aircraft Reviewer.Company (BKAC)

D. Appleton Company Responsible for IDEF support,(DACOM) state-of-the-art literature

search.

General Dynamics/ Responsible for factory viewFt. Worth function and information

models.

i lii

-v. 'N

UN 6201411001 November 1985

Suboontractors Role

Illinois Institute of Responsible for factory viewTechnology function research (IITRI)

and information models ofsmall and medium-size business.

North Amerioan Rockwell Reviewer.

Northrop Corporation Responsible for factory viewfunction and informationmodels.

Pritsker and Associates Responsible for IDEF2 support.

SofTech Responsible for IDEFO support.

TASKS 4.3 - 4.9 (TEST 83W)

Subcontractors Role

Boeing Military Aircraft Responsible for consultation onCompany (DMAC) applications of the technology

and on IBM computer technology.

Computer Technology Assisted in the areas ofAssociates (CTA) communications systems, system

design and integrationmethodology, and design of theNetwork Transaction Manager.

Control Data Corporation Responsible for the Common Data(CDC) Model (CDM) implementation and

part of the CDM design (sharedwith DACOM).

D. Appleton Company Responsible for the overall CDM(DACON) Subsystem design integration

and test plan, as well as partof the design of the CDM(shared with CDC). DACOM alsodeveloped the IntegrationMethodology and did the schemamappings for the ApplicationSubsystems.

iv

UK 6201411001 November 1985

Subcontractors Role

Digital Fquipment Consulting and support of theCorporation (DEC) performance testing and on DEC

software and computer systemsoperation.

McDonnell Douglas Responsible for the support andAutomation Company enhancements to the Network(NoAuto) Transaction Manager Subsystem

during 1984/1985 period.

On-Line Software Responsible for programming theInternational (OSI) Communications Subsystem on the

IBM and for consulting on theIBM.

Rath and Strong Systems Responsible for assistance inProducts (RSSP) (In 1985 the implementation and use ofbecame NoCormack & Dodge) the MRP II package (PIOS) that

they supplied.

SofTech, Inc. Responsible for the design andimplementation of the NetworkTransaction manager (NTI) in1981/1984 period.

Software Performance Responsible for directing theEngineering (SPE) work on performance evaluation

and analysis.

Structural Dynamics Responsible for the UserResearch Corporation Interface and Virtual Terminal(SDRC) Interface Subsystems.

Other prime contractors under other projects who havecontributed to Test Bed Technology, their contributingactivities and responsible projects are as follows:

Contractors ICAM Project Contributing Activities

Boeing Military 1701, 2201, Enhancements for IBMAircraft Company 2202 node use. Technology(BMAC) Transfer to Integrated

Sheet Metal Center(IsMC).

v

UK 6201411001 November 1985

Contractors ICAN ProJect Contributing Activities

Control Data 1502, 1701 IISS enhancements toCorporation (CDC) Common Data Model

Processor (CDP).

D. Appleton Company 1502 IISS enhancements to(DACOM) Integration Methodology.

General Electric 1502 Operation of the TestBed and communicationsequipment.

Hughes Aircraft 1701 Test Bed enhancements.Company (MAC)

Structural Dynamics 1502, 1701, IISS enhancements toResearch Corporation 1703 User Interface/Virtual(SDRC) Terminal Interface

(UI/VTI).

Systran 1502 Test Bed enhancements.Operation of Test Bed.

vi

UK 6201411001 November 1985

TABLE OF CONTENTS

Pafe

SECTION 1.0 INTRODUCTION ......................... 1-1

SECTION 2.0 NDDL OVERVIEW ........................ 2-12.1 NDDL Environment ................... 2-12.1.1 Batch Environment ................ 2-12.1.2 Interactive Environment

(Without II88 UI/VTI) ........... 2-12.1.3 Interactive Enviornment

(with 1188 UI/VTI) .............. 2-22.2 Using the NDOL Form ................ 2-22.2.1 NDDL Form Description ............ 2-22.2.2 Form Use ......................... 2-42.2.3 NDDL Command ..................... 2-42.2.4 Error Message Reporting .......... 2-62.3 NDDL Command Syntax ................ 2-72.4 NDDL Reserved Words ................ 2-7

SECTION 3.0 NDDL COMMANDS ........................ 3-13.1 Alter Alias ........................ 3-23.2 Alter Attribute .................... 3-33.3 Alter Domain ....................... 3-43.4 Alter Entity ....................... 3-63.5 Alter Map ........................... 3-83.6 Alter Model ........................ 3-113.7 Alter Relation ..................... 3-123.8 Check Model ........................ 3-143.9 Combine Entity ..................... 3-153.10 Compare Model ....................... 3-173.11 Copy Attribute ..................... 3-183.12 Copy Description ................... 3-193.13 Copy Entity ........................ 3-203.14 Copy Model ......................... 3-233.15 Create Alias ....................... 3-243.16 Create Attribute ................... 3-253.17 Create Domain ...................... 3-263.18 Create Entity ...................... 3-273.19 Create Map ......................... 3-293.20 Create Model ....................... 3-313.21 Create Relation .................... 3-323.22 Create View ........................ 3-343.23 Define Database .................... 3-37

vii

UK 6201411001 November 1985

TABLE OF C)ONTENTS (Conti£nued)

3.24 Define Record.........................3-393.25 Define Set ............. 3-423.26 Describe .............. 3-443.27 Drop Alias ............. 3-463.28 Drop Attribute........................3-473.29 Drop Database........................ 3-483.30 Drop Douaila......................... 3-493.31 Drop Entity.......................... 3-503.32 Drop Field........................... 3-513.33 Drop Keyword ......................... 3-523.34 Drop Map............................. 3-533.35 Drop Model........................... 3-543.36 Drop Record.......................... 3-553.37 Drop Relation.........................3-563.38 Drop Set............................. 3-573.39 Drop View............................ 3-583.40 Halt................................. 3-593.41 Merge Model.......................... 3-603.42 Rename............................... 3-62

APPENDIX A. NDDL COMMAND ERROR MESSAGES............A-1

APPENDIX B. GLOSSARY............................... B-1

APPENDIX C. REFERENCES............................. C-i

LIST OF ILLUSTRATIONS

Figure Title Page

2-1 VT Function Keypad......................2-5

LIST OF TABLES

Table Title Page

2-1 Cross Reference of Object Typesand NDDL Commands..................... 2-9

viii

UN 6201411001 November 1985

SEC'ION 1

INTRODUCTION

The Neutral Data Definition Language, hereafter NDDL, is aninterpretive language that was developed to populate andmaintain the Common Data Model database (CDX1 Doc. ControlNo.-OCS 620141000). As the NDDL is intended to be used by dataprocessing professionals who are experts with various data basemanagement systems, a discussion of data base management systemsis not included in this document (see CDX Administrators ManualDoe. Control No. UK 620141000). Furthermore, an understandingof the CDX database is necessary.

The CDX Database uses a Three-Schema approach based upon"The ANSI/X3/SPARC DBMS Framework: Report of the Study Group onData Base Management Systems". In the IISS, the Three-SchemaArchitecture is implemented through the CDK facilities to storeeach of the three types of schemas and the interschema mappings.The NDDL supports the population and maintenance of appropriaterepresentations for each of the three types of schemas.

The conceptual schema is represented by an IDEF-l model.The CDM stores this model in terms of entity classes, attributeclasses, and relation classes.

The external schemas are represented by tables. Themappings between these tables and the IDEF-l model of theconceptual schema are part of the CDM database.

The internal schemas are represented in terms of physicaldatabase components, including record types and inter-recordrelationships.

Section 2 of this manual is a discussion of how tointerface with the NDDL processor and the NDDL syntax which issimilar to that of the Neutral Data Manipulator Language (seeNDML Guide PRM 620141200).

Actual NDDL commands are explained in Section 3 which isfollowed by NDDL Command Error Messages which are listed inAppendix A.

Appendix B is a Glossary of the more important terms usedin this guide and is followed by a list of references.

1-I

UK 6201411001 November 1985

SECTION 2

OVERVIEW

* 2.1 NDDL ENVIRONMENT

NDDL can be executed from three environments within IISS:

- batch environment- interactive environment without the IISS User

Interface/Virtual Terminal Interface (UI/VTI)- interactive environment with the IISS User

Interface/Virtual Terminal Interface (UI/VTI)

The environment is determined from the users response to the"args" prompt upon NDDL activation as depicted below.

2.1.1 Batch Environment

args: , file specification , file specification

, file specification - redirect the input for NDDL tocome from the file specified

) file specification - redirect the output for NDDL to

be written to the file specified

file specification - DISKNAME /UFD/SFD/FILE.EXTENSION

Example:

args: 'NDDL.INP )NDDL.OUT

NDDL.INP is a file containing NDDL commands.

Note:This file name must follow the Unix standardfor naming files, not that of the host operatingsystem.

2.1.2 Interactive Environment (without IISS UI/VTI)

args: (carriage return)

The NDDL "NEXT COMMAND" prompt will be displayed, at which time

2-1

r ,,, . . ,. 2 •. N . .... .

UK 6201411001 November 1985

the user may enter any valid NDDL command.

Example:

aLrgs: (carriage return)

NEXT COMMAND--

CREATE MODEL test-model ;

--COMMAND SUCCESSFUL--

NEXT COMMAND--

HALT;

2.1.3 Interactive Environment (with IIS UI/VTI)

args:-I

The NDDL form viii be displayed, at which time the user mayenter NDDL commands. A description of the form and how it isused for NDDL is contained in the next section of this document*Using the NDDL Form.*

2.2 Using the NDDL Form

This section describes the use of the NDDL form. The formmanipulations are supported by the IISS User Interface/VirtualTerminal Interface (UI/VTI) software. This section will alsodescribe the detailed forms procedures unique to the NDDLapplication. For general information regarding forms use, referto the IISS UI/VTI Terminal Operator's Guide.

2.2.1 NDDL Form Description

The NDDL form appears immediately following NDDLactiviation with the -I parameter as explained in the "NDDLEnvironmentu section. A description of the individual fieldsfollows.

Field 1 - Current Model Field

This field displays the current model name. The currentmodel field is modified each time a CREATE MODEL or ALTERMODEL command is successfully executed. If neither

2-2

UN 6201411001 November 1985

command has been executed in a session, the NOT YETSPECIFIEDO message will appear In this field.

Field 2 - Current Database Field

This field displays the current database name. Thecurrent database field is modified each time a DEFINEDATABASE, DEFINE SET, or DRFINE RECORD command issuccessfully executed. If none of the commands have beenexecuted in a session, the ONOT YET SPECIFIED* messagewill appear in this field.

Field 3 - eDOL Command Field

This is the field in which NDI) commands are entered.This field is 78 columns wide and 100 lines long and isviewed 3 lines at a time. This field may be paged andscrolled as described in the IISS UI/VTI TerminalOperator's Guide.

Field 4 - Message Area

This field displays NDDL error and Informative messages.The message area is 30 lines long and is viewed 3 lines ata time. This field may be paged and scrolled as describedin the IISS UI/VTI Terminal Operator's Guide.

Field 5 - Message Line Number Field

The message line number field serves two purposes. It isused to display the number of the message displayed infield 6, the message line. The message line number isalso used to select a particular message in field 6 forviewing. The user can position the cursor to this field,enter a number from 01 to 99 and read the correspondingmessage, assuming one exists.

Field 6 - Message Line

The message line is 99 lines long, viewed one line at atime. This field may contain informative and errormessages which overflow field 4. In addition, this fieldwill contain summary messages indicating whether or noterrors have occurred and the number of generated messages.

2-3

UK 6201411001 November 1985

2.2.2 Form Use

VTlOO Keypad

The VT0 keypad is depicted in Figure 2-1. The keys whichapply uniquely to UDOL are:

pf4 - Press pf4 to terminate NDlL. This key forces anMD HALT command, freeing the user fromexplicitly entering the HALT.

enter - Press enter to initiate execution of the enteredNDlL command(s). After the oommands areexecuted or syntax checked, the form reappears.If an error was encountered, all commandsreappear along with their error messages. If,however, no errors are encountered, the commandsdo not reappear when the form is repainted.

0 (pf16) Press 0 to initiate execution of the enteredNDDL command(s). After the commands areexecuted or syntax checked, the form reappearswith the previously entered commands showingwhether or not error occurred. This feature isintended to be used when the user has a numberof similar commands to execute. The user needonly modify that dynamic portion of the commandfor each subsequent execution.

All other keypad keys operate as described in the UI/VTITerminal Operator's Guide. In addition, there are a number ofnon-keypad keys that manipulate the form and are described inthe same document.

2.2.3 NDDL Command Entry

All NDDL commands must be entered in the NDDL command fieldwith syntax as described in the "NDDL Commands" section of thisdocument. The terminating semicolons are mandatory for allcommands. The user may enter as many complete commands as maybe contained in 100 lines. After execution has started, theform will not reappear until all commands have executed or hadtheir errors diagnosed.

2-4

UN 6201411001 November 1985

--------- I---- I--------Ipfl I pf2 1 pf3 1 pf4100WD I help I debug I quit

II I I HALTIII---------------- I --------1 7 (pf5 1 8 (pfe) 1 9 (pf7) I - (pf8)scroll I scroll I scroll I scrollIhleft I right I up IdownI--------I---------------I------------I---------------I14 (pf9)I 5 (pflO) 1 6 (pfll) I , (pfl2)page I page Ipage I PageIIheft I right I up I downI--------I---------------I------------I---------------I91(pfl3)1 2 (pf14) 1 3 (pfl5) I enterI

I I Execute NDDL iI 1 commands - I

--------I--------------I-----------I redisplay thel90 (pf 16) 1 (pfl7) Icommands onlyiExecute NDDL commands i I if errors Iredisplay the commandsi I encountered Ilunconditionally I I II------------------------I------------ I--------------- I

Figure 2-1. MOO0 Function Keypad

2-5

UK 6201411001 November 1985

2.2.4 Error Messiago Reportia

After a form of commands has executed, error messages mayor may not appear. If no errors have occurred, a "no errorsencountered" message will appear In the message line of theform. If errors have occurred. a "command(s) completed - nerror messages" message will appear with n equal to the numberof messages generated. Note that a particular command maygenerate many error messages. The message area may contain upto 30 messages, displayed 3 messages at a time. Should there bemore than 30 messages generated, the final line of the messagearea will contain the following message: PLEASE REFER TO THEMESSAGE LINE FOR REMAINING MESSAGES. Since the message lineindicates that there were n messages generated and since 30messages are contained In the message area, (n-30) messagesremain to be viewed in the message line. Position the cursor tothe message line number field (field 4), key In 01 and pressenter for the first message. For each subsequent message,increment field 4 by one and press enter.

If many commands have been entered and errors wereencountered, all commands preceding the erroneous command willhave executed, applying their specified database modifications.The erroneous command and all subsequent commands in the sameform will not execute. The commands following the orroneouscommand on the same form will be syntax checked only.

To assist in matching the error messages with the properNDDL commands, the following messages are generated:

--COMMAND SUCCESSFUL-- - The command hassuccessful ly executed.

--NO CHANGE MADE-- - Errors were encountered.The detailed error messageswhich apply to this messageprecede it.

--COMMAND SYNTAX CORRECT-- - An error In a previousNDDL command caused allsubsequent commands in theform to be syntax checkedonly.

2-6

UN 6201411001 November 1985

--INVALID SYNTAX-- - The command syntax isIncorrect.

For example, if five "--COMMAND SUCCESSFUL--" messages aregenerated before the first error message appears, the offendingNDDL command is the sixth one on the form.

2.3 NDDL COMMAND SYNTAX

In the syntactic description of the NDDL commands, thefollowing symbols are used:

[ ] indicates an optional word or phrase{ ) indicates a choice of only one word or phrase... indicates repetition of the last element; indicates the end of a command and must be entered by

the userI indicates a choice of options

All uppercase words must be specified as indicated; lowercasewords indicate a user-defined variable which the user may fillin with uppercase or lowercase letters. Lowercase words arecase sensitive, e.g., variable XYZ is not the same as variablexyz. The user may enter any string of up to 30 characters forlowercase words. These characters may be any combination ofletter, digit, dash, or underscore

Comments may be embedded by surrounding the comment with /*and */

Most repetitions are separated by a single blank space;

however, a few commands must be separated by commas.

2.4 NDDL RESERVED WORDS

Following is a list of NDDL reserved words. These wordscannot be used as a user-defined variable in any NDDL command.

ACCESSED FILES PCBADD FLOAT POSITIONALIAS FROM PRIMARYALTER HALT PSBAND HL6 RECORDAREAS HOST RELATINGAS IBM RELATIONATTRIBUTE IDMS RENAMEBY IDSII REQUIRED

2-7

MOW -

UK 6201411001 November 1985

CHARACTER INS ROLLBACKC1 CK Is SCLASS INTEGER SCEGMACOLUMNS INTO SECONDCOMBINE Is SELEETCOMMIT ITEM SELECOMPARE ITEMS SETCopy KEY aImEDEATE KZYWORD SIZEDATA LINKED STANDARDDATABASE LENGTH STARTDATA ITEM MANY RUCTUREDATAIZL MAPTSBSEDECIEm MERGE TABLEDEFINE MIGRATES TODESCRIBE MODEL TOTALDESCRIPTION NAMED UDOMAIN NUMERIC UNKNOWNDROP OF UNSIGNEDELEMENTS ON TYPEENTITY OPTIONAL VALUEEXCEPT ORACLE VAX_11EXIT OWNED VAXFEEDBACK P VIEWFIELD PACKED WHEREFIELDS PATH WITHFILENAME PASSWORD

2-8

UK 6201411001 November 1985

A cross reference between NDDL object types and NDDL

command is contained in Table 2-1.

TABLE 2-1

CROSS REFEREN CE OF OBJECT TYPES AND NDDL COMMANDS

OBJECT TYPE mom COMMAND

ALIAS ALTER ALIASCOMBINE ENTITYCOPY ATTRIBUTECOPY ENTITYCOPY MODELCREATE ALAISDROP ALIASMERGE MODEL

AREA DEFINE DATABASEDEFINE RECORD

ATTRIBUTE CLASS ALTER ATTRIBUTEALTER ENTITYALTER MAPCOPY ATTRIBUTECOPY DESCRIPTIONCREATE ALIASCREATE ATTRIBUTECREATE ENTITYDESCRIBE ATTRIBUTEDROP ALIASDROP ATTRIBUTERENAME ATTRIBUTE

CARDINALITY ALTER RELATIONCREATE RELATION

DATA ITEM CREATE VIEW

2-9

UK 6201411001 November 1985

TABLE 2-1 (Continued)

CROSS REFERENCE OF OBJECT TYPES AND NDDL COMMANDS

OBJECT TYPE NDDL COMMAND

DATABASE ALTER NAPCREATE MAPDEFINE DATABASEDEFINE RECORDDEFINE SETDROP DATABASEDROP FIELDDROP RECORDDROP SET

DATA TYPE ALTER DOMAINALTER NAPCREATE DOMAINCREATE NAPCREATE VIEW

DESCRIPTION COMBINE ENTITYCOPY ATTRIBUTECOPY DESCRIPTIONCOPY ENTITYCOPY MODELDESCRIBE ATTRIBUTEDESCRIBE ENTITYDESCRIBE RELATIONMERGE MODEL

DOMAIN ALTER DOMAINCREATE ATTRIBUTECREATE DOMAINDROP DOMAINRENAME DOMAIN

2-10

UN 6201411001 November 1985




ENTITY CLASS ALTER ENTITYALTER MAPALTER RELATIONCOMBINE ENTITYCOPY DESCRIPTIONCOPY ENTITYCREATE ALIASCREATE ENTITYCREATE MAPCREATE RELATIONCREATE VIEWDESCRIBE ENTITYDROP ALIASDROP ENTITYDROP MAPDROP RELATIONRENAME ENTITYALTER MAPCREATE MAPDEFINE RECORDDEFINE SETDROP FIELD

FILE COMBINE ENTITYCOPY ATTRIBUTECOPY ENTITYCOPY MODELDEFINE DATABASEDESCRIBE ATTRIBUTEDESCRIBE ENTITYDESCRIBE RELATIONMERGE MODEL

KEYCLASS ALTER ENTITYALTER RELATIONCREATE ENTITYCREATE RELATION

KEY FIELD DEFINE RECORD

2-11

UN 6201411001 November 1985



OBJECT TYPE NDDL COMMAND----------------------------

KEY WORD ALTER ATTRIBUTEALTER ENTITYALTER RELATIONCOMBINE ENTITYCOPY ATTRIBUTECOPY ENTITYCOPY MODELCREATE ATTRIBUTECREATE ENTITYCREATE RELATIONIROP KEYWORDMERGE MODELRENAME KEYWORD

MAP ALTER MAPDROP MAP

MODEL ALTER MODELCHECK MODELCOMBINE ENTITYCOMPARE MODELCOPY ATTRIBUTECOPY DESCRIPTIONCOPY ENTITYCOPY MODELCREATE MODELDROP MODELMERGE MODELRENAME MODEL

PASSWVORD DEFINE DATABASE

PATH DEFINE SETDROP SET

2-12

UN 6201411001 November 1985



OBJECT TYPE NDDL COMMAND----------------- ------------

PCB DEFINE DATABASEDEFINE RECORDDEFINE SETDROP DATABASEDROP FIELDDROP RECORDDROP SET

PSE DEFINE DATABASE

RECORD ALTER MAPCREATE MAPDEFINE RECORDDEFINE FIELDDEFINE SETDROP FIELDDROP RECORD

RELATION CLASS ALTER MAPALTER RELATIONCOPY DESCRIPTIONCREATE MAPCREATE RELATIONCREATE VIEWDESCRIBE RELATIONDROP NAPDROP RELATIONRENAME RELATION

SCHEMA DEFINE DATABASE

SEGMENT DEFINE RECORDDROP FIELDDROP RECORD

2-13

UN 6201411001 November 1985


CROSS REFERENCE OF OBJECT TYPES AND NDEJ COUNANDS


SET ALTER MAPALTER RELATIONCREATE MAPCREATE RELATIONDEFINE SETDROP SET

SUBSCHEMA DEFINE DATABASE

TABLE DEFINE RECORDDIROP FIELD

TAG MNZ ALTER MAPALTER RELATIONCREATE MAPCREATE RELATIONCREATE VIEWDROP MAP

VIEW CREATE VIEWDROP VIEWRENAME VIEW

2-14

UN 6201411001 November 1985

SECTION 3

NDDL COMMANDS

This section describes each NDDL comaand. The syntax ofeach command is given followed by command semiantics and commandexamples.

3-1~ *

UN 6201411001 November 1985

3.1 ALTER ALIAS

Syntax:

ALTER ALIAS { ENTITY eQ namel [IS] ec name2I ATTRIBUTE ac namel [IS] ac-name2 );

Comments:

• The following elements must exist in the Common DataModel:

entity or attribute with both primary and alias names

• The command svitches the current primary and the aliasnames.

• The current primary names are ec nanel and ac namel; thecurrent aliases are ec name2 and a&cname2.

Examples:

ALTER ALIAS ENTITY CUSTOMER IS CUSTALTER ALIAS ATTRIBUTE ORDER NUMBER ORDNO

3-2

UN 6201411001 November 1985

3.2 ALTER ATTRIBUTE

Syntax:

ALTER ATTRIBUTE (CLASS) ac name [DOMAIN domain_name][DROP KEYWORD keyword-...[ADD KEYWORD keyword... ];

Comments:

* The following elements must exist in the Common DataModel:

modelattribute

* ALTER ATTRIBUTE (CLASS] ac name

The attribute is altered with one of the optionsspecified.

* [DOMAIN domain_name]

When a domain name is specified the validity of the Domainis checked and processing will halt if it is invalid.

If the domain name is valid, ATTRIBUTE CLASS ac name willbe updated to indicate the new domain-no.

" DROP KEYWORD keyword...

Keyword references are deleted.

" ADD KEYWORD keyword...

The keyword(s) is created if it does not already exist.

The attribute keyword reference(s) is created.

Examples:

ALTER ATTRIBUTE CLASS ACORDERINFO DOMAIN ADDRESSADD KEYWORD ZIPDROP KEYWORD COUNTY:

3-3

UK 620141100I November 1985

3.3 ALTER DOMAIN

Syntax:

ALTER DOMAIN domain nameCAMV I DATA ITYPEdata-type Dame / INTEGER integer 1C: Integer2l I

I CHARACTERISIGNEDFLOATUNSIGNEDPACKED/

(DROP I DATA I TYPE data -type-name ...ALTER [ DATA I TYPEdata-type name /INTEGER Integerl[:integerz] I

CHARACTERSimNED

I FLOATUNSIGNEDPACKED/

CTO STANDARD 13;

Comments:

* The following elements must exist In the Common DataModel:

domaindata type

0 Integeri [integerz] ... states a range of permissablevalues where integerl is the ending value and Integer2 isthe beginning value (integer2 cannot be greater thanintegerl). Integer I can be used to specify a singlevalue for a data type.

0 The NDDL data types correspond to the followingCOBOL/FORTRAN data types:

NDDL Data Type COBOL/FORTRAN Data Type

INTEGER FORTRAN binary integerCHARACTER XC n)SIGNED 599 V99FLOAT FORTRAN floating pointUNSIGNED 99V99PACKED COMP-3

3-4

UK 6201411001 November 1985

* Am [ DATA ] TYPEdata type_name / INTEGER Integer [ :Integer2] \

I CHARACTER ISIGNED

I FLOAT II UNSIGNED\ PACKED /

The data type will be inserted as user defined.

* DROP ((DATA] TYPE datatype name)...

If it is determined that the data type is associated witha data field, data item or attribute class the data typewill not be dropped. All attribute classes that use thedata type are reported to the user.

A standard data type cannot be dropped.

ALTER [ DATA ] TYPEdata typename / INTEGER integerl[:integer2] \

I CHARACTER ISIGNED

I FLOATI UNSIGNED I\ PACKED /

TO STANDARD ]

The data type is altered to "standard" (it will become thecurrent standard), and the previous standard will become auser defined data type for the same domain.

The data type may also be altered to another legal typewith a new size and decimal specifications.

Examples:

ALTER DOMAIN ADDRESSADD DATA TYPE ALPHANUMERC integer 5:2DROP DATA TYPE NUMERICALTER TYPE ALPHA character 30 to standard;

3-5

UK 6201411001 November 1985

3.4 ALTER ENTITY

Syntax:

ALTER ENTITY [CLASS) e name[ADD [KEY [CLASS] k name[- ac name ... ]]...

[[OWNED) ATTRIBUTE-[CLASS) a&cname ... ][KEYWORD keyword ... 11

[DROP [KE [CLASS) ko name ] ...[OWNED) ATTRIBUTE TCLASS) acname ... ]

[KEYWORD keyword ... ]];

Comments:


entityattribute to be dropped or addedkey class to be dropped

* ADD KEY [CLASS] kcname [sacname ...I ...

An occurrence of attribute for acname must exist.

A new occurrence of attribute use class is created forac name if one does not already exist. If the attributeuse class does already exist, acname may not be owned byany other entity.

A new occurrence of key class is created for the entityusing kc-name.

A new occurrence of key class member Is created for theentity for each ac name. If ac name is omitted, a keyclass member occurrence is created using kc name as thename of the attribute.

0 ADD [OWNED] ATTRIBUTE [CLASS] ac name ...

New attributes for the entity being created are added.

Each attribute is created as an owned attribute class forthe entity.

A new occurrence of attribute use class is created.

3-6

A )(1 0

UK 6201411001 November 1985

* ADD KEYWORD keyword ...

The keyword references are created.

The keyword will be created if it does not already exist.

* DROP KEY [CLASS] kcname

The key class for the entity is deleted.

All key class members for the key class are deleted.

If the key class being dropped is from a completerelation, the complete relation is deleted.

All attribute use classes which were formed from amigration of that key class member and any migration ofthose attribute use classes are deleted.

The inherited attribute use class occurrence of a migrated

attribute use class is deleted.

* DROP [OWNED] ATTRIBUTE [CLASS] ac name ...

The owned attribute occurrence and the attribute use classfor ac-name is deleted.

* DROP KEYWORD keyword ...

The keyword reference is deleted.

Examples:

ALTER ENTITY CLASS EC CUSTOMERADD KEY CLASS KC CUST INFO - ACCUSTNAMEKEYWORD CUSTOMER;

3-7

UK 6201411001 November 1985

3.5 ALTER MAP

syntax:

ALTER MAP ec-name. tag-name

CADD ( TO FIELD database-aiame.reoord-name.datafield-nameCTYPE datatype-name I ) ...

I( TO SET database-name. set-name VALUEC#string) .. I1

M DOP (TO FIELD database-name.record-name.dtafield-name)..

I ( TO SET database-name . et-m) ...tALTER I TO FIELD database-name.record-name.datafield-name [(p)J [TYPE datatype-namel) ...

I ( TO SET database-name .set-name VALUEstring')... .2;

--or--

ALTER MAP ec-name ro-name ec-name

EADD I TO SET database-name .set-mane (.member-reoord-name)..]

CDROP ( TO SET database-name .set-name [.member-record-name]) .. .;

Comments:


map to be altereddatafield to be mapped toset to be mapped to

* Tag-name Is a unique name for an attribute use classwithin an entity class. The following rules apply whenaltering Attribute Use Class (AUC) to datafield mappings:

a. ALTER ADD rules are the following:

- The AUC must not have previously been mapped toa set.

- The AUG must not have been previously mapped toa data field.

3-8

UK 6201411001 November 1985

If the data type name is not entered, thestandard data type for the AUC's domain is used.

- Only one primary mapping may exist for an AUC.- Multiple secondary mappings may exist if there

is a pro-existing primary mapping.If the primary or secondary mapping is notspecified, the default is primary.

b. ALTER DROP will not drop a primary datafield map ifsecondary maps exist for a particular AUC.

c. ALTER ALTER will modify the primary-secondaryindicator and/or the datatype name. To change asecondary map to primary and to change the previousprimary map to secondary, include the (P) option. Tochange the datatype name, include the datatype namein the ALTER ALTER command.

* The following rules apply when altering AUC to set

mappings:


- A data field mapping must not exist for the AUC.- The set to be mapped to must have a single

record type for its members.- The member record name is not used in AUC to set

mappings.- The set to be mapped to must not previously have

been mapped from a relation class or anotherAUC.

- All AUC to set maps must map to the samedatabase for a particular AUC.

- All AUC to set maps must contain a value thatmust be unique for a particular AUC.

- Each set mapped to from the AUC must have thesame record type as its owner.

b. No special rules apply to ALTER DROP.

c. ALTER ALTER will modify the AUC value for aparticular AUC to set map. The new AUC value must beentered and must be unique for that particular AUC.

* The following rules apply when altering Relation Class(RC) to set member mapping:

3-9

UK 6201411001 November 1985


The member record name may be omitted if the setto be mapped to is & single member record typeset; otherwise the member record name isrequired.

- There must be no previous mappings to the set.- The value is not used in Relation Class to set

mappings.

b. ALTER DROP requires a member record name entry if, byomitting it, the "to set" specification would beambiguous.

c. ALTER ALTER is invalid for RC to set maps.

Examples:

ALTER MAP DEPARTM ENT. EMPLOYEEADD TO FIELD ENPDB.ERECI .RATETO FIELD EMPDB.EREC2.SSNO TYPE SS

DROP TO FIELD EfPDB. AREC. DEPTIOALTER TO FIELD EMPDB.EREGl. EMPNO (P)TO FIELD ENPDB.EREC2.TITLE TYPE JOBTITLE;

ALTER MAP PART.COMPOSITIONALTER TO SET MATERIAL.COMPOSITE VALUE 'COMPOSITE';

ALTER MAP INVENTORY HAS SHELFLIFEDROP TO SET SLDB.BATTERY.NICAD;

3-10

UM 6201411001 November 1985

3. 6 ALTER MODEL

* Syntax:

ALTER MODEL model-name;

Comments :

* Required existence in the Common Data Model:

model class

* The model is updated and marked as unchecked.

* The model becomes the "current" model for all othermodeling commands and remains current until another CREATEMODEL or ALTER MODEL command is entered.

Examples:

ALTER MODEL ABCCOMPANY;

3-11

UN 6201411001 November 1985

3.7 ALTER RELATION

Syntax:

ALTER RELATION [(CLASS] [(INTEGERIliNANY)] ind ec namelrc name [{INTEGER2: INTEGER3IMANY) depecname2

[ADD [MIGRATES (kc name [SET (tagnamel -tagname2 ... )] K EYWORD keyword... ] ]

[DROP [MIGRATES kcname ]... [KEYWORD keyword... 1];

Comments:

9 The above command the following elements must exist inCommon Data Model:

modelrelation classindependent entity (ind ec namel)dependent entity (dep_ec-name2)

0 ALTER RELATION [CLASS] [E.NTEGERltANY] ind ec namel

rcname [INTEGER2: (INTEGER31ANY)] depec_name2

The relation is altered if any cardinality is altered.

Integerl or many indicates the cardinality for theindependent entity class. Integer2 and integer3 indicatethe cardinality for the dependent entity class.

Cardinality values default to the current cardinality forthe Relation.

A warning message may be generated to indicate either leftor right dependent cardinality too large. This will nothalt processing but defaults the value to the currentcardinality of the relation class. The right dependentcardinality (integer2) cannot be less than the leftdependent cardinality (integer3).

Individual cardinalities may be changed without changingall the cardinalities.

The right dependent (integer3) cardinality cannot be zero.

[ (ADD (MIGRATES (kc_name [SET (tagnamel - tag_name2)...])(KEYWORD keyword... I]]

3-12

UN 620141100

1 November 1985

The following elements must exist in the Common DataModel:

key class for independent entitykey class members for the independent entityattribute use class for each key class memberassociated with the Independent entity

The key class cannot have been previously migrated to thedependent entity.

An attribute use and an inherited attribute use class forthe dependent entity is created for each key class memberof the independent entity migrated to the dependententity.

If the set phrase is specified, tagnamel (the independententity's tag name) is migrated with the new name oftag name1.

A complete relation class occurrence is created.

The keyword is created in the Common Data Model if it doesnot already exist.

A relation class keyword reference is created.

* [DROP EMIGRATES kc_name]... (KEYWORD keyword... ];

The key class migration will be dropped from each relationand entity in the model.

The relation class keyword reference is deleted.

Examples:

ALTER RELATION CLASS INDECSTORE RCINVOICINGDEP EC CUSTOMER

ADD-MIGRATES KCORDER SET ACINVOICE - ACFORMDROP KEYWORD KCORDER;

ALTER RELATION CLASS INDECDEPARTMENT HASDEPECEMPLOYEE;

3-13

bE

UK 6201411001 November 1985

3.8 CHECK MODEL

Syntax:

CHECK MODEL modelname;

Comments:

* model name must exist.

* If the model meets all rules, the model will be marked aschecked.

" The following rules are checked for the model:

a. no non-specific relations are allowed (independentcardinality greater than one)

b. no incomplete relations (key has not been migrated)c. each entity has at least one attribute use classd. each owned attribute has a domain and that domain has

a standard data typee. a key is defined for each entityf. multiple key classes of an entity are not subsets of

one anotherg. no one to one relationsh. no dependency loops, e.g., A-,B-,C-,A.i. at least one entity exists in the model

0 The following rules cannot be checked for the model:

a. one to none or one relationships implying identicalkeys

b. key uniqueness throughout the model is not checked,i.e., no two entities may have the same key unlessthey are related to each other with a one to none orone relation

Examples:

CHECK MODEL A;

CHECK MODEL INTEGRATEDMODEL;

3-14

UK 6201411001 November 1985

3.9 COMBINE ENTITY

Syntax:

COMBINE ENTITY ec name_1 FROM MODEL model-name] INTOec-name 2 ON FILE 'file name'

[EXCEPT EDESCRIPTIONI [ALIAS] [KEYWORD]];

Comments:

* If model-name is not entered, an intra-model combine isassumed and ec name 1 must not be the same as ec name_2.The current model will be used.

* The NDDL statements necessary to physically combine thetwo entities are generated on the file named. If thenamed file does not exist, it is created and opened. Ifthe named file does exist, the generated NDDL is appendedto the file.

0 On an intra-model combine, any relations between ecname_1and ec name_2 will be dropped and ec name_1 will bedropped.

* All owned attributes of ec name_1 and their aliases,keywords, and descriptions are generated for ec name 2, orthe corresponding keyword appears in the EXCEPT-clause.

* All entity name aliases, keywords, and descriptions ofec name_1 are generated as aliases, keywords, anddescriptions of ec name 2 unless they already exist forec name_2, or the corresponding keyword appears in theEXCEPT clause.

* All relations in which ecname_1 is the dependent entityare generated for ec name_2, provided the independententities in '.he relations already exist in the currentmodel and the relation names are not already associatedwith ecname 2. The key classes of the independententities are migrated to ec name 2 and all key classes ofecname_1 are generated for ec_name_2.

0 All relations in which ecname 1 is the independent entityare generated for ec name 2, provided the dependententities already exist in the current model and therelation names are not already associated with ec name_2.The key class of ecname_1 is migrated to the dependent

3-15

p .p

UK 6201411001 November 1985

entities.

* If the EXCEPT clause is entered, at least one option mustbe specified. If used, the options must appear in theorder indicated. If DESCRIPTION Is entered, nodescriptions for entities, attributes, and relations willbe generated or copied. If ALIAS is entered, no aliasesfor entities and attributes will be generated or copied.If KfYWORD is specified, no keywords for entities,attributes, and relations will be generated or copied.

0 Generated Commands:

The generated NDDL commands should be examined forpotential run-time errors.

a. If the entity being combined has inheritedattributes, then the generated NDDL must be changedeither to add the inherited attributes to the newentity as owned attributes, or all references to theinherited attributes must be deleted from KEY CLASSand MIGRATES clauses.

b. A create/alter entity command may attempt to add anowned attribute when the attribute is already ownedby another entity in the target model. The modelermust decide which entity should own the attribute andchange the NDDL accordingly.

NOTE:When an attribute is added to an entity and theattribute already exists in the target model, acomment is generated in the NDDL command followingthe attribute. The comment is:

/* ATTRIBUTE MAY BE OWNED IN TARGET MODEL */

Examples:

COMBINE ENTITY ENT8 INTO ENTB ON FILE 'ENTB.DAT' EXCEPTDESCRIPTION;

COMBINE ENTITY EN?_B FROM MODEL SPARKY INTO ENTB ON FILE'CNBKNT.ZZZ';

3-16

UK 62141 100I November 1985

3.10 OMIPARE MODEL

syntax:

COMPARE MODEL model name_1 WITH model name_2;

Comments:

• model name_1 and modelname_2 must both exist.

* Similarities, or points of correspondence of the twomodels will be reported:

a. entity names correspond, (match identically) eitherthrough primary name or alias

b. attribute names correspond, either through primaryname or alias

c. entity keywords correspondd. attribute keywords corresponde. relation keywords correspond

Examples:

COMPARE MODEL A WITH MODEL B;

3-17

UK 6201411001 November 1985

3.11 COPY ATTRIBUTESyntax:

COPY ATTRIBUTE attr name I[FROM MODEL model_nae][TO attr name 2] lON FILE 'file name° ]

[EXCEPT [DiESCRIPTION] [ALIAST [KEYWORD] ;

Comments:

* If from model is used. attr name_1 must exist in thatmodel.

* If attr name 2 is not entered, the copy attribute must bean inter-model copy and attr name_2 will be the same asattr name_1.

* The attribute will always be copied to the current modelunless the FILE clause is specified.

0 If from model has been omitted, copy attribute will be anintra-model copy and attr name_2 must be entered.

* All of the attr name l's descriptions, aliases, andkeywords will be copied, unless the corresponding appearsin the EXCEPT clause.

* If the FILE clause is specified, NDDL commands will begenerated/appended on the file specified.

0 Refer to COMBINE ENTITY for a complete description of theEXCEPT clause.

Examples:

COPY ATTRIBUTE Al FROM M1 TO A4;

COPY ATTRIBUTE A3 FROM M2 ON FILE 'A3.DAT';

COPY ATTRIBUTE A5 TO A6EXCEPT DESCRIPTION ALIAS;

3-18

A_4 11116 11 1

UK 6201411001 November 1985

3.12 COPY DESCRIPTION

Syntax:

COPY desc_type OF object type object id 1[FROM MODEL model_namel TO object Id_2;

Comments:

0 Objectid can be an Attribute Use Class. Entity Use Class,or a Relation Class.

* This is a partial description copy. Only the descriptionlines of the identified description type of the givenobject will be copied, rather than all description types.

* object-type and descrtype are defined in the DESCRIBEcommand.

* If model-name is omitted, the current model will be usedwhen looking for object id I and objectId_2 must not bethe same as object_Id_1.

* A description cannot be copied from an occurrence of oneobject type to a different object type.

* Object id's can consist of multiple words for relations,(ref DESCRIBE command).

* object_id_2 must exist in the current model.

Examples:

COPY DEFINITION OF ENTITY E1 TO E2;

COPY USAGE OF ENTITY E2 FROM MODEL Ml TO E2;4ICOPY DEFINITION OF RELATION El USES E3 TO E6 OWNS E7;

3-19

UN 6201411001 November 1985

3.13 COPY ENTITY

Syntax:

CoPY ENTITY (CLASS) ec-name_1 (FROM MODEL model_name)

[TO ec name_2] [ITH { STRUCTURE ) ON FILE 'file name']( RELATION -

[EXCEPT [DESCRIPTION) [ALIAS) [EimWORD)];

Comments:

0 The following elements must exist in the Common DataModel:

entity being copiedcurrent model

0 If the FROM clause is omitted, an Intra-model copy isassumed and the following rules apply:

a. ec nme_2 must be entered and may not be the sane asecname 1.

b. The WITH clause must be omitted.c. A new entity is built for the current model.d. All keywords, aliases, and descriptions for the

entity being copied are created for the new entityunless excepted.

e. All key classes and key class members for the en~itybeing copied are created for the new entity.

f. Attributes associated with the entity are not copied.

0 If the FROM clause is entered, an inter-model copy isassumed and the following rules apply:

a. The entity being copied must not exist In the currentmodel.

b. If ec name_2 is omitted the name of the new entitywill be the same as ec name_1.

c. The WITH clause is required.d. The entity being copied and its relations or

structures are not physically added to the currentmodel. Instead, the NDDL commands necessary to addthe entity to the current model are generated andwritten to the file named on the 'FILE' clause. If

3-20

UK 6201411001 November 1985

the named file does not exist, & now file is createdand opened. If the named file does exist, thegenerated commands are appended to the file.

e. A new entity is generated for the current model.f. The following items are generated for the new entity

unless they already exist in the current model orhave been excepted:

- All keywords, aliases, and descriptionsassociated with the entity being copied.

- All the attributes owned by the entity beingcopied. Note that attributes inherited by theentity being copied are not generated.

- All key classes and key class members belongingto the entity being copied.

e If the RELATION option is chosen on an inter-model copy,the following applies:

a. All relations in which the entity being copied is thedependent entity are generated for the current model,provided the independent entities in the relationsexist in the current model.

b. All relations in which the entity being copied is theindependent entity are generated for the currentmodel, provided the dependent entities in therelations exist in the current model.

c. All key classes that were migrated in the relationsbeing copied are migrated in the current model. Thesame names used in the relation being copied aregenerated for the current model.

e If the STRUCTURE option is chosen on an inter-model copy,the following applies:

a. The tree structure dependent on the entity beingcopied is generated for the current model. Thisincludes the entities, their keywords, aliases,

descriptions, owned attributes, key classes and keyclass members; the relations, their migrated keys andset names. Note that everything associated with thestructure is generated for the current model, whetheror not it exists in the current model.

* Refer to COMBINE ENTITY for complete description of EXCEPTclause.

3-21

UN 6201411001 November 1985

0 Generated Commands:

The generated NDDL commands should be examined forpotential run-time errors.

a. If the entity being copied has inherited attributes,then the generated NDDL must be changed either to addthe inherited attributes to the new entity as ownedattributes, or all references to the Inheritedattributes must be deleted from KEY CLASS andMIGRATES clauses.

b. If a tree structure is being copied, then the createcommands for any entities, attributes, aliases, andrelations that already exist in the current modelmust be deleted.

c. A create/alter entity command may attempt to add anowned attribute to an entity when the attribute isalready owned by another entity in the target model.The modeler must decide which entity should own theattribute and change the NDDL accordingly.

NOTE:When an attribute is added to an entity and theattribute already exists in the target model, acomment Is generated in the NDDL command followingthe attribute. The comment is:


Examples:

COPY ENTITY INVOICE TO NEWINVOICEEXCEPT DESCRIPTION ALIAS KEYWORD;

COPY ENTITY INVOICE FROM MODEL ABCCOMPANY WITH STRUCTUREON FILE 'EXAMINE.NDL'

EXCEPT ALIAS;

3-22

UN 6201411001 November 1985

3.14 COPY MODEL

Syntax:

COPY MODEL [FROM MODEL model name] TO new model ON FILE'file-name' [EXCEPT [DESCRIPTION] [ALIAS] (KEYWORD]];

Comments:

0 If the FROM clause is entered, model name must exist. Ifit is omitted, the current model will be copied.

0 new-model must not exist.

* The model being copied may not contain any dependencyloops.

* NDDL commands are generated in the proper sequence tocreate a new model containing all the entities, ownedattributes, inherited attributes, key classes, key classmembers, relations, aliases, keywords, and descriptions inthe model being copied.

* Aliases, keywords, and/or descriptions will be excludedfrom the generated NDDL if the corresponding optionappears in the EXCEPT clause. Refer to COMBINE ENTITY fora complete description of the EXCEPT clause.

0 If the named file does not exist, a new file is createdand opened. If the file does exist, the 5eneratedcommands are appended to the file.

Examples:

COPY MODEL FROM MODEL Ml TO M2 ON FILE 'M2.DAT';

3-23

UK 6201411001 November 1985

3.15 CREATE ALIAS

Syntax:

CREATE ALIAS IENTITY Sc, namel [IS) Sc, name2

I ATT'RIBUTE ac-namel (181 ac-name2)

Comments:


entityattribute

* ec-name2 and ac name2 are the names to be created asaliases for entity and attribute respectively.

Examples:

CREATE ALIAS ENTITY CUSTOMER IS CUST.

CREATE ALIAS ATTRIBfUTE ORDERNUMBER IS ORDNO;

3-24

w ~ ~VAN"

UN 6201411001 November 1985

3.16 CREATE ATTRIBUTE

Syntax:

CREATE ATTRIBUTE [CLASS ac-_name [DOMAIN domain-name]* [KEYWORD keyword ... 1;

Comments:

* CREATE ATTRIBUTE [CLASSI ac-name

Required existence in the Common Data Model:

the current model

A new attribute is created for the current model.

0 [DOMAIN domain-name]

The domainname must name an existing domain.

If domain name is not specified, the domain-no for theattribute-class will be undefined.

* KEYWORD keyword ...

The keyword will be created in the Common Data Model if itdoes not already exist.

Keyword references are created for the attribute.

Examples:

CREATE ATTRIBUTE ORDERDATE DOMAIN DATEKEYWORD KEYDATE;

3-25

'S '~

UM 6201411001 November 1985

3.17 CREATE DOMAIN

Syntax:

CREATE DOMAIN domain-name STANDARD[DATA] TYPE datatypename / CHARACTER \

I PACKED ISIGNED

I UNSIGNED I\ INTEGER /

integerl[: integer2l ...;

Comments:

* A new domain is created within the system.

0 All specified data types are added for the domain.

0 A standard data type must be specified. Remaining datatypes for that domain will be user defined data types.

* Integerl [integer2]... states a range of permissablevalues where integerl is the ending value and integer2 isthe beginning value (integer2 cannot be greater thanintegerl. Integerl can be used to specify a single valuefor a data type.

* The NDDL data types correspond to the following

COBOL/FORTRAN data types:


CHARACTER X(n)PACKED COMP-3SIGNED S99V99UNSIGNED 99V99INTEGER FORTRAN binary integerFLOAT FORTRAN floating point

Examples:

CREATE DOMAIN ZIPCODE standardTYPE ABC character 30TYPE XY2 integer 6:2;

3-26

UK 6201411001 November 1985

3.18 CREATE ENTITY

Syntax:

CREATE ENTITY [CLASS] ec-name[KEY [CLASS] kc name[- ac name ... 1]...

[[OWNED] ATFTRIBUTE (CLASS] ac name ... ][KEYWORD keyword ... ];

Comments:

* CREATE ENTITY [CLASS] ecname

A new entity is created for the current model.

0 KEY [CLASS] kc name ( - ac name ... ]


attribute

A new occurrence of attribute use class and ownedattribute is created for ac name if one does not alreadyexist. If the attribute use class does not already exist,ac name may not be owned by any other entity.

A new occurrence of key class is created for the entityusing kcname.

A new occurrence of key class member is created for theentity for each ac name. If ac name is omitted, a keyclass member occurrence is created using kc-name.

* (OWNED] ATTRIBUTE [CLASS] ac name ...


attribute

New attributes for the entity being created are added.

Each attribute class is created as an owned attributeclass for the entity.

A new occurrence of an attribute use class is created.* KEYWORD keyword...

3-27

UK 6201411001 November 1985

Keyword references are created for the entity.

The keyword viii be created if it does not already exist.

Examples:

CREATE ENTITY SALES PERSONKEY ORDER - ORDER NUMBER

OWNED ATTRIU SALESKEYWORD SALESID;

3-28

UN 6201411001 November 1985

3.19 CREATE MAP

Syntax:

CREATE MAP I ec name. tagname* I tnd ec namel rc name dep ec name2)

((TO FIELD database name.record name.datafield name[1(p) 1(s))] [TYPE datatype name]) ...

I(TO SET database name.set name [.member record name][ VALUE 'stringi)...);

Comments:


Integrated Model (model number - 1)Attribute Use Class (AUC) to be mappedRelation Class to be mappedData field mapped toDatabase mapped toRecord mapped toSet mapped to

* The following rules apply to AUC (eename.tagname) todatafield mappings:

a. The AUC must not have previously been mapped to aset.

b. The AUC must not have been previously mapped to adatafield.

c. If the datatype name is not entered, the standarddatatype for the AUC's domain is used.

d. Only one primary mapping may exist for an AUC.e. Multiple secondary mappings may exist if there is a

pre-existing primary mapping.f. If the primary or secondary mapping is not specified,

the default is primary.

- The following rules apply to AUC to set mappings:

a. A datafield mapping must not exist for the AUC.b. The set to be mapped to must have a single record

type for its members.

c. The member record name is not used in AUC to setmappings.

3-29

UN 6201411001 November 1985

d. The set to be mapped to must not previously have beenmapped from a relation class or another AUC.

e. All AUC to set maps must map to the same database fora particular AUC.

f. All AUC to set maps must contain a value which mustbe unique for a particular AUC.

g. All sets mapped to from the AUC must have the samerecord type as its owner.

0 The following rules apply to Relation Class to setmappings:

a. The member record name may be omitted if the set tobe mapped to is a single member record type set;otherwise the member record name is required.

b. There must be no previous mappings to the set.c. The value is not used in Relation Class to set

mappings.

0 A Relation Class to datafield map is illegal.

Examples:

CREATE MAP PART.SIZE TO FIELD PARTDB.PREC.PSIZETO FIELD PARTDB.PREC2.PSIZE2 (S)TYPE METRIC ;

CREATE MAP ORDER.STATUS TO SET CUSTDB. INPROCESS VALUE '1'TO SET CUSTDB.BAKORDER VALUE '2'TO SET CUSTDB.SHIPPED VALUE '3';

CREATE MAP EMPLOYEE POSSESSES SKILLSTO SET SKILLDB.SETA.RECATO SET SKILLDB.SETB

3-30

KIM 6201411001 November 1985

3.20 CREATE MODEL

* Syntax:

CREATE MODEL model-name;

Comments:

* A new model is created as unchecked In the system.

* The model Is the "current' model for following modelingcommands until another CREATE MODEL or ALTER MODEL commandIs entered.

Examples:

CREATE MODEL DEFCOMPANY;

3-31

UN 6201411001 November 1985

3.21 CREATE RELATION

Syntax:

CREATE RELATION [CLASS] [(INTEGERI MANY) I mnd ecnamelrcname INTEGER2: INTEGER3 MANY) depec_name2

(MIGRATES (kc name (SET (tagnamel - tag name2}... ]][KYORD keyword ... ];

Comments:

.o CREATE RELATION [CLASS] [(INTEGERIMANY)] ind ec namelrcname [{INTEGER2: INTEGER3IMANY) depec naue2


modelindependent entity (mnd ec namel)dependent entity (dep"ecname2)

A new relation is inserted.

Cardinalities for the entities of the relation areinserted. Integerl or many indicates the cardinality forthe independent entity class. Integer2 and integer3indicate the cardinality for the dependent entity class.If integerl or many is omitted, the independentcardinality defaults to one. If integer2 is omitted, theleft dependent cardinality defaults to zero. If integer3or many is omitted, the right dependent cardinalitydefaults to many. For example, if DEPARTMENT (exnamel)can have 0 or many Employees (ec name2):

CREATE RELATION 1 DEPARTMENT HAS 0:MANY EMPLOYEES

- or -

CREATE RELATION DEPARTMENT HAS EMPLOYEE

Integer3 may not be less than integer2.

Integer3 may not be zero.I MIGRATES kc name [SET (tagnamel - tagname2) ... ]

3-32

L WORM,

UK 6201411001 November 1985


key class for Independent entitykey class members for Independent entityattribute use class for each key class memberassociated with the Independent entity

The key class cannot have been previously migrated.

The dependent entity cannot end up with attribute useclasses with the same tag name (a unique name for anattribute use class within an entity class).

An attribute use class and an inherited attribute useclass for the dependent entity are created for each keyclass member of the independent entity migrated to thedependent ENTITY.

If the set phrase Is specified, tag_name2 (the Independententity's tag name) is migrated with the new name oftag_namel.

A complete relation class occurrence is created.

KEYWORD keyword ...

The keyword is created if It does not exist.

A relation keyword reference is created.

Examples:

CREATE RELATION INVOICE SUPPLIES ORDERINFOMIGRATES ORDER SET ORDERNUMBER - ORDNOKEYWVORD ORDERDATA;

3-33

UN 6201411001 November 1985

3.22 CREATE VIEW

Syntax:

CREATE VIEW view name [DATA ITEM data itemname([DATA] TYPE dita type_name] ]..

AS SELECT( 1*tag name ... I(abbrev.]tag_name...)

FRO( o_nameiec name.abbrev...)

[WHERE Indec_name rcname dep_ec_name [and...]]

Comments:

* To create a VIEW (SURROGATE ENTITY CLASS) using the abovecommand, the following elements must exist in the CommonData Model:

independent entitydependent entityrelation classentitydata items and attribute use classes from the same

domain existence of standard data type

0 CREATE VIEW view-name

A new view (SURROGATE ENTITY CLASS) is created if it doesnot exist.

The relationship between view and relation is created.

0 DATAITEM data_item_name ((DATA] TYPE datatypename]...

Must be specified when views are built from more than oneentity.

The data items must correspond in order and number to theattribute use class tags specified in the select clause.

If data type name is not specified, the data type willbecome the standard data type for the correspondingattribute use class.

0 AS SELECT*itag-name... I

3-34

UK 6201411001 November 1985

[abbrev. ] tag_name

If an * is specified:

a. The FROM clause may not be omitted.b. A data item and project data item occurrence are

created for each attribute use class associated withthe entity named on the FROM clause.

If the tags (unique attribute use classes within an entityclass) are selected from a single entity, the ABBREV maybe omitted provided a FROM clause is specified without anabbreviation.

If tags are selected from more than one entity, bothabbreviations and tag names must be specified and a FROMclause with entity names and abbreviations must bespecified.

Data item and project data Item occurrences are createdfor each attribute use class named in the select.

If abbreviations are used, they must be used for allattribute use classes.

e FROM (ec namelec name.abbrev)...

The abbreviation for the entity must be included if the

ABBREV is used in the select clause.

0 WHERE (indecname rc name dep_ecname [and] ...

The WHERE clause must be specified when tags are selectedfrom more than one entity.

Each entity specified in the FROM clause must appear aseither the independent entity or dependent entity in aWHERE clause relation.

The relation class name must be valid.

Abbreviations are not allowed in the WHERE clause.

The WHERE clause selects those relation classes that jointhe entities into a "surrogate entity class" structure.The structure is checked using the rules found in the

3-35

UN 6201411001 November 1985

CDII-1 model, June 1983.

Exa6mples:

CREATE VIEW SUPPLIES DATA ITEM p0NUN PODATE SUPPLIERLOCATION DATADEL REQUESTOR

AS SELECT P0. p0RDER NUMER P0. PORDER-DATE P0. ITEMSUPPLIERDL.DELIVERY LOCATion DL.DELIVERY LOCATIONDL.DATEOFBELIVERY MR.REQUESTIiiGSEC

FROM PURCHASE_ ORDER. P0 DELIVERY.DL MATERIAL-REQUEST .MR

WHERE PURCHASE-ORDER SPECIFIES DELIVERY ANDMATERIALREQUEST REQUESTS PURCHASEORDER;

3-36

UK 6201411001 November 1985

3.23 DEFINE DATABASE

Syntax:

DEFINE /ORACLE \(DATABASE )NAMED db-name ON HOST( IBM)ITOTAL I PCB ) VAX)IDlES (L6)I DS-IlII VAX-li I\ INS /

WITHI( (PASSWORD pvid(SCHEMA a-name AND SUNSCUEXA as-name AREAS

area_name. .. I[FILES file name...)[POSITION integerl IN PSB psbnae FEEDBACK

LENGTH Integera]);

Comments:

* The database name must be unique.

0 A database Is defined for one of the following types:ORACLE. TOTAL, IDlES, IDS-Il, VAX-l1 or INS.

0 The database created is established as the currentdatabase until such time the user defines anotherdatabase.

e The three choices of host are not meant to be exclusive.The user may enter any valid three character NTM hostdesignator, uppercase. The values are stored and notchecked.

0 Oracle Database:

DEFINE ORACLE DATABASE NAMED db-name ON HOST IIBM)(VAX)(HL6)

* WITH PASSWORD pwid;

A password is required.

0 Total Database:

35-37

10 1k 11 1A

UK 6201411001 November 1985

DEFINE TOTAL DATABASE NAMED db name ON HOST { IBM )VAX)

WITH FILES file name...

At least one file is required.

* VAX-I1/IDNS/IDS-II database:

DEFINE ( VAX-i1 ) DATABASE NAMED db name ON HOST ( IBM I(IDMS ) (VAX)I IDS-I ) (mH )

WITH SCHEMA asname AND SUBSCHREA ss_name AREASarea_ nm....

The schema, subsohema, and at least one area are required.

* INS database:

DEFINE INS PCB NAMED db name ON HOST IBM VITH POSITIONintegerl IN PSB psb name FEEDBACK LENGTH integer2

An INS database requires the term 'pcb'.

The start position and feedback length (the length of thefully concatenated key of the longest path in the PCB) arerequired.

Examples:

DEFINE ORACLE DATABASE NAMED ORCDB ON HOST VAX WITHPASSWORD SOS;

DEFINE TOTAL DATABASE NAMED TOTDB ON HOST IBM WITH FILESITEM LOCC STOK ;

DEFINE VAX-11 DATABASE NAMED COD DB ON HOST VAX WITHSCHEMA SI AND SUBSCHEMA SSI AREAS Al A2 ;

DEFINE INS PCB NAMED INS DB ON HOST IBM WITH POSITION 1 INPSB SSPSB FEEDBACK LENGTH 20

3-38

UK 6201411001 November 1985

3.24 DEFINE RECORD

Syntax:

DEFINE TABLE recname C OF ( DATABASE )dbname]RECORD PCB )SEGMENT I

{ (IN AREAS area name ... ][SEGMENT SIZE integerl ]

/\WITH I FIELDS I field name ...

COLUMNS ,I ELEMENTS II ITEMS I

[(START integer2 [UNKNOWN] ) ... ][ ACCESSED B DY KEY key_name [(u)] key fieldname

... ) ... ]);

Comments:

* This command defines a table/reoord/segment for apreviously defined database.

0 The "OF DATABASE/PCB db name" option may be omitted if acurrent database is established in the session.

0 A keyfieldname must have been previously entered as afield-name.

0 (U) on the keyfieldname enforces a unique key. Defaultis a non-unique key.

0 This syntax does not support repeating groups, componentdata fields, or redefined data fields.

* Oracle Records:

DEFINE TABLE rec-name [ OF DATABASE dbname]/\

WITH I COLUMNS I field-name...FIELDS

I ELEMENTS II ITEMS I\ /

fieldname is the only required option.

3-39

UN 6201411001 November 1985

0 Total Records:

DEFINE RICORD roename [ OF DATABASE db name]/\

WITH I FIELDS I field name ... [ ACCESSED (BYCOLUMNS

I ELEMENTS II ITEMS I

\ /

KEY keyname [(u)] key_field_name ...) ... ]

FIELDNAME is required.

ACCESSED BY clause is required for "MASTER" records.

* VAX-l1/IDHS/IDS-II Records:

DEFINE RECORD rec_name C OF DATABASE db_name]/\

IN AREAS area name... WITH I FIELDS ICOLUMNS

I ELEMENTS II ITEMS I\ /

fieldname... [ACCESSED { BY KEY key_name [(u)]key_fieldname... )... ];

At least one area and one field are required.

* INS Records:

DEFINE SEGMENT recvname [ OF PCB db name]SEGMENT SIZE integerl WITH ELEMENTSfield-name

START integer2 [UNKNOWN] ...

Segment size and start byte information are required.

Examples:

DEFINE TABLE TAB-OR OF DATABASE ORCDB WITH COLUMNS C1 C2

3-40

UK 6201411001 November 1985

C3C4

DEFINE RECORD RECTOT WITH FIELDS ITENCTRL ITENIIIIITEMI222 ACCESSED BY KEY ITENKEYI (U) ITENCTRL BY KEYITENKEY2 ITEMI111 ITEMI222 ;

/* assumes a current TOTAL database has been establishedin the session */

DEFINE SEGMENT SEGI OF PCB INS DB SEGMENT SIZE 20 WITHELEMENTS SIID START 1 SI_QTY START 11

DEFINE RECORD RECI OF DATABASE COD DB IN AREAS Al A2WITH FIELDS ITEMID ITEM QTY ACCESSED BY KEY RECIKEYlITEMID

3-41

UK 6201411001 November 1985

3.25 DEFINE SET

Syntax:

DEFINE ( SET ) [setname] OF ( DATABASE ) data base name(PATH) PCB -

{ RELATING ) record_idl TO (recordid2{ FROM }

[REQUIREDIOPTIONAL])...

[LINKED BY data_field name]

Comments:


databaserecord typedata field

0 The above command is illegal for an Oracle database.

* The following rules govern the creation of a set/path fora DBMS type:

a. Sets may be created for TOTAL, INS (called paths),and the Codasyl DBMSs: VAX-11, IDMS, and IDS.

b. Codasyl DBMSs require an entry for required/optionalmembers.

c. TOTAL DBMSs require a linked by Data Field Nameclause.

d. Single members are allowed in all DEMSs. Multiplemembers (RecordListID) may be used for the CODASYLDBMSs.

0 DEFINE { SET } [setname] OF { DATABASE ) data base name(PATH {PCB )

The set or path is a required entry for TOTAL and CODASYLDBMSs. Path is used as a more natural entry for an INSdatabase. For an IMS database, if "path" is used, the setname is derived from combining the owner (RecordIDl) and

3-42

UK 6201411001 November 1985

member (RecordID2) names.

The DataBaseName or pob is an optional entry if aDataBase Name or pob has previously beent establishedduring the session using a define database, define record,or define set command. The use of pcb is more natural foran INS database.

0 { RELATING ) recordidl TO (record_id2FROM )(REQUIRED I OPTIONAL]) ...

The RELATING/FROM clause is a required entry. From ismore natural with an IMS database. RecordIDI denotes theowner of the set and Record ID2 denotes the member(s) ofthe set. RecordID2 is used for Codasyl DBMSs to showmultiple members and includes the member RecordIDsseparated by a space. The required or optional clause mayonly be used for the Codasyl DBMSs. All other DBMSsdefault to required.

* [LINKED BY datafieldname]

The LINKED BY clause may only be used for a TOTAL DBMS andmust include a DataFieldName from the variable record(RecordID2).

Examples:

DEFINE SET MAY HAVE OF DATABASE DBl RELATING CUSTOMERRECTO CUSTOMERACTIVITY ;

DEFINE PATH OF PCB DBIMS2 FROM SUPPLIERACCT TOSUPPLIERINVOICE ;

DEFINE SET CONTROLLED BY OF DATABASE DBTOTAL14 RELATINGSHOPSUPPLY TO SHOP-REQUESTS LINKED BY SHOPNO

3-43

UK 6201411001 November 1985

3.26 DESCRIBE

Syntax:

/ \ /\

DESCRIBE I DEFINITION I [OF] I ENTITY ec nameI DESCRIPTIVENAME < ATTRIBUTE ac nameI EXAMPLE I I RELATION lnd ec name 1 II SOURCE I I ro_name dep ec-name2l

" DESCRIPTION TEXT"I FROM 'file name' ];

Comments:


attribute database data fielddata item entity record setrecord type relation user datatype.view

0 There are three sources of descriptive text: the commanditself, a named file, or the forms text editor. The thirdoption is not implemented and will generate a user warningmessage if attempted.

0 All new descriptive text will replace any preexistingdescriptive text for a particular description type andobject.

* To delete descriptive text from the model, use thedescribe command with an empty description text string,e.g.,

DESCRIBE SOURCE OF ENTITY E3 ";

* No embedded quotation marks may be entered in thedescription text string.

* When using a file as the source of the descriptive text,each record may be no longer than 80 characters. There isno practical limit on the number'of records. Eachquotation mark in the descriptive text from a file will bereplaced by an apostrophe.

3-44

UK 6201411001 November 1985

* The description types can be anything preloaded in the

CDN.

Examples:

DESCRIBE DEFINITION OF ATTRIBUTE customer address "This isthe customer bill-to-address.0;

DESCRIBE DESCRIPTIVE NAME ENTITY emp info FRM'expinfo.txt°;

3-45

UK 6201411001 November 1985

3.27 DOP ALIAS

Syntax:

DROP ALIAS { ENTITY ecnameI ATTRIBUTE ao name } ;

Comments:

0 The folloving elements must exist in the Common DataModel:

alias for the entity

- or -

alias for the attribute

* The ec name or ac name specified must be an alias for theentity or attribute.

0 The specifled alias is deleted.

Examples:

DROP ALIAS ENTITY CUST;

DROP ALIAS ATTRIBUTE ORDNO;

3-46

UK 6201411001 November 1985

3.28 DROP ATTRIBUTE

* Syntax:

DROP ATTRIBUTE attribute-name

Comments:


modelattribute

* The attribute is deleted; if owned, all occurrences of theattribute are removed from owned attribute, attribute useclass, key class member, and Inherited attribute useclass.

* The attribute occurrence Is deleted from the model.

* Those key class occurrences with no remaining key classmembers are deleted.

0 If a key class is deleted, the occurrence of a completerelation is also deleted.

* All keywords associated with the attribute will bedropped.

0 The primary name and all aliases for the attribute will bedeleted.

* All description texts for the attribute will be deleted.

Examples.

DROP ATTRIBUTE PHONENO;

3-47

UK 6201411001 November 1985

3.29 DROP DATABASE

Syntax:

DROP I VAX-1l I 4 DATABASE ) NAMED db name;I IDS I PCBI IDS-II 14 ORACLE1 TOTAL IINS I\ /

Comments:


database/pob

* An INS database requires the term 'PCB.'

* This command drops the database, all associated recordtypes, record sets, data fields, and mappings.

* If any of the data fields for this database were mapped tothe INTEGRATEDMODEL, their mapping will be dropped. Ifit was a primary mapping, any secondary mappings, even toother databases, will also be dropped. If it was asecondary mapping, the primary mapping would not bedropped.

0 All description texts for the database, all associatedsets, fields, or records will be deleted.

Examples:

DROP ORACLE DATABASE NAMED ORCDB;

DROP TOTAL DATABASE NAMED TOT_DB;

DROP VAX-11 DATABASE NAMED CODDB;

DROP INS PCB NAMED INS_DB;

3-48

UN 6201411001 November 1985

3.30 DROP DOMAIN

Syntax:

DROP DOMAIN domain name

Comments:


domain

* If data types of the domain to be dropped are associatedwith any project data fields, data items, or attributeclasses, the usage will be reported and the domain willnot be dropped.

0 If the above condition (2) is not met, the data typesassociated with the domain are deleted, and the domainitself is deleted.

* All description texts will be deleted for the Domain.

Examples:

DROP DOMAIN ADDRESS;

3-49

UK 6201411001 November 1985

3.31 DROP ENTITY

syntz:

DOP ENTITY ecname ... ;

Comments:


entitymodel

* Any owned attribute class occurrences are deleted. Alsoremoved are attribute use, inherited attribute, key classmember, and key classes.

* All relation classes involving the entity are deleted, asare any keywords associated wth the entity.

* The entity is deleted.

* The primary name and all aliases for the entity aredeleted.

* All description texts for the entity are deleted.

Examples:

DROP ENTITY ORDERINFO;

3-50

UM 6201411001 November 1985

3.32 DROP FIELD

Syntax:~/\

DROP I COLUMNS I fieldname ... OF { TABLE )rec-nameFIELDS { RECORD }

i ELEMENTS I { SEGMENT )I ITEMS I

\ /

OF { DATABASE ) db name;{PCB )

Comments:

• The following elements must exist in the Common DataModel:

columns/f ields/elements/i temstable/record/segmentdatabase/pcb

* This command deletes the field(s) specified, allassociations, and all associated mappings.

0 If the data field(s) being dropped was mapped to theINTEGRATEDMODEL, its mapping would be dropped. If it wasa primary mapping, any secondary mapping, even to otherdatabases, would also be dropped. If It is a secondarymapping, the primary mapping would not be dropped.

* All description texts of the data field will be deleted.

Examples:

DROP COLUMNS Cl C2 OF TABLE TABOR OF DATABASE ORCDB;

DROP ELEMENTS SI_ID SI_QTY OF PCB IMS_DB;

3-51

UN 6201411001 November 1985

3.33 DROP KEY VORD

Syntax:

DROP KZEYVORD key_word ...

Coments:


keyword

0 The keyword reference Is deleted from any entity,

attribute, and relation.

0 The keyword is deleted.

0 NOTE:This command will drop a keyword irrespective of themodel.

Examples:

DROP K EORD KEYADDRESS;

3-5z-

UK 6201411001 November 1985

3.34 DROP MAP

I Syntax-

DROP NAP (ecname. tag namelindec name rename depecuname);

Comments:

* The following elements must exist in the common datamodel:

independent entitydependent entityattribute use classrelation class

0 The map is deleted.

* Tagname is a unique name for an attribute use classwithin an entity class.

Examples:

DROP NAP PART.SIZE;

DROP MAP EMPLOYEE POSSESSES SKILL;

3-53

UK 6201411001 November 1985

3.35 DROP MODEL

Syntax:

DROP MODEL model name;

Comments:

* Model name must exist.

0 Everything associated with a model will be dropped. Thisis: all entities, owned attributes, attribute useclasses, key classes, key class members, inherited attri-bute use classes, relation classes and complete relationclasses, and all attributes. The descriptions, aliases,and keywords for the entities, attributes, and relationsof the model will be dropped.

0 The model_name and its descriptions will be deleted.

0 The integratedmodel cannot be dropped.

Examples:

DROP MODEL X;

3-54

UK 6201411001 November 1985

3.36 DROP RECORD

Syntax:

DROP { TABLE ) recname OF { DATABASE ) db name(RECORD) PCB)SEGMENT

Comments:


table/record/segmentdatabase/pcb

* This command deletes the record specified and allassociated fields, areas, and sets.

* If any of the datafields for this record were mapped tothe Integrated-model, their mapping will be dropped. Ifit was a primary mapping, any secondary mapping, even toother databases, will also be dropped. If it was asecondary mapping, the primary mapping would not bedropped.

* All description texts will be deleted for therecord/table/segment and any fields.

Examples:

DROP TABLE TABOR OF DATABASE ORCDB;

DROP SEGMENT SEGi OF PCB INSDB;

3-55

MO %: ' ' ' / . ,,i

UN 6201411001 November 1985

3.37 DROP RELATION

Syntax:

DROP RELATION ( Ind_ec name_1 rc_name depecname_2 ) ... ;

Comments:


relation classmodel

* If a key class had been migrated, it is "unmigrated";i.e., the attribute use and inherited attributes areremoved from the dependent entity and from any otherentities to which they have migrated.

* The relation class and oomplete relation are deleted fromthe model.

* The keywords associated with the relation are dropped.

0 All description texts for the relation are deleted.

Examples:

DROP RELATION SALESPERSON MANAGES ACCOUNT;

3-56

LI

UM 6201411001 November 1985

3.38 DROP SET

Syntax:

DROP { SET ) setname OF { DATABASE ) dbname;{PATH) PCB )

Comments:


set/pathdatabase/pcb

a This command deletes the set specified, and all associatedmappings.

* All description texts for the set will be deleted.

Examples:

DROP SET TESTI OF DATABASE TOT DB;

DROP PATH TEST2 OF PCB INSDB;

3-57

-=' : : IV I p/-illW l .. *,¢.s -,_','_ a . '_'-'._ ._' -,'.', ".". - ".' " ",' " ". . " * A s-.

UN 6201411001 November 1985

3.39 DROP VIEW

Syntax:

DROP VIEW view-name ... ;

Comments:

* A valid VIEW must exist in the Common Data Model.

* All project data items associated with the view beingdeleted are deleted.

* The surrogate entity (user view) to relation mappingsassociated with the view are deleted.

* All data items associated with the view are deleted.

* The view is deleted from the system.

* All description texts for the view and data itemsbelonging to the view are deleted.

Examples:

DROP VIEW SUPPLIES MATERIALLIST ;

3-58

UK 6201411001 November 1985

3.40 HALT

syntax:

HALT;

Comments:

a The current NDDL session will be terminated.

Examples:

HALT;

3-59

UK 6201411001 November 1985

3.41 UG NOI

Syntax:

3330 MODCL model name 1 WITH model name 2[ITO model iame 33 ON FILE 'tie nume'[ncan (nS-RipTionj (ALIAS] EEVORDJ1;

Comments:

* model_name_1 and modelname_2 must exist.

• The NDDL commands necessary to merge model name_1 andmodel name_2 are generated on the file named. If thenamed file does not exist, a new file Is created andopened. If the named file does exist, the generatedcommands are appended to the file.

• If modelname 3 Is ,ntered, model name_3 must not exist.The result of the merge will create model name_3. Allattributes, entities, relations, key classes, aliases,keywords, and descriptions of model name 1 will begenerated for model name_3, unless exoepted. The outputis the same as output from & COPY MODEL of model_name_1 tomodelname_3.

0 If model name_3 is omitted, the result of the merge willalter modelname_1.

• For each entity in modelname_2. if the entity does notexist in modelname_1, the generated commands are the sameas the output of a COPY ENTITY from modelname_2 withrelation.

• For each entity in modelname_2, if the entity does existin model name_l, the generated commands are the same asthe output of a COMBINE ENTITY from modelname_2.

• Refer to COMBINE ENTITY for a complete description of the

EXCEPT clause.

• Generated Commands:

The generated NDDL commands should be examined forpotential run-time errors.A create/alter entity command might attempt to add anowned attribute to an entity when the attribute is already

3-60

" " , .. ,% _ , . f ,,- . .. -. .j* . ," , . .. ' ',. ,

UK 6201411001 November 1985

owned by another entity in the target model. The modelermust decide which entity should own the attribute andchange the NDDL accordingly.

NOTE:When an attribute is added to an entity and the attributealready exists in the target model, a comment is generatedin the NDDL command following the attribute. The commentis:


Examples:

MERGE MODEL INTEGRATEDMODEL WITH MODELA ON FILE'INTEGNOD.FIL';

MERGE MODEL MODELA WITH MODELB INTO NEW MODELON FILE 'NEWHODEL.FIL' EXCEPT ALIAS KEYWORD;

3-61

UN 6201411001 November 1985

3.42 RENAKE

Syntax:

RENAME I ENTITY ec-name 1 TO eo-name2II ATTRIBUTE ac-name 1 TO ac-aame2;II KEYWORD keyword 1 TO keyword2I1MODEL model-namel TO model-name2I DOMAIN don name 1 TO don name2II VIEW view7 -na0el TO view-name2 IIRELATION Ind -ec namel re namel depec naae2l

ITo Ina_@0_ -namil ro-name2II depec-name2I

Comments:


entity or attribute or keyword or model ordomain or view or relation

0 After determining that the above elements exist, and theelement to be renamed does not previously exist, theobject is updated.

* Rename relation command requires the entity class namesfor the relation class to be updated.

Examples:

NAME ENTITY INVOICE to ORDER;

RENAME RELATION INVOICE SUPPLIES ORDERINFO to

INVOICE DESCRIBES ORDER-INFO;

3-62

UK 6201411001 November 1985

APPENDIX A

NDDL COMMAND ERROR MESSAGES

J This section describes UDDL Command Error messages that maybe encountered during NDDL execution. These error messagesinform the user about error conditions for the object type(Entity, Attribute, Database) being processed. For example, thecommand ODROP MODEL" may encounter error messages concerning allobjects associated with the model (Entities, Attributes,Relations, etc).

The error message report contained in this section isformatted to indicate the type of error (warning, error, fatal),the object type that is associated with the error, and theactual error message (with the object indentification) that willbe issued during NDDL execution.

The error types are categorized as:

FATAL - A system or CD DBMS error that caused the process tofail or be interrupted and stopped.

ERROR - A condition that will not allow the iDDL command toprocess as expected.

WARNING - An informational message issued to the user based ona nonfatal or nonprocess interrupting condition.

A-1

UN 620141100I November 1965

S

q

S

ol

S

o ofaa

a.*

o l o

I a 0 M bmaq

of 09 4 43

1 o IA r a

:e wm 4j w

* mia V

U. gs-c' aII€ '

B t

S.4 to I O. .

VV

4A a-r t

a-1 o a

off W .. A -6 '

31

A-..-......

a *4*t

mm d 5 e 5 *

A- a - ' i

* UK 620141100* 1 November 1985

.1OL

:I 1 040c W

IL 121 0 S C1 0 004 n46 W

1 0 a ) 9 . s

1. 0 0 W I-nOoa 0 4w PA I

s- V VA 5O 0 2 wV 00 a 0 " CoSb V z u , 410 0 P55 a 0I6 no t N o#

.1 AWNOg4 a OC awc aon * 043 Q S*a a ww 41 -

oilc u w&Ww ZS onA A

*2 1 ou 0 P. $ I S$o0 s- 3 250 02 e- U %aVa a VI a 6 *1 " 3of 0 0 2D OU I

PO lI 0 4O£~ on z toZOO & *iUjea b, a w e AL V 3.

ma 0 afe-- O 0- do~ ago.C mao

a * f a 0 1- 9_ 3 7_30g.3ZvSW~. 30. 2 c owo d aI O a m - f a. "I &a D or m

40 P. . .S 3. qS0 AAo -34 of aa~ 0 Sw -g. a . z ~ zzII

ma ~ ~ ~ C 0u 0aa ILIo (IgS.u %AO kA A4"1 u.6; Z 0j d v O n 0 wr o al.

5~~~~ 0 M atOO-a ' AMCb* S

MaO 0- -3 O3-b -iI

* UN 620141100*I November 1985

Z

a av

G 0-

* 3.

• 1. 04W an 44 O o4w Of W

• S, A

V V- IL 0

W A - a& f

Cl, a 8 0 m41 MO W 0a a

W lu Wi to 0" no W GA M V

o. SoO, A , AC

40 4AN 5 45S ~ 4 a. q- A U A S

€~ ~o I V A,,t WI P- IV1

o. MO 33~o 41S S b a

O .- I. V : V $.. " $- " -OD 4, Cm ' I * S *46 ,

we. S IS S. 0- Co SO ma 4

W " aS0 ol 0- I5 ". a 0 -&R S 09 SW 00 S0 IV*.

A a La & 0 4*S 0 W

ft 9 S 6 40 a -a & IL Co

a 0 e a .- 0- 4 4 6o . a *

1 144,0 . OI ,, 411 W 6

I- j I.q .,, 1- 40' $-a $- $ &4 ... .

II o * l am in 4 .4 44 l

u. s 0 1 • @0 0 a

t a .,o Co a OS4

10.* Is 9. lo. 0 0 V 9. O -9I 4-4

0. *.a a .u _u *.- 0.I

a * * 4' 4 m - S 0WA0W 49 C.

0 u

A-4

ml I SIC ~ m~u~gui amor

UK 6201411001 November 1985

A I

A us

* Li

4. o- Am 4 ISOaso " "" j .VWI0

IL I GA 0- 4 aa J VVU1 C2 0 z 40 11 S .I Us o

as, So oB WA 0 000 c o odo 0 0 4A WA

-I - - 4 WI RP --. L tV1ma ~ ~ u ss 0 z I 22

.0 * 0 mec I- C a% 9 a P L I @ L o " 3C 6~. I Sb-V " ? urs 9 w: as- s 1Li s - 1' . 00. Us no "ISIC ra 403 O

LI " %so C) X WmAs43$ t - " % Wvao JA a.. r-V Ois 0A V VS us 45 4410W WaV91 oi r, L S V W C Us 01, A. -J 0 0 i f J $s % Tar on A 43 0 3 1- a z 4Lrs-49 a 4 tas.10J_ 0: 0 4

eta 5 = s Z - J ^ A *- .J beW -0 S WA qK as - At4'VIUC I- us us a, A 6-

'1Se 414 Au b jesVt er w b41 Z V 4IM4 '

a. I usA s-..S'O 4S- 'i S- at z iUIVISb-s-w n V J33 .M o p W 0 L V s U ICR

* S.J a4A 0Js M0. 044 O- a a J~M~V

up 1ss 0- 1 110sU0 al . N . a ft weI W IItseu 41 e " 1 to -00 . 1001 aaDW an. s- an Us %L i WI A T I

ts ato 1-w UW acustnuVo OU 0 ZOO s-o JA.if a. tu o s no V um. as161e %,n s-INaSoins-0 a= u s

o', 3r',~s w .u ata s n~W as -

I- lo LA 1 'v-AA o- 0- A 1-a r s 1 fa-20 8 *ju s M5 005 S Mz a = - - . assass Va.F -s WD V~ V M s C0. 04 19 1 5

a -. W4 40J a8 46.0Va w O O3U j -t j 4 V aftcc 0u on #10s-Uin% on sW Ot 1 4" 4WA WI. WA ; -4 ; 100,.s- - sup = 5 ; " 9a

£ I ,s too 04 oil -J'I as V j = WE 03 s aA Us

%OA ft asCS4 s KS p V1 S toS V 5 A-,4 A4 &CA a.,~l~UD S -10f :A nIV

W nU U M 4A. 4A SaC a' tA A&.0 6 4%-

I a -AI^4

0 orI Us a x 2 V2 mO U4 i

Ii, IL ~ I

I, CXC 444 *J gLZ I &so~a .tJiI

SIC5 U~U 2 2t 4A-5 2

L M*sssIbsssssssss-----3Ssss ----

UM 6201411001 November 1985

00 0 00W1* 2: a

* 0 Ir a c so IU

*A Va aI- at IIP I I x&"

IL 644a as 4 a us ofA -a4 c c M 000 a o A -

0 MA 0 )M46" 44 z 4104 OZ z 0 4 A c

o S a 5 900 44 wB bOB ^ 00 4 w

00 aft1 00 V w 6- CAB :t a a c wS -ww0 * w n a s c w~ te0 wM astj

4La L ag -0 a 40 a ~ ~ a0di w pS *0 CA Bl., Z Y a-0 us0

U 0-29 0 S =1 ll alla 0 4 40 0 upWI 3&5.t OS UN U 0- 0- all a V -=4 W WIEI"

04 g us~~q I-3. us i02 w5 WI '4411 4

* a a. in 0 E.WI. as60aU I- a or 4 WEAOf alWfrg .a I

w 50 L 44 @S WIU0b0 04B L Ewe-11 OLSZC OAL, 4L~ So Osab sami w~z IfS-4

1i 48 ^0* or ta 46 c 1 V a a in A do40 a -to al oou 00h .mb~ . aa ftA , - oa. M-anUs SWV XBL AILE~ Z aAB ave41 &b3W OR0-0- aV-0 WO C E

a 0 -# we O CV' . , ; . . 4 .u0 .-00WI 5- as W01 -1 wA d * 0 R ll0 S. 0 J 1 a B Aa

of (OW w04S "C wK 700- 0 IWa* p4 30.50- 40 I 0%A 4 40 Z E 0 4. b. C1 U.O g-r 4 al%

gq *W MI0 .4 1 .0 $- I'A 14 C 0aa 11- ft 0 Sal IW Ie4 UD 0W~ 0 *A4WE

44 a~.. 01E IS. 1 ~ ~ OR.. j 0 P 4 wewac

if 0 U01 B. 0E . nD - 0- C4 .1 C3CE ~~ ~ ~ 4 LA %J~ %B 0 CA. a @ jA

tI all 0- weall of am B us is off IIIa W= =-i .J E C .na .. a"a ".j aAU 0

mci we6 ll a ft.SU "4 7 640-l V I -f PP Pmflb S.UBW i-a ort5 14 2416L0-1,44 41 7Z 9

a 1 900 ,C A 0 0 n40 061 C n 4Ba-4 0 f %a^w 6

mom e a~a- a~..a " wea *~

mS~5..as~aCBS.W Ila we:1 1,, C~04 1- .Se c

UK 6201411001 November 1985

0. 0 oU

IL

IL I

Cq I

so, ~~ UsI

* aa O

I-

do

Ic, o 126B

us I Il Ii Il

WE I I. '

Ii i., '

U.

C.

49

A-7

6maiman~iticli'* 1111b us..f, QI

UK 6201411001 November 1985

* v0i1,

* Iw. W L

L 0119

0 a go 404 1 s s

No M Z a WOg4

4L I a~ a W 0..on Cie g a ss a a D

aw "S OWs V W on, or 1 .No 00 13 e- 44 44 an

No 1* 0I on- 0 10 S. cc7 1 . a 6w weN T - 0

IL I W do u1" #0 a :a 00 we0 f OU -1 as L

ne6 mon" .1 1 I~a No am W2' C*On see 755 0 on A a a t o

No 0~ 16 as ao I r, 000 - . ~ 46 IS'1e s NI 0 we s- a *, am a -4 USi W1 0.a b..me -, No at aV. maa

Is.JlmC.A .5 mS Oaf% .a a

5 s arI eI I z o Noan a ; 1 o. . moo" A3

vi, sconviuAviA~nama A 1 0 CA g sOC. Vm vVamss

V. I.- mo a =a V el n.6i5.a ai NO g srl

S aa m e am No No " 00 m ew% a, ie w or a we

II..!. ma us , o aI ms ow o

* - m~fe w.ii iviv

mae~~~~7 sei jF J1on n .46 0I IN J 4 .J S

. or a1 . vvvv

I- s& 14 o% %A40% iAv a VS m.u 8.8 3SFW40* s 46 .. o oa a j anna A.iv OOU400

ap I j 4.e 4LW 1 %jW jn C . 1 1"o a.. a S @

wme

5.5

she0.N

UN 6201411001 November 1985

qI V IWO

I* WlE wa Or

0:1 'K 0 Z

IL 4 Ma 6A

V

a. -=, A 't., 4A @-6 61

MA -A 6 "1 4A

ffV 7pzTzwwV %01 u%if V :1 3V

;r z V CV

C3 au 0 aa 6 oil

Ct z z L

u a0 umiu s fLO U P U * w w f M O 6 4 ) C

n 0 Ub .. J Mi L.I61)0 - 0

?UC, m. W

w @3 ~ ~iA-9

t-81S1 955 INTEGRATED INFORMATION SUPPORT SYSTEM (IISS) YOLUME 5 242COMMON DATA MODEL S.. (U) OENERAL ELECTRIC COSCHENECTADY NY PRODUCTION RESOURCES CONSU.

SIFID JL ALHOF ETAL. 91 NOY 05 UN-62814110S F/O 12/5 k

UNSm onsooh-mmmh huEEEEolhhhhhhEEIEl.'ssnsn

i'soon

1111 ~Q~ 2.0

1.2 132 IL

MIROOP RESOUTIO TETCHR

NATIONAL BUEUO SADRS-16-

UK 6201411001 November 1985

z a

I ma 0

I naa

o s G aa a

K I U bb o

a, 0 a a-I M a a

u &u A, = a

i~jl[ tu r z* u

ml I ma GA8 ~ Vs; ~=.4 I Z I A iJ

a. 1- . V t 3 c. W. 60% *

Ge S w a z V .,

UIw 3r IMA o- no

Ml I C[ a,-I,, l a- 4 a,. -

at a a IL 4a-

* a maef-f n ,l mlo- Vs.fa r Ml *WC(= Mi , = *, *.

I* - 'a - = -

Z toI C r soU I P A3

11 - "I . i e " .. ar.

ma a. - I I- m -A . a. .a-1.

IL A z- -011 cogoa a ~ M

an~ & A a 1 4. I l IIel I 9

f2 3r 46 OU . &. ust on A got %A -

0 40 A a

r. a a a asz "V k"1* ~ ~ ~ ~ 6 9 N aC 4 .

* r nwm 0f651 ma T2 $A

i *nmrvaef a a

* u m •0 z f u4

46 U. A -V u .. a -

U :J. atV~ aZ V a- aV S azasuw 0agm5'MI

0 z fs V0W n we as 6

a S m s-~ CS s- atV 0-

a.. , g.ir-- V Paa .- sa- ot 10beu

SuI FWA I-w -K a.N6- - *.- a a-

4A aon ~ a 60V a' 6n

I M. 1. t~ wC~ 10a- s.IN -

1.- 0- $-M $-UI- -aa- 5.3 62I

0 IAS If' US.1

4M~AARS

eas Ah~iA-10 J J

D a& 6"aaaU h

UN 6201411001 Novbr 1985

* a2 z at

*0 V 4

0 3

0 3 Zu K-~~ * -

3 6 0 .103~ ~ I h

a a I

U. w ow 0 V6I

o 0 1, 1-

zulu 4 IW I z4 "0 V0o Li 34 =

I.., I z ^-6- 43

0 i i WV 63rtIM 49 w- 6 M -6

hIt 4 Ac 6- 1t* 00 -W 30 z

a j ua i w3 a

03 0 0 U w w USw I a0 a 1 0 V .

W I i 1 04 V- 1- 6.

I- 4czU 3

I-

* P

0 c W z£44hc me~ x

A-113

3 041I

*1 , 1 ' '

UK 620141100

Iss, 1 November 1985'to

1*05

a" 0 L4a

Ca 6- z on9 a-S z : 01411# aa5

IL us a 6A41

ma * goo-m n uss o~~& Me Nou.s a S..

400 "0 0. xe am~

0-- so Ze Ul

0 4# 2z ow ae mV 0 ofa ** 'a am. *.eI-a is

elm a use on n 4 . V

an o- T- se 44 6- 601e-s Ow a iF 16 "'a.e a m

ft s asa .$-;;A IOup c a a a i

ar I S6 Lb e- z U~a C C4 ft 0 3SD*: asi a oar4po 4 se41

ma V ma 34 W.0se us 46 "1

0a a-e3 C) -6AS 1. nA 0 S m mea ' "141 p0 C34

Sol aum - .-a .aae rs

W "C 04 &0J 0 W0 0 _ A=

8uIa a a W vWu~v *,u a...SR is

At A onAO A 1 A4i 4A OU 4.1 -10 s1 -- 4A s0 0 a

!o "- I i :i~we -0 "ma".w.

weO' '40..U .4. Is . s s .. 41~-P 41- a-40.-0-e6-e a US.to'It M a-_- .% = =1 = 4,01 4A

I On 0.R g o WOi .' 0 or f" 44

* 0. 1- ;; f &" ; 4 as a 0 as

P. I- I-' o- o- ell I

'.... a ~ a o- 0.. I- CIOsts,4a- 40 de sl.e4 45 -0 m 4 a 42 0zAr

suIL

GoS

el. :

A- 12


z

o o

, u . C ,

w 0 z u0

IL ^ V,, toll" ,,so I - s o

Io IJ

4., A is I 004

0 u u. sre -

or wjus 'i U

Owl, I,,I l,

Owl 1 ,64 C2, i -4~, 0,

aI-

&

W

.o

Olp

40 a aA4Or 1g 0a 0 #

K I Z

0 0 aK L

IL

.4 6

A-13

~, S

MK 6201411001 Novemnber 1965

v a*r I fua

US 4"G

so 0UG

3 5V a a

at= a So av-a 0, "Z u "a ura #

a Q NO See %j o- 0 -U'top 0V o

e a w W We" I-aCIO wel GwmU 04 MW GAn 11 b- CA

a.5" 0 wol w 41091 0-a e e u04mi w faa co 00 :00 a- 0a" amse ma 6.6- to m0a .. 1 di a, t,* - .

1 40 ""o m I'l lose "I b- -W I 0 w II - a s Emell UL I1A -0 a bi Sa Or%~--~ C u .aw a 100 ma 4..mad am o e % mas

49 lw10 90 aO101 ma NO- wei U m anstb 0p wOWv- W m a s^ -a I*t Ingm 0GA4m3 ag $am.z so a 24

a. ~ ~ ~ ~ ~ Z %I WAGAIG -1E@P~ V~nb *S a.

00 16 1.. CS.. " to owA~aS mau@ ana so @Mm a W 40- Da b--3WWWZA Um

w*44 *b-a 4 feelaa mmm mae J_ Z1 aw wu0 W.1 IO NORS- ~ "$.aE S *2 aU mO&ma :I 6".e 110ru'J mm m aa. .wa- SM cat-S 40

* 1011 1 *I AU Wm~ m V A A m..b W0 SG~ , 1a3,:Ge 033 ao a.a ftailee, &:$-a o:zxzq 0=1 1 a 111 o 41

b~~~~~aO OWPO GAu m e a g GA1 to, f *5

S40 .0 45A5 fi -U 0 03 3 4C sb- fe goO Iset -0 b - A A m -1 "O~ m -. 1- t AsotoI- I-%jt W80 PV 1ACt GA W-~ m nm n t GA w. 40% % Its

8 . o" o- o-w o-o - .1- -o o . W jW W 8 - - 0 meweeas9 6" GAU uV " &AP .4 wo We o" 8" Zws t NOA Ass~ , W "

as- -o ma wu w o eosoWw oU w me -~js~a at madG xc *"r.~ CE)rCUw - bb5V--bb lV % bG GA A U 5 Cj -E5IbL ~mavan Gl a a o a,

*rc b-b m m -- % ba --- U*10 b 5zg maa~a- :m ear-A~a~O .Csta hWeai Im muVwag~aao NOt uA- 14

620141100

I November 1985C

0SC

I

* U8

4w a 03 co

a 'a

lo I UI.

&o %f 6" ci -

*4 1

U. C 5,d

G^ 0 LWL .

a. I =N I a

to uI ju IL Cl

&0 c J P 1 "I "I U i.,

4) O 1 0,. L OF. L 0 8 ^A-01

a0 0 e .40

*t ee p£ 2~ m0,,

ii O S I , --I oo u in i% Ill I s -Us

*q S '3-I..,S . ta .* t'S3O L k.P W S* ,,*

aA i 0 a a I ,,,

ZI Ir z 0v- 4aII

el I O. as .. il. u up oi

W . OIW UWoI 32 UVo- n

Lj #1 o,-0 C

o o *O.Jf P@ vSI

U.

El 0 % @1 toasA-15

*f3fC2

8 * ICSSS)*IU.*SC A@anSI 0a'U I P

as

* * J 2i 7. .V Vi C. .3 -C

onI

'-S'

SAI

9-I

I [:: S -

B UK 620141100S* 1 November 1985OO9S

0

I *

I e t* 0

o 0 tJ S

A a auLo44-

V of we A AZ"

mJ J Wl

a. o my qe

on I *so*

of s S- a -ft, I @-

or I o Ze,

a. *S. 640

* a,. ui Z

o o 5W ~l, o Go- a.-*. .. s.. ar.

* 5 ~6 64

a I M,- b II *

ft~f ~NJ0 SJ W ..AN

Owe w o

rl I do. 8-a9,&

O £iuW UoW

3 I .I , r J

I I I I I 6 I

ue I ij B ,,,

OF M, 1 1 I' l

a * * -a al .a.aI C eI I -Iu~eI

atS!.a aaN

C

U,. I U'-1 I4

64

O 4

hi SI IV ft I- V 64 I I I

o-, a -8IP 8.4 SPI 8

v'11 a a . a'N

ii, S

A-1g

UK 6201411001 November 1985

0

I DJ

4j I , ,,

C Sl

CI 6A~g V .I .l

o ~o, 48z- -lo- ' @-e

44

if"

,~ ~ ~ ~~s o" .+-,,,.,.== .

a a-

I~~~~~ €t • "it u O

q =

SO6 Z of $A in Z C3

C, CI I

S I , ,a4w a, A v -

r 4, , .,- at a4-

4C I to a -f I m'1 . All

'- C U

c. eu I .ifl NI I or c t -

0 ~ Ii C U 21 &. A f

..,I ,.,.

* I 9. -.A 4 O* ' 4A OR- A :I

411 U C UO a O 4.

~~~~~~l ,",Jr .' *' e 'le

SOA w I. -00 ='n -" 0 C, r, C.I

in'

VI w'

do z 31 us oiS ll usZ us O

04 46 4 0. ,, -_! _j1 j Zit

M I e I w All O ' on t 1" 0. L.1a I.a--.om .- 1 ll

10. V )i

A-l

a' "3.1 COL 0 41 an

Ii. a'c Cup c.~ a~fe

a~~~ Il 1. -to414 W

rI W Wa'4 wnA be3

IV IT IK~~ZZC Z z a*

of 9 a&5W Ok

Ao 17. .. *

* ~ t)~C~LI leiI

UK 6201411001 November 1985

lW

* IA

03O

6I-S

si N V IA

so I uI

0 ~lt 4 , h

A

o do1iOa aI aI~ -4 •

0D I O.V i S O*. |. I ~e AC Q

ac" go. 0

.4, * 0 03 5'o P C€

qI I i V I S SSD O SD C @

100I - -0 o- a co

I Onaa 4 8 1-

us e- ew w , S V o r

Io * n " a 6 TV m . mr so

ul a C)a 00 I I - J

s. at fl. 1- p or Z &I

# 0- a -0 a 4 X " "' T

1 40 a* S V 0 U '

a, ell to 11 l WsU 0 0

eS I a iAAP.IU • .o o $4• I0 r

SD lIP (pgufCOUP V.k CM I = Qg151 MT J-I A 0A 0 II , f ' U° I M.4 6 S $ .4 ' W Ul P" SiC

La r V S1M w 0 D M, U B

I~ ~ C ca4 p. pn 401 0 4e dt ar 0 -%I

to I w ILOfatw* w *Is.S 5 4A A e W

C. I .I, .4 0 4 - A

w O f-e O ° ? Ot"

A 30. a .. W a .aA Is CA in, le,"

us I

II

ala- og l

I elS

Io o a aoli .iaaeC A

an a a AE8 -4

fA SW es 01 0 0co ele'A.Ja

106s. ZSD PE

3,q.9

5P g..P.PA-Is5

les

UN 620141100

0 1 November 1985

I I

Cl w

OW or

Za

C3 .

at ai I

• w z -I3l I 4

0 A

L to I-

1b 11. AC I V I A

I- Q a. J U. 19 M I.- I M

f^ at :: V- vz V V su l sl cc b- lo-

su e" IS4 -0 - 41 .*, 0 L

do w o oi of 2 & -

O 4A a uz Ci"Is zsi jj0 r

a do & a- b. i-. = .

* ut lit % a m 1mtI* I l U IA An w AN bie N- i -- I

o S VL x II 3 W z V 0A0 s C2B S o- in s-a.4. j Z FC3L9

ar o 4j hi 2 at w rui 4n 0

i . I u * ,= I l 1 "0 V !us u = . "I I-- @A -- 1

Io IA=4 *- 2I VI a'q eu CC 1

, I 4 a Ul a

GA146o I J (ICj. a 2In ~II %A A V

" Za en on be I.

w I j 1 ; j UP *z aZ 49"As fliI

A-1A

3. W 1 JN

Li S-U 1VSi C.) . I "wI I iIn

as "t *VILI 22 -a or jAi

n *.,U i . J 9 I %* I

CLL

C3 IAI zeiSAat

6. 5 A-19

UK 6201411001 November 1985

SL

3, Ac 0.0 "a 6 0

6L6

z go 00q

""0 u, AA & p,C6 4e V Af a 5-,.60 ~ ,

*U 4A a or to lo

I * e I C. w asa. ^ ,. 1: IL *z i- C 3J

o M S 0-6 .41A 0 MSW5 a: 0

en 0f~ 4B o , tn a *J4

04 41 &4 weu a 2 s'A "A

a 326 a .4 i to,aa .aV a" Ven & 4 A aC 234 on t aOA dgM- eza a T t- IL f in 0....$-i f. ' 4 0 Ca Ct z w wL A OU tooUanC 4* .C 0 p. to 4n 2P1;a a #A s Z -1 I

& ~ 1 *b' IL5 *O UO Z Z0% em aas -0 " In-. mzts" - 06wa "

30M b 0 U, N&Ii5 O a i * 1- ii 5- -%40 ft uiC usen Si V z ~~ en 41 to4

.u s S~l s-utC .e e

C ~ . a wKf LfW-AuiL 4-US

u 1 419 d. o -4 005-C tRRLipg# X 9*- f 'U2Wa n 'm

on til 44 .44t i a 3 . J z a 6I M i t t L o - .J. 1 #1e1g 4 0C3n ID 2 . wis en Ill 2. 41CM A Ait.oo 5 K AL5 n- 5.

ai -taa .a 00 ZW geA VMne.a4.,~,~.,lt 'S

LAS MS U45 4 -LI rD S P,7.B'. 4 sa .9 ZOtrViik.

S~~fK~A-20 -ua-.cc

L i ANS5-4.45-Cfl.4S5-ft5- of. or Ro

UK 620141100

*1 November 1985

I

* 1 5

* 4

IWO O

w C

a Sg S S

0 1 "

uss v41 I nI

at &A Go us

as S

3-0- wo d- 1U I ) ff 0 o

o * . ll

* a 7 0,.7 I

W.- I

in I d i

ZA Z an t

or wq A A

Oh z =of 4-4

.A- Cau '

I-' V. I

.A 0

It a 0.1

9 I -

M --

=l I J ;E in, O JUo r I Dl.3 S1- m do 1

r r

C .pg - WA- a 3 u1 a n

t-/-

it I or WI. O

ac!41160!

AI-21

ga. * ft ga t3Z

UK 6201411001 November 1965

* a 10-

* &fdo- a

C.a aa Io- x-

NoV VIN a ac

Mo IF Ft

-a s-t s-PC11 I I- ~

S. I abVik0

a. 0 L OrGA4a, uf a aN . a

IL -643 . 10us of ana sIu WV 'i a

30 W -aa V In ofC .1- 1 .

to A~ 0 011 inZ %VI.

gog, V a 0. 19

Mo USwC as 40a22.1 go 1", 00 1,4 l WI. U'Vo- '0 aM z rIm1

f. 41. seeu aa ax3 5' u- "0 V lo a 40U j "I% 0s S

I. b. mel Z.' onflt z4e It c s.

a 6 16.. on . 40o oA 9 o- Ii- =a L Or CI mu L-a

4c~~ 0 af a:0.

09 I )IW ' A" .4j a. acj

e us j as up od 3 sN 4 0 a 9 9 oi Mo 40% s Mo * or Is fC

ar jo-~f 3s- of- CCI Im m Ip&"3.48 - ~ -#11 V A J. -jl * a dew wl -l"f

"a I0 = IkI 24124 0 O"Woo- =56 Wu. Joea " u-a

C,Vo (. C A4 o%A*A - & .#

*4 do Q 14ijto a Sol j 1

M a-. e ft "~ n 05 .4 c Or " o -

5-~oo 30- 16 4-01 4-0-'1 a

o" P s- s-b. - too S. is- .I 5. 10 1 49 .' 48 5 - 1 too P. lt W#2 16. 3e mu BE 3e at orgJu'*umsa u a a ofa 'I a% as or or m

fcc

1~ cia

ia. a 4

A-22

M illi N

UK 620141100I Novembe' .1985

* 4 V A

* 4 I VrW or" W I Ut

* AZ 4t 0-S

* 4 q t 0 UUI~ ,.1 Ix I Wa W UP .0 'a aw i

no oi Of 0 10 3? 0 3 I

* .a 0 a m0 SR

* 6 0- 30 1 0 3 m 3

*. am o, V V $4V 6300Arn SI 4 4 IjI r w 9Ie i

~~~~~~~4 S . I za sA A 01-o -W 3. N Z r I

man 1 a. a 25 3 V 1..db0-4 m

C, ccZ0- Us 40 I,. WOI ZU Vl IL %V IMW49Wealw1IL 1W "' W a~ Oaft "' CO 40 0%,

a S a- I"- 0v 0 I S am I 4 a

0- 1- 0 A I VE 0 a mII I Ia 7 S.

4~~01 %. a0 me z04 4 45I a B a -V a I V1 3 Co 0 us

aW- o- a4-I CA4 W . SI.6 T a0-

U.W1". n 0 . a ao 1-33 * O 0 R 0V s~ot I wo4 II l IS UI

I I 4

0- S A P so. - 0--~-- "0 W0-46 V as*0- 4h0

motdo0 0 *O 3 5J 4440,11 a out us r a.V0 I 3 4 o 41 Isw IWO. 4 o o O ma

U,S M SK o- CID. E O. ie, , a o0f

So Ir S 0 I r a US 42 P m "I .L of us

0- n0 A B 41it imWea 0 L u CI0-J 4 300 M $ a

an 11 10 Q I-' 1- 0., 1- - e , . 43i

toS "4SI0 c t: s0- 0-S ?W 0.*- W

4K ot I0-S W -0 $A -%A 0-U we 0 .. 0- 0 . ~

0-0I I X G aM 4W W0 flM "04 3

5 a U.- ""&raw 0-0WIV0S." am UI

00- 1.. SI a"OUU. fe3t* or at 0- 0

40 1 up0 a 0 44-00 0-o) a~ MV 0~l 4to IM -a EM VolS W40 v-pSS O~ U sow aeo-o-o

a 34 050-3 C'I' n,33 0- W.0 I. CIS~

at 50 4U 0& up J444 *u0g'o ""I-E mi.l 4

50 40 - 00 00 I- C I 404101. - 0141a l 44 6

wo 31 " 1, zVD 3 0 0 O 4 - 0 ~UW O W~ J we% 0-a1m9 o 0-

I- I.l~ f I- S.- W. 1ee 1.5 be %

11. MU .4O ORRSSSI I-0 a0-U0-a-0-h~ St- Is s- s- J 01s- 10 z J z -0 '4.1 Us J

,o S9 32 0I 16 ~ m49 A 0 01 a b Is. P. 0 4411 V-9

L6 IP U- OJ .1Fr.C ,114aA43Wo W -ASE %A 6n-0- I 10 4 M

0 OR

# of

A-2

* LI,

US 620141100* I November 1985

M0 J C

e-"6"oSLs- jG n n

ao -SLI

aw S& S

"1 S 04%pmaO~ ff aS

w = %9 a Cr=At Aa rm .3 2lo n#

LA S.4m z 4A 0 04 W wf as

sw0I on z as kc aC 5A VV do. a wMIu j q u I %j Us &e'S .40 a w u 1 0 "4A Ow kuo -$ l a atm i ~ a 4e 0 * Ca

vs o S n . o Zm~sm I'l us s metoI. on 00 a i V tuo bO 46 domg as.b a U S U w

S~b an oa CC @ U 4WA C3 a a C~4*40 zaaa~ mO Ocsf1 .. de Go

0. W. l4 q"m au "usII a as o" 1.0. 4.10 ;U0 W

1- 6- 1- o- o- o-b I- I-amum

"W3 Z 3 JM3~ifes1 j19.1m ~ J~f~ m 4a C C 44 a.

o* s M m4*44a4.IL~a~r ~

U@0CuUOM .~.M .0A-24LD ~

UK 6201411001 November 1985

C,

IL

SO

a-a

40%A 1 S C

lu I

IS I

a.

4.0

wI 0

A-2

UK 6201411001 November 1985

a

0

S

S

3. S

Asw" 0 4

Iaf

I&I I cis" . I OCI 0,4

o ^a V j to I-

So C%0 a I 0 o ,4

o,- I rI)12 D O " tDm

a w I " j t

ra W% a 0 r NO. ono j1 Ih clJ %A1L:o.,,e*- zio,. t. mua rol w "0 *

S A as _,,A a V f

I~ n,,og 0' n,, O Uo UPt $*- - = o ,~

I ___ a u ,,J .N I

ns M OL Ao r 4A St *o.' -- S lS, ci.a . U I' L

• i Los WZ 0- IA " F. 03 4) no

" 0 to-u,,, I..- I - me- , or 4, J ,.

44141m 441 $-lu , em11M1

a~~~ I L~ .

' A os

Us IL or SM 7i .. a It

us 0 VV ac. 7 3 s s

I $IB GL W u - 4 .'s

W A o GA) GJ.CUI'll *p zim ~ m 4 a

Ii s o sot o 0i 4 , 1 .1 U sa ~ ~ ~ L a, *06gUA~l~f

on -un j~.

SeA26 . Stu


0

O ~ ~ 0 gisIP oa VC 4pa

lZl

S

* a

w U92 0

al an 4

ar au, a M ZI

0 of jai u. 0* - 1- 0 V-

Szr

c S

CA o-0 I-,,, i.4 1- .W

I " ,4 SoD

o , S al ft 0

OV 0 4A

C' ' U'

LM P orU ft -j 4.

-2 w L- S *0 i,,,

en S ~ ut r

geor I USAM I so &

A-27U

W~

UK 6201411001 November 1985

0w

00

S

•~ 0q

Il 1,d 0,

I on .1or 1 q 0#Ab

0 a" &,-

Aj I " *

ILl

A-28

- - - - - - - - - -

aal,

g2 4

A-2

U I

*~ 1November 1985

66 J.*f

0 S

an 0 no

a r i

.s 5 af Sus 34 a

a," Se OA 1-0 Vb0 SaW SWM11

WA 00 of -N- f

a.~ daeo aa- s o :E 94 IVO$-

&A ws Ca-u. Z

MO S .a Oc 40D, fl

* a e f .4 a CA5.A A 40 61. IU.

: 05.5 a* .WO BU go0 41a 1 a a 4 a a 66 0 L o

& *A a 05m. * ova a -outaU S" aw s ft kse '.U3

: a an I"Iu : . ~ A A 11$ 0 J0-0o

o, 00iH~ 404 04 01 A&0o ws w .4 E~d .4U 5 E "dW S, If

KW : 4a- S6 b Ow WA a- a w

*~~~ %c .~E

sob V1 6^ A &I A

*L I

*~~~0 a- a- : .,-q -L* ~~ zn =- en -

ft. ft off5 5 5 . 5 .n

qiI *4 .46.L** .. sgbfrevg~gI

.

C A-29

* R

UK 620141100* 1 November 1965

ILIUP a IWSWO0 B

Us 0 6G

o fd S am a sua u9Aa

a.o n ew ew we a$ m .ul we I"usItu0- 41 ~ 0-V G-0-1 S 0- 6. 0. op 6. 0. - &

l n.no S U S N N oaI S- asjNo qas

1 N s a l *aau.. m u s -g u us g a# ta .--~~c S a Lt 3' in 02 0 0 nl a 4M a n 0l

l *Cl.C o 0004pfO*0CScan4Va S a- wa a-U-JLU S 4*- *S

for S .59.0w.tm.a . o t. .

Z 40 asia a0 1* 10 coo a0 0 o 18 49S in41 0404 411 4111WW swa -o

do aS4a0G n4 64 1 4-

Ma 0 C3 .1

N ~ ~UahaaaSUe~sM~eaCWIm

* o Aogooag30c

UKE 620141100S 1 November 1985

Iw

An

*2 a

SL , z V

I * 0 am Cl @

I v wo- 4

4. IL %#_j o

am s oa a

so. ma m'i

0 Lo 0 a l 4... VS. CAa

ZC Z Z U.

a. 4 0 affs-. a9 -$i : A .z x o

ue s w s

f 1 r2aDofW

A c31

o UK 620141100S

1 November 1985

OO* e A* em. S

o 0 IM UaI a a V

US 0-mw aa I U.

US ^ ampS 0 0 " U S

C% a lb O I- O IC -U. I A S I .

* G U C -% UsI* * u * *olr a

I,, I PO'de. . U"

SI

UP ap a weW @ Uc . 4 1s C I

0 IM~fA * n .(-

, 0 uu4Ia s- c% All 41 US

a a# on~ e C

#- 1^" ~ M e r q Uo

46 be o A0 Is VC . Oftsui j * o i si. O S on a

* .D~q A s " a urs

,us, I Wlt3IAT1 56 C. I

II. O .5.40r6.l~ lPl 'a*

kI~ ~~~Q 490:mett I PI ,, S I s o o aB L I .JC .eu.4¢WA .e

o 0 : 1 . 0 -o ,& a ll Iw I l ia i, ift zW, a t t S

uso W, an. %A.. 6n -A uS t=^ A"

I5.4 4-1. :61 I 7.i"11

SU

ofI

I O I

1, S 4.44 a s5 4~me tr

aI I, &

S,. * ,o .4S,. n.i. 4IAm a ,-

*I I A

I* a

* IA

* t IA .45 .,A 4t I '

to S U &, I-A- 3 aa q 1

Ui 620141100

1 November 19850O

I

6 &

SA

a

f w

* A A

tj O U

to S CI '1C tL bC

IjI l I 4 W. vS 0 0 S-i Q

l I 4^ u se o

Mi 0 04i Od i .

Sw IL L UI I a

V2 * sr m a" CI

"77.. Z7-140,1.

F. A6 O O OL

aMO if i iC I IB I eiMi l U'D

9 MiMlM

if 6 I •IIWW

M-. S .4 3II M Semi IL I

I 2 annlolr

* M, Wpi~M i M UMiO iJ* 3 C' 0 (. 0, 0" O"a ... a,.I. I -

*, I 4OfJC1a OO

Se 0 O loo~ooa ~o .O * sggO I OI ii

S if" I €MM. U.S U- . . UL

4.9 0 2V V V V v v v

'A I Mo .5 ..J .,J .J ., ., .

el I t .11 li. I Ml .. M

IfS a,, U. U.- U.- I S,- . U.

I

A I S ,.5 .J, il .JO --hJ .I. .=* Mi .4 .i .4oi i . .

Mi, C U. N.- U U. Nl. SI . U.a

h~' MI i M~I .M Mi i Mi.

II S

ft,

i-3*iX I if

A-33

E' q~ ~

UK 6201411001 November 1985

0lISIS

I 0 0

ISA

& 6 I 'lif I SAL

o f s I ' #Oo I I I.i~d I I O 9

- S a-

O I WE'I__J I 0Vk,.l

4 o-IL II 1 O.1

6 0

I* p o eA

& I O0

I 0 a 0.. A"IVo to, ,4

0 u .Rv o. 0 o&

1. 0 4 1 Ia* I )a Go 0 0-

S.~~3 I.a0s 2a. so I. , =-

I O 19 i lme

a

IL I a I- i

O 0 r3o 0 L- to .1o

aA I t.U 25 0 f

IN lo P. . 1 05

bI U I 0. 60-0i l4 m

S * , W,.* p

u1t 111 -11 -0 01

a.,O CUI .Jd lm.

agle I I U*

q' I O13O3O I,I

lv S a 1eG Oil all *.. bcu O In [ m

+

I

II

su @

A- O U.f34J, .acII e 13I tie 1 il

Owl Ial e 1 m U

II- I

5i- I

mI

S. I I

A-34lUI&

UK 6201411001 November 1985

0 0

_ I ,,

0 14 WOO 0 W

ad

we as 0 00114

0 i as

$- fw

qlo af q 3

-I Z 7us .

MI it3 J .u

4.4

* i

*w ia S W..

A-35

* Iu

UK 620141100*~ N ovmbr 1985

0

IL61 3

o or

4a S w" U

8 as. 0*. 4II I V a a

.S C 3,

u4 s w z o mpo

I- do aO zG

ub 1-a. &n & V

a~a I" AO o-~ifusf. * ~m a

"s 96 aas #.-.'I. I w Zu

a. It af cto

a S VZ~A CsususU64 "";-Aoeuu"~

f~o SI *ZC*B

4A q Aj#

b ~ 3 n 4As.u v z0 ~ ~~4 0 ... 0a,0a.

e su .a o 0 of I l of 3 . 6F. Coa C.e e j s - jc 0

Z r f C m 1E S 1 4 M tit Si' ftW 1

I&A gw ii.

05i *e'eu ' 0u J

i&6YZ"'V17 eL

A-236~V3.

6I ON 6201411001 Novmbr 1985

ow

0.-0 0OR so :

S- T nSt

IIS o lg

ag fam r4 4o

0 Sowlv SSw

I L11 6U

I4 A

LI S ataf0on

ma SSIA,*i 0s FAA W;fU'

.4 5 V a 0.4 '

* U a g00fl* S 5 9 i.4 s

4j t ~& .404 re I Ra 9' rO .U. * U40, ' U SO , U0

*~~~ 4. O. SW S Vi U S"I fi us Usa of u.s~us

o a* gat . cr wa O a.O SSma SL *-,DUqD3

ft w.i~aafD4

* a c '~

ma A-37

zu ~ t II! lm V1 P 1(V ,1,1(Ill11V,1,S D I

UK 6201411001 November 1985

0 a

SS

C 3-5

V 0 1-

4 I-

Z Uw

lt 4A -07

Me' . -j o 0

S o S- C

1 -

be *

Us5a.

* Ira m

4d$ 00 SOA-38

A-31-


a

o

S

~~PI- G pt

Gg. fl M

ON II9 C% 0 0

Ul "JI w ofa

fu o o I O O

wU fI o0W 'uuI at

iF onI 6A on an

K I V

I f Ii--I o "I--au I oen oGo 6t .

4goL

0

I

Ao39

if "~a .

SiSr

ma€SIlS 5-

S. , f S

A-39*~tSD

I, S* I

UN 6201411001 November 1985

lu6 64

n~~~ INSa ua

SS

LI

lw I ia l O u

•a 0 us

es1Q V. 0 m

OU LO 0 .# ,

atI , II a .W 46

#

S

ZO I--

4A l,.

ca W

4 S SW

A-54

3 5 UU

MN 6201411001November 1985

A-4

C 1 111a 1111id ,1il!R III II~ i i'I 11

MN M 141100I Novmber" 1985

1

0*a

w a

to Go w

01 a

aI~ sw of . . 4 a B lam f t -to0

a z W& f a o wl

a 4

It

0 0B6 94

CA 0S e a a

m r I anftmS I 3.4

4

it S NJ - .a- .Aw I" m ."-s w"

do I w V

A-420

UN 620141100I November 1985

Sa

S

00

ONO

lu I W 1I P O ,

as0S

L S

a S mm

L 0

I. LA V AJL

Ion a doaaC3 a= 0 A

A-43,

F S "WWOMWS

n i ,ir r P~x '9 * a 5 0;

UK 6201411001 November 1985

APPENDIX B

GLOSSARY

Alpha-Yumeric Data Format

A data format for values that can contain characters otherthan numerals (0-9). numerals may be permitted also.

Attribute Class

A collection of all the same kind of attributes, i.e.,those that have the same meaning. An attribute is acharacteristic or fact about an entity. An attribute consistsof a name (e.g., employee hire date) and a value (e.g., 15August 1980). An attribute value may be:

A. Nondivisible (e.g.. state name)

B. Divisible, i.e., a concatenation of two or more otherattribute values (e.g., part number formed byconcatenating drawing number and material code).

C. Computed from one or more other attribute values(e.g., age computed as current date minus birth date).

Attribute Class Data Description

A generic data description that applies to a particular

attribute class.

Attribute Use Class

A model attribute class that appears In a model entityclass. Each attribute use class represents either an ownedattribute class or an Inherited attribute class.

Attribute Use Class/Data Field flapping

Indicates that an attribute use class corresponds to a dataitem; i.e. that they have the same meaning and that the dataitem can be used to access the values for the attribute useclass.

B- 1

UK 6201411001 November 1985

Attribute Use Class/Record Set Mapping

Certain attribute use classes can be represented in adatabase by a group of record sets rather than be a data field.For example, Project:Task record sets called Pending, In-Process, On-Hold, and Completed. An attribute use class/recordset mapping indicates that a particular record set correspondsto a particular attribute use class value.

Component Data Field

A data field that Is part of another data field; e.g., ifdata field A is made up of data fields B. C, and D, each ofthese latter data fields is a component of A. A data fieldcannot be a component of more than one other data field.

Component Domain

An elementary domain that Is part of another domain; e.g.,a Date domain might be made up of a Month domain, a Day of Monthdomain, and a Year domain. Each of these latter domains wouldbe a component of the Date domain. An elementary domain can bea component of several other domains.

DBD

An INS database Is defined by a Database Description (DED).The DED consists of statement which map an INS structure intophysical storage.

Database Area

A subdivision of a CODASYh database. This subdivision is atechnique for Improving the efficiency accessing database recordtype Instances. When a database Is subdivided into databaseareas, some or all of its records types are assigned toparticular areas. Instances of these record types are storedonly vithin the assigned areas. Then, these record typeinstances can be accessed by searching only the appropriateareas rather than the entire database. This access method isonly used when the record type Instances cannot be located byother means (e.g., by calc keys or record sets).

Database Area Assignment

Indicates that a record type is assigned to a database

area.

B-2

UK 6201411001 November 1985

Database Directory

A software library that must be used when accessing adatabase.-

Database Password

A code that must be supplied when logging on to a DBMS touse a database. The DBMS verifies the password before acceptingany other messages.

Data Field

A port.ion of a record type in which data values can bestored

Data Field/Record Set Linkg

A data field In a variable data set In a TOTAL databasethat Is used as the variable control key for a linkpath from amaster data set.

Data Field Redefinition

A data field that occupies the same space In a record typeas another data field. A record instance cannot contain valuesIn both data fields. One Instance can contain a value in onefield while another contains a value In the other.

Data Item

An attribute class as seen by a user in a user view, i.e.,a kind of data (e.g., employee hire date), not a particular datavalue (e.g., 15 August 1980)..

Data Type

The combination of a type of values (e.g., alphanumeric,signed numeric, etc.) and a type of storage (e.g.. binary,packed, etc.)

Data Type Name

Names of NDDL data types. The NDDL data types correspond to

the following COBOL/FORTRAN data types:

B-3

UN 6201411001 November 1985


INTEGER FORTRAN binary integerCHARACTER x(n)SIGNED S99V99FLOAT FORTRAN floating pointUNSIGNED 99V99PACKED COMP-3

Descrip tion Type

A generic object may have several different kinds or stylesof description (short, long, technical, nontechnical, etc.).Each is a description type.

Domain

A set of rules about the values that are allowed for a dataitem, attribute class, or data field. A domain is either anelementary domain or a group of two or more elementary domains,called component domains.

Domain Range

A series of consecutive values that represent all or partof an elementary domain.

Domain Value

A single value within an elementary domain.

Elementary Data Field

A data field that does not have any component data fields.

Entity Class

A collection of similar entities, i.e.. those that have thesame kinds of attributes. An entity is a person, place, event.thing, concept, etc.

Entity Class/Record Type Mapping

Indicates that an entity class corresponds to a recordtype, i.e., that they both have the same meaning and that therecord type can be used to store instances of the entity class.

B-4

UK 6201411001 November 1985

If a record type has more than one EC-RT mapping, some ofIts Instances correspond to Instances of one entity class whileothers correspond to Instances of another. I.e.. the record typeIs the relational union of the entity classes. An example Is aReplenishment Order record type that maps to both the PurchaseOrder and Manufacturing Order entity classes. Each recordInstance represents either a purchase order or a manufacturingorder.

Feedback

The length of the key feedback area for an INS PCE3. WhenINS retrieved a segment from the database. the requested segmentis fetched and a fully concatenated key Is placed in the keyfeedback area. The fully concatenated key consists of theconcatenation of the sequence field of values of all segments Inthe the hierarchical path from the root down to the retrievedsegment. They key feedback area must be large enough toaccommodate the maximum length for a fully concatenated key andstated in the KEYLEN entry of the PCE macro.

File

A set of stored data that Is managed by a file managementsystem (e.g.. VSAN).

File/Database

A set of stored data, I.e., either a computer file (e.g., aVSAM or flat file) or a database (e.g., an ORACLE or INSdatabase).

Generic Data Description

A detailed description of the values for one or more dataitems, attribute classes, data fields, and/or module parameter.It includes format, measurement, and domain characteristics ofthe values.

IL Generic Data Description Domain

A domain that is specified as part of a generic datadescription.

Generic Data Description Unit of Measure

A unit of measure that is specified as part of a generic

B-5

UK 6201411001 November 1985

data description.

Host

A computer In the IISS.

INS segment

A record type in a database that Is controlled by IBM's INSDBMS.

Inherited Attribute Class

A key class in the independent entity class of a relationclass that has migrated to appear in the dependent entity classof that relation class.

Key Class

A group of one or more of an entity's attributes that canbe used to uniquely Identify the entity within its entity class.An entity can have more than one key. A key class is acollection of the attribute classes whose member attributescomprise the keys for the entities in an entity class. Anentity class has the same number of key classes as each of itsmember entities has keys. For example, if each entity has threekeys, the entity class has three key classes.

Key Class Member

An attribute use class that is part of a key class.

Keyword

A word that has been designated as a means of locating ageneric object or a number of similar generic objects.

Model

A representation of the information requirements of all orpart of an enterprise in terms of entity classes, relationclasses, and attribute classes.

Object Type

Sets of attributes are, in relational terms, calledobjects. Objects participate in relationships with other

B-6

UK 6201411001 November 1985

objects. Entitles within the Common Data Model (see GenericObject in the CDM1 Doc. Control No. CCS620l4lOOO) are calledOBJECT TYPES for the Integrated Information Support System.

Owned Attribute Class

A model attribute class that appears as an attribute useclass in a model entity class and is not an inherited attributeclass.

Program Control Block

A portion of a PSE that describes and controls how an INSdatabase can be accessed.

Profram Specification Block

A group of logical views of INS databases that is used forinteracting with the INS DBMS.

Record Set

An association between one record type, called the owner,and one or more other record types, called the members.

Record Set Member

A record type that is a member of a record set.

Record T7)e

A group of data values that are stored together as a unitin a computer file or database. A record type is the collectionof all the records of the same kind, I.e., all the records thatcontain the same kind of data values.

Relation Class

An association between an entity in one entity class andone in another. A relationship has a label that describes theassociation. For example, a customer named ABC Corp. isassociated with an order numbered 123 in a manner labeled*placed". A relation class is a collection of the Identicallylabeled relationships between the members of the same two entityclasses. Each relation class is either specific ornon-specific.

B-7

UK 6201411001 November 1985

In a specific relation class, one entity class is"independent" while the other is "dependenta; i.e., entities inthe first can exist without being associated with any in thesecond, but those in the second cannot exist without beingassociated with one in the first. One key class from theindependent entity class "migrates" through each specificrelation class to appear in the dependent entity class asinherited attribute classes.

In an nonspecific relation class, neither entity class isdependent on the other; i.e., entities in either entity classcan exist without being associated with any in the other. Forconvenience, one entity class is arbitrarily calledwindependento and the other is called "dependent".

Segment Data Field

A data field is an INS segment.

Subsohema

The description, in the DDL of a CODASYL DBNS, of all orpart of a database. For IISS, only one subschema is needed fora CODASYL database, and it must describe all the common datawithin the database that is to be accessible with NDIKL.

Tag Name

A unique name for an attribute use class within an entityclass.

Unit of Measure

A standard scale for determining the magnitude ofsomething. Examples include inch, foot, foot-inch, meter,ounce, pound, hour, minute, second, etc.

User View

A group of data items that a user wants to deal with as agroup. It is similar to an entity class but does notnecessarily meet all the conditions for being one, it can bethought of as an unnormalized entity class. A user view isoften the result of combining several entity classes viarelational join operations and selecting particular attributeuse classes as data items via relational project operations.

B-8

If 6201411001 November 1985

APPENDIX C

REFERENCES

Rel&ted ICAN Documents Included:

U0I82014100 CDIf Administrtor's Ma ual

T3N520141000 CDII, An IDEFI Model of the Common Dat& Model

PR10141200 Embedded NDIL Programmer's Reference Manual

011820141002 ICAM Definition Method for Data Modeling (IDEFI- Extended)

D8620141200 Development Specification for the IISS NDKLPrecompiler Confifur&tion Item

D620141320 Development Specification for the II5Agfrelfator Configuration Item

DS620141310 Development Specification for the IISSDistributed Request Supervisor ConfigurationItem

C-1

aU.S.Government Pyinting Office: 1987- 748-061/60875