DB-Access. User Manual. Version 9.1 March 1997 Part No

Transcription

1 DB-Access User Manual Version 9.1 March 1997 Part No

2 Published by INFORMIX Press Informix Software, Inc Bohannon Drive Menlo Park, CA Copyright by Informix Software, Inc. or their subsidiaries, provided that portions may be copyrighted by third parties, as set forth in documentation. All rights reserved. The following are worldwide trademarks of Informix Software, Inc., or its subsidiaries, registered in the United States of America as indicated by, and in numerous other countries worldwide: INFORMIX ; INFORMIX -OnLine Dynamic Server ; DataBlade The following are worldwide trademarks of the indicated owners or their subsidiaries, registered in the United States of America as indicated by, and in numerous other countries worldwide: Adobe Systems Incorporated: PostScript X/OpenCompany Ltd.: UNIX ; X/Open All other marks or symbols are registered trademarks or trademarks of their respective owners. Documentation Team: Jill Berman, Twila Booth, Evelyn Eldridge-Diaz, Tom Noronha To the extent that this software allows the user to store, display, and otherwise manipulate various forms of data, including, without limitation, multimedia content such as photographs, movies, music and other binary large objects (blobs), use of any single blob may potentially infringe upon numerous different third-party intellectual and/or proprietary rights. It is the user's responsibility to avoid infringements of any such thirdparty rights. RESTRICTED RIGHTS/SPECIAL LICENSE RIGHTS Software and documentation acquired with US Government funds are provided with rights as follows: (1) if for civilian agency use, with Restricted Rights as defined in FAR ; (2) if for Dept. of Defense use, with rights as restricted by vendor's standard license, unless superseded by negotiated vendor license as prescribed in DFAR Any whole or partial reproduction of software or documentation marked with this legend must reproduce the legend. ii DB-Access User Manual

3 Table of Contents Table of Contents Introduction About This Manual Organization of This Manual Types of Users Software Dependencies Assumptions About Your Locale Demonstration Database Major Features Documentation Conventions Typographical Conventions Icon Conventions Command-Line Conventions Sample-Code Conventions Additional Documentation On-Line Manuals Printed Manuals On-Line Help Error Message Files Documentation Notes, Release Notes, Machine Notes Compliance with Industry Standards Informix Welcomes Your Comments Chapter 1 Working with DB-Access What Is DB-Access? Preparing to Use DB-Access Setting Environment Variables Using DB-Access with a Non-Default Locale Creating the Demonstration Database Finding Your Way in DB-Access What to Check Before You Start DB-Access How to Use Your Terminal Keyboard Invoking DB-Access

4 Calling up the DB-Access Main Menu Invoking DB-Access and Selecting a Database Selecting a Menu Option Going to a Submenu and Submenu Option Executing a Command File Echoing File Input to the Screen Checking for ANSI Compliance Displaying Session Information Displaying the Software Version Number Activating the XLUF Feature for Nonprintable Characters Other Command-Line Features The DB-Access Main Menu The DB-Access Menu Structure Using DB-Access Menus and Screens Using Menu Screens Using Text-Entry Screens Using the HELP Screen Using a Text Editor Using the SQL Editor Using a System Editor Chapter 2 Creating Databases and Tables Working with a Database Selecting a Database Creating a Database Dropping a Database Closing a Database Getting Database Information Working with a Table Creating a Table Modifying a Table Dropping a Table Getting Table Information Querying a Table Manipulating Data in a Table The DB-Access Facilities Using the Interactive Schema Editor Using SQL Statements Method 1: Using the Menu Options How To Create a Database (Menu) How to Select a Database (Menu) Leaving the Menu Where System Information Is Stored iv DB-Access User Manual

5 How To Create a Table in the Database (Menu) Calling Up the Table Schema Exiting the Schema Editor Specifying Column Constraints Creating a Fragmented Table Where Table Information Is Stored How To Modify a Table in the Database (Menu) Using the Alter Option How To Get Table Information (Menu) Displaying Information About a Column How to Select Data from a Table (Menu) How to Drop a Table (Menu) How to Drop a Database (Menu) How to Close a Database (Menu) How to Get Database Information (Menu) Method 2: Using SQL How To Create a Database (SQL) How to Select a Database (SQL) How to Create a Table (SQL) Assigning Column Constraints Creating an Index on a Table How to Modify a Table (SQL) Adding a Column to a Table Modifying a Column in a Table Dropping a Column from a Table Renaming a Column in a Table Adding and Dropping Constraints Modifying Fragmentation Strategy How To Get Table Information (SQL) How to Select Data from a Table (SQL) How to Drop a Table (SQL) How to Drop a Database (SQL) How to Close a Database (SQL) How to Get Database Information (SQL) Table of Contents v

