Documentation Updates

Transcription

1 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: Not e: If you are not logged into the Product Support site, you will be asked to do so.

2 MCP/AS Extended Retrieval with Graphic Output (ERGO) Operations Guide Copyright 1998 Unisys Corporation. All rights reserved. Unisys is a registered trademark of Unisys Corporation. HMP 4.0 and SSR 45.1 June 1998 Printed in USA Priced Item

3 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 or related information described herein is 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 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 Use, reproduction, or disclosure is restricted by DFARS and /FAR & for commercial computer software. Correspondence regarding this publication should be forwarded to Unisys Corporation either by using the Business Reply Mail form at the back of this document or by addressing remarks to Software Product Information, Unisys Corporation, Jeronimo Road, Mission Viejo, CA U.S.A. Comments about documentation can also be sent through to aspgpi@unisys.com. Unisys and ClearPath are registered trademarks of Unisys Corporation. CTOS is aregistered trademark of Convergent Technologies, Inc., a wholly owned subsidiary of Unisys Corporation. All other 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.

4 Contents About This Guide... xvii Section 1. Introducing ERGO Understanding the Elements of a Report Request Report Type (Required) Item List (Required) Global Selection Expression (Optional) Output Attributes (Optional) General Output Attributes (Optional) Report-Specific Output Attributes (Optional) PATH Specification (Optional) Sorting Specification (Optional) SORTED Clause (Optional) VIA Clause (Optional) USING Specification (Optional) Understanding Utility Commands Example ERGO Session Understanding ERGO Architecture Section 2. Running ERGO Starting ERGO Opening Databases and Files with the OPEN Command Opening Databases Opening Files Closing Databases and Files with the CLOSE Command Running an ERGO Session Running ERGO in an Interactive Session Running ERGO in a Batch Session Batch Session Operations Batch Session Defaults Choosing a Mode of Interaction Using Command Mode Using Prompt Mode Using Menu Mode Ending ERGO Ending an Interactive Session Ending a Batch Session Increasing Disk Space for Large Reports iii

5 Contents Section 3. Creating a Report Tabulate Report Request Statistics Report Request Plot Report Request Dplot Report Request Bargraph Report Request Histogram Report Request Kiviat Report Request Extract Report Request Section 4. Browsing and Updating the Database Selecting Records Displaying Records Browsing Records Updating Records Updating Single Records with the UPDATE Command Updating Multiple Records with the UPDATE Command Updating Records with the DB-UPDATE Screen Creating New Records Creating New Records with the CREATE Command Creating New Records with the RECREATE Command. 4 8 Creating New Records with the DB-CREATE Screen Deleting Records Section 5. Relating Data Sets Establishing Data Set Relationships Using the Two-Way RELATE Command Using the One-Way RELATE Command Understanding Implicit Relationships Section 6. Using Help Section 7. Expressions Item List Group Data Items in the Item List Occurring Data Items in the Item List Qualifying Data Items with the Same Name Data Items with Null Values SAME Keyword Selection Expression AS Clause Arithmetic Expression Arithmetic Operand iv

6 Contents Arithmetic Intrinsic Functions Multirecord Functions Multirecord Functions with Multiple Items Multirecord Functions and Item Selection Expressions String Expression Boolean Expression Global Selection Expression Preventing Unexpected Results Preventing Divide-by-Zero Errors Search Efficiency Linear Search by ERGO Binary Search by DMINTERPRETER DMINTERPRETER Search Restrictions DMINTERPRETER Search Conditions Expressions Using DMINTERPRETER Search Conditions and Restrictions PATH Specification Default Path Same Path Multiple Paths and Path Specification Selection Efficiency and Path Specification Selection Algorithm with Path Specification USING Specification Sorting Specification VIA Clause SORTED Clause User-Defined Functions Function Head Function Body Conditional Statement CASE Statement RETURN Statement ABORT Statement Arithmetic Expression Assignment String Expression Assignment WHILE Statement WRITE Statement User-Defined Function Examples Section 8. General Output Attributes AUTOSORT BUFFERSIZE COMMANDLINE CONCISELINE DESTINATION FILTERLINE FULLPAGE HEADING HEADINGLINE v

