Data Management System (DMS 2200) FORTRAN Data Manipulation Language (FDML)

Transcription

1 !()+ OS 2200 Data Management System (DMS 2200) FORTRAN Data Manipulation Language (FDML) Operations and Programming Reference Manual Copyright ( 1997 Unisys Corporation. All rights reserved. Unisys is a registered trademark of Unisys Corporation. Release Level 15R1 September 1997 Printed in U S America Priced Item

2 The names, places, and/or events used in this publication are not intended to correspond to any individual, group, or association existing, living, or otherwise. Any similarity or likeness of the names, places, and/or events with the names of any individual, living or otherwise, or that of any group or association is purely coincidental and unintentional. NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product and related material enclosed herein are only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such an agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. RESTRICTED RIGHTS LEGEND. Use, reproduction, or disclosure is restricted by DFARS and /FAR and for commercial computer software, as applicable. Unisys Corporation is interested in receiving your comments and suggestions about this information. You can send your comments in four ways: the Business Reply Mail form in the printed document; our Internet address (rsvldoc@rsvl.unisys.com); our fax number ( ); or our postal address (Unisys Corporation, PI Response Card, P.O. Box 64942, St. Paul, MN , U.S.A.). TRADEMARKS. All terms mentioned in this document that are known to be trademarks or service marks have been appropriately capitalized. Unisys Corporation cannot attest to the accuracy of this information. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark.

3 Contents About This Manual ::::::::::::::::::::::::::::::::::::::::::::: xiii Section 1. Introducing the FORTRAN Data Manipulation Language 1.1. What Is a Database System? ::::::::::::::::::: Defining and Manipulating Data :::::::::::::::: Defining Data (Administrator) ::::::::::::::::: Manipulating Data (Programmer) :::::::::::::: Using FDML Statements in a FORTRAN Program :: FDML Programming Tasks :::::::::::::::::: How Subschema Changes Affect Your Program :: DDL/SDDL/FDML Interface :::::::::::::::::::: 1-7 Section 2. Introducing FDML Statements 2.1. Summary of FDML Specification Statements ::::: Summary of FDML Executable Statements ::::::: Processing FDML Statements :::::::::::::::::: Using the FDML Preprocessor and the ASCII FORTRAN Compiler :::::::::::::::::::::::: FDML Preprocessor and ASCII FORTRAN Processing :::::::::::::::::::::::::::: Forming an Executable Run Unit by Using FDMLP and the ASCII FORTRAN Compiler :::::::::::::: Using the UCS FORTRAN Compiler :::::::::::::: UCS FORTRAN Compiler Processing ::::::::::: Forming an Executable Run Unit by Using the UCS FORTRAN Compiler ::::::::::::::::::::: iii

4 Contents Section 3. Introducing the FDML Program 3.1. FDML Program Structure :::::::::::::::::::::: Sample FDML Program ::::::::::::::::::::::: FDML Specification Statements :::::::::::::::: FDML Executable Statements :::::::::::::::::: 3-4 Section 4. FDML Components, Terminology, and Syntax Notation 4.1. FDML Components ::::::::::::::::::::::::::: Character Set :::::::::::::::::::::::::::: Delimiting Characters :::::::::::::::::::::: Commentary ::::::::::::::::::::::::::::: FDML Keywords ::::::::::::::::::::::::::: FORTRAN Terminology Used in This Manual :::::: FDML Terminology Used in This Manual ::::::::: Database Data Name ::::::::::::::::::::::: Generalized Name ::::::::::::::::::::::::: Integer Name ::::::::::::::::::::::::::::: Item Name ::::::::::::::::::::::::::::::: Key Count Name :::::::::::::::::::::::::: Key List Name :::::::::::::::::::::::::::: Key Name ::::::::::::::::::::::::::::::: Realm Key Name :::::::::::::::::::::::::: Realm Name ::::::::::::::::::::::::::::: Record Name ::::::::::::::::::::::::::::: Run Unit Name :::::::::::::::::::::::::::: Schema Name :::::::::::::::::::::::::::: Set Name :::::::::::::::::::::::::::::::: Subschema Name ::::::::::::::::::::::::: Overall Considerations :::::::::::::::::::::: FDML Syntax Notation :::::::::::::::::::::::: 4-13 Section 5. FDMLP and UCS FORTRAN Control Statements 5.1. Processor Call for FDMLP ::::::::::::::::::::: Processor Call for UCS FORTRAN ::::::::::::::: 5-5 iv

5 Contents Section 6. Sample FDML Runstreams 6.1. Sample Runstreams Using FDMLP and ASCII FORTRAN :::::::::::::::::::::::::::::::: Sample Runstream Using UCS FORTRAN :::::::: 6-6 Section 7. Using FDML Specification Statements 7.1. Overview of FDML Specification Statements :::::: Syntax Summary for FDML Specification Statements ::::::::::::::::::::::::::::::: INVOKE Statement :::::::::::::::::::::::::::: SUBSCHEMA and SCHEMA Clauses ::::::::::: INVKEY Clause :::::::::::::::::::::::::::: ENVIRONMENT Clause :::::::::::::::::::::: RUNID Clause ::::::::::::::::::::::::::::: PRIORITY Clause :::::::::::::::::::::::::: POINTERS Clause ::::::::::::::::::::::::: INCLUDE Clause :::::::::::::::::::::::::: LIST Clause :::::::::::::::::::::::::::::: COMMON Clause :::::::::::::::::::::::::: EQUIVALENCE Clause :::::::::::::::::::::: RECOVERY Clause ::::::::::::::::::::::::: ERRITEMS Clause ::::::::::::::::::::::::: ERROR (or ERR) Clause ::::::::::::::::::::: Action for ERROR, ROLLBACK, or END ::::::::: RECORD NAME Statement ::::::::::::::::::::: SET NAME Statement ::::::::::::::::::::::::: REALM NAME Statement :::::::::::::::::::::: KEY Statement ::::::::::::::::::::::::::::::: REALM KEY Statement :::::::::::::::::::::::: ACQUIRE LIST Statement :::::::::::::::::::::: 7-28 Section 8. Using FDML Executable Statements 8.1. Overview of FDML Executable Statements ::::::: Syntax Summary for FDML Executable Statements Detailed Descriptions of FDML Executable Statements ::::::::::::::::::::::::::::::: ACCEPT Statement and Key Expression Functions ACQUIRE Statement :::::::::::::::::::::::::: CONNECT Statement ::::::::::::::::::::::::: v

6 Contents 8.7. DEPART Statement ::::::::::::::::::::::::::: DISCONNECT Statement :::::::::::::::::::::: ERASE Statement ::::::::::::::::::::::::::::: FIND and FETCH Statements ::::::::::::::::::: Fetch-with-Lock Feature ::::::::::::::::::::: Record Selection Expressions :::::::::::::::: FINISH Statement ::::::::::::::::::::::::::::: FREE Statement :::::::::::::::::::::::::::::: GET Statement ::::::::::::::::::::::::::::::: IF Statement ::::::::::::::::::::::::::::::::: IMPART Statement :::::::::::::::::::::::::::: KEEP Statement :::::::::::::::::::::::::::::: LOG Statement ::::::::::::::::::::::::::::::: MODIFY Statement ::::::::::::::::::::::::::: READY Statement :::::::::::::::::::::::::::: RETAINING Clause :::::::::::::::::::::::::::: STORE Statement :::::::::::::::::::::::::::: 8-66 Section 9. Data Management Communications Area 9.1. Overview of the DMCA :::::::::::::::::::::::: DMCA Data Items and Statement Functions :::::: 9-2 Section 10. DMR and FDML Error Handling Error Handling Options :::::::::::::::::::::::: Error Notification ::::::::::::::::::::::::::::: Error Handling Example ::::::::::::::::::::::: DMR Basic Error Codes ::::::::::::::::::::::: DMR Rollback Error Codes :::::::::::::::::::: Repository Interface Messages ::::::::::::::::: FDMLP Interface to UREP ::::::::::::::::::: UCS FORTRAN Interface to UREP ::::::::::::: FDMLP Error Messages ::::::::::::::::::::::: UCS FORTRAN Error Messages ::::::::::::::::: Debugging Aids When Using FDMLP and ASCII FORTRAN :::::::::::::::::::::::::::::::: DMS Area Dumps :::::::::::::::::::::::::: UDS D-Bank Dumps :::::::::::::::::::::::: Debugging Aids When Using UCS FORTRAN :::::: Error Code List ::::::::::::::::::::::::::: Declaring List Components :::::::::::::::::: vi

7 Contents Dump Option ::::::::::::::::::::::::::::: Number of Error Codes ::::::::::::::::::::: Initializing List Fields ::::::::::::::::::::::: $LIST Call Format ::::::::::::::::::::::::: Appendix A. Identifiers Generated by FDMLP and UCS FORTRAN Appendix B. Comparing CDML and FDML Keywords and Statements Appendix C. Restrictions and Operational Considerations C.1. FDML Preprocessor Restrictions and Considerations :::::::::::::::::::::::::::: C-1 C.2. FORTRAN Restrictions and Considerations ::::::: C-3 C.3. HVTIP Restrictions :::::::::::::::::::::::::::: C-5 Appendix D. Comparing UCS FORTRAN to ASCII FORTRAN Glossary Bibliography Index vii

8

9 Figures 1-1. DDL/SDDL/FDML Interface Using FDMLP ::::::::::::::::::::::::: DDL/SDDL/FDML Interface Using UCS FORTRAN ::::::::::::::::::: FDMLP and FTN Compiler Processing :::::::::::::::::::::::::::: Forming a Run Unit When Using FDMLP ::::::::::::::::::::::::::: FORTRAN Compiler Processing ::::::::::::::::::::::::::::::::: Forming a Run Unit When Using UCS FORTRAN ::::::::::::::::::::: ix

10

11 Tables 2-1. FDML Specification Statements ::::::::::::::::::::::::::::::::: FDML Executable Statements :::::::::::::::::::::::::::::::::: DMCA Statement Functions :::::::::::::::::::::::::::::::::::: Types of Database Data Names :::::::::::::::::::::::::::::::: Types of Generalized Names ::::::::::::::::::::::::::::::::::: Syntax Notation Conventions ::::::::::::::::::::::::::::::::::: FDMLP Option Letters :::::::::::::::::::::::::::::::::::::::: Summary of FDML Specification Statements ::::::::::::::::::::::: INVOKE Clauses ::::::::::::::::::::::::::::::::::::::::::::: Summary of FDML Executable Statements :::::::::::::::::::::::: READY Usage Modes ::::::::::::::::::::::::::::::::::::::::: DMCA Statement Functions :::::::::::::::::::::::::::::::::::: DMCA Equivalences of Existing Statement Functions :::::::::::::::: DMCA Error Statement Functions ::::::::::::::::::::::::::::::: FDMLP Error Messages ::::::::::::::::::::::::::::::::::::::: B-1. CDML and FDML Keywords and Statements ::::::::::::::::::::::: B-1 B-2. CDML and FDML Record Selection Expressions :::::::::::::::::::: B-2 B-3. CDML and FDML Error Handling ::::::::::::::::::::::::::::::::: B xi

12

13 About This Manual Purpose This manual explains how to store, retrieve, modify, and delete data in an OS 2200 Data Management System (DMS 2200) database (hereafter referred to as DMS database) by embedding FORTRAN Data Manipulation Language (FDML) statements in an ASCII FORTRAN or Universal Compiling System (UCS) FORTRAN program. Scope This manual $ Discusses FDML programming in the Universal Data System (UDS) environment for both the ASCII FORTRAN and the UCS FORTRAN host languages $ Describes the FDML statements used to store, retrieve, update, and delete records in a DMS database $ Presents sample FDML programs and the runstreams used to process them $ Provides reference material on FDML statements and error handling Audience The primary audience for this manual is the FORTRAN applications programmer who writes programs that manipulate data in a DMS database. Database administrators are a secondary audience. The network data model distinctly separates data definition from data manipulation: $ The database administrator is responsible for data definition: designing, monitoring, and enhancing the database. The database administrator uses the Data Definition Language (DDL) and support utilitiesto perform these data definitionfunctions. Related manuals, listed later in this section, contain information on how to perform these tasks. $ The applications programmer is responsible for data manipulation: storing, retrieving, modifying, and deleting data in the database. You embed data manipulation language (DML) statements in one of the host language programs (ASCII COBOL, UCS COBOL, ASCII FORTRAN, or UCS FORTRAN) to perform these data manipulation functions. You can also use the Query Language Processor (QLP 2200), subsequently referred to as QLP) to access DMS data xiii