6 Chapter 3 The Query-language Menu Option Choosing an Approach to Databases and Tables Choosing the Query-language Option Entering a New SQL Statement Running an SQL Statement Running Error-Free Statements What Happens When There Are Errors Viewing the Next Page of Data Modifying an SQL Statement Editing an SQL Statement Redirecting Query Results Sending Output to a Printer Sending Output to a File Sending Output to a Pipe Choosing an Existing SQL Statement Sample SQL Command Files Saving the Current SQL Statement Displaying Table Information The Columns Option The Indexes Option The Privileges Option The References Option The Status Option The constraints Option The triggers Option The Table Option The Fragments Option Dropping an SQL Statement Selecting Data from a Table How to Run Queries on the SQL Menu Basic Forms of the SELECT Statement Retrieving All the Data in a Table Performing a Selection Operation on Table Data Performing a Projection Operation on Table Data Performing Selection and Projection Operations at the Same Time 3-39 Performing Join Operations on Tables Display of Data Types in Query Results Display of Built-in Types Display of Floating-Point Data Types Display of Large Objects Display of Opaque Types Display of Row Types vi DB-Access User Manual

7 Display of Collection Types Support for Table Inheritance in Queries How to Exclude Subtable Rows from the Query Result How to Select All Columns of a Supertable and Its Subtables Using Other SQL Statements Deciding on a Database and Tables Learning SQL Statements Choosing a Method for Entering SQL Statements Example of an SPL Routine in a Command File Chapter 4 Chapter 5 The Database Menu Option Choosing the Database Option Selecting a Database The SELECT DATABASE Screen List of Available Databases Selecting a Database on Another Server Exiting the Screen Creating a Database Guidelines for Naming Databases Effects of Creating a Database Creating a Database on Another Server The CREATE DATABASE Menu Displaying Database Information Retrieving Information on Dbspaces Retrieving Information on Native Language Support Retrieving Information on Global Language Support Retrieving Information on Routines Selecting a Different Database Exiting the Screen Dropping a Database The DROP DATABASE Screen Confirming Your Decision to Drop a Database Exiting the Screen Closing a Database The Table Menu Option Selecting the TABLE Menu Creating a Table The CREATE TABLE Screen Naming the Table Building the Table Schema Exiting the CREATE TABLE Menu Adding a Column to a Table Table of Contents vii

8 Adding to the Table Schema Building the Table Schema Modifying a Column in a Table Dropping a Column Rebuilding the Table Schema Displaying Subsequent Table Screens Setting Table Options Defining Constraints Defining a Fragmentation Strategy Altering a Table The ALTER TABLE Screen Exiting the ALTER TABLE Screen Adding a Column with the ALTER TABLE Menu Modifying a Column with the ALTER TABLE Menu Dropping a Column with the ALTER TABLE Menu Using the Screen Option on the ALTER TABLE Menu Changing Table Options with the ALTER TABLE Menu Altering the Fragmentation Strategy of a Table Altering or Defining a Fragmentation Strategy The ALTER FRAGMENT Menu: Round-robin Strategy The ALTER FRAGMENT Menu: Expression Strategy The ALTER FRAGMENT Menu: No Fragmentation Displaying Table Information The Columns Option The Indexes Option The Privileges Option The References Option The Status Option The constraints Option The triggers Option The Table Option The Fragments Option Dropping a Table Confirming Your Decision Exiting the DROP TABLE Screen viii DB-Access User Manual

9 Chapter 6 Appendix A Appendix B The Connection and Session Menu Options Choosing the Connection Option Connecting to a Database Environment Disconnecting from a Database Environment Choosing the Session Option Sample Command Files How to Read On-Line Help for SQL Statements Index Table of Contents ix

10

11 Introduction Introduction About This Manual Organization of This Manual Types of Users Software Dependencies Assumptions About Your Locale Demonstration Database Preparing to Create the Demonstration Database Creating the Demonstration Database Permissions for the Demonstration Database Major Features Documentation Conventions Typographical Conventions Icon Conventions Comment Icons Command-Line Conventions How to Read a Command-Line Diagram Sample-Code Conventions Additional Documentation On-Line Manuals Printed Manuals On-Line Help Error Message Files Documentation Notes, Release Notes, Machine Notes Compliance with Industry Standards Informix Welcomes Your Comments

12 2 DB-Access User Manual