7 Contents MAXPRINTLINES OBSLIMIT OBSLINE PAGEDELAY PAGELENGTH PAGESKIP PAGEWAIT PAGEWIDTH SORTDISKSIZE Determining the Disk Size in Words Calculating the Number of Words Needed SORTLINE SORTMEMORYSIZE TITLELINE VIDEO Section 9. Report-Specific Output Attributes Formatting Specifications Format Item Specification Picture Format Specification Title Part Attributes DTSFILE FILETYPE Specification File Types for the CTOS Workstation PALETTE Specification for the CTOS Workstation TEMPLATE Specification for the CTOS Workstation File Types for the PC Operating ERGO with the Data Transfer System (DTS) EXTRACTDISPLAYFORM EXTRACTFILE EXTRACTFORMAT HISTOGRAMINTERVALS HISTOGRAMTITLE HISTOGRAMTYPE KIVIATAVERAGE KIVIATSCALING KIVIATTITLE PLOTCHARS PLOTCONNECT PLOTFILL PLOTGRID PLOTINFO PLOTSMOOTHING PLOTSTATS PLOTTITLE STATSFORMAT vi

8 Contents STATSTITLE TABFORMAT TABHEADING TABLEGEND TABSUMMARY TABTITLE XAXISBORDER XAXISFORMAT XAXISINTERVAL XAXISSCALE XAXISTITLE XMAX XMIN YAXISBORDER YAXISFORMAT YAXISINTERVAL YAXISSCALE YAXISTITLE YMAX YMIN Section 10. Browse and Update Commands CREATE DELETE DISPLAY NEXT RECREATE SELECT UPDATE Section 11. Utility Commands ABORT AX CALCULATE CANCEL CLEAR DEFINE Creating a Define Including a Command in a Define DISPLAYODT DO EDIT GLOSSARY LABEL LIMITS LIST MODE PROMPT vii

9 Contents RECESS RESET RESTORE SAVE Understanding How ERGO Handles Saved Information Tailoring an ERGO Session with a Profile SET SETUP SHOW SKIPTOHEADING SPEAK SPLIT STATUS WHEN Section 12. Interpret and Execute Commands INTERPRET EXECUTE Appendix A. Error Messages Messages Displayed When an Expected Syntax Element Is Missing... A 2 Messages Displayed during Menu Mode Operation... A 3 Messages Displayed in Response to Various Conditions... A 9 Appendix B. Example Database SALES Data Set... B 2 CUSTOMER Data Set... B 3 PRODUCT Data Set... B 3 EMPLOYEE Data Set... B 4 Appendix C. Operators and Functions Arithmetic, Boolean, and Relational Operators... C 1 Multirecord Functions... C 5 Mathematical, Trigonometric, and Bit-Counting Functions... C 6 Time Function... C 10 Appendix D. Software, and Memory and Disk Requirements Software Requirements... D 1 Memory and Disk Requirements... D 2 Appendix E. Description Files viii

10 Contents File Attributes for a Description File... E 1 Words 1 and 2 in a Description File... E 2 Group of 10 Words in a Description File... E 3 Example of a Description File... E 6 Appendix F. EBCDIC Characters Appendix G. Understanding Railroad Diagrams Railroad Diagram Concepts... G 1 Paths... G 1 Constants and Variables... G 2 Constraints... G 3 Vertical Bar... G 3 Percent Sign... G 3 Right Arrow... G 4 Required Item... G 4 User-Selected Item... G 4 Loop... G 5 Bridge... G 5 Following the Paths of a Railroad Diagram... G 6 Railroad Diagram Examples with Sample Input... G 7 Index ix

11 Contents x

12 Figures 1 1. ERGO Architecture The Home Menu DB-UPDATE Screen DB-CREATE Screen Establishing a Relationship between Two Data Sets Establishing a Relationship between Three Data Sets xi

13 Figures xii

14 Tables 1 1. ERGO Report Types Item List Requirements for a Report Request List of Intrinsic Functions Report Format Items Picture Format and Format Item Correspondence Report Types and Output Attributes Data Type Default Format for Extracted Data Extract Picture Format and Item Correspondence C 1. Arithmetic Operators... C 1 C 2. Boolean Operators in Boolean Expressions... C 2 C 3. Boolean Truth Table... C 3 C 4. Relational Operators with Arithmetic Expressions... C 3 C 5. Relational Operators with String Expressions... C 4 C 6. Multirecord Functions... C 5 C 7. Mathematical Functions Returning Integer Values... C 6 C 8. Mathematical Functions Returning Real Values... C 7 C 9. Trigonometric Functions Returning Real Values... C 8 C 10. Bit-Counting Functions within a Word... C 8 C 11. Other Mathematical Functions Returning Real Values... C 9 E 1. Words 1 and 2 in a Description File... E 2 E 2. Group of 10 Words in a Description File... E 3 E 2. Group of 10 Words in a Description File... E 4 E 2. Group of 10 Words in a Description File... E 5 F 1. EBCDIC Characters... F 1 G 1. Elements of a Railroad Diagram... G xiii