14 About This Manual Prerequisites The DMS database is based on the CODASYL (network) data model. Although this guide defines many terms related to network databases, you should already be familiarwith $ The network data model $ FORTRAN programming for the ASCII FORTRAN (FTN) compiler or for the UCS FORTRAN compiler $ Executive Control Language (ECL) $ Exec and TIP file structures How to Use This Document If you are new to the network data model or to DMS, read Section 1, Section 2, and Section 3 in order. You should also read the DMS SDDL Administration, Operations, and Programming Guide for background information on defining and accessing data. If you are an experienced FDML programmer, you can skip Section 1 and Section 2. Use Section 7 and Section 8 to reference syntax and semantic rules, and use Section 10 to reference error codes. Use 7.2 and 8.2 as a summary of FDML statement syntax. See Section 6 for examples of FDML programs and the runstreams that process them. See Appendix D if you are converting an ASCII FORTRAN program that contains FDML statements to a UCS FORTRAN program. Organization Section 1. Introducing the FORTRAN Data Manipulation Language This section presents background information on the FORTRAN Data Manipulation Language (FDML). It describes FDML and explains how it relates to components of DMS. Section 2. Introducing FDML Statements This section introduces the FDML statements and discusses FDML processing. It summarizes the FDML specification and executable statements and introduces the FDML preprocessor (FDMLP) and the UCS FORTRAN compiler. The section concludes with a discussion on how to form an executable run unit. Section 3. Introducing the FDML Program This section describes the structure and content of an FDML applications program. It also provides an example of an FDML program. xiv