13 Read this introduction for an overview of the information provided in this manual and for an understanding of the documentation conventions used. About This Manual The DB-Access User Manual describes how to use the DB-Access utility to access, modify, and retrieve information from INFORMIX-Universal Server. This book is both a user guide and reference manual. Organization of This Manual This manual includes the following chapters: This Introduction provides an overview of the manual and describes the documentation conventions used. Chapter 1, Working with DB-Access, provides an overview of how to use DB-Access with Universal Server. It explains how to use your terminal and the system editor, how to invoke the utility, and how to use the various screens and menus. It also illustrates and describes the DB-Access main menu structure and tells how to get on-line Help. Chapter 2, Creating Databases and Tables, is a tutorial-style chapter that illustrates how to create, modify, drop, and select databases and tables using either a main menu option or an SQL statement. It also introduces the Interactive Schema Editor (ISED) and the Informix implementation of SQL. Introduction 3

14 Types of Users Chapter 3, The Query-language Menu Option, illustrates and describes how to use the various menus and screens when you select the Query-language option from the DB-Access main menu. This chapter also contains an extended tutorial on the SELECT statement that emphasizes the display of different data types in query results. Chapter 4, The Database Menu Option, illustrates and describes how to use the various menus and screens when you select the Database option from the DB-Access main menu. Chapter 5, The Table Menu Option, illustrates and describes how to use the various menus and screens when you select the Table option from the DB-Access main menu. Chapter 6, The Connection and Session Menu Options, illustrates and describes how to use the various menus and screens when you select the Connection option or the Session option from the DB-Access main menu. Appendix A illustrates and briefly describes all the command files that you can use for practice. These example files are provided with DB-Access when you run the script to install the demonstration database. Appendix B illustrates how to read the syntax for SQL statements described on the DB-Access on-line Help screens. Types of Users This manual is written for all users of Informix products who use the DB-Access utility to access, modify, and retrieve the information in a relational database. If you have limited experience with relational databases, SQL, or your operating system, refer to Getting Started with INFORMIX-Universal Server for a list of introductory texts. 4 DB-Access User Manual

15 Software Dependencies Software Dependencies This manual assumes that you are using INFORMIX-Universal Server, Version 9.1, as your database server. In this manual, all instances of Universal Server refer to INFORMIX-Universal Server. Assumptions About Your Locale Informix products can support many languages, cultures, and code sets. All culture-specific information is brought together in a single environment, called a GLS (Global Language Support) locale. This manual assumes that you are using the default locale, en_us This locale supports U.S. English format conventions for dates, times, and currency. In addition, this locale supports the ISO code set, which includes the ASCII code set plus many 8-bit characters such as é, è, and ñ. If you plan to use nondefault characters in your data or your SQL identifiers, or if you want to conform to the nondefault collation rules of character data, you need to specify the appropriate nondefault locale(s). For instructions on how to specify a nondefault locale, additional syntax, and other considerations related to GLS locales, see the Guide to GLS Functionality. Demonstration Database The DB-Access utility includes a demonstration database called stores7 that contains information about a fictitious wholesale sporting-goods distributor. The script that creates the demonstration database also provides sample SQL command files that you can use for practice with the stores7 database. The stores7 database is described in detail and its contents are listed in Appendix A of the Informix Guide to SQL: Reference. Introduction 5

16 Demonstration Database Preparing to Create the Demonstration Database To create or use the demonstration database, you or your database administrator must configure the environment, as follows: Set the INFORMIXDIR environment variable so that it contains the name of the directory in which your Informix products are installed. Set the INFORMIXSERVER environment variable to the name of the default database server. The name of the default database server must exist in the $INFORMIXDIR/etc/sqlhosts file or the file that the INFORMIXSQLHOSTS environment variable specifies. (For a full description of environment variables, see Chapter 4 of the Informix Guide to SQL: Reference.) For information about sqlhosts, see the INFORMIX-Universal Server Administrator s Guide. To use the relative pathnames as described in the following sections, set your PATH environment variable to include $INFORMIXDIR/bin. Creating the Demonstration Database The script that you use to install the demonstration database is called dbaccessdemo7 and is located in the $INFORMIXDIR/bin directory. If you choose to name your database, you must use the following naming conventions: A name can have a minimum of 1 character and a maximum of 18 characters. The first character of a name must be a letter; other characters can be letters, numbers, or underscores (_). The name must be unique among the database names on the same database server. (DB-Access makes no distinction between uppercase and lowercase letters; therefore stores7 and STORES7 refer to the same database.) For example, you might want to name the demonstration database mystores. 6 DB-Access User Manual

17 Demonstration Database To create and populate the stores7 demonstration database 1. Create a new directory for the SQL command files by entering the following command: mkdir dirname You can create this directory wherever you want the command files to be. The dirname can be any name that you choose. For example, you might want to name the directory demo_db. 2. Make the new directory the current directory by entering the following command: cd dirname 3. Create the demonstration database by entering any one of the following commands: To create the database and specify a name that you choose, enter: dbaccessdemo7 dbname If you do not specify a database name, the database name defaults to stores7. To create the database with logging, enter: dbaccessdemo7 -log dbname If you do not specify the -log option, your demonstration database will not support transaction logging. Introduction 7