15 Tables xiv

16 Examples 7 1. Report Request and Output Using the SORTED Clause Report Request and Output Using Multirecord Function User-Defined Function Example Report Output from a User-Defined Function xv

17 Examples xvi

18 About This Guide Purpose Scope Audience The Extended Retrieval with Graphic Output (ERGO) Operations Guide provides you with an overview of ERGO and information on how you can use ERGO to generate reports on Data Management System II (DMSII) databases and conventional files. This guide is presented in two parts-one guide part and one reference part so that you can quickly access the information you need. The first part provides basic information on how to do the following: Begin and end an ERGO session. Open and close databases and conventional files. Interact with ERGO in command, prompt, or menu mode. Create eight report types. Relate data sets in order to use the information in unrelated data sets. Browse or update the database. Use the help system to access online information. The second part is intended for the more experienced ERGO user. It provides information on the following topics: Expressions you can use as part of the item list General and report-specific attributes you can use to control the format and destination of your report Commands you can use to browse and update the database, commands you can use to communicate with ERGO interactively, and commands that cause ERGO to make two passes over the database if this suits your reporting requirements. This guide is intended for use by managers, programmers, analysts, and support personnel involved in preparing reports from DMSII databases and conventional files xvii

19 About This Guide Prerequisites Although this guide gives you all the information you need to use the ERGO program immediately, you can greatly enhance efficient search and retrieval of data if you are familiar with Basic DMSII concepts Data and Structure Definition Language (DASDL) Data manipulation operators such as equal to (=), greater than (>), AND, and OR. For information on DMSII concepts and DASDL, you can refer to the DMSII Technical Overview and the DMSII Data and Structure Definition Language (DASDL) Programming Reference Manual. How to Use This Guide This guide is organized in two parts. If you are a new ERGO user, read Part 1, which is composed of Sections 1 through 6. Part 1 explains all the concepts you need to use ERGO immediately. Section 1, Introducing ERGO, describes the elements of a report request and presents a typical step-by-step ERGO session. Section 2, Running ERGO, shows you how to begin and end an ERGO session. It also explains how to open and close databases and conventional files. If you are an experienced ERGO user, use Part 2, which is composed of Sections 7 through 12. These sections provide reference information on how to use expressions, output specifications, and utility commands. Reference is made to microcomputers in this guide. Workstations that are part of the CTOS family of workstations are called CTOS workstations in this guide, and the other microcomputers are called personal computers (PCs). Organization This guide consists of the following sections and appendixes. In addition, an index is included at the end of this guide. Section 1. Introducing ERGO This section provides an overview of the function of ERGO. It explains the elements of a report request and presents a sample ERGO session. Section 2. Running ERGO This section explains how to begin and end an ERGO session and how to open and close databases and conventional files. It also describes the various ways you can run ERGO in command mode, menu mode, or prompt mode. xviii

20 About This Guide Section 3. Creating a Report This section describes the eight report types. It provides examples of each report request and of the output from each report request. Section 4. Browsing and Updating the Database This section provides step-by-step instructions for browsing and updating your database using command mode or menu mode. Section 5. Relating Data Sets This section explains how to form temporary relationships between database data sets in order to report on many data sets at one time. Section 6. Using Help This section explains how to use the ERGO help facility to find information about ERGO without going to a manual. The online help is a shortened, earlier version of this guide. Section 7. Expressions This section describes the mathematical functions and expressions you can use to narrow the search for the information you need. It also provides information on how to define search expressions that cause the DMUTILITY library to retrieve fewer records for ERGO to search through, thus saving time. Section 8. General Output Attributes This section describes how to use certain attributes to control such output information as the report destination or whether the report request statement should appear on the first report page. Section 9. Report-Specific Output Attributes This section describes the attributes you can use to format each of the report types. For example, you can use the PLOTFILL attribute to fill in the line of a Plot report type, or use PLOTGRID attribute to overlay a grid on a plot. Section 10. Browse and Update Commands This section describes the commands you can use to browse and update a database. Section 11. Utility Commands This section describes the commands you can use to communicate interactively with ERGO. For example, you can use the CANCEL command to interrupt the processing of a report request, or you can use the SHOW command to display information about the current ERGO session and about the database and its structure. Section 12. Interpret and Execute Commands This section describes the two commands you can use when your report requires two passes over the database and information is passed by way of user-defined functions xix

