SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Introduction to SQL/MX Database Management

HP NonStop SQL/MX Installation and Management Guide—523723-004

1-8

DEFINE Names

Use class MAP DEFINE names as logical names for SQL/MP tables or views in DML

statements. When NonStop SQL/MX compiles such statements, it replaces the

DEFINE name in the statement with the associated Guardian physical name. You can

create DEFINE names within MXCI or names can be inherited from the TACL process

or the OSS shell.

You cannot assign DEFINE names to SQL/MX tables or views. However, you can use

prototyped host variables to name SQL/MX tables or views in C and COBOL

programs. For more information about prototyped host variables, see the SQL/MX

Programming Manual for C and COBOL.

For more information about using DEFINE names, see the SQL/MX Programming

Manual for C and COBOL and the SQL/MX Programming Manual for Java.

Object Namespaces

Multiple objects with the same logical name can exist in the same schema, provided

each belongs to a different namespace. For more information about object

namespaces, see the SQL/MX Reference Manual.

Using ANSI Names for SQL/MP Objects

NonStop SQL/MX supports the use of ANSI names (SQL/MP aliases) to query

SQL/MP database objects. The mapping from ANSI logical name to physical SQL/MP

partition is stored in the MP_PARTITIONS table in the definition schema.

For information about logical-to-physical name mapping using SQL/MP aliases, see

the SQL/MX Reference Manual.

SQL/MX Metadata

NonStop SQL/MX stores system metadata for all SQL/MX format objects in SQL/MX

tables, automatically creating and maintaining metadata as users create, alter, drop, or

update SQL/MX objects. The metadata maintains an accurate record of the information

that constitutes the definition of SQL/MX objects and how the objects are used by other

SQL/MX objects.

System metadata about objects is stored in numerous tables in system schemas and

definition schemas. You cannot modify data in these system metadata tables directly.

However, they are secured for PUBLIC SELECT access so that you can query them.

Table 1-1

on page 1-9 describes these metadata tables and the schemas in which they

are stored.