Scribd
Upload
298 views

SQL400

SQL/400 is an implementation of the industry standard SQL language on the AS/400 platform. It allows users to define and manipulate base objects like tables and views through its data definition language and retrieve and modify data using its data manipulation language. SQL statements can be executed interactively, as embedded statements in a program, or from a source file member. SQL/400 objects have corresponding OS/400 objects like libraries for collections, physical files for base tables, logical files for views and indexes, and fields map to columns.

Uploaded by

raju
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
298 views

SQL400

SQL/400 is an implementation of the industry standard SQL language on the AS/400 platform. It allows users to define and manipulate base objects like tables and views through its data definition language and retrieve and modify data using its data manipulation language. SQL statements can be executed interactively, as embedded statements in a program, or from a source file member. SQL/400 objects have corresponding OS/400 objects like libraries for collections, physical files for base tables, logical files for views and indexes, and fields map to columns.

Uploaded by

raju
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 4

SQL/400

DDL

SQL AN INDUSTRY STANDARD LANGUAGE

Defines and manipulates base objects


SQL/400 and DB2/400 are
implementations of AS/400
Includes Data definition language(DDL)
and data manipulation language(DML)
SQL Statements can be executed
a. Interactively
b. As embedded statements in a program
c. From a source file member using
RUNSQLSTM command.

SQL/400 objects and OS/400 objects


SQL/400 object or
element

OS/400 object
type or
element

Attribute and notes

Collection

Library(*LIB)

Contains QSQJRN Journal


QSQJRNnnn Journal reciever
12 view logical files for collection catalog

Base Table

Physical File(*FILE)

Single member
Externally described
Has keyed access path for each primary
unique and foreign key constraint

View

Logical File(*FILE)

Single member
Externally Described
No Keyed access path

Column (of a base table


or a view

Field

Row in a base table or a


view

Record

Index

Logical file(*FILE)

Catalog

Set of physical and

Single member
Externally Described
Keyed access path over one PF member

You might also like