21 About This Guide Appendix A. Error Messages This appendix lists the possible error messages, specifies the possible cause each error, and offers advice to correct the error, if applicable. Appendix B. Example Database This appendix presents a small sample database called SALESINFO. This database information is used for the examples in this guide. Appendix C. Operators and Functions This appendix presents in table format the mathematical operators and functions you can use in your report expressions. Appendix D. Software, and Memory and Disk Requirements This appendix describes the software you need to run the ERGO program. This appendix also offers information and advice on the amount of memory and disk space ERGO needs and on ways to optimize memory usage. Appendix E. Description Files This appendix describes the file layout of a description file that is needed for using ERGO to report on a conventional file. The appendix includes an example of a description file. Appendix F. EBCDIC Characters This appendix presents in table format the EBCDIC equivalents of decimal and hexadecimal values. Appendix G. Understanding Railroad Diagrams This appendix explains how to read railroad diagrams. Related Product Information Unless otherwise stated, all documents referred to in this publication are MCP/AS documents. The titles have been shortened for increased usability and ease of reading. The following documents are included with the software release documentation and provide general reference information: The Glossary includes definitions of terms used in this document. The Documentation Road Map is a pictorial representation of the Product Information (PI) library. You follow paths through the road map based on tasks you want to perform. The paths lead to the documents you need for those tasks. The Road Map is available on the PI Library CD-ROM. If you know what you want to do, but don t know where to find the information, start with the Documentation Road Map. The Information Availability List (IAL) lists all user documents, online help, and HTML files in the library. The list is sorted by title and by part number. xx

22 About This Guide The following documents are included with the software release documentation and provide general reference information: ALGOL Programming Reference Manual, Volume 1: Basic Implementation The shortened title for this document is the ALGOL Reference Manual, Vol. 1. This manual describes the basic features of the Extended ALGOL programming language. This manual is written for programmers who are familiar with programming concepts. ALGOL Programming Reference Manual, Volume 2: Product Interfaces The shortened title for this document is the ALGOL Reference Manual, Vol. 2. This manual describes the extensions to the Extended ALGOL language that allow application programs to use the Advanced Data Dictionary System (ADDS), the Communications Management System (COMS), the Data Management System II (DMSII), the Screen Design Facility Plus (SDF Plus), or the Semantic Information Manager (SIM). This manual is written for programmers who are familiar with Extended ALGOL programming language concepts and terms. DMSII Data and Structure Definition Language (DASDL) Programming Reference Manual The shortened title for this document is the DMSII DASDL Reference Manual. This manual provides instructions for defining and maintaining a Data Management System II (DMSII ) database using DASDL. This manual is written for database administrators and staff. DMSII Interpretive Interface Programming Reference Manual The shortened title for this document is the DMSII Interpretive Interface Programming Manual. This manual details the Data Management System II (DMSII ) interpretive interface functions, including generating the DMINTERPRETER library, using entry points, and coding application programs. This manual is written for application programmers and database administrators who are already knowledgeable in the basic concepts of DMSII. DMSII Technical Overview This overview describes the Data Management System II (DMSII) environment, which includes DMSII databases and software. This overview is written for end users, system programmers, database designers, and database administrators who need information on creating, changing, restoring, accessing, and maintaining a DMSII database. DMSII Utilities Operations Guide This guide shows you how you can use the Data Management System II (DMSII) utility programs. These programs allow you to perform such database management tasks as initialization, reorganization, backup, recovery, and verification. This guide is written for database administrators and programmers who are responsible for database integrity and recovery xxi

23 About This Guide InfoExec Advanced Data Dictionary System (ADDS) Operations Guide The shortened title for this document is the InfoExec ADDS Operations Guide. This guide describes InfoExec ADDS operations, such as creating and managing database descriptions. This guide is written for those who collect, organize, define, and maintain data and who are familiar with the Data Management System II (DMSII), the Semantic Information Manager (SIM), and the Structured Query Language Database (SQLDB). Personal Workstation Data Transfer System (DTS) Installation and Configuration Guide The shortened title for this document is the PW DTS Installation and Configuration Guide. This guide explains how to install and configure DTS on a workstation running under the MS-DOS, OS/2, or CTOS operating system. It is written for system administrators, analysts, or programmers who are responsible for installing, configuring, and managing disk or printer resources. Personal Workstation Data Transfer System (DTS) Operations Guide, Volume 1: Simple Transfers The shortened title for this document is the PW DTS Operations Guide, Vol. 1. This guide explains how to write simple transfer definitions and how to use the virtual disk and virtual printer capabilities. It also explains how to run data transfers between enterprise servers and workstations running under the MS-DOS, OS/2, or CTOS operating system. This guide is written for all users of DTS systems. Simple Installation (SI) Operations Guide This guide describes how to install a software release using the Simple Installation (SI) program in three modes: menu, command, and batch. The guide is written for anyone using the SI program. For users who modify system software, the guide also describes how to compile the software using the Work Flow Language (WFL) job WFL/COMPILE/SOFTWARE. System Software Utilities Operations Reference Manual The shortened title for this document is the System Software Utilities Manual. This manual provides information on the system utilities BARS, CARDLINE, COMPARE, DCAUDITOR, DCSTATUS, DUMPALL, DUMPANALYZER, FILECOPY, FILEDATA, HARDCOPY INTERACTIVEXREF, ISTUTILITY, LOGANALYZER, LOGGER, PATCH, PRINTCOPY RLTABLEGEN, SORT, XREFANALYZER, and the V Series conversion utilities. It also provides information on the PL/I Indexed Sequential Access Method (PLIISAM), KEYEDIO support, Peripheral Test Driver (PTD), and mathematical functions. This manual is written for applications programmers, system support personnel, and operators. xxii