18 Demonstration Database To specify a dbspace for the database, enter: dbaccessdemo7 dbname -dbspace dbspacename Make sure that the dbspace that you specify exists. If it does not exist, you or your system administrator can create the dbspace with the onspaces utility. The onspaces utility is described in the INFORMIX-Universal Server Administrator s Guide. If you do not specify a dbspace name, by default, the data for the database is put into the root dbspace. To specify all of the options in one command, enter: dbaccessdemo7 -log dbname -dbspace dbspacename After you enter one of the previous commands, a series of messages appear on the screen as each table in the database is created. If you use the default database name, the following messages appear: Dropping existing stores7 database... Creating stores7 database.... The creation of the demonstration database is now complete. The remainder of this script copies the examples into your current directory. Press "Y" to continue, or "N" to abort. 4. Press Y to copy the command files into the directory that you have created or press N to specify that the command files should not be copied. You can now use the demonstration database and sample command files. If you make changes to your database that you do not want to keep, you can run the dbaccessdemo7 script to create a fresh demonstration database. When the creation of the new demonstration database is complete, the script prompts you and asks if you would like to copy the sample command files to the current directory. Press N if you have made changes to the sample files and do not want them replaced with the original versions. Press Y if you want to replace the command files with the original versions. 8 DB-Access User Manual

19 Major Features Permissions for the Demonstration Database To use the command files that have been copied to your directory, you must have UNIX read and execute permissions for each directory in the pathname of the directory from which you ran the dbaccessdemo7 script. Check with your system administrator for more information about operating-system file and directory permissions. UNIX permissions are discussed in the INFORMIX-Universal Server Administrator s Guide. When you run dbaccessdemo7, you are, as the creator of the database, the owner and Database Administrator (DBA) of that database. To give someone else the permissions to access the command files in your directory, use the UNIX chmod command. To give someone else access to the database that you have created, grant them the appropriate privileges using the GRANT statement. The GRANT statement is described in the Informix Guide to SQL: Syntax. To revoke privileges, use the REVOKE statement. The REVOKE statement is described in the Informix Guide to SQL: Syntax. Major Features The following list includes only those features of DB-Access that are new with Universal Server. You can run the new SQL statements in Universal Server from the SQL menu. For example, you can enter and run CREATE ROW TYPE, CREATE CAST, and CREATE DOMAIN statements from the SQL menu. For SELECT statements, DB-Access displays the output of columns with new data types, such as opaque types, large objects, row types, collection types, and the built-in types INT8, SERIAL8, and BOOLEAN. DB-Access supports table inheritance in SELECT statements. When you query against a supertable, DB-Access displays the specified columns from the supertable and also the inherited columns in any subtables. Introduction 9

20 Major Features In queries that retrieve values from columns with floating-point data types, DB-Access now displays a maximum of 14 digits to the right of the decimal point. You can override this default behavior by setting the DBFLTMASK environment variable. The Columns option on the TABLE INFO menu and the SQL INFO menu displays the data type of columns that have any of the new data types. The Indexes option has a new display on the TABLE INFO menu and the SQL INFO menu. This display has a new column, Access Method, that indicates the index access method, such as B-tree or Functional. The Procedures option on the DATABASE INFO menu has been renamed the Routines option, and the SELECT PROCEDURE screen has been renamed the SELECT ROUTINE screen. The UNLOAD statement can unload data from tables with new data types to operating-system files. The tables to be unloaded can contain opaque types, row types, collection types, large objects, or built-in data types. For further information on the UNLOAD statement, see the Informix Guide to SQL: Syntax and the Informix Migration Guide. The LOAD statement can load data from operating-system files into tables that contain new data types. The tables to be loaded can contain opaque types, row types, collection types, large objects, or built-in data types. For further information on the LOAD statement, see the Informix Guide to SQL: Syntax and the Informix Migration Guide. You can now display a maximum of 512 database names on the SELECT DATABASE screen. The Introduction to each Version 9.1 product manual contains a list of major features for that product. The Introduction to each manual in the Version 9.1 Informix Guide to SQL series contains a list of new SQL features. Major features for Version 9.1 Informix products also appear in release notes. 10 DB-Access User Manual