15 About This Manual Section 4. FDML Components, Terminology, and Syntax Notation This section describes the components of FDML and defines FDML terms used in this manual. It also describes the syntax notation used to define the syntax of FDML statements. Section 5. FDMLP and UCS FORTRAN Control Statements This section describes the processor control statements for the FDMLP and the UCS FORTRAN compiler. Section 6. Sample FDML Runstreams This section provides sample runstreams for programs using FDML statements. The examples illustrate various programming considerations. Section 7. Using FDML Specification Statements This section describes how to use FDML specification statements, which serve as declarations. The section provides detailed information about the INVOKE statement and other specification statements. Section 8. Using FDML Executable Statements This section presents an overview and syntax summary of the FDML executable statements, followed by detailed descriptions of each statement. These detailed descriptions present the purpose, syntax, explanation, and examples of each FDML executable statement in alphabetical order. Section 9. Data Management Communications Area This section describes the contents of the general portion of the data management communications area (DMCA). It also identifies the statement functions used to access the general portion of the DMCA. Section 10. DMR and FDML Error Handling This section describes the error handling performed by the Data Management Routine (DMR), the FDML preprocessor, and the UCS FORTRAN compiler. It describes the error handling options provided by the FDML/DMS interface and the available dump options that serve as debugging aids. The section also explains various error codes and diagnostic messages. Appendix A. Identifiers Generated by the FDMLP and UCS FORTRAN This appendix lists the identifiers generated by the FDMLP preprocessor (FDMLP) and UCS FORTRAN, which may clash with application program identifiers xv