24 About This Guide Work Flow Language (WFL) Programming Reference Manual The shortened title for this document is the WFL Reference Manual. This manual presents the complete syntax and semantics of WFL. WFL is used to construct jobs that compile or run programs written in other languages and that perform library maintenance such as copying files. This manual is written for individuals who have some experience with programming in a block-structured language such as ALGOL and who know how to create and edit files using CANDE or the Editor xxiii

25 About This Guide xxiv

26 Section 1 Introducing ERGO Extended Retrieval with Graphic Output (ERGO) is a flexible and powerful tool that enables you to access and analyze information stored in DMSII databases or conventional files. Following are some of the tasks you can perform: Create Tabulate or Statistics reports. Create five types of graphics reports: Plot, Dplot, Bargraph, Histogram, and Kiviat. Extract data from the database. You can then report on the extracted data and transfer the report to a PC or CTOS workstation. Create user defines for frequently needed reports. Specify or change the report format, as follows: Edit some report attributes such as report titles and column headings. Use picture format strings to control how the data displays in a report. Control the report destination. Browse and update the database. Inquire about database content. Customize the ERGO session. Choose from three modes of interaction with the ERGO program: command, prompt, or screen. You can display the reports you generate with ERGO on your terminal or a microcomputer running a terminal emulator. You can use the Data Transfer System (DTS) to transfer extracted data or reports generated from extracted data from the enterprise server to such devices as the CTOS workstation, the Unisys Personal Workstation, the IBM PC microcomputer, the Personal Computer AT microcomputer, and compatible microcomputers. Microcomputer applications, such as the Multiplan and the Lotus software on the PC and the Business Graphics Package (BGP) and the Multiplan software on the CTOS workstation, can use the transferred data as part of spreadsheets or to produce bar graphs and pie charts

27 Introducing ERGO Although ERGO provides a great variety of ways to analyze your database, you need only know two things to create a simple report request or query: the type of report you want to create, and the name of the data items you want in the report. The examples in this guide use a sample database called SALESINFO. You can see the data set information for SALESINFO in Appendix B, Example Database. Most of the examples in this guide use the Tabulate report request because Tabulate is the most commonly used report type. You can shorten Tabulate to TAB for convenience. Following is a simple report request using the two required elements, the report type and the data items: This simple request displays in two columns on your terminal screen the names of all the products in your database and the product price. Generally, you would not want all of the information in your database. You would want to restrict the information by setting a condition or adding an expression to the simple report request. The following example uses a greater than sign to narrow the search and retrieval process, thus saving your time and processor time: This simple request displays results similar to the previous request except that the product names retrieved are only those whose price is greater than $300. Products with prices under $300 are not retrieved

28 Introducing ERGO Understanding the Elements of a Report Request Once you have initiated the ERGO program, opened the database, and related the data sets you want in a report, you are ready to enter the report elements that comprise the report request. Refer to Section 2, Running ERGO, for instructions on how to begin an ERGO session. The report request elements, or parts, of a command statement tell ERGO what data to select, what function to perform on the data, and how the data must be formatted. The report request is the command statement you use to request data from the database. This request consists of the following elements: Report type Item list Global selection expression Output attributes PATH specification Sorting specification USING specification The first two elements, report type and item list, are required and must be specified in order; the other elements are optional and can be specified in any order. The following report request has the two required elements the report type and the data item name and two optional elements a WHERE expression and a PAGELENGTH output specification: This request causes ERGO to retrieve and display on the terminal screen all customer codes over 125. Each page of the report will be 30 lines in length. You can enter report requests by transmitting separate lines (continuation character is not needed) or by transmitting partial commands on each line (continuation character and percent signs (%) are needed). On your terminal, or PC running a terminal emulator, you can also enter a command that spans several lines and transmit after the last line. The following pages describe each element of the report request. Descriptions consist of the element name, identification of the element as being mandatory or optional in a command statement, the actual description, and an example. Each element is explained in more detail in Part 2 of this guide