21 Documentation Conventions Documentation Conventions This section describes the conventions that this manual uses. These conventions make it easier to gather information from this and other Informix manuals. The following conventions are covered: Typographical conventions Icon conventions Command-line conventions Sample-code conventions Typographical Conventions This manual uses the following standard set of conventions to introduce new terms, illustrate screen displays, describe command syntax, and so forth. Convention KEYWORD italics boldface monospace KEYSTROKE Meaning All keywords appear in uppercase letters in a serif font. Within text, new terms and emphasized words appear in italics. Within syntax diagrams, values that you are to specify appear in italics. Identifiers (names of classes, objects, constants, events, functions, program variables, forms, labels, and reports), environment variables, database names, filenames, table names, column names, icons, menu items, command names, and other similar terms appear in boldface. Information that the product displays and information that you enter appear in a monospace typeface. Keys that you are to press appear in uppercase letters in a sans serif font. This symbol indicates the end of feature-, product-, platform-, or compliance-specific information. Introduction 11

22 Icon Conventions Tip: When you are instructed to enter characters or to execute a command, immediately press RETURN after the entry. When you are instructed to type the text or to press other keys, no RETURN is required. Icon Conventions Throughout the documentation, you will find text that is identified by several different types of icons. This section describes these icons. Comment Icons Comment icons identify warnings, important notes, or tips. This information is always displayed in italics. Icon Description The warning icon identifies vital instructions, cautions, or critical information. The important icon identifies significant information about the feature or operation that is being described. The tip icon identifies additional details or shortcuts for the functionality that is being described. Command-Line Conventions This section defines and illustrates the format of commands that are available in Informix products. These commands have their own conventions, which might include alternative forms of a command, required and optional parts of the command, and so forth. 12 DB-Access User Manual

23 Command-Line Conventions Each diagram displays the sequences of required and optional elements that are valid in a command. A diagram begins at the upper-left corner with a command. It ends at the upper-right corner with a vertical line. Between these points, you can trace any path that does not stop or back up. Each path describes a valid form of the command. You must supply a value for words that are in italics. You might encounter one or more of the following elements on a commandline path. Element command variable -flag.ext Description This required element is usually the product name or other short word that invokes the product or calls the compiler or preprocessor script for a compiled Informix product. It might appear alone or precede one or more options. You must spell a command exactly as shown and use lowercase letters. A word in italics represents a value that you must supply, such as a database, file, or program name. A table following the diagram explains the value. A flag is usually an abbreviation for a function, menu, or option name or for a compiler or preprocessor argument. You must enter a flag exactly as shown, including the preceding hyphen. A filename extension, such as.sql or.cob, might follow a variable that represents a filename. Type this extension exactly as shown, immediately after the name of the file. The extension might be optional in certain products. (.,;+*-/) Punctuation and mathematical notations are literal symbols that you must enter exactly as shown. '' Privileges p Privileges Single quotes are literal symbols that you must enter as shown. A reference in a box represents a subdiagram. Imagine that the subdiagram is spliced into the main diagram at this point. When a page number is not specified, the subdiagram appears on the same page. (1 of 2) Introduction 13

24 Command-Line Conventions Element ALL Description A shaded option is the default action. Syntax within a pair of arrows indicates a subdiagram. The vertical line terminates the command. -f OFF ON, variable A branch below the main path indicates an optional path. (Any term on the main path is required, unless a branch can circumvent it.) A loop indicates a path that you can repeat. Punctuation along the top of the loop indicates the separator symbol for list items. 3, A gate ( 3 ) on a path indicates that you can only use that path the indicated number of times, even if it is part size of a larger loop. Here you can specify size no more than three times within this statement segment. (2 of 2) How to Read a Command-Line Diagram Figure 1 shows a command-line diagram that uses some of the elements that are listed in the previous table. Figure 1 Example of a Command-Line Diagram setenv INFORMIXC compiler pathname To construct a command correctly, start at the top left with the command. Then follow the diagram to the right, including the elements that you want. The elements in the diagram are case sensitive. 14 DB-Access User Manual

25 Sample-Code Conventions Figure 1 on page -14 diagrams the following steps: 1. Type the word setenv. 2. Type the word INFORMIXC. 3. Supply either a compiler name or pathname. After you choose compiler or pathname, you come to the terminator. Your command is complete. 4. Press RETURN to execute the command. Sample-Code Conventions Examples of SQL code occur throughout this manual. Except where noted, the code is not specific to any single Informix application development tool. If only SQL statements are listed in the example, they are not delimited by semicolons. For instance, you might see the code in the following example: CONNECT TO stores7. DELETE FROM customer WHERE customer_num = 121. COMMIT WORK DISCONNECT CURRENT To use this SQL code for a specific product, you must apply the syntax rules for that product. For example, if you are using the Query-language option of DB-Access, you must delimit multiple statements with semicolons. If you are using an SQL API, you must use EXEC SQL at the start of each statement and a semicolon (or other appropriate delimiter) at the end of the statement. Tip: Ellipsis points in a code example indicate that more code would be added in a full application, but it is not necessary to show it to describe the concept being discussed. For detailed directions on using SQL statements for a particular application development tool or SQL API, see the manual for your product. Introduction 15

