DB2 REXX SQL for VM/ESA^(R): Installation and Reference

About This Manual

Part 1 of this manual describes how to install the DB2 REXX SQL for VM/ESA (DB2 RXSQL) program on a Virtual Machine (VM) system. The DB2 RXSQL software is a feature of the DB2 Server for VM relational database manager

Part 2 of this manual describes how the DB2 REXX SQL for VM/ESA (DB2 RXSQL) allows REXX programs to access the IBM DATABASE 2^(R) Server for VM in a VM environment.

Who Should Use This Manual

Part 1 of this manual is for the person who installs DB2 RXSQL. It assumes you are familiar with CMS commands and EXECs, and the Virtual Machine/Enterprise Systems Architecture (VM/ESA) system.

Part 2 of this manual assumes that readers are familiar with the concepts of relational databases, the facilities of the DB2 Server for VM relational database manager, and the elements of the REXX programming language.

How This Manual Is Organized

Part 1 -- Installation

Part 1 of this manual focuses on the installation of DB2 RXSQL and contains the chapters described here.

Chapter 1, Before You Begin: defines the prerequisites needed to install DB2 RXSQL
Chapter 2, Installing DB2 RXSQL: describes how to install DB2 RXSQL and verify the installation
Chapter 3, Installing a REXX SQL NLS Language: contains the information concerning the material and procedures associated with the installation of DB2 REXX SQL NLS Languages
Chapter 4, Installing Preventive and Corrective Service: provides instructions for installing preventive and corrective service

Part 2 -- Reference

Part 2 of this manual focuses on how the DB2 REXX SQL for VM/ESA (DB2 RXSQL) allows REXX programs to access the IBM DATABASE 2^(R) Server for VM in a VM environment; it contains the chapters described here.

Chapter 5, Getting Started with DB2 RXSQL: Introduces the DB2 RXSQL interface, describes how the interface relates to REXX and DB2 Server for VM, and lists some sample programs to help you learn the interface.
Chapter 6, RXSQL-Supplied Programs: Provides information on the use of the general-purpose programs supplied with DB2 RXSQL.
Chapter 7, Concepts: Introduces concepts needed for SQL applications.
Chapter 8, Using Dynamic and Extended Dynamic SQL Statements in RXSQL: Explains how to write Dynamic and Extended Dynamic RXSQL applications.
Chapter 9, Coding DB2 RXSQL Requests: Outlines how to code RXSQL requests.
Chapter 10, RXSQL Request Descriptions: Contains detailed descriptions of each DB2 RXSQL request.

Part 3 -- Appendixes

The Appendixes of this manual contain the following reference information associated with both the installation and usage of DB2 RXSQL.

Appendix A, Files Supplied by IBM: lists the files supplied by IBM
Appendix B, Installation and Service EXECs: provides instructions for running the installation and service EXECs
Appendix C, Online HELP Information: describes the HELP information available with DB2 RXSQL
Appendix D, Installation Messages: provides a summary of the installation messages
Appendix E, RXSQL Return Codes and Messages: Lists DB2 RXSQL return codes and error messages.
Appendix F, Sample Programs with Examples of RXSQL Requests: Illustrates typical DB2 RXSQL request functions within sample programs.
Appendix G, Performance and Diagnosis: Contains performance and diagnosis information.
Appendix H, Support for CMS Work Units: Describes how DB2 RXSQL uses CMS work units.
Appendix I, RXSQL Subcommand Environment: Explains how DB2 RXSQL requests can be executed in the DB2 RXSQL subcommand environment.
Appendix J, RXSQL Runtime Environment: Explains the DB2 RXSQL run-time environment.
Appendix K, Single User Mode Environment: Describes how to run DB2 RXSQL in single user mode.
Appendix L, Considerations and Restrictions Using the DRDA Protocol: Outlines the considerations for running RXSQL using the Distributed Relational Database Architecture^(TM) (DRDA^(R)) protocol.
Appendix M, DB2 RXSQL Incompatibilities by Release: Explains the incompatibilities by release.

Terminology

In the past, the term database was used in a general sense to refer to the database management system as well as stored objects and storage devices. However, using database in this context has proven to be misleading. Accordingly, the following terminology has been adopted and is used consistently in the text:

Term: Meaning
application server: Refers to the database management system including the accumulated data.
application requester: Refers to the facility that transforms a request from the application into a form suitable for communicating with an application server.
database: Refers only to the collection of data.
ISQL: Interactive Structured Query Language
IUCV: Inter-user communication vehicle
LUW: Logical unit of work
Request: Either a DB2 RXSQL statement or command
REXX: Restructured Extended Executor Language
RXSQL: DB2 REXX SQL for VM/ESA
SAA: Systems Application Architecture
user ID: Userid, user identification
VM/ESA: Virtual Machine/Enterprise Systems Architecture Version 2 Release 2 or later
XEDIT: System Product editor

If You Need More Information

Prerequisite IBM Publications

For information on the REXX programming language, refer to:

VM/ESA: REXX/VM Reference, SC24-5770
VM/ESA: REXX/VM User's Guide, SC24-5465.

The following manual is to be used in conjunction with the DB2 REXX SQL for VM/ESA Installation and Reference manual.

DB2 Server for VSE & VM SQL Reference, SC09-2989.

See Bibliography for related VM and DB2 Server for VM publications.

Related IBM Publications

Various IBM publications are mentioned throughout this document. Refer to them if you require additional information on related IBM products.

Only the short titles of the manuals are given in the text. For the long titles and their corresponding document numbers, see the Bibliography.

Highlighting Conventions

This manual observes the following text highlighting conventions.

Convention Meaning
Italics Italic type is used to denote the first occurrence of a term listed in the Glossary, titles of stand-alone documents, command variables, parameter values and their symbolic equivalents, and strings ofcharacters referred to as such.
Boldface Bold type is used for emphasis or for an important term that is being defined.
Monospace Type Monospace type is used to indicate material that is entered at a display station, displayed on a screen, coded, or printed on a computer printing device.
ALL CAPS Capital letters are used to indicate:

Acronyms and other all-cap abbreviations
Names of programs and other coded entities
Names of files, tables, libraries, logs, and so forth
Command, statement, and parameter names or constants
Keyword and option names
Data area and storage names.

"Quotation Marks" Quotation marks (double) are used to enclose the headings of parts, chapters, and lesser sections of stand-alone documents when they are referenced.

Convention	Meaning
Italics	Italic type is used to denote the first occurrence of a term listed in the Glossary, titles of stand-alone documents, command variables, parameter values and their symbolic equivalents, and strings ofcharacters referred to as such.
Boldface	Bold type is used for emphasis or for an important term that is being defined.
`Monospace Type`	Monospace type is used to indicate material that is entered at a display station, displayed on a screen, coded, or printed on a computer printing device.
ALL CAPS	Capital letters are used to indicate: Acronyms and other all-cap abbreviations Names of programs and other coded entities Names of files, tables, libraries, logs, and so forth Command, statement, and parameter names or constants Keyword and option names Data area and storage names.
"Quotation Marks"	Quotation marks (double) are used to enclose the headings of parts, chapters, and lesser sections of stand-alone documents when they are referenced.

|How to Send Your Comments

|Your feedback is important in helping to provide the most accurate and |high-quality information. If you have any comments about this book or |any other DB2 Server for VSE & VM documentation: |

|Visit our home page at:

|http://www-4.ibm.com/software/data/db2/vse-vm/

|A form for readers' comments is provided at the back of this |publication. If the form has been removed, address your comments |to:
|IBM Canada Ltd. Laboratory
|Information Development
|2G/345/1150/TOR
|1150 Eglinton Ave East
|North York, Ontario, Canada M3C 1H7
|Send your comments by electronic mail to one of the following |addresses:
|

Format Address
Internet torrcf@ca.ibm.com
Facsimile (416) 448-6161 (Attention RCF Coordinator)

|Be sure to include the name of the book, the form number (including the |suffix), and the page, section title, or topic you are commenting on.
|If you choose to respond through the Internet, please include either your |entire Internet network address, or a postal address.
|Fill out the form at the back of this book and return it by mail, by fax, |or by giving it to an IBM representative. |

	Format	Address
	Internet	torrcf@ca.ibm.com
	Facsimile	(416) 448-6161 (Attention RCF Coordinator)

Syntax Notation Conventions

Throughout this manual, syntax is described using the structure defined below.