16 About This Manual Appendix B. Comparing CDML and FDML Keywords and Statements This appendix compares the DML keywords and statements in the COBOL and FORTRAN host languages. Appendix C. Restrictions and Operational Considerations This appendix describes the restrictions and programming considerations that apply to the FDML preprocessor (FDMLP) and those that apply to the UCS FORTRAN compiler. Appendix D. Comparing UCS FORTRAN to ASCII FORTRAN This appendix describes how the use of UCS FORTRAN to access data in a DMS database differs from the use of ASCII FORTRAN. Related Product Information You may also find the following documents helpful. Use the version of the document that corresponds to the level of software in use at your site. OS 1100 ASCII COBOL Programming Reference Manual (UP-8582) This manual describes ASCII COBOL and is intended for programmers using COBOL under control of the Executive. OS 1100 ASCII COBOL Supplementary Reference Manual (UP-8584) This manual describes items of ASCII COBOL that are not part of American National Standard COBOL, X OS 1100 ASCII FORTRAN Programming Reference Manual (UP-8244) This manual provides the necessary information for you to write programs in ASCII FORTRAN. It describes all the features of the American National Standard FORTRAN, X (also known as FORTRAN 77), as well as the extensions that provide increased programming capabilities. OS 2200 Data Management System (DMS 2200) Administration and Support Guide ( ) This guide explains how to use DMS support facilitiesto ensure data integrity, set up a TIP interface, run programs in different modes, and simultaneously access multiple schemas from a single data manipulation language program. Further, it explains how to monitor database performance, reorganize data storage, and use database procedures. OS 2200 Data Management System (DMS 2200) COBOL Data Manipulation Language (CDML) Operations and Programming Reference Manual ( ) This manual explains how to store, retrieve, change, and delete data in a DMS database by using ASCII or UCS COBOL Data Manipulation Language (CDML) statements. xvi

17 About This Manual OS 2200 Data Management System (DMS 2200) Schema Data Definition Language (DDL) Administration, Operations, and Programming Guide ( ) This guide explains how to design a DMS database and how to use Data Definition Language (DDL) commands to define a schema. OS 2200 Data Management System (DMS 2200) Subschema Data Definition Language (SDDL) Administration, Operations, and Programming Guide ( ) This guide explains how to use SDDL commands to define subschemas. OS 2200 Integrated Recovery Utility (IRU) Operations Guide ( ) This guide explains how to use IRU commands for backing up and reconstructing databases and transaction messages. It also explains how to avoid recovery situations by using IRU commands to maintain databases, describes when and how to use IRU commands and procedures for recovering data, and provides information needed for reading audit trails. OS 1100 MACRO Programming Reference Manual (UP-8336) This manual describes the MACRO system and its two separate program modules: the compilation module and the processor module. OS 1100 Message Control Bank (MCB) Programming Reference Manual ( ) This manual is a reference for MCB information used in applications programming on OS 2200 systems. It contains general information about MCB and message processing; information about MCB external interfaces; MCB internal technical information for software maintenance; and information about MCB programming conventions for use with database management programs, external error processing, and message processing programs. OS 2200 Transaction Processing Administration and Operations Reference Manual ( ) This manual describes how to use the TIP utilities to create and maintain TIP user files. The manual should be used as a reference for establishing and maintaining a Transaction Processing system. OS 2200 Unisys Repository Manager (UREP) Administration Guide ( ) This guide explains how to design, build, and maintain a data dictionary. It also explains how UREP works in the UDS environment. This guide describes how to create and update entities, relationships, and attributes, and provides a sample data dictionary xvii

18 About This Manual OS 2200 Universal Compiling System (UCS) COBOL Programming Reference Manual Volume 1, COBOL Statements ( ) This manual documents the components, syntax specifications, and structure requirements of UCS COBOL programs. UCS COBOL generates code for execution in extended mode on Unisys 1100/90 and 2200 Series systems. OS 2200 Universal Compiling System (UCS) COBOL Programming Reference Manual Volume 2, Compiler and System Interface ( ) This manual describes the UCS implementation of the COBOL language. It describes how to compile, link, and debug programs and how to interact with other system software, such as relational databases or Executive requests. OS 1100 Universal Compiling System (UCS) FORTRAN Programming Reference Manual Volume 1, FORTRAN Statements ( ) This manual documents the components, syntax specifications, and structure requirements of UCS FORTRAN programs. UCS FORTRAN generates code for execution in extended mode on Unisys 1100/90 and 2200 Series systems. OS 2200 Universal Compiling System (UCS) FORTRAN Programming Reference Manual Volume 2, Compiler and System Interface ( ) This manual provides programmers and analysts with detailed information on the UCS implementation of the FORTRAN language. This volume describes how to compile, link, and execute UCS FORTRAN programs and how to interface with other system software. OS 2200 Universal Data System (UDS) Configuration Guide ( ) This guide explains product configuration procedures for the Integrated Recovery Utility (IRU) and the Universal Data System (UDS) products: UDS Control, the Relational Data Management System (RDMS), Data Management System (DMS), Unisys Repository Manager (UREP), and Shared File System (SFS). It also presents product-specific tasks performed in conjunction with SOLAR installation. This guide is a companion to the UDS Planning and Installation Overview, thesystem Base Planning and Migration Overview, andthesoftware Products Installation Guide. OS 2200 Universal Data System (UDS) Planning and Installation Overview ( ) Previous title: OS 2200 Universal Data System (UDS) Planning and Migration Overview This overview presents information used when planning an installation of IRU and UDS products. Flowcharts summarize the tasks involved in twenty typical UDS product installation and migration scenarios. This overview information provides a conceptual framework that lets you plan detailed and interrelated UDS installation and migration tasks. Its companionvolume, the UDS Configuration Guide, presents individual product generation procedures and installation-related tasks that are part of the scenarios presented in this overview. xviii