26 Additional Documentation Additional Documentation For additional information, you might want to refer to the following types of documentation: On-line manuals Printed manuals On-line help Error message files Documentation notes, release notes, and machine notes On-Line Manuals A CD that contains Informix manuals in electronic format is provided with your Informix products. You can install the documentation or access it directly from the CD. For information about how to install, read, and print online manuals, see either the installation guide for your product or the installation insert that accompanies the documentation CD. The documentation set that is provided on the CD describes Universal Server, its implementation of SQL, and its associated application-programming interfaces. For an overview of the manuals in the Universal Server documentation set, see Getting Started with INFORMIX-Universal Server. 16 DB-Access User Manual Printed Manuals The Universal Server documentation set describes Universal Server, its implementation of SQL, and its associated application-programming interfaces. For an overview of the manuals in the Universal Server documentation set, see Getting Started with INFORMIX-Universal Server. To order printed manuals, call or send to moreinfo@informix.com. Please provide the following information: The documentation that you need The quantity that you need Your name, address, and telephone number

27 On-Line Help On-Line Help DB-Access provides on-line Help files that walk you through each menu option. To invoke the Help feature, simply press CTRL-W wherever you are in DB-Access. The notational conventions and rules governing SQL statement syntax shown in on-line Help are illustrated in Appendix B. Error Message Files Informix software products provide ASCII files that contain all the Informix error messages and their corrective actions. To read the error messages in the ASCII file, Informix provides scripts that let you display error messages on the screen (finderr) or print formatted error messages (rofferr). For a detailed description of these scripts, see the Introduction to the Informix Error Messages manual. Documentation Notes, Release Notes, Machine Notes In addition to printed documentation, the following on-line files, located in the $INFORMIXDIR/release/en_us/0333 directory, supplement the information in this manual. On-Line File DBACCDOC_9.1 SERVERS_9.1 IUNIVERSAL_9.1 Purpose The documentation-notes file describes features that are not covered in this manual or that have been modified since publication. The release-notes file describes feature differences from earlier versions of Informix products and how these differences might affect current products. This file also contains information about any known problems and their workarounds. The machine-notes file describes any special actions that are required to configure and use Informix products on your computer. Machine notes are named for the product described. Please examine these files because they may contain vital information about application and performance issues. Introduction 17

28 Compliance with Industry Standards Compliance with Industry Standards The American National Standards Institute (ANSI) has established a set of industry standards for SQL. Informix SQL-based products are fully compliant with SQL-92 Entry Level (published as ANSI X ), which is identical to ISO 9075:1992, on INFORMIX-Universal Server. In addition, many features of Universal Server comply with the SQL-92 Intermediate and Full Level and X/Open SQL CAE (common applications environment) standards. Informix Welcomes Your Comments Please tell us what you like or dislike about our manuals. To help us with future versions of our manuals, we want to know about corrections or clarifications that you would find useful. Include the following information: The name and version of the manual that you are using Any comments that you have about the manual Your name, address, and phone number Write to us at the following address: Informix Software, Inc. SCT Technical Publications Department 4100 Bohannon Drive Menlo Park, CA If you prefer to send , our address is: doc@informix.com Or send a facsimile to the Informix Technical Publications Department at: We appreciate your feedback. 18 DB-Access User Manual

29 Working with DB-Access Chapter 1 What Is DB-Access? Preparing to Use DB-Access Setting Environment Variables Using DB-Access with a Non-Default Locale Creating the Demonstration Database Finding Your Way in DB-Access What to Check Before You Start DB-Access How to Use Your Terminal Keyboard Invoking DB-Access Calling up the DB-Access Main Menu Invoking DB-Access and Selecting a Database Selecting a Menu Option Going to a Submenu and Submenu Option CONNECTION Menu Options DATABASE Menu Options SQL Menu Options TABLE Menu Options Sample DB-Access Command-Line Commands Executing a Command File Echoing File Input to the Screen Checking for ANSI Compliance Displaying Session Information Displaying the Software Version Number Activating the XLUF Feature for Nonprintable Characters

30 Other Command-Line Features Reading from Standard Input Interactive Input through Standard Input Executing Shell Commands from Standard Input Connecting to a Database Environment in Non-Menu Mode Viewing the XPG4 Information Schema The DB-Access Main Menu The DB-Access Menu Structure Using DB-Access Menus and Screens Using Menu Screens Selecting an Option Leaving a Menu Screen Getting Help Using Text-Entry Screens Entering Text on the Screen Leaving a Text-entry Screen Getting Help Using the HELP Screen Using a Text Editor Using the SQL Editor Using the Editing Keys Editing Restrictions Using a System Editor DB-Access User Manual