Read the syntax diagrams from left to right and from top to bottom, following the path of the line.
The >>--- symbol indicates the beginning of a statement or command.
The ---> symbol indicates that the statement syntax is continued on the next line.
The >--- symbol indicates that a statement is continued from the previous line.
The --->< symbol indicates the end of a statement.
Diagrams of syntactical units that are not complete statements start with the >--- symbol and end with the ---> symbol.
Some SQL statements, Interactive SQL (ISQL) commands, or database services utility (DBS Utility) commands can stand alone. For example:
>>-SAVE--------------------------------------------------------><
Others must be followed by one or more keywords or variables. For example:
>>-SET AUTOCOMMIT OFF------------------------------------------><
Keywords may have parameters associated with them which represent user-supplied names or values. These names or values can be specified as either constants or as user-defined variables called host_variables (host_variables can only be used in programs).
>>-DROP SYNONYM--synonym---------------------------------------><
Keywords appear in either uppercase (for example, SAVE) or mixed case (for example, CHARacter). All uppercase characters in keywords must be present; you can omit those in lowercase.
Parameters appear in lowercase and in italics (for example, synonym).
If such symbols as punctuation marks, parentheses, or arithmetic operators are shown, you must use them as indicated by the syntax diagram.
All items (parameters and keywords) must be separated by one or more blanks.
Required items appear on the same horizontal line (the main path). For example, the parameter integer is a required item in the following command:
>>-SHOW DBSPACE--integer---------------------------------------><
This command might appear as:
```
  SHOW DBSPACE 1
```

Optional items appear below the main path. For example:

>>-CREATE----+---------+--INDEX-------------------------------->< '-UNIQUE--'

This statement could appear as either:

  CREATE INDEX

  CREATE UNIQUE INDEX

If you can choose from two or more items, they appear vertically in a stack.

If you must choose one of the items, one item appears on the main path. For example:

>>-SHOW LOCK DBSPACE----+-ALL-----+---------------------------->< '-integer-'

Here, the command could be either:

  SHOW LOCK DBSPACE ALL

  SHOW LOCK DBSPACE 1

If choosing one of the items is optional, the entire stack appears below the main path. For example:

>>-BACKWARD----+---------+------------------------------------->< +-integer-+ '-MAX-----'

Here, the command could be:

  BACKWARD

  BACKWARD 2

  BACKWARD MAX

The repeat symbol indicates that an item can be repeated. For example:

.---------. V | >>-ERASE-------name---+----------------------------------------><

This statement could appear as:

  ERASE NAME1

  ERASE NAME1 NAME2

A repeat symbol above a stack indicates that you can make more than one choice from the stacked items, or repeat a choice. For example:

.-,-----------------------. V | >>-VALUES--(------+-constant-----------+--+--)----------------->< +-host_variable_list-+ +-NULL---------------+ '-special_register---'

If an item is above the main line, it represents a default, which means that it will be used if no other item is specified. In the following example, the ASC keyword appears above the line in a stack with DESC. If neither of these values is specified, the command would be processed with option ASC.
.-ASC--. >>-+------+---------------------------------------------------->< '-DESC-'
When an optional keyword is followed on the same path by an optional default parameter, the default parameter is assumed if the keyword is not entered. However, if this keyword is entered, one of its associated optional parameters must also be specified.
In the following example, if you enter the optional keyword PCTFREE =, you also have to specify one of its associated optional parameters. If you do not enter PCTFREE =, the database manager will set it to the default value of 10.
.-PCTFREE = 10------. >>-+-------------------+--------------------------------------->< '-PCTFREE = integer-'
Words that are only used for readability and have no effect on the execution of the statement are shown as a single uppercase default. For example:
.-PRIVILEGES--. >>-REVOKE ALL----+-------------+-------------------------------><
Here, specifying either REVOKE ALL or REVOKE ALL PRIVILEGES means the same thing.

Sometimes a single parameter represents a fragment of syntax that is expanded below. In the following example, fieldproc_block is such a fragment and it is expanded following the syntax diagram containing it.

>>-+----------------------------+---| fieldproc_block |-------->< '-NOT NULL--+-------------+--' +-UNIQUE------+ '-PRIMARY KEY-'

fieldproc_block |--FIELDPROC--program_name----+-------------------------+-------| | .-,-----------. | | V | | '-(-----constant---+---)--'

EXEC Conventions

When running the EXECs included with DB2 RXSQL, you might receive a message such as the following:

   Do you want to use these values?
   Enter 0 (NO) or 1 (YES) OR 111 (QUIT)

To answer no, type one of the following:

NO, No, no, N, n, 0.

To answer yes, type one of the following:

YES, Yes, yes, Y, y, 1.

To stop the EXEC and exit processing, type one of the following:

QUIT, Quit, quit, Q, q, 111.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

DB2 REXX SQL for VM/ESA(R): Installation and Reference

|How to Send Your Comments

DB2 REXX SQL for VM/ESA^(R): Installation and Reference