29 Introducing ERGO Report Type (Required) There are eight types of ERGO reports: Tabulate, Statistics, Extract, Plot, Dplot, Bargraph, Histogram, and Kiviat. Table 1 1 describes the reports in the order of most common use the Tabulate report type being the most frequently used. Table 1 1. ERGO Report Types Report Type Tabulate Statistics Extract Plot Dplot Bargraph Histogram Kiviat Description Produces a table in which data items are listed horizontally. Both numeric and alphabetic data can be listed. Produces statistical information about data items, including the count, the mean value, the maximum value, the minimum value, and the standard deviation. Produces a file of data items. A description of this extracted file can optionally be stored in another disk file for later use by ERGO or in the Advanced Data Dictionary System (ADDS). Plots one or more dependent variables against one independent variable on an X Y coordinate graph. The horizontal axis, X, is used for the independent variable. The vertical axis, Y, is used for dependent variables. ERGO determines plot positions by interpolating data values relative to the minimum and maximum values of the X Y axes. Only numeric data can be plotted. Produces a plot of discrete items. The dependent variable is shown horizontally, on the top of the page, while the independent variable is shown vertically, on the left side of the page. No interpolation is performed. Both numeric and string data can be plotted. Similar to Dplot, but instead produces a bar chart. Both numeric and string data can be plotted. Produces relative and cumulative frequency distributions of any single numeric data item. The resulting plot is in the form of a bar graph on an X Y scale. Histograms show fluctuations of a data item over several data intervals. Produces kiviat diagrams. A kiviat diagram is a circular diagram of data items plotted along radial axes of equal angular intervals. This diagram shows patterns or shapes instead of numerical results. Following is an example report request using the Tabulate report type: This report request causes ERGO to retrieve all customer names with their respective addresses and display them in a horizontal list on the terminal screen

30 Introducing ERGO Item List (Required) The item list is the list of database items you want in a report. The list can include simple data items, group items, and an expression that narrows the search and retrieval of data. The following simple item list causes ERGO to retrieve each product name with its respective product price: Note: Remap items, including virtual items, cannot be accessed without first defining a logical database and then creating a DMINTERPRETER library for that logical database. If you wanted to display only those products whose price was greater than $200, you could add a WHERE clause to the item expression, as follows: The addition of the WHERE clause as part of the item list allows you to display only the data about which you are interested. An expression to limit data retrieval is generally applied to a single data item in the item list; this is in contrast to a global selection expression that can apply to all data items in the list. (The global selection expression is explained in the later in this section.) You can see that the item list can include very simple expressions such as in the preceding example, but it can include more complex expressions, depending upon your needs and knowledge. An expression can involve arithmetic or string expressions that use simple data items, built-in functions like MEAN, and user-defined functions. Note that although the item list is required, an expression is optional; an expression to limit the search and retrieval is a useful and efficient element to add to your report requests. Refer to Section 7, Expressions, for more information on the item list. The list of data items can span several disjoint data sets and databases if previous RELATE commands have established appropriate relationships. If the data items you want in your report are from different data sets, a relationship must exist between the data sets. This relationship might have been established by your database administrator or you can establish a temporary relationship by using the RELATE command before running the report request. For often-used data sets, you can include data set relationships in your customized profile so that the relationships are established when you sign on to your ERGO session. Refer to Section 5, Relating Data Sets, for information on how to use the RELATE command. Refer to the SAVE command information in Section 11, Utility Commands, for information on how to create a profile. The following example uses the Tabulate report type and data items from two different data sets, the PRODUCT data set and the SALES data set. In order for ERGO to process this request, a relationship must exist between the datasets; otherwise, ERGO informs you that no relationship exists between the specified data sets