31 This chapter introduces DB-Access. It tells you how to get started with DB-Access and acquaints you with the various types of menus, screens, terminal functions, and editors that you use when working with the utility. If you are new to DB-Access, you should take time to understand the basic concepts and tasks presented in this chapter. This manual also refers to other relevant Informix publications, which can be helpful if you have limited experience with computers or database-management systems. If you are already familiar with DB-Access, you might prefer to skip this chapter and Chapter 2, Creating Databases and Tables, and go directly to the relevant sections of the subsequent chapters or appendixes. The following table shows the topics covered in this chapter. Topic What Is DB-Access? on page 1-4 Scope This section explains the purpose of DB-Access and shows what you can do with DB-Access. Preparing to Use DB-Access on page 1-6 This section describes the steps you must follow before you can work with DB-Access. It shows you how to set environment variables, create the demonstration database, and optionally install a language supplement. Finding Your Way in DB-Access on page 1-10 Invoking DB-Access on page 1-12 This section provides a checklist of prerequisites for starting DB-Access and explains how to use your terminal keys in DB-Access. This section shows how to invoke DB-Access from the command line. It explains various command-line options for accessing submenus and customizing your use of DB-Access. It also explains other command-line features such as reading from standard input. (1 of 2) Working with DB-Access 1-3

32 What Is DB-Access? Topic The DB-Access Main Menu on page 1-29 Using DB-Access Menus and Screens on page 1-31 Using a Text Editor on page 1-35 Scope This section describes the DB-Access main menu and provides a graphic overview of the DB-Access menu hierarchy. This section describes the organization of information on DB-Access menus and screens. It shows how to use the three types of screens in DB-Access: menu screens, textentry screens, and help screens. This section shows how to use the SQL Editor to create and modify SQL statements and command files. It explains the editing keys on the NEW and MODIFY textentry screens and describes editing restrictions. This section also shows how to use a system editor as an alternative to the SQL editor. (2 of 2) Tip: If you are new to DB-Access, you might want to look immediately at the overview of the menu hierarchy in Figure 1-5 on page That figure provides a graphic overview of all options on all menus in DB-Access. You can use that figure to see at a glance all the tasks you can perform with DB-Access. What Is DB-Access? DB-Access is a utility that lets you access and manipulate the data in a relational database and perform a variety of data-management tasks such as organizing, storing, retrieving, and viewing data. A database is a collection of information or data that is arranged in tables. In turn, the tables are made up of rows and columns. The stores7 database provided with your database server is described in detail in Appendix A of the Informix Guide to SQL: Reference. Database fundamentals are introduced in Chapter 1 in the Informix Guide to SQL: Tutorial. 1-4 DB-Access User Manual

33 What Is DB-Access? You can use DB-Access menus and screens to perform the following types of database tasks: Create, drop, and close databases Create, modify, and drop nonfragmented and fragmented tables Create, modify, and drop indexes and constraints Connect to a database server Obtain information about the current session Obtain information about the objects in the database, such as tables, columns, fragments, indexes, routines, triggers, constraints, and privileges You can use the SQL menu to perform the following types of tasks: Insert, update, delete, and retrieve information in a database using SQL (Structured Query Language) statements Enter and execute SQL data definition statements and many other types of SQL statements Create and execute SPL routines Create command files to capture the text of SQL statements and SPL routines and execute these command files Tip: If you are not familiar with using the SELECT statement and other SQL statements in DB-Access, see Selecting Data from a Table on page This section provides a tutorial on working with the SELECT statement in DB-Access and prepares you for working with other SQL statements in DB-Access. Working with DB-Access 1-5

34 Preparing to Use DB-Access Preparing to Use DB-Access This section describes the steps you must follow before you can work with DB-Access. It explains how to set environment variables, how to use DB-Access with a non-default locale, and how to create the demonstration database that is provided with DB-Access. It assumes that the INFORMIX- Universal Server is installed on your computer according to the installation instructions that come with the database server software. Setting Environment Variables You must set the following Informix and UNIX environment variables before you can properly use DB-Access: The INFORMIXDIR environment variable specifies the directory where your database server files are installed. The INFORMIXSERVER environment variable specifies the default INFORMIX-Universal Server to which an explicit or implicit connection is made. The INFORMIXTERM environment variable specifies whether DB-Access should use the termcap file or terminfo directory to locate terminal-capability information. The UNIX environment variable TERMCAP or TERMINFO must be set so that DB-Access can communicate with your terminal. TERM is a UNIX environment variable that lets DB-Access recognize and communicate with the kind of terminal you are using. PATH is a UNIX environment variable that determines the search path so that the shell searches the correct directory for executable DB-Access files. 1-6 DB-Access User Manual