19 About This Manual Compiler-Specific Notation This document contains information for the ASCII FORTRAN and UCS FORTRAN compilers. To help you identify information specific to one or the other, this document uses the following context indicators: $ Heading checkboxes A filled box under a section or subsection heading indicates that the text in the section or subsection applies either to ASCII FORTRAN or UCS FORTRAN, depending on which box is filled (ASCII or UCS). If no boxes appear below a heading, the section or subsection applies to both ASCII FORTRAN and UCS FORTRAN. $ Margin brackets A bracket in the margin indicates that the text next to the bracket applies either to ASCII FORTRAN or UCS FORTRAN, depending on the label specified in the bracket (ASCII or UCS). Reader Response If you have any questions or comments about this document, you can either mail or fax the Business Reply Mail form at the back of this document or send comments to the following Internet address: You can help us by including the following information: $ Your name $ Your company s name (optional) $ Your Internet address $ The document title and the 11-digit part number for the document (if applicable) $ The software level (software documents only) $ Any additional information that will help us in responding to your comments xix

20

21 Section 1 Introducing the FORTRAN Data Manipulation Language This section presents background information on the FORTRAN Data Manipulation Language. It describes FDML and explains how it relates to components of DMS What Is a Database System? A database system is essentially a computer-oriented record-keeping system. It provides a simple, automated way to obtain information from a database. The data stored in a database system is organized into one or more databases. In general, a database is both integrated and shared: $ A database integrates several distinct data files, eliminating much if not all data redundancy. $ Data can be shared among several different application programs. Each application program can access the same data; each can use the data for different purposes. A database system provides an organization with centralized control of operational data, which presents the following advantages: $ Allows different applications to share data $ Identifies data relationships $ Reduces redundant and inconsistent data $ Provides uniform methods to add, modify, and retrieve data $ Enforces standards and security restrictions

22 Introducing the FORTRAN Data Manipulation Language 1.2. Defining and Manipulating Data The Data Management System (DMS) is a database system that conforms to the CODASYL (network) data model. One of the characteristics of the CODASYL model is a strict separation of data definition from data manipulation. $ The database administrator is responsible for data definition: designing, monitoring, and tailoring the database. $ The applications programmer is responsible for data manipulation: storing, retrieving, modifying, and deleting data in the database Defining Data (Administrator) The database administrator first defines the DMS database through a schema. The schema describes the database both physically and logically. For example, the physical description specifies $ The size and organization of every file in the database. $ The types of records in the database. $ The characteristics of the data each record contains. The logical description specifies $ The relationships among record types, which are called set types. $ Ownership, membership, linkages, and other rules for set definition and usage. The database administrator writes a source schema with COBOL-like Data Definition Language (DDL) statements. The DDL processor then translates the source schema into an absolute schema, which contains tables that the DMS run-time routine (the Data Management Routine, or DMR) uses to fulfill your data requests. DDL Source DDL Processor Absolute Schema The database administrator also defines subsets of the schema - that is, logical views of the database. These subsets are called subschemas

23 Introducing the FORTRAN Data Manipulation Language One schema can have many subschemas, each with its own name. The subschemas can overlap, or they can be independent. Schema Subschema B Subschema A Subschema C The database administrator writes a source language subschema with another set of COBOL-like statements, called Subschema Data Definition Language (SDDL) statements. The SDDL processor translates the source subschema into an absolute subschema, which contains tables that the DMR uses when it processes applications that use the subschema. SDDL Source SDDL Processor Absolute Subschema In addition to the absolute subschema, the SDDL processor generates $ S$PROC $ S$WORK S$PROC is a symbolic procedure that contains skeleton descriptions of the data names and records defined in the subschema. It is automatically included in the FDML program at compilation time. S$WORK is an element that contains information about the subschema records, areas, sets, and data names. ASCII UCS For FDML programs using the FDML preprocessor (FDMLP), S$WORK is a relocatable that must be collected with the compiled FDML program before execution. For FDML programs using the UCS FORTRAN compiler, S$WORK is an object module. If the program is dynamically linked, S$WORK must be available to the executing program. If the program is statically linked, S$WORK must be included in the link source

24 Introducing the FORTRAN Data Manipulation Language Manipulating Data (Programmer) Programmers write DML applications to store, retrieve, modify, and delete the data in a DMS database. These programs manipulate the database through a named subschema that defines the portion of the database available to the program. Schema Subschema A Subschema B Appl Program 1 Appl Program 2 Appl Program 3 Appl Program 4 Appl Program 5 Database The applications programmer embeds Data Manipulation Language (DML) statements in one of the host language programs (ASCII COBOL, UCS COBOL, ASCII FORTRAN, or UCS FORTRAN) to manipulate database files defined in the subschema. The applications programmer can also access the database by using the Query Language Processor (QLP) host language and a subschema