31 Introducing ERGO Global Selection Expression (Optional) The global selection expression is an optional element you can use to restrict the selection of records. This expression applies to the report request as a whole rather than to only one data item in the item list. Following is an example report request using a global selection expression with a Tabulate report type: In the preceding example, the WHERE clause causes ERGO to base the data selection on an item not named in the item list. Thus, the search and retrieval in this example is global in nature. Notice that the preceding example spans three data sets the PRODUCT data set, the SALES data set, and the CUSTOMER data set. All three must be related in order for ERGO to process this request. The global selection expression also features string pattern-matching with the ISIN operator. Refer to Section 7, Expressions, for more information on the global selection expression. Output Attributes (Optional) To tailor reports to your specifications, you can use more than 50 output attributes to control everything from the final report format to the kind of device on which you want your report to appear. ERGO assigns attributes default values so you need to specify only those attributes you want to change. These output attributes are particularly easy to adjust interactively, since you can format a report and immediately see the results of your format change on the terminal. Output attributes are separated from the rest of the report request by a colon (:). There are two kinds of output attributes: general output attributes and report-specific output attributes. General Output Attributes (Optional) The general output attributes apply to all report types. Once set to specific values, these attributes retain those values for the current session until new values are specified. These attributes include DESTINATION, PAGEWIDTH, PAGELENGTH, and HEADING. Following is an example of a general output attribute used with the Tabulate report type: Refer to Section 8, General Output Attributes, for more information on all general output attributes

32 Introducing ERGO Report-Specific Output Attributes (Optional) The report-specific output attributes apply to specific report types. For example, attributes such as specifications of X Y axes and plot characters can be used for the Plot report type but not with the Tabulate report type. Unlike general output attributes, these report-specific output attributes do not retain their values across different report types. Each time you change your report, ERGO restores the report-specific output attributes to their default values. If you use the same report but change the items used in that report, some of the report-specific output attributes are automatically set to default values. Following is an example using a report-specific attribute for a Tabulate report type: Refer to Section 9, Report-Specific Output Attributes, for more information. PATH Specification (Optional) ERGO selects the data from left to right by default unless you specify otherwise. This order of selection is called the path. You can override this automatic data selection by employing a PATH specification to explicitly choose the order in which the records are selected from different data sets. For example, you can specify that a PRODUCT record be selected before a SALES record, as in the following example: If you did not specify the path in the previous example, ERGO would automatically select the records first from the CUSTOMER data set, then the PRODUCT data set, and finally from the SALES data set. Refer to Section 7, Expressions, for more information on PATH specification

33 Introducing ERGO Sorting Specification (Optional) The sorting specification consists of the SORTED clause and the VIA clause. These clauses are briefly described in the following paragraphs. SORTED Clause (Optional) The SORTED clause is an optional report request element you can use to sort data before you generate a report. You can specify sort keys in either ascending or descending order. Following is an example SORTED clause used with the Tabulate report type: In this example, ERGO sorts the data based on the first item, PRODUCT-NAME. ERGO uses the default option, ASCENDING, since no option is specified. Refer to Section 7, Expressions, for more information on how to create more complex SORTED clauses. VIA Clause (Optional) The VIA clause is an optional element you can use to specify a particular set when selecting the first data set in the path. Following is an example request using the VIA clause with a Tabulate report type: Refer to Section 7, Expressions, for more information on the VIA clause. USING Specification (Optional) The USING specification is an optional report request element you can use to specify a list of relationship names, called a relate in ERGO. This element is useful when you want to define more than one relationship between two data sets. For example, assume you have two relationships labeled PRODSALES and SALESPROD, both defining relationships between the PRODUCT and SALES data sets. If you want to specify the PRODSALES relationship, you can use the following report specification: Refer to Section 7, Expressions, for more information on the USING specification

34 Introducing ERGO Understanding Utility Commands When you become familiar with ERGO, you can use the ERGO utility commands to do such things as ask for information while a report request is executing, change the manner of interacting with ERGO, or include a previously created define in your report request. Following are some of the utility commands you can use. Utility Command SHOW HELP CALCULATE GLOSSARY DO Description Displays functions, defines, database items, and the last command entered. Provides online information about using ERGO. Enables you to use ERGO as an on-screen calculator. Enables you to store information in your ERGO session that you can later access with the HELP command. For example, you can save a phrase that describes a define you create. Causes ERGO to execute commands from a disk file. Refer to Section 11, Utility Commands, for a full description of all of the ERGO utility commands

35 Introducing ERGO Example ERGO Session The following is an example ERGO session. It gives you a general idea of how to run ERGO and what ERGO can do. All of the steps involved are fully explained in other parts of the manual. This is an example only. Your first step is to run the ERGO program. From a Command and Edit (CANDE) session, enter the following statement: If you are running with the Communication Management System (COMS) and have an ERGO window, you can run ERGO by entering the following statement instead: ERGO displays the following messages on your terminal when the program is ready for your input: One convenient feature of ERGO is the start-up file, called a profile. You can enter into the profile all the commands you use on a regular basis at the beginning of your ERGO session. If you previously created a profile, ERGO executes the commands in the profile at the beginning of the session and displays appropriate responses to the commands in the profile. For example, if you have a command in your profile that opens the database you usually use, ERGO responds with the a message to inform you that the database is open. Refer to the SAVE command information in Section 11, Utility Commands, for information on how to create a profile. When ERGO displays the ENTER COMMAND message, you can open a database and then enter a report request. For an example report request, assume that you need a report about recent sales from the information contained in the example database called SALESINFO. You need information from the EMPLOYEE data set, the PRODUCT data set, and the SALES data set. A relationship already exists between these three data sets

