WRDC-TR-90-8007 Volume V Part 14 AD-A250 454 INTEGRATED INFORMATION SUPPORT SYSTEM (IISS) Volume V - Common Data Model Subsystem Part 14 - Neutral Data Manipulation Language (NDML) Precompiler Transform NDML Request from External Schema to Conceptual Schema Product Specification IDTICW9 M. Apicella, J. Slaton, B. Levi F O TE.- Control Data Corporation M 0 1992 Integration Technology Services 2970 Presidential Drive Fairborn, OH 45324-6209 September 1990 Final Report for Period 1 April 1987 - 31 December 1990 * Approved for Public Release; Distribution is Unlimited MANUFACTURING TECHNOLOGY DIRECTORATE WRIGHT RESEARCH AND DEVELOPMENT CENTER AIR FORCE SYSTEMS COMMAND WRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433-6533 92-12197
222
Embed
INTEGRATED INFORMATION SUPPORT SYSTEM (IISS) Neutral … · INTEGRATED INFORMATION SUPPORT SYSTEM (IISS) Volume V -Common Data Model Subsystem Part 14 -Neutral Data Manipulation Language
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
WRDC-TR-90-8007Volume VPart 14
AD-A250 454
INTEGRATED INFORMATION SUPPORT SYSTEM (IISS)Volume V - Common Data Model SubsystemPart 14 - Neutral Data Manipulation Language (NDML) PrecompilerTransform NDML Request from External Schema to Conceptual SchemaProduct Specification
IDTICW9M. Apicella, J. Slaton, B. Levi F O TE.-Control Data Corporation M 0 1992Integration Technology Services2970 Presidential DriveFairborn, OH 45324-6209
September 1990
Final Report for Period 1 April 1987 - 31 December 1990
* Approved for Public Release; Distribution is Unlimited
MANUFACTURING TECHNOLOGY DIRECTORATEWRIGHT RESEARCH AND DEVELOPMENT CENTERAIR FORCE SYSTEMS COMMANDWRIGHT-PATTERSON AIR FORCE BASE, OHIO 45433-6533
92-12197
NOTICEA
When Government drawings, specifications, or other data are used for any purpose otherthan in connection with a definitely related Government procurement operation, the UnitedStates Government thereby incurs no responsibility nor any obligation whatsoever, regardlesswhether or not the government may have formulated, furnished, or in any way supplied thesaid drawings, specifications, or other data. It should not, therefore, be construed or impliedby any person, persons, or organization that the Government is licensing or conveying anyrights or permission to manufacture, use, or market any patented invention that may in any waybe related thereto.
This technical report has been reviewed and is approved for publication.
This report is releasable to the National TechnicalInformation Service (NTIS). At NTIS, it viii be
available to the general public, including foreign nations
DA D L. J S N, Pr"Ject Manager DATE
Wri t-Pat rs AFB, OH 45433-6533
FOR THE COMMANDER:
8RUCE A. RASMUSSEN, Chief DATE y"WRDC/MTWright-Patterson AFB, OH 45433-6533
If your address has changed, if you wish to be removed form our mailing list, or if theaddressee is no longer employed by your organization please notify WRDC/MTI, Wright-Patterson Air Force Base, OH 45433-6533 to help us maintain a current mailing list.
Copies of this report should not be returned unless return is required by securityconsiderations, contractual obligations, or notice on a specific document.
WRDC-TR-90-8007Volume VPart 14
INTEGRATED INFORMATION SUPPORT SYSTEM (IISS)Vol ime V - Common Data Model SubsystemPart 14 - Neutral Data Manipulation Language (NDML) PrecompilerTransform NDML Request from External Schema to Conceptual SchemaProduct Specification
M. Apicella, J. Slaton, B. Levi
Control Data Corporationintegration Technoloay Services2970 Pres-'ential veFairbcrr., OH 4532-1 5209
September 1990
Final Report for Period 1 April 1987 - 31 December 1990
Approved for Public Release; Distribution is Unlimited
_"F:A:T'z.'. TECHNOLOGY DIRECTORATEVPHRESEARCH AND DEVELCPIMEIT CEN- R
A:R"- FORCE SYSTEMS CC"MA,>-,B. I 436.... :H-PA::ERS: AIR FRCEn BASE, OHIO 45433-6533
NOTICE
When Government drawings, specifications, or other data are used for any purpose otherthan in connection with a definitely related Government procurement operation, the UnitedStates Government thereby incurs no responsibility nor any obligation whatsoever, regardlesswhether or not the government may have formulated, furnished, or in any way supplied thesaid drawings, specifications, or other data. It should not, therefore, be construed or impliedby any person, persons, or organization that the Government is licensing or conveying anyrights or permission to manufacture, use, or market any patented invention that may in any waybe related thereto.
This technical report has been reviewed and is approved for publication.
This report is releasable to the National TechnicalInformation Service (NTIS). At NTIS, it will be
available to the general public, including foreign nations
DAN D L. J SON, Pr ject Manager DATE
Wri hta rsJAFB, OH 45433-6533
FOR THE COMMANDER:
bRUCE A. RASIUSSEN, Chief DATE u
WRDC/MTIWright-Patterson AFB, OH 45433-653;
If your address has changed, if you !, .h to be removed form our mailing list, or if theaddressee is no longer employed by yo,:: - -,anization please notify WRDC/MTI, Wright-Patterson Air Force Base, OH 45433-0,Y to help us maintain a current mailing list.
Copies of this report should not be -.c:urned unless return is required by securityconsiderations, contractual obligations. or ..(,tice on a specific document.
6a. NAME OF PERFORMING ORGANIZATION 6b. OFFICE SYMBOL 7a. NAME OF MONITORING ORGANIZATIONControl Data Corporation; (if applicable) WRDC/MTIIntegration Technology Services
&c. ADDRESS (City, State, and ZIP Code) 7b. ADDRESS (City, State, and ZIP Code)2970 Presidential DriveFairbom, OH 45324-6209 WPAFB, OH 45433-6533
8a. NAME OF FUNDING/SPONSORING Bb. OFFICE SYMBOL 9. PROCUREMENT INSTRUMENT IDENTIFICATION NUM.ORGANIZATION (if applicable)
Wright Research and Development Center, F33600-87-C-0464Air Force Systems Command, USAF WRDC/MTI
10. SOURCE OF FUNDING NOS.8c. ADDRESS (City, State, and ZIP Code)
Wright-Patterson AFB, Ohio 45433-6533 PROGRAM PROJECT TASK WORK UNITELEFMENT NO. NO. I NO. I NO.
11. TITLE linclude S.curitv Cla..qificr tinnE
See block 19 78011F 595600 F95600 20950607
li. t't":)MUNAL AU I HUHI(Z)
Control Data Corporation: Apicella, M. L., Slaton, J., Levi, B.
13a. TYPE OF REPORT 113b. TIME COVERED 114. DATE OF REPORT (Yr.,Mo.,Day) 15. PAGE COUNTFinal Report 4/l/87-12/31/90 1990 September 30 221
16. SUPPLEMENTARY NO IAI IU N
WRDC/MTI Project Priority 6203
17. COSATI CODES 18. SUBJECT TERMS (Continue on reverse if necessary and identify block no.)
FIELD GROUP SUB GR.
1308 10905
19. ABSTRACT (Continue on reverse if necessary and identify block number)
This specification establishes the design of Function PRE4, "Transform ES/CS", one of the major functions of the ConfigurationItem "Precompiler" to be built and formally accepted by the ICAM program office.
BLOCK 11 :
INTEGRATED INFORMATION SUPPORT SYSTEM
Vol V - Common Data Model Subsystem
Part 14 - Neutral Data Manipulation Language (NDML)Precompiler Transform
NDML Request from External Schema to Conceptual Schema Product
Specification
20. DISTRIBUTION'AVAILABILITY OF ABSTRACT 21. ABSTRACT SECURITY CL.,SSIFICATION
UNCLASSIFIED,'UNLIMITED x SAME AS RPT. DTIC USERS Unclassified
22a. NAME OF RESPONSIBLE INDIVIDUAL 22b. TELEPHONE NO 22c. OFFICE SYMBOLI (Include Area Code)
David L. Judson (513) 255-7371 WRDC'MTI
EDITION OF 1 JAN 73 IS OBSOLETEDD FORM 1473,83 APR Unclassified
SECURITY CLASSIFICATION OF TH!S PAGE
PS 62034123130 September 1990
FOREWORD
This technical report covers work performed under Air ForceContract F33600-87-C-0464, DAPro Project. This contract issponsored by the Manufacturing Technology Directorate, Air ForceSystems Command, Wright-Patterson Air Force Base, Ohio. It wasadministered under the technical direction of Mr. Bruce A.Rasmussen, Branch Chief, integration Technology Division,Manufacturing Technology Directorate, through Mr. David L. Judson,Project Manager. The Prime Contractor was Integration TechnologyServices, Software Programs Division, of the Control DataCorporation, Dayton, Ohio, under the direction of Mr. W. A.Osborne. The DAPro Project Manager for Control Data Corporationwas Mr. Jimmy P. Maxwell.
The DAPro project was created to continue the development, test,and demonstration of the Integrated Information Support System(IISS) . The IISS technology work comprises enhancements to IISSsoftware and the establishment and operation of IISS test bedhardware and communications for developers and users.
The following list names the Control Data Corporationsubcontractors and their contributing activities:
SUBCONTRACTOR ROLE
Control Data Corporation Responsible for the overall CommonData Model design development andimplementation, IISS integration andtest, and technology transfer of IISS.
D. Appleton Company Responsible for providing softwareinformation services for the CommonData Model and IDEFlX integrationmethodology.
ONTEK Responsible for defining and testing arepresentative integrated system basein Artificial Intelligence techniquesto establish fitness for use.
Simpact Corporation Responsible for Communicationdevelopment.
Structural Dynamics Responsible for User Interfaces,Research Corporation Virtual Terminal Interface,and Network
4.1 Introduction and Definitions ......... 4-14.2 Computer Programming Test and
Evaluation ......................... 4-1
iv
PS 62034123130 September 1990
* SECTION 1
SCOPE
1.1 Identification
This specifidatkon establishes the design of Function PRE4,##Transform ES/CS", ghe of the major functions of theConfiguration Item "Precompiler" to be built and formallyaccepted by the ICAM program Office. This CI constitutes one ofthe subsystems of the Common Data Model Processor (CDMP).
1.2 4Iunctional summaryvThe purpose of this Computer Program Configuration Item
(CPCI) is to convert an NDML or SQL request, expressed in an externalschema, and to terminate one or more NDML or SQL requests expressed inconceptual schema terms.
The following functions will be performed by this CPCI:
i) Translate each user view into the corresponding entityclasses and each data item into the correspondingattribute use classj
2) Identify the relational join operations needed toconstruct each user view table, ,
3) Identify the integrity tests that will be employed witheach NDML or SQL update request.
2. D. Appleton Co., CDM Administrators Manual;UM620141000, March, 1984.
3. D. Appleton Co., CDMI-IDEF, Model of the Common DataModel; CCS620141000, 15 May, 1985.
4. D. Appleton Co., Computer Program DevelopmentSpecification (DS) for ICAM Integrated Support System(IISS) Configuration Item: NDML Precompiler;DS620141200, October, 1984.
7. Control Data Corp., Computer Program DevelopmentSpecification (DS) for ICAM Integrated Support System(IISS) Configuration item: NDDL Command Processor:DS620141100, June 1985.
2.2 Terms and Abbreviations
Attribute Use Class: (AUC)
Conceptual Schema: (CS)
Common Data Model Processor: (CDMP)
Common Data Model: (CDM) Describes common data applicationprocess formats, form definitions, etc, of the IISS and includesconceptual schema, external, internal schemas, and schematransformation operators.
Data Field: (DF) An element of data in the externalschema. It is by this name that an NDML programmer referencedata.
Database Management System: (DBMS)
Distributed Request Supervisor: (DRS) This IISS CDMsubsystem configuration item controls the execution ofdistributed NDML queries and non distributed updates.
Domain: A logical definition of legal attribute classvalues.
2-1
PS 62034123130 September 1990
Domain Constraint: Predicate that applies to a single
domain.
External Schema: (ES)
Forms: Structured views which may be imposed on windows orother forms. A form is composed of fields where each field is aform, item, or window.
Forms Processor: (FP) A set of callable execution timeroutines available to an application program for formprocessing.
Internal Schema: (IS)
Integrated Information Support System: (IISS) A testcomputing environment used to investigate, demonstrate and testthe concepts of information management and informationintegration in the context of Aerospace Manufacturing. The IISSaddresses the problems of integration of data resident onheterogeneous databases supported by heterogeneous computersinterconnected via a local Area Network.
Mapping: The correspondence of independent objects in twoschemas: ES to CS or CS to IS.
Network Transaction Manager: (NTM) Performs thecoordination, communication and housekeeping functions requiredto integrate the application processes and system servicesresident on the various hosts into a cohesive system.
Neutral Data Manipulation Languaqe: (NDML) A languagedeveloped by the IISS project to provide uniform access tocommc- data, regardless of database manager or distributioncriteria. It provides distributed retrieved and single nodeupdates.
ORACLE: Relational DBMS based on the SQL (Structured QueryLanguage, a product of ORACLE Corp, Menlo Park, CA). The CDM isan ORACLE database.
Parcel: A sequential file containing sections source codeof the input application program.
Request Processor: (RP) A COBOL program that will satisfya retrieval or update NDML subtransaction against a particularDatabase Management System.
User Interface: (UI) Controls the user's terminal andinterfaces with the rest of the system.
Virtual Terminal Interface: (VTI) Performs the interfacingbetween different terminals and the UI. This is done bydefining a specific set of terminal features and protocols whichmust be supported by UI software which constitutes the VirtualTerminal Definition. Specific terminals are then mapped againstthe Virtual Terminal software by specific software moduleswritten for each type of real terminal supported.
2-2
PS 62034123130 September 1990
SECTION 3
REQUIREMENTS
3.1 Structural Description
A graphic portrayal of this CPCI is included in Section3.10. This chart shows the hierarchical relationship of eachmodule making up this CPCI.
This CPCI uses a number of lower level modules to handle
specific operations such as:
1. Verifying the user view (CDVIEW).
2. Verifying user data items (CDEMD).
3. Determining all data items in a view (CDEMDA).
4. Match view names with view abbreviations (CDABVW).
5. Determine if a partial entity class was inserted(CDPTEC).
6. Determine if a data item is mapped to conceptual schema(CDPDI).
7. Look up meta data for a conceptual attribute (CDCMD).
8. Determine if a view maps to multiple entities (CDNNEC).
9. Develop type 1 integrity test (CDINEC, CDIRIT).
10. Develop key uniqueness integrity test (CDKYUQ).
11. Check for modification of a partial inherited key class(CDMPIK).
12. Develop type 2 integrity test (CD2RIT).
13. Add rows to the CSACTIONLIST (CDACAL).
14. Add a row to the CS ACTION LIST and CSQUALITYLIST fora type I integrity test (CDACAQ).
15. Add a row to the TEMPXFORMLIST (CDATXL).
16. Retrieve a tag name (CDGTN).
17. Retrieve type 2 qualifications for a view (CDG7VW).
18. Verify join to target user view for delete and modify (CDJUV).
19. Build ES/CS Action List entries (CDMQAL).
20. Populate Boolean List (CDPBL).
3-1
PS 62034123130 September 1990
21. Transform ES schema to CS (CDPRE4).
22. Obtain relation class number for outer join (CDRCNR).
23. Get the relation class and owner tag of an inheritedattribute (CDRCTG).
24. Retrieve all tags to which a view maps (CDTGVW).
25. Update a row of the TEMPXFORMLIST (CDUTXL).
26. Verify a numeric value (CDVNV).
27. Verify that a TEMPAUC is not a key class member (CDVT'K).
3.2 Functional Flow
This CPCI implements the logic defined in the DevelopmentSpecification for this CPCI. Details of inputs/outputs andrelationships between modules are to be found in Section 3.10.
This CPCI has been designated to operate in a batch orinteractive mode. It must use the ORACLE DBMS installed on a DEC VAXcomputer.
3.3 Interfaces
The following diagram depicts the interface of PRE4 withother CPCI's in the system.
----------------------------- PRE2 I
I PS41212
+ .... ---- +- ----.- -.... -
PRE3 PRE4PS41213 I
------------------
±PRE 5PS41232
3.3.1 Inputs/Outputs
The following table depicts the inputs and outputs of thisCPIC. A detail description for each item can be found in the DSfor this CPCI.
3-2
PS 62034123130 September 1990
INPUT OUTPUT
ES Qualify List Return StatusES Action ListCS Qualify ListUser View Abbreviation ListCS Action ListParcel 1 File PointerParcel 2 File PointerParcel 3 File PointerParcel 4 File PointerError File PointerHor. of the precompilerHoE the AP is to run onSou. e LanguageCode generator tableUser Module IdentificationLog., Al Unit of Work NameNDML CounterBoolean ListResult Field TableJQG Attribute Pair ListBlock StackNDML StackFirst Inner SelectFortran Variable TableSubroutine LanguageEmbedded LanguageCursor TableWhenever Table
3.4 Program Interrupts
Not applicable to this CPCI.
3.5 Timing and Sequencing Description
This CPCI is called for each NDML or SQL statement parsed by PRE3and identified to be semantically correct by PRE2. Thus, PRE4may execute many times in a precompiler run. PRE 4 in turncalls PRE5 for each conceptual request. A conceptual request iseither the original user NDML or SQL request or referential integritytests, which are implemented as a conceptual schema retrievals.
3.6 Special Control Features
Not applicable to this CPCI.
3.7 Storage Allocation
3.7.1 Database Definition
The database used by this CPCI is the Common Data Model(CDM) database. This model is defined by the CDM1, the IDEF-1model of the CDM, Reference Document Number 3.
3-3
PS 62034123130 September 1990
3.7.1.1 File Description
No permanent files have been defined for this CPCI. It mayuse temporary scratch files for such things as generated programsource code or temporary query results.
3.7.1.2 Table Description
All tables used by this CPCI have been defined by theDevelopment Specification for this CPCI.
3.7.1.3 Item Description
Not applicable to this CPCI.
3.8 Object Code Creation
The object code for this CPCI will be created by the systemintegration test team by using defined IISS SoftwareConfiguration Management procedures. This CPCI will use theCOBOL language compilers.
3.9 Adaptation Data
This CPCI has been coded using ANSI COBOL language. Theintent was to provide a transportable system. Any systemenvironment supporting this language, a virtual memorymanagement scheme, the ORACLE Database Management System shouldbe able to support this CPCI. Every possible attempt has madebeen to localize and identify any machine or environment dependentmodules through the original design of the IISS and application ofConfiguration Management Procedures.
3-4
PS 62034123130 September 1990
3.10 Details Design Description
The following sections have been computer generated forthis CPCI.
3.10.1 Where Include File Used List
The following lists each include file in thedocumentation group and all the modules documented in thisspecification which include them. The purpose of eachmodule is listed as well.
The following lists eazh external function or routinein the documentation group and all the documented moduleswhich call it. The purpose of each module is listed aswell.
The following lists each Main Program in thedocumentation group and all the modules which are calledeither by that module itself or by any of the documentedmodules which it calls. It is possible for a non-mainmodule to be listed more that once if it is called bymultiple modules. The called modules, in this case known asprogram parts, are marked as to whether they are documentedhere. If so, the phrase "well-defined module" appears bythe module name, if not it is an "external "routine". ThePurpose of the Main Program module is listed as well.
The following documentation describes informationwhich is specific to each individual module in thedocumentation group being documented in this specitication.It provides a compact way of getting information that wouldbe otherwise buried within each module's source code.
The specific items in this module documentation have the
following meanings:
NAME: Name of program Module.
PURPOSE: Purpose of Module as detailed in thesource code.
LANGUAGE: Programming language source code iswritten in.The choices are:
VAX-11 FORTRANC (I/S-I Workbench 'C')VAX-11 COBOL
MODULE TYPE: Whether a Program, Subroutine, orFunction.
SOURCE FILE: Name of Source File from filespecification.
SOURCE FILE TYPE: Source File Extension from filespecification.
HOST: Whether this is a host-dependentroutine (VAX or IBM) or blank ifhost-independent.
SUBSYSTEM: IISS sub-system this file resides in.
SUBDIRECTORY: Sub-directory of that subsystem inwhich this file resides.
DOCUMENTATION GROUP: Name of documentation group of whichthis source file is a member.
DESCRIPTION: A description of the module as otainedfrom the source code.
ARGUMENTS: The arguments with which this routineis called if it is a Subroutine or aFunction.
INCLUDE FILES: A list of all the files that areincluded into this module as well astheir purposes.
ROUTINES CALLED: Subroutines or Functions, eitherdocumented or external, called bythis module, if any.
3-38
PS 62034123130 September 1990
CALLED DIRECTLY BY: The documented routines which callthis module, if any.
USED IN MAIN PROGRAM(S): The documented Main Programs whichcontain this module in their partslist according to the list in section3.10.3.
The Module Documentation is arranged alphabetically accordingto Module iiame.
3-39
PS 62034123130 September 1990
DOCGROUP PS41231 Module Documentation
NAME: CDlRITPURPOSE: PERFORMS SEARCH OF LINKRELATION TO EXTRACT IND ECNO
FOR TYPE 1 R.LANGUAGE: VAX-Il COBOLSOURCE FILE: CDlRITSOURCE FILE TYPE: PCOHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
PERFORM SQL SEARCH OF LINK RELATION TABLE TO EXTRACT THEINDEPENDENT EC NO WHICH CORRESPONDS TO EACH TEMP-RC-NO. CALLCDACAQ TO FILL ROWS OF CS-ACTION-LIST AND CS-QUALIFY-LISTAND GENERATE A TYPE 1 REFERENTIAL INTEGRITY TEST.MODIFIED FOR EMBEDDED SQL -- 19 MAY 1986ADD LUW-NAME AS PASS-THROUGH PARAMETER -- 23 MAY 1986CHANGED TO DO LOOKUPS INTO LINK RELATION -- 1 MAY 1989FOR EACH NON-ZERO RELATION CLASS, OBTAIN ALL INDEPENDENTENTITY CLASS NUMBERS. FOR EACH UNIQUE INDEPENDENTENTITY CLASS NUMBER, CALL CDACAQ TO EVENTUALLYGENERATE A TYPE 1 REFERENTIAL INTEGRITY TEST.
NAME: CD2RITPURPOSE: SETS UP TYPE 2 REFERENTIAL INTEGRITY CHECKLANGUAGE: VAX-Il COBOLSOURCE FILE: CD2RITSOURCE FILE TYPE: PCOHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
FILL IN CS ACTION LIST AND CS-QUALIFY LIST FOR TYPE 2 RITEST. ON EXIT, RESET CSQ-USED TO ITS VALUE ON INPUT.MODIFY FOR EMBEDDED SQL -- 23 MAY 1986CHANGE NDML-COUNTER AND NDML-HOLD TO PIC 9(6) -- 23 MAY 1986CHANGE VH-COUNTER TO PIC X(6) -- 23 MAY 1986DELETE CE-WORK-LIST AND USER-ERROR-COUNT -- 23 MAY 1986ADD BOOLEAN-LIST AND LUW-NAME -- 23 MAY 1986ADD CDMQAL AND CDPBL CALLS -- 23 MAY 1986CHANGE CDPRE6 CALLS TO CDPRE5 CALLS -- 23 MAY 1986MOVE U TO CSQ-SOURCE (CS-QUALIFY) -- 4 MAR 1987CHECK FOR "V" IN CSQ-SOURCE (CS-QUALIFY) BEFOREMOVING COUNTER TO CSQ-VARIABLE -- 23 JUN 1987FOR EACH INDEPENDENT ENTITY OF THE ENTITY TO BEDELETED, GENERATE A TYPE 2 REFERENTIAL INTEGRITYTEST BY POPULATING THE CS-ACTION LIST AND ADDING TOTHE CS-QUALIFY AND BOOLEAN LISTS.
SCAN THE UV-ABBR-LIST SEARCHING FOR A UVABBRMATCHING THE INPUT ARGUMENT, ABBREV. IF FOUND, RETURNTHE CORRESPONDING VIEW NUMBER AND UV-INDEX, OTHERWISE ZERO.
SCAN THE UV-ABBR-LIST FOR A UV-ABBR MATCHING ABBREV.RETURN CORRESPONDING UV-NO AND INDEX.
NAME: CDACALPURPOSE: ADD ROWS TO THE CS-ACTION-LISTLANGUAGE: VAX-I COBOLSOURCE FILE: CDACALSOURCE FILE TYPE: COBHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
FILL THE CS ACTION LIST FROM THE TEMP TRANSFORM LISTINITIALIZE CS-DELETE-FLAG -- 16 MAY 1986INITIALIZE CS-SOURCE -- 16 MAY 1986DETERMINE IF ENTITY IS GENERIC AND SET NEW FLAGCS-CATEGORY-FLAG IF AUC IS THE CATEGORY DISCRIMINATOR -10 APR1989MOVE ROWS, 1 AT A TIME, FROM THE TEMP TRANSFORM LISTTO THE CS-ACTION-LIST. IF CSAL OVERFLOW, GENERATEAN ERROR MESSAGE. CHECK EC-NO TO DETERMINE IF GENERICIF SO, RETRIEVE AUC OF CATEGORY DISCRIMINATOR.
FOR THE FIRST TEMP-RC-NO ENTRY WHICH MATCHES THE INPUTARGUMENT, FILL IN A CS-ACTION ENTRY AND A CS QUALIFY ENTRY.FOR EACH ADDITIONAL MATCH, FILL IN A CS QUALIFY ENTRY.ELIMINATE CSQ DUPLICATES AND CALL CDPRE6 TO GENERATE ATYPE 1 REFERENTIAL INTEGRITY TEST.ADD BOOLEAN-LIST -- 21 MAY 1986DELETE USER-ERROR-COUNT -- 21 MAY 1986CHANGE NDML-COUNTER TO PIC9(6) -- 21 MAY 1986DELETE LDA REFERENCES -- 21 MAY 1986ADD CDMQAL AND CDPBL CALLS -- 21 MAY 1986POPULATE 2 NEW CS-ACTION FIELDS(CS-SOURCE AND CS-DELETE-FLAG) -- 21 MAY 1986MODIFY CSQ DUPLICATE ELIMINATION LOGIC - 21 MAY 1986ADD LUW-NAME AS PASS-THROUGH PARAMETER -- 23 MAY 1986CHANGE CDPRE6 CALL TO CDPRE5 CALL -- 23 MAY 1986MOVE U TO CSQ-SOURCE (CS-QUALIFY) -- 5 MAR 1987CHECK FOR "V" IN CSQ-SOURCE BEFORE MOVINGCOUNTER TO CSQ-VARIABLE -- 23 JUN 87DELETED IOS-SECTION PARAMETER -- 2 MAY 1989POPULATE THE FIRST CS ACTION ROW, AND AS MANYCS QUALIFY ROWS AS THERE ARE TEMP-RC-NO'S
3-49
PS 62034123130 September 1990
MATCHING THE INPUT PARAMETER RC-NO. AFTERALL ACTION AND QUALIFY TABLE ENTRIES HAVE BEENPOPULATED, MOVE ALL AUC ENTRIES IN THE QUALIFYLIST WHICH AREN'T ALREADY ON THE ACTION LIST TOTHE ACTION LIST. ALSO POPULATE THE BOOLEAN LIST.FINALLY, CALL CDPRE5 TO GENERATE THE TYPE 1REFERENTIAL INTEGRITY TEST.
FILL IN NEXT TEMP-XFORM LIST ENTRY WITH CORRESPONDING INPUTPARAMETERS. ADJUST ROW-USED INDICATOR TO POINT TO LAST USEDROW GUARDING AGAINST TABLE OVERFLOW.CHANGE NDML-COUNTER TO 9(6) -- 19 MAY 1986POPULATE NEXT ROW OF TEMP TRANSFORM LIST
NAME: CDEMDPURPOSE: RETRIEVE EXTERNAL METADATA AND DATA ITEM NUMBERLANGUAGE: VAX-Il COBOLSOURCE FILE: CDEMDSOURCE FILE TYPE: PCOHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
PERFORM SQL SELECT TO RETURN EXTERNAL METADATA (TYPE, SIZE,NUMBER OF DECIMALS), AND THE DATA ITEM NUMBER GIVEN THEVIEW NUMBER AND THE DATA ITEM NAME.MODIFIED FOR EMBEDDED SQL -- 5/9/86MODIFIED TO ACCEPT SOURCE-LANGUAGE PARAMETER AND CHECKFOR F, C OR I DATA TYPE IF SOURCE LANGUAGE IS FORTRAN -- 3/5/87SELECT DATA ITEM NUMBER, DATA TYPE, SIZE ANDNUMBER OF DECIMAL DIGITS FOR A PARTICULARDATA ITEM NAME WITHIN THE GIVEN VIEW. IF NOTFOUND, GENERATE AN ERROR MESSAGE.
EXTRACT DI NAMES FOR ALL DATA ITEMS IN A USER VIEW.FOR EACH DI NAME EXTRACTED, MAKE AN ENTRY IN THEES ACTION LIST. FOR THE FIRST DI NAME EXTRACTED, EXPAND THELASTUSED ROW OF THE ES ACTION LIST. FOR EACH ADDITIONAL DI NAME,FILLIN A NEW ROW.MODIFIED FOR EMBEDDED SQL 5/5/86ADDED NEW PARAMETER NDMLSTK TO SOLVE ES-ACTION-LIST BUCWHEN DOING SELECT ALL WITH CURLY BRACKET 07/31/90EXTRACT ALL DATA ITEMS FOR THE GIVEN VIEW ANDINSERT THEM INTO THE ES-ACTION-LIST.
- THIS ROUTINE WILL SELECT TYPE 2'SQUALIFICATIONS FOR A SPECIFIED VIEW FROMVIEW QUALIFIY CRITERIA (CONDITION, TEXT TYPEAND TEXT). IT-POPULATES THE CS-QUALIFY ANDBOOLEAN LISTS. THIS ROUTINE IS CALLED FROMCDPRE4 FOR SELECT, MODIFY, DELETE AND QUERY-COMBINATION NDML ACTIONS.
PERFORM SQL SEARCH OF LINKRELATION TABLE TO FIND ANY IN-DEPENDENT ENTITY CLASSES. FOR EACH FOUND, CALL CDACAQ TO SETUP TYPE 1 REFERENTIAL INTEGRITY TEST.CONVERTED TO EMBEDDED SQL -- 14 MAY 1986NDML-COUNTER MADE PIC 9(6)-- 14 MAY 1986USER-ERROR-COUNT DELETED -- 14 MAY 1986ADD LUW-NAME AS PASS THROUGH PARAMETER -- 22 MAY 1986CONVERT TO CHECK OF LINK RELATION TABLE --- 10 APR 1989PERFORM SQL SEARCH OF LINK RELATION TABLE FOR ALLINDEPENDENT ENTITIES OF TEMP-EC-NO (1). FOR EACHINDEPENDENT ENTITY FOUND, CALL CDACAQ TO GENERATEA TYPE 1 REFERENTIAL INTEGRITY TEST.
NAME: CDJUVPURPOSE: VERIFY JOIN TO TARGET USER VIEW FOR DELETE AND MODIFYLANGUAGE: VAX-lI COBOLSOURCE FILE: CDJUVSOURCE FILE TYPE: COBHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
CDJUV ENSURES, THAT FOR A DELETE OR MODIFY WITH A USINGCLAUSE, THAT AT LEAST ONE OF THE "USING" VIEWS JOINSBACK TO THE TARGET TABLE.SEARCH BOTH RIGHT AND LEFT SIDES OF THE ESQ TRYINGTO MATCH ESQ-UV-ABBRR AND ABBRL WITH UV-ABBRR(1).IF A MATCH IF FOUND, CHECK IF THE OPPOSITE SIDECONTAINS A VIEW REFERENCE NOT EQUAL TO THE TARGETVIEW. IF NO JOINS TO THE TARGET VIEW ARE FOUND,GENERATE AN ERROR MESSAGE.
ARGUMENTS:
UV-ABBR-LISTES-QUALIFY-LISTFCB-EERROR-STATUS
INCLUDE FILES:
3-67
PS 62034123130 September 1990
UVABBRESQUAL
ROUTINES CALLED:
RPTERR
3-68
PS 62034123130 September 1990
DOCGROUP PS41231 Module Documentation
NAME: CDKYUQPURPOSE: SET UP KEY UNIQUENESS TEST FOR AN ENTITYLANGUAGE: VAX-lI COBOLSOURCE FILE: CDKYUQSOURCE FILE TYPE: PCOHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
FILL IN NEXT ROW OF CS-ACTION-LIST FOR EVERY UNIQUE KC-NORETURNED. FILL IN NEXT ROW OF CS-QUALIFY-LIST FOR EVERYROW RETURNED. ELIMINATE ALL DUPLICATE CS-QUALIFY ENTRIES.FOR EACH UNIQUE KC-NO, GENERATE KEY UNIQUENESS TEST.CONVERT TO EMBEDDED SQL -- 15 MAY 1986ADD CDMQAL CALL -- 15 MAY 1986ADD CDPBL CALL -- 15 MAY 1986ENHANCE CSQ DUPLICATE ELIMINATION LOGIC -- 15 MAY 1986ADD LUW-NAME AS CDPRE5 PASS-THROUGH PARAMETER -- 22 MAY 1986CHANGE ALL CDPRE6 CALLS TO CDPRE5 -- 23 MAY 1986MOVE SPACES TO NEW FIELD IN CS-QUALIFY -- 3 MAR 1987CHECK FOR "V" IN CSQ-SOURCE BEFORE INSERTING COUNTERIN CSQ-VARIABLE FIELDSET UP A KEY UNIQUENESS TEST FOR EACH UNIQUE KEYKEY CLASS BY POPULATING BOTH THE CS ACTION ANDQUALIFY LISTS. POPULATE A COMPLETELY NEW BOOLEANLIST (CDPBL) AND MOVE ANY CS-QUALIFY ENTRIESNOT IN THE CS-ACTION-LIST TO THE CS-ACTION-LIST(CDMQAL) PRIOR TO THE CDPRE5 CALL.
NAME: CDMPIKPURPOSE: CHECK FOR MODIFICATION OF PARTIAL INHERITED KEYLANGUAGE: VAX-lI COBOLSOURCE FILE: CDMPIKSOURCE FILE TYPE: PCOHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
FOR EACH UNIQUE RC-NO IN THE TEMP XFORM LIST, SELECT THETAG-NOS FROM INHERTIED ATT USE WHERE THE RC NOS ARE EQUAL.FOR EACH TAG-NO SELECTED, SEARCH THE TEMP XFORM LIST FORA MATCH. IF FOUND, OK; OTHERWISE GENERATE ERROR MESSAGE.CONVERTED TO EMBEDDED SQL -- 20 MAY 1986IMPROVED ERROR HANDLING -- 20 MAY 1986FOR EACH INHERITED TAG TO BE MODIFIED, CDMPIK MUSTINSURE THAT ALL OF THE OTHER INHERITED TAGS FROM THESAME KEY CLASS ARE ALSO TO BE MODIFIED. IF NOT,THE ERROR MESSAGE MUST IDENTIFY THE MISSINGINHERITED ATTRIBUTES.
- THIS ROUTINE PLACES ES-QUALIFY AND/ORCS-QUALIFY ENTRIES WHICH ARE NOT REPRESENTED IN THEES-ACTION-LIST AND CS-ACTION-LIST RESPECTIVELY ONTHOSE LISTS IN SUPPORT OF CONCEPTUAL EVALUATIONOF THOSE QUALIFY ENTRIES NOT INTERNALLY EVALUATABLE.
CHECK VIEW EC XREF TO SEE IF VIEW IS MAPPED TO MORETHAN ONE ENTITYROUTINE CHANGED FROM COB TO PCO FOR CREATE VIEWENHANCEMENTS - REL 2.3CHECK VIEW-EC-XREF FOR MORE THAN ONE EC-NO.IF MORE THAN ONE EXISTS, GENERATEAN ERROR MESSAGE APPROPRIATE TO THE ES-ACTION.
- THIS ROUTINE, FOR TYPE 1 REFERENTIALINTEGRITY AND KEY UNIQUENESS TESTS, BUILDS A COMPLETEBOOLEAN LIST. FOR SELECTS, MODIFYS, DELETES AND TYPE2 REFERENTIAL INTEGRITY TESTS, THIS ROUTINE POPULATESBL-ESQ-PTR'S AND BL-CS-PTR'S.
MODIFIED TO ADD TO BOOLEAN LIST FOR TYPE 2'S WHICH WERERETRIEVED FROM VIEW QUALIFY CRITERIAJUN 1989 - MODIFIED TO ADD CSAL CODES FOR CATEGORY DELETE
NAME: CDPDIPURPOSE: VERIFY THE EXISTENCE OF A MAPPED DATA ITEMLANGUAGE: VAX-lI COBOLSOURCE FILE: CDPDISOURCE FILE TYPE: PCOHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
PERFORM SQL SEARCH FOR THE TAG NUMBER OF THE PROJECT DATAITEM WHOSE VIEW NUMBER AND DATA ITEM NUMBER MATCH THE INPUTARGUMENTS AND WHOSE ID MATCHES THE CORRESPONDING DATA ITEMID. IF NOT FOUND, RETURN A TAG NUMBER OF ZERO.THE CALLING PROGRAM GENERATES THE ERROR MESSAGE.MODIFIED FOR EMBEDDED SQL -- 13 MAY 1986PERFORM SQL SELECT OF THE TAG NUMBER FROMPROJECT DATA ITEM GIVEN THE VIEW NUMBER ANDDATA ITEM NUMBER. RETURN A TAG NUMBER OFZERO IF NOT FOUND.
THE FUNCTION OF THIS EXTERNAL-SCHEMA-TO-CONCEPTUAL-SCHEMATRANSFORMER IS TO CONVERT AN NDML REQUEST EXPRESSED INEXTERNAL SCHEMA TERMS INTO ONE OR MORE NDML REQUESTSEXPRESSED IN CONCEPTUAL SCHEMA TERMS. THE CONVERSIONINVOLVES TRANSLATING EACH USER VIEW INTO THE CORRESPONDINGENTITY CLASSES AND EACH DATA ITEM INTO THE CORRESPONDINGATTRIBUTE USE CLASSES. IT ALSO INVOLVES IDENTIFYING THERELATIONAL JOIN OPERATIONS THAT ARE NEEDED TO CONSTRUCTEACH USER VIEW TABLE FROM THE ENTITY CLASS TABLES ANDIDENTIFYING THE INTEGRITY TESTS THAT WILL BE EMPLOYED WITHEACH NDML UPDATE REQUEST. THIS IMPLEMENTATION WILL NOTSUPPORT DERIVED DATA ITEMS.CONVERT TO EMBEDDED SQL -- 10 JUNE 1986DELETE SEC-DECOMPOSITION-LIST -- 10 JUNE 1986DELETE CE-WORK-LIST -- 10 JUNE 1986MAKE CS-ACTION-LIST AN OUTPUT PARAMETER -- 10 JUNE 1986ADD USER-MOD-ID, LUW-NAME AND BOOLEAN-LIST ASINPUT PARAMETERS -- 10 JUNE 1986MAKE NDML-COUNTER PIC 9(6) AND INPUT/OUTPUT PARAMETER --10 JUNE 1986DELETE USER-ERROR-COUNT REFERENCES -- 10 JUNE 1986ADD CHECK FOR MODIFYS AND DELETES WITH USING CLAUSES
3-82
PS 62034123130 September 1990
TO ENSURE THAT THE TARGET VIEW IS JOINED TO --ADD LOGIC TO MOVE CS QUALIFICATIONS TO THE CS ACTIONLIST IN SUPPORT OF COMPLEX MAPPING -- 10 JUNE 1986ADD LOGIC TO CREATE OR ADD TO THE BOOLEAN LIST --ADD LOGIC TO UPDATE THE CDM CROSS REFERENCE -- 10 JUNE 1986ADD CHECK TO INSURE THAT USED ES-VALUES ARE NUMERICWHEN THE DATA TYPE IS NUMERIC -- 10 JUNE 1986POPULATE CSQ-VARIABLE ONLY WHEN ESQ-UV-ABBRR IS BLANK-- 10 JUNE 1986CHECK THAT LEFT AND RIGHT SIDE QUALIFY TYPES ARECOMPATABLE -- 10 JUNE 1986CHANGE INITIALIZATION OF TEMP-XFORM-LIST, CS-QUALIFY-LIST,CS-ACTION-LIST AND TEMP-JOIN-LIST -- 27 FEB 87CHANGE CALL TO CDVIEW TO RETRIEVE DISTINCT IND. IF USERDID NOT SPECIFY 'DISTINCT' BUT ONE VIEW IS DISTINCTED,THEN ES-DISTINCT-FLAG IS SET TO 'YI - 25 FEB 87ADD CALL TO CDGTVW TO PICK UP TYPE 2 QUALIFICATIONSFROM VIEW QUALIFY CRITERIA AND ADD TO CS-QUALIFY ANDADD TO THE BOOLEAN LIST FOR DELETE, MODIFY, SELECTAND QUERY-COMBINATION ACTIONS -- 25 FEB 87CHANGED LOGIC IN DECOMPOSE-USER-VIEW (STEP 9) (SELECT ANDQUERY-COMBINATION ACTIONS) TO RETRIEVE THETYPE 3 QUALIFICATIONS FROM VIEW QUALIFYCRITERIAFOR A SPECIFIC VIEW AND BUILD THE TEMP-JOIN-LIST USINGTHE TAG NUMBERS RETRIEVED - 25 FEB 87CHANGE TO SET A NEW FIELD IN CS-QUALIFY (CSQ-SOURCE) TO'V' IF INFORMATION IS FROM VIEWQUALIFYCRITERIA, ELSESET TO 'U' -- 25 FEB 87CHANGE PARAMETERS TO CALL "CDNNEC" WHICH WAS CHANGEDFROM COB TO PCC -- 25 FEB 87CHANGE PARAMETERS TO CALL "CDEMD" -- 25 FEB 8715-jul-87 -- after all view "joins" have been retrieved, andpopulated, delete any csq entries which have the left aucequal the right auc. this could happen if views are madeup from the same entity(s) 10.52 MAY -1989 -- ADD PROCESSING TO SUPPORT IDEFIX AS FOLLOWS:INSERT - ADD CALL TO CD2NEC TO LOOK UP INTO CATEGORY RELATIONMODIFY - ADD CALL TO CDAUC TO DETERMINE IF CATEGORYDISCRIMINATOR IS BEING MODIFIED.ADD CALL TO CDCRIT TO LOOK UP INTO CATEGORY RELATION
3-83
PS 62034123130 September 1990
FOR TYPE 1.DELETE - ADD CALL TO CDERC TO DETERMINE IF ENTITY IS GENERICIF ENTITY IS NOT GENERIC - FOLLOWING CALLS ARE BY PASSED:ADD CALL TO CDASEL FOR SELECT FOR CASCADE IF ENTITYIS GENERIC.ADD CALL TO CDELIS TO BUILD LIST OF TYPE 2'S ANDLIST OF ENTITIES FOR CASCADE DELETEADD CALL TO CD2SEL TO BUILD TYPE 2'SADD CALL TO CDZDEL TO BUILD CASCADE DELETES2 MAY 1989 - ADD A NEW ROW TO TEMP-XFORM-LIST TO HOLDCATEGORY TYPEADD A NEW .INC TO HOLD TABLE OF ECS FROM WHICH TOBUILD TYPE 2'S FOR CASCADE DELETEADD A NEW .INC TO HOLD TABLE OF ENTITIES TO BEDELETED FOR CASCADE DELETE.ADD A NEW CS-QUALIFY CLONE TO HOLD CS-QUALIFICATIONSFOR CASCADE DELETE SO AS NOT TO DESTROY USER'SQUALIFICATIONS.
ERIRCDMERRFSCSQ VARDELCATTYP2TBEOTJLISTTXLISTNDMLSTKBLSTACKESQUALESALCSQUALUVA BBRCSALAPLRFTABLEFORVARCGTABLEBOO LSTCURTABWHEN TA BERR PRO
3-85
PS 62034123130 September 1990
ROUTINES CALLED:0
RPTERRCDGTVWCDMQALCDPBLCDPRE5CDIDIUERRPROCDVIEWCDABVWCDEMDACDEMDCDPDICDCMDCDPTECCDINECCD2 NECCDKYUQCDACALCDNNECCDATXLCDRCTGC DUTX LCDVTGKC DMP 1KCD1RITCDCRITCDJUVCDAUCC DTGVWCD2RITCDERCC DAS ELODELISCD2SELCDZ DEL
INSURE THAT TAG NUMBER EXTRACTED FROM ATTRIBUTEUSECLMATCHES AT LEAST 1 TEMP-AUC, OTHERWISE, ERROR.CONVERTED TO EMBEDDED SQL, ALL USER-ERROR-COUNTREFERENCES DELETED -- 14 MAY 1986FOR EACH TAG BELONGING TO AN ENTITY CLASS,FIND IF IT IS EQUAL TO AT LEAST ONE TEMP-AUC.IF NOT, GENERATE AN ERROR MESSAGE APPROPRIATETO THE ES-ACTION.
NAME: CDRCTGPURPOSE: GET THE RC AND OWNER TAG OF AN INHERITED ATTRIBUTELANGUAGE: VAX-lI COBOLSOURCE FILE: CDRCTGSOURCE FILE TYPE: PCOHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
PERFORM SQL SEARCH OF THE INHERITED-ATT-USE TABLE LOOKINGFOR RELATION CLASS NUMBER AND KEY CLASS MEMBER TAG NUMBERWHERE THE TAG NUMBER MATCHES THE INPUT PARAMETER.CONVERTED TO EMBEDDED SQL -- 19 MAY 1986ADD RETRIEVAL OF RELATION TYPE -- 2 MAY 1989PERFORM 1-ROW SELECT OF RC NUMBER AND KCM TAG NUMBERGIVEN THE TAG NUMBER. PERFORM STANDARD ERROR HANDLING.
NAME: CDTGVWPURPOSE: RETRIEVE ALL TAGS TO WHICH A VIEW MAPSLANGUAGE: VAX-lI COBOLSOURCE FILE: CDTGVWSOURCE FILE TYPE: PCOHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
SELECT ALL TAGS FOR A VIEW, RETRIEVE CONCEPTUAL METADATA ANDFILL INA ROW OF THE TEMP-XFORM-LIST FOR EACH TAG SELECTED.CONVERT TO EMBEDDED SQL -- 2 JUNE 1986MODIFY NDML-COUNTER TO PIC 9(6) -- 2 JUNE 1986DELETE USER-ERROR-COUNT AS OUTPUT PARAMETER -- 2 JUNE 1986SEARCH PROJECT DATA ITEM FOR ALL TAGS IN THE GIVENVIEW. FOR EACH TAG, EXTRACT CONCEPTUAL METADATA ANDFILL IN A NEW ROW OF THE TEMP-XFORM-LIST.
SQLS CASQLBS1SQLSCHSQLS CCSQ LTO CS QLOSQSQLADRSQLAB 1SQ LE XESQLCLSSQLADISQLFCHCDCMDCDATXLERRPRO
3-95
PS 62034123130 September 1990
DOCGROUP PS41231 Module Documentation
NAME: CDUTXLPURPOSE: UPDATE A ROW OF THE TEMP-XFORM-LISTLANGUAGE: VAX-Il COBOLSOURCE FILE: CDUTXLSOURCE FILE TYPE: COBHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
UPDATE THE TEMP-RC-NO AND THE TEMP-KCM-TAG-NO AND TEMP-RELATIONENTRIES OFTHE CURRENT ROW OF THE TEMP-XFORM-LIST WITH THE INPUTPARAMETERS.MODIFY FOR TEMP TRANSFORM LIST EXPANSION -- 19 MAY 1986MODIFY FOR TEMP TRANSFORM LIST CHANGE TO INCLUDE RELATION TYPE=2 MAY 1989UPDATE THE CURRENT TEMP-RC-NO AND TEMP-KCM-TAG-NO.
NAME: CDVIEWPURPOSE: VERIFY THE EXISTENCE OF A VIEW IN THE CDMLANGUAGE: VAX-lI COBOLSOURCE FILE: CDVIEWSOURCE FILE TYPE: PCOHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
PERFORM SQL SEARCH OF TABLE SEC TO VERIFY A VIEWGIVEN THE VIEW NAME. THE VIEW NUMBER IS RETURNED. IF THE VIEWDOESN'T EXIST, 0 IS RETURNED AS THE VIEW NUMBER.
MODIFIED TO EMBEDDED SQL - 5/5/86SEARCH FOR USER VIEW NUMBER GIVEN USER VIEW NAME.IF NOT FOUND, GENERATE ERROR MESSAGE.
FUNCTION CDVNV VALIDATES A CHARACTER STRING TO DETERMINEWHETHER IT IS NUMERIC. THE FOLLOWING RULES ARE APPLIED:1. A SIGN, IF PRESENT, MUST BE EITHER "+" OR "-" ANDMUST IMMEDIATELY PRECEED A DECIMAL DIGIT OR DECIMALPOINT.2. THE NUMBER, INCLUDING SIGN, DOES NOT HAVE TO BE LEFTJUSTIFIED IN THE FIELD, AS LONG AS THERE ARE NOEMBEDDED BLANKS.3. THERE MAY BE, AT MOST, ONE DECIMAL POINT.4. A DECIMAL NUMBER MUST EITHER PRECEED OR FOLLOW THEDECIMAL POINT. A DECIMAL NUMBER MAY BOTH PRECEEDAND FOLLOW THE DECIMAL POINT.5. AT LEAST ONE DECIMAL DIGIT MUST APPEAR IN THE NUMBER.IF VIOLATIONS OF THE ABOVE RULES OCCURS, AN ERROR MESSAGEIS GENERATED.APPLY RULES 1 THROUGH 5. GENERATE FATAL ERROR MESSAGEIF NECESSARY.
NAME: CDVTGKPURPOSE: VERIFY THAT A TEMP-AUC IS NOT A KEY CLASS MEMBERLANGUAGE: VAX-lI COBOLSOURCE FILE: CDVTGKSOURCE FILE TYPE: PCOHOST:SUBSYSTEM: CDMSUBDIRECTORY: NDML
DESCRIPTION:
PERFORM SQL SEARCH OF KEYCLASSMEMBER ON ALL TEMP-AUCS TOVERIFYTHAT THE TAG IS NOT A KEY CLASS MEMBERCONVERTED TO EMBEDDED SQL -- 19 MAY 1986PERFORM SINGLE-ROW SELECT OF ALL TEMP TAGS TOVERIFY THAT THEY ARE NOT MEMBERS OF THEKEY CLASS MEMBER TABLE. IF FOUND, GENERATE ANERROR MESSAGE.
The following list contains a purpose and description ofeach include file in the documentation group as specified inthe source code. The language it is written in is also given.
I(CONT)I ICDTGVW I jCD2RIT I (CDERC I I(CONT)I+----57 ---------- 71+ +---------- +----------- +----72+--- ---------------- +-----------------------+--------------
jSQLSCA I ISQLBS1 I ISQLSCH I ISQLSCC I I(CONT)I+------------ ------------- ------------- +------------+ ----- 73+
This information is contained in the Module Descriptions inSection 3.10.
3-214
PS 62034123130 September 1990
SECTION 4
QUALITY ASSURANCE PROVISIONS
4.1 Introduction and Definitions
"Testing" is a systematic process that may be preplannedand explicitly stated. Test techniques and procedures may bedefined in advance, and a sequence of test steps may bespecified. "Debugging" is the process of isolation andcorrection of the cause of an error.
"Antibugging" is defined as the philosophy of writingprograms in such a way as to make bugs less likely to occur andwhen they do occur, to make them more noticeable to theproqrammer and the user. In other words, as much error checkingas is practical and possible in each routine should beperformed.
4.2 Computer Programming Test and Evaluation
The quality assurance provisions for test consists of thenormal testing techniques that are accomplished during theconstruction process. They consist of design and codewalk-throughs, unit testing, and integration testing. Thesetests are performed by the design team. Structured design,design walk-through and the incorporation of "antibugging"facilitate this testing by exposing and addressing problem areasbefore they become coded "bugs."