25 Introducing the FORTRAN Data Manipulation Language 1.3. Using FDML Statements in a FORTRAN Program When writing an FDML program, you embed FDML statements into a FORTRAN program. You use FDML statements to code special instructions to manipulate data in a DMS database. ASCII UCS The ASCII FORTRAN Data Manipulation Language preprocessor (FDMLP) is a preprocessor to the ASCII FORTRAN (FTN) compiler. The preprocessor checks the syntax of FDML statements in a program and translates the FDML statements into appropriate ASCII FORTRAN statements or declarations. The preprocessor passes the program to the ASCII FORTRAN compiler. The UCS FORTRAN compiler accepts FORTRAN programs with embedded FDML statements. The compiler checks the syntax of the FDML statements and generates appropriate executable code. An FDML program follows standard FORTRAN rules. For example, it includes specification statements and executable statements. The program is compiled, collected or linked, and executed FDML Programming Tasks When you write an FDML program, you must also $ Embed special FORTRAN-like statements in the program s specification statements. These FDML specification statements describe the storage placement of database data names and records in the subschema. $ Embed FDML executable statements in the program to store, retrieve, and manipulate data in the part of the DMS database (subschema) available to the program. ASCII $ Call the FDML preprocessor (FDMLP), which converts FDML statements to a form understandable to the FTN compiler. The FDMLP automatically invokes the FTN compiler unless an FDMLP option prevents it from doing so. UCS $ Call the UCS FORTRAN compiler to compile the FDML program

26 Introducing the FORTRAN Data Manipulation Language How Subschema Changes Affect Your Program How data is defined in the subschema has implications for the FDML program. You need to determine what changes you must make in your program if the database administrator makes any of the following changes to the subschema definition: $ Renames schema entities (using the FROM option) $ Creates subsets of schema entities $ Adds subschema attributes If the data administrator renames a schema entity, you must use the subschema name in your FDML program. If you do not include schema entities in your program, the entities will not be available to the program. Likewise, you should avoid issuing FDML statements that require the DMR to access entities not included in the subschema. In the subschema definition, the data administrator can add EQUIVALENCE and DATA statements to the subschema data items for the convenience of the FDML program. However, the DMR does not recognize this feature. For example, an FDML statement cannot refer to a variable used in an EQUIVALENCE statement in place of a database item

27 Introducing the FORTRAN Data Manipulation Language 1.4. DDL/SDDL/FDML Interface The Data Definition Language (DDL) processor must be executed before the Subschema Data Definition Language (SDDL) processor. Its inputs are the source schema and the meta schemas, and its outputs are the object schema and a set of records on the meta database (the internal database used by the DDL and SDDL processors). These records on the meta database contain all the information the SDDL needs when defining a subschema for the schema and to produce the object schema. You must run the SDDL processor after running the DDL processor and before running the FORTRAN Data Manipulation Language preprocessor (FDMLP) or the UCS FORTRAN compiler. The SDDL processor uses the meta schemas and the meta database created by the DDL processor as input. This meta database describes the schema for which the subschema applies. The output of the SDDL processor is used as input to the FDML preprocessor or UCS FORTRAN compiler and also to the Data Management Routine (DMR). The output consists of object subschema tables (analogous to the object schema), an element called S$PROC/subschema-name that describes the records and data names to the FDMLP or UCS FORTRAN compiler, and a relocatable or object module element called S$WORK/subschema-name, which must be collected or linked with the run unit. After processing the schema and subschema by using DDL and SDDL, you use the repository to create a file description table (FDT). The FDT contains information about your files, such as the kinds of files, the page sizes and data formats, and the potential for auditing input/output operations. The next step involves either using the FDMLP and the FTN compiler or using the UCS FORTRAN compiler

28 Introducing the FORTRAN Data Manipulation Language ASCII $ Input to the FDML preprocessor consists of the FDML source program, the object subschema tables, and the symbolic element S$PROC/subschema-name, which describes the records and data names. The output of the FDMLP is a program that you must compile by using the host language (ASCII FORTRAN) compiler, and a relocatable D$WORKnnnnnn that you must map with the program. Figure 1-1 illustrates the entire interface. DDL Source DDL Processor Absolute Schema SDDL Source SDDL Processor Absolute Subschema Source Appl. Program (with FDML statements) S$PROC (output of SDDL) S$WORK (output of SDDL) FDMLP FTN Compiler Collector D$WORK (output of FDMLP) Absolute Applications Program DMR Database Figure 1-1. DDL/SDDL/FDML Interface Using FDMLP

29 Introducing the FORTRAN Data Manipulation Language UCS $ Input to the UCS FORTRAN compiler consists of the FDML source program, the object subschema tables, and the symbolic element S$PROC/subschema-name, which describes the records and data names. The output of the UCS FORTRAN compiler is an object module that can be executed. A static link is required if any of the program units involved in the execution contain LOG or ACQUIRE FDML statements, or if the program is a multischema run unit. (See Appendix D for more information.) Figure 1-2 illustrates the entire interface. DDL Source DDL Processor Absolute Schema SDDL Source SDDL Processor Absolute Subschema S$PROC (output of SDDL) S$WORK (output of SDDL) Source Appl. Program (with FDML statements) UCS FORTRAN Compiler Linker Absolute Applications Program DMR Database Figure 1-2. DDL/SDDL/FDML Interface Using UCS FORTRAN