35 Setting Environment Variables You can set additional Informix environment variables for enhanced performance; DB-Access observes their settings: Set the DELIMIDENT environment variable if you want DB-Access to automatically accept delimited identifiers in SQL statements. This means that database object names consisting of alphabetic or nonalphabetic characters can be placed within quotes, and that strings in double quotes (") are treated as identifiers rather than strings. Set the FET_BUF_SIZE environment variable to determine the size of the fetch buffer for data sent by the database server. Set the OPTCOMPIND environment variable to indicate a preferred join method and help the optimizer select the appropriate join method for parallel database queries. Set the PDQPRIORITY environment variable to dynamically control the priority level of parallel database queries. Set the DBFLTMASK environment variable to control the default number of digits displayed to the right of the decimal point for columns with floating-point data types. Set the DBEDIT environment variable to specify a default text editor for the Use-editor option of the SQL menu. You can activate Native Language Support (NLS) capability and specify certain behaviors by taking the following steps: The DBNLS environment variable enables the NLS features. Set this environment variable before starting the application. If DBNLS is not set, DB-Access does not provide NLS functionality. Once DBNLS is set, set the LANG environment variable to specify the language environment of the database operations that follow. The LANG setting determines the messages, collating sequences, character classifications, and local customs information. For example, you could set LANG to a value for German. If you activate NLS capability and want messages and menu options in a language other than English, you must also install one or more language supplements for the language(s) you want to use. Installation instructions for the supplements are provided with their on-line or printed Language Supplement Release Notes. Working with DB-Access 1-7

36 Using DB-Access with a Non-Default Locale You can set any of the environment variables described in this section at the system prompt, in your.profile (Bourne shell or Korn shell) file, in your.login or.cshrc (C shell) file, or in an environment-configuration file. If you set these environment variables at the system prompt, you must reassign them every time you log on to the system. If you set these environment variables in your.profile,.login, or.cshrc file, they are assigned automatically every time you log on to the system. Important: If you set or modify the environment variables in a file rather than on the command line, log out and then log back on or source the file before you begin to work with DB-Access so the shell can read your entries. Details of how to set and use environment variables are provided in Chapter 4 of the Informix Guide to SQL: Reference. This chapter describes all the environment variables listed in this section except for the DBNLS and LANG environment variables. For further information on the DBNLS and LANG environment variables, see the Guide to GLS Functionality. Using DB-Access with a Non-Default Locale GLS The Global Language Support (GLS) feature lets Informix products, including DB-Access, easily handle different languages, cultural conventions, and code sets for Asian, European, Latin American, and Middle Eastern countries. Culture-specific information resides in a GLS locale. For information about GLS locales, see the Guide to GLS Functionality. If you are using the default locale (U.S. English), you do not need to set any environment variables or perform any special steps to enable the GLS feature for DB-Access. If you are using a non-default locale, you must set environment variables to identify the appropriate locale: Set the CLIENT_LOCALE environment variable to specify a nondefault client locale. Set the DB_LOCALE environment variable on each client computer to specify a non-default database locale. Set the SERVER_LOCALE environment variable to specify a nondefault server locale. 1-8 DB-Access User Manual

37 Creating the Demonstration Database You can also customize your use of the GLS feature by setting additional GLS-related environment variables, such as DBDATE, DBLANG, and DBMONEY. For information about setting the CLIENT_LOCALE, DB_LOCALE, and SERVER_LOCALE environment variables, see Chapter 1 of the Guide to GLS Functionality. For descriptions of these three environment variables and other GLS-related environment variables, see Chapter 2 of the Guide to GLS Functionality. For information on how the GLS feature affects the Informix implementation of SQL in DB-Access, see Chapter 3 of the Guide to GLS Functionality Important: NLS is an older Informix product that is retained for backward compatibility with client applications that are based on NLS features. GLS is a newer Informix product that provides several advantages over and above those of NLS. GLS is the preferred method of adapting DB-Access and other Informix products to your own language and culture. Creating the Demonstration Database The examples in this manual are based on the stores7 demonstration database. The structure, contents, and relationship of all the tables that comprise the stores7 database are described in Appendix A of the Informix Guide to SQL: Reference. The system catalog tables for the stores7 database are described in Chapter 2 of that book. If you have not already done so, create the demonstration database as described in Demonstration Database on page -5 in the Introduction to this manual. Working with DB-Access 1-9