36 Introducing ERGO Before you can create a report, you must first open the database from which you need the information. To do this, you must use the OPEN command as follows: ERGO opens the database called SALESINFO and displays the following message on your terminal: ERGO takes about 10 to 15 seconds to open this small database. ERGO requires more time to open larger databases. When the database is opened, ERGO displays the following message on your terminal: Another useful ERGO feature is the restore file. There are two kinds of restore files, a global restore file created by the database administrator and a local restore file prefixed with your usercode. When you create relates, defines, functions, or glossary text, ERGO saves them in your local restore file. Everything you create and then save with the SAVE command is saved in this file and available for you to use for all of your ERGO sessions. If there is any information in the default restore file, ERGO automatically restores that information and displays messages such as the following on your terminal: Refer to the RESTORE command information in Section 11, Utility Commands, for information on how to use the local restore file. The database you opened is ready to use. Notice that ERGO always displays the ENTER COMMAND message to indicate that you can continue. At this point, if you want to be reminded of what data item names are in the database, you could use the SHOW DBITEMS command. If you already know enough about the data items in the database, you are ready to create a report request

37 Introducing ERGO For the following examples, assume you want a report that lists sales representatives and the dollar amounts they generated. The names of the salesmen are in the EMPLOYEE data set, and the sales information is in the PRODUCT and SALES data sets respectively. You can enter the following request: ERGO begins to retrieve the data from the database and displays the following status message: ERGO begins formatting the data and displays the following status message: Then ERGO displays the first page of your report on your terminal screen. You can change the format of the report. For example, if you want to assign a specific heading and print the report on a line printer, enter the following command: This command changes the first line of the report from the default heading ERGO REPORT to Revenue by Salesrep, writes the entire report to a line printer, and displays the following message on your terminal: Following is a shortened version of what the report might look like:

38 Introducing ERGO ERGO can also create X Y plots, histograms, bar graphs, and other graphic output on your terminal. Assume that you wanted the same information in a bar graph format. You could create a Bargraph report using the same information, as follows: ERGO formats the information into a Bargraph report, similar to the following: When you want to end the ERGO session, enter BYE or QUIT. ERGO then closes all files and databases, and ends the program

39 Introducing ERGO Understanding ERGO Architecture As you become familiar with ERGO, you can create more complex report requests. It will be useful for you to know how the ERGO program interacts with the DMINTERPRETER library, the Accessroutines, and your DMSII databases. The ERGO program has no inherent knowledge of databases. ERGO obtains its database descriptions from the DMINTERPRETER library and its conventional file descriptions from the Advanced Data Dictionary System (ADDS) or a disk file where the description is stored. In order for you to report on DMSII databases, ERGO must be attached to DMINTERPRETER libraries. (A DMINTERPRETER library can be generated by running the BUILDINQ program. Refer to the DMSII Interpretive Interface Programming Reference Manual for more information on the BUILDINQ program.) Each DMINTERPRETER library contains information about a particular database. However, each DMINTERPRETER library must use the Accessroutines that service the database. The Accessroutines access all of the data in the database. The DMINTERPRETER library takes from the data only the information requested and passes the requested information on to ERGO to format appropriately and display on your terminal screen. Figure 1 1 illustrates the interaction between ERGO, the DMINTERPRETER library, the Accessroutines, and the database. ERGO program DMSII statement Data and errors DMINTERPRETER for database Requests Data and errors Accessroutines Database Figure 1 1. ERGO Architecture The DMINTERPRETER library works with ERGO to process parts of your report requests. When you become familiar with ERGO, you can learn to specify your requests in such a way as to maximize search efficiency as described in Search Efficiency in Section

40 Introducing ERGO Descriptions of every data object known to ERGO are stored in an internal dictionary called the symbol table. These objects include the following: Names of the database items, their types (numeric, string, Boolean, and so on), and their lengths Define names and their expansions Relationships of the data sets User-defined functions When ERGO opens a database, it automatically loads all descriptions into the symbol table. These descriptions include any defines, functions, and relations that have been saved in the default save file. If your declarations have been saved in a file other than the default save file and you want to use them, then you must use the RESTORE command to restore them from the appropriate disk file