30 Introducing the FORTRAN Data Manipulation Language 1.5. Documentation Updates This document contains all the information that was available at the time of publication. Changes identified after release of this document are included in problem list entry (PLE) To obtain a copy of the PLE, contact your Unisys representative or access the current PLE from the Unisys Product Support Web site: Note: If you are not logged into the Product Support site, you will be asked to do so

31 Section 2 Introducing FDML Statements This section introduces the FDML statements and discusses FDML processing. It summarizes the FDML specification and executable statements and introduces the FDML preprocessor (FDMLP) and the UCS FORTRAN compiler. The section concludes with a discussion on how to form an executable run unit Summary of FDML Specification Statements Table 2-1 summarizes the FDML statements that you can intermix with standard FORTRAN specification statements. For the function, syntax, rules of usage, explanation, and examples of each specification statement, see Section 7. Table 2-1. FDML Specification Statements Statement INVOKE RECORD NAME SET NAME REALM NAME KEY REALM KEY ACQUIRE LIST Purpose Required in every FORTRAN program that contains FDML statements. Specifies the subschema and schema used by the run unit. Declares generalized record names that are used to contain database record names. Declares generalized set names that are used to contain database set names. Declares generalized realm names that are used to contain database realm names. Declares key names that are used to contain database keys. Declares realm key names that are used to contain realm keys. Declares an FDML array that receives keys from the ACQUIRE statement

32 Introducing FDML Statements 2.2. Summary of FDML Executable Statements Table 2-2 summarizes the FDML executable statements that you can intermix with standard FORTRAN executable statements. The statements are listed functionally: $ Control statements Used to initiate and terminate the run unit or to obtain and relinquish access to the database realms (that is, areas) defined within the subschema. $ Retrieval statements Allow you to locate and retrieve data in the database. $ Update statements Used to store, change, or delete data in the database. $ Support statements Provide additional data handling functions and help maintain data integrity. For the function, syntax, rules of usage, explanation, and examples of each executable statement introduced in this subsection, see Section 8 Table 2-2. FDML Executable Statements Control Statements IMPART DEPART FREE READY FINISH Starts DML processing. Registers the run unit with UDS Control and the DMR. It also creates the necessary DMR interface with the object schema and subschema. Terminates DML processing. Deregisters the run unit and closes open areas. Releases all page locks and quick-looks. Opens program access to specified areas. Closes program access to specified areas. Retrieval Statements FIND GET FETCH ACQUIRE Locates a record and establishes currency, making that record the object record. Makes the record s database key available to the run unit. Copies the contents of the object record to the program s data space. Locates a record and copies the contents of that record to the program s data space. Makes the record s database key available to the run unit (combines FIND and GET). Transfers a set of database keys from a specified pointer array set to a selected acquire list in the program. continued

33 Introducing FDML Statements Table 2-2. FDML Executable Statements (cont.) Update Statements STORE ERASE MODIFY CONNECT DISCONNECT Establishes a new occurrence of a record in the database. Links the record into all sets in which it is an automatic member. Deletes an occurrence of a record. If the record is the owner of set, deletes all automatic members of the set. Changes values of data items in an existing record. Links an existing record into manual sets. Deletes a record from manual sets. Support Statements KEEP LOG ACCEPT IF Applies a selection lock to the object record s current page. Saves non DMS data on the DMS audit trail (tape or mass storage). Transfers a currency indicator to the program s DMCA. Converts a database key into a realm name, realm key, or both. Evaluates a condition as true or false. The system executes statements according to the evaluation

34 Introducing FDML Statements 2.3. Processing FDML Statements FDML programs can be processed and executed in two environments: $ Basic mode $ Universal Compiling System (UCS), also referred to as extended mode In basic mode, the FDML preprocessor (FDMLP) and the ASCII FORTRAN compiler are used. Various relocatables are mapped together to form an executable run unit. See 2.4 for details. In UCS, the UCS FORTRAN compiler is used. Various object modules are linked together to form an executable run unit. See 2.5 for details Using the FDML Preprocessor and the ASCII FORTRAN Compiler v ASCII y UCS This subsection describes the ASCII FORTRAN compiler processing and how to form an executable run unit FDML Preprocessor and ASCII FORTRAN Processing v ASCII y UCS Before the FTN compiler can compile an FDML program, the program must be preprocessed. During preprocessing, the FDML preprocessor (FDMLP) $ Examines the FDML syntax and issues diagnostic errors if there are FDML syntax errors. Syntax errors prevent the creation of D$WORK and the ASCII FORTRAN source. $ Inserts a copy of the proper S$PROC procedure (see 1.2) into the program. $ Inserts specification statements into the program to represent the data management communication area (DMCA) for the run unit. The DMCA serves as an interface area between the DMR and the run unit. $ The DMCA declaration is inserted into the program s declarations. It contains two types of data items: those used exclusively by the DMR and those the run unit can examine or initialize. $ Converts the FDML statements into statements acceptable to the FTN compiler

35 Introducing FDML Statements $ Generates a relocatable element that contains a table of relevant program addresses (D$WORK). The name of the relocatable element is formed by appending to D$WORK the run-id from the RUNID clause (if it is present) of the INVOKE statement. For example, RUNID=PAYROL generates the relocatable element D$WORKPAYROL.D$WORK is generated only if there is an IMPART statement in the program unit. $ May call UREP to create a relationship in the repository (UREP database) between the subschema and the program. This link is created if you include the RUNID clause in the INVOKE statement. Figure 2-1 shows the inputs and outputs of the FDMLP and the ASCII FORTRAN compiler. Subschema File Program File S$PROC Absolute Subschema FDMLP ASCII FORTRAN Compiler Source Program D$WORK ASCII FORTRAN Source Relocatable Program Figure 2-1. FDMLP and FTN Compiler Processing

36 Introducing FDML Statements Forming an Executable Run Unit by Using FDMLP and the ASCII FORTRAN Compiler v ASCII y UCS After preprocessing and compiling an FDML program, you must collect the compiled program with these other relocatable elements: $ The D$WORK table $ The S$WORK work area $ Interface routines provided on the FDMLP release tape that allow transitions between executing user code and DMR code Note: D$WORK and S$WORK are copied by IMPART statements from your user program into UDS Control banks. This makes D$WORK/S$WORK more secure than in previous DMS levels. However, the system can still be affected if a user program is not collected properly or corrupts its D-bank. If a specific D-bank is used in the collection, it is more efficient when the user D-bank address resides in the range of 20K to 200K decimal. The effective allowable address range for the user D-bank is 5K to 200K decimal. As the run unit executes, the DMR, in conjunction with UDS Control, transfers a requested database page into its work buffer and searches the page for the correct record. When the DMR locates the record, the system transfers the record occurrence into the program s data space (see 1.2). Figure 2-2 depicts run unit formation and execution when you are using the FDMLP and the ASCII FORTRAN compiler. D$WORK Relocatable FDML Program S$WORK Collector Database Interface Routines Run Unit Absolute DMR/UDS Schema Absolute Figure 2-2. Forming a Run Unit When Using FDMLP

37 Introducing FDML Statements 2.5. Using the UCS FORTRAN Compiler y ASCII v UCS This subsection describes UCS FORTRAN compiler processing and how to form an executable run unit UCS FORTRAN Compiler Processing y ASCII v UCS The UCS FORTRAN compiler provides access to a DMS database by enabling UCS FORTRAN to process FDML statements. During compilation of a program containing FDML statements, the compiler $ Examines the FDML syntax. Major or fatal errors prevent the creation of an object module. $ Includes in the program, through an implicit INCLUDE statement, a copy of the proper S$PROC procedure. $ Includes, through an implicit INCLUDE statement, specification statements to represent the data management communications area (DMCA). The DMCA serves as an interface area between the DMR and the run unit. The DMCA contains two types of data items: those used exclusively by the DMR and those the run unit can examine or initialize. $ Processes all FDML statements and generates the appropriate object code. $ Generates a table of relevant program addresses, which the DMR will use, into a common block that provides shared storage between the FDML program and the DMR. $ May call UREP to create a relationship in the repository between the subschema and the program. This link is created when you specify the UREP-XREF option on the UCS compiler. Figure 2-3 shows the inputs and outputs of the UCS FORTRAN compiler

38 Introducing FDML Statements Subschema File Program File S$PROC Absolute Subschema UCS FORTRAN Compiler Source Program Object Module Figure 2-3. FORTRAN Compiler Processing Forming an Executable Run Unit by Using the UCS FORTRAN Compiler y ASCII v UCS After compiling the FDML program with the UCS FORTRAN compiler, you are ready to link and execute the program. Dynamic linking may be used in some cases; other cases require static linking (See Appendix C for more information.) The S$WORK object module created by SDDL must be available when linking. While the run unit executes, the DMR, in conjunction with UDS Control, transfers a requested database page into its work buffer and searches the page for the correct record. When the DMR locates the record, the system transfers the record occurrence into the program s data space. Figure 2-4 depicts run unit formation and execution when you are using the UCS FORTRAN compiler

39 Introducing FDML Statements FDML Object Module S$WORK Linking Database Run Unit Absolute DMR/UDS Schema Absolute Figure 2-4. Forming a Run Unit When Using UCS FORTRAN

40

41 Section 3 Introducing the FDML Program This section describes the structure and content of an FDML applications program. It also provides an example of an FDML program FDML Program Structure The structure of an FDML program resembles that of a standard FORTRAN program. For example, an FDML program contains FORTRAN specification statements and executable statements. In addition, an FDML program includes $ An INVOKE statement naming the subschema $ FDML executable statements These additions distinguish an FDML program from a standard FORTRAN program. In particular, an FDML program contains $ Specification statements (see Section 7), which are extensions to standard FORTRAN specification statements. $ Executable statements (see Section 8), which are extensions to standard FORTRAN executable statements

42 Introducing the FDML Program 3.2. Sample FDML Program Following is a sample FDML program containing FDML statements and FORTRAN host-language statements. The FDML statements appear in boxes. ZDDDDDDDDDDDDDDD? 3 ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD? ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD? ZDDDDDDDDDDDDDDDDDDDDDD? 3 ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD? 3